Hi Authors, I’m not sure if this point was considered and rejected (in which case let’s close it out in email please), or (more likely) just dropped?
> On Feb 18, 2022, at 4:48 PM, Robert Raszuk <rob...@raszuk.net> wrote: > > > Hi John, > >> Question: SAFI 128 is called “MPLS-labeled VPN address” in the IANA SAFI >> registry. Shouldn’t this be renamed? I mean, I guess it should have been >> renamed as of RFC 8365, but better late than never. I’m not sure quite what >> the name should become, but “MPLS-labeled” is manifestly wrong. Even >> “labeled” is wrong since the thing you’re stuffing in there isn’t a label. >> Since you’re the last one to touch it :-) if we can agree a better name for >> the SAFI I think it would be appropriate to add that to your IANA >> Considerations. >> > My suggestion would be: "VPN address & context" or "Context & VPN address" > > Thx, > R. I like either of Robert’s suggestions. This would go some small way towards addressing my concern #2. Suggested text for the IANA Considerations section: 9.X Subsequent Address Family Identifiers (SAFI) Parameters Registry IANA maintains a registry called Subsequent Address Family Identifiers (SAFI) Parameters. In that registry, value 128 has the description "MPLS-labeled VPN address”, references [RFC4364][RFC8277]. This specification, as well as [RFC 8365] before it, changes the semantics of SAFI 128 such that it can carry values other than an MPLS label. Therefore, IANA is requested to update the description of value 128 to be "VPN address & context” and to add [RFC 8365] and [this document] as references. Regards, —John _______________________________________________ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
