[saag] Re: [nasr] Re: Re: Re: Re: NASR BOF Follo w-Up

Watson Ladd <[email protected]> wrote:
    > However, the properties being claimed are nontrivial semantic claims
    > dependent on the configuration and the software that uses this
    > configuration to route packets. There's a big gap here, and I don't
    > believe it has been solved. To the extent that NASR needs these to be
    > solved to provide certain things, it won't be able to provide them,
    > and I think that undermines a lot of the presented rationale.

Some router vendors, and some operational people seem to think it can be
solved.  One possible answer is that routing platforms will be *simplified*
until they can be reasoned about.  I think that there are lots of economic
reasons why they will go this way.

1. SRv6 is essentially replacing all sorts of specialized forwarding engines
   (MPLS, ATM, metro-ethernet, IPv4) with a single mechanism.

2. There may be a thousand knobs that, if turned on, might do something
   bad. (Or might be innoculous).  But, it could be, yes, hard to reason
   about their interation. Turing completeness, halting problem, etc..
   What matters if that they aren't turned on though.

3. RESTCONF and Orchestration means that forwarding platforms do not need to
   be directly manipulated by human operators.  Is this true across the
   entire industry today?  No.  Is it true among some operators? Yes.

Anyway, I'm working on a PoC.

--
Michael Richardson <[email protected]>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide

_______________________________________________
saag mailing list -- [email protected]
To unsubscribe send an email to [email protected]

-----BEGIN PGP SIGNATURE-----

iQFKBAEBCgA0FiEEbsyLEzg/qUTA43uogItw+93Q3WUFAmgD12QWHG1jcitpZXRm
QHNhbmRlbG1hbi5jYQAKCRCAi3D73dDdZVkaB/96neob6O7bTdpAZ/pd5qncjDDp
nOHvNm841oOvZPvbCZ8QzLxc0UYW5tekvrHuIcOqKTwHF16ixGz266tZDXK0Rds+
TjP5irh5vCHsgWhuAeDG+brjJzyBq4ENkn6XudghRQq5OJO8NRJOnUdyo1rByBd/
M7xRjaaGsmL5PXCs7vyhvNZCT4RrzEMhkz9cnXBFeaKRBcUOVe5iMuxRUSGHRyJ0
r5hGNSMY7AsrxfnHRYEmzcW4M16sRq3WzJgrrAR3EGOX5e/BLbF7p1d2ogWM6P+C
P3C6F4/Zpl2/mkHGqELCyR1DlUxHQhhNfFO3NCeFFOHEXUJ0vP9B/RVAfIcV
=eDGm
-----END PGP SIGNATURE-----