> On Sep 8, 2019, at 1:26 PM, Brian E Carpenter <[email protected]> > wrote: > >>> >>> Wouldn't that require the middle box to become an architectural element? >> >> Yes, but not just “an” (one): >> >> Touch, J: Middlebox Models Compatible with the Internet. USC/ISI >> (ISI-TR-711), 2016. (Type: Technical Report | Links | BibTeX) >> >> * https://www.strayalpha.com/pubs/isi-tr-711.pdf >> <https://www.strayalpha.com/pubs/isi-tr-711.pdf> > > I'll take the liberty of pointing out that we've known for many years that > there are multiple types of middleboxes and they have multiple facets: > https://tools.ietf.org/html/rfc3234 <https://tools.ietf.org/html/rfc3234>
Facets are just properties. That doc makes no attempt to describe them as architectural roles. > > So far, we haven't added them to any formal architectural description of > the Internet, probably because we don't have one. RFC1122, RFC1123, RFC1812 as standards. I (and IMO those RFCs) disagree with the position you took in RFC1958, FWIW. Joe
_______________________________________________ Int-area mailing list [email protected] https://www.ietf.org/mailman/listinfo/int-area
