[alto] [IANA #1230654] [Errata Verified] RFC7285 (6876)
Hi, The headers for the affected registries now read as follows: ALTO Cost Metrics Registration Procedure(s): IETF Review Reference: [RFC7285][RFC Errata 6874] Note: Identifiers prefixed with 'priv:' are reserved for Private Use (see [RFC7285], Section 10.6). ALTO Endpoint Property Types Registration Procedure(s): IETF Review Reference: [RFC7285][RFC Errata 6876] Note: Identifiers prefixed with 'priv:' are reserved for Private Use (see [RFC7285], Section 10.8.2). The "priv:" registration has been removed from each registry. thanks, Amanda Baber IANA Operations Manager On Fri May 13 20:48:24 2022, ietf-a...@skiesel.de wrote: > Hi, > > On Fri, May 13, 2022 at 07:58:06PM +, Amanda Baber via RT wrote: > > Hi all, > > > > This question relates to both 6874 and 6876: > > > > Should "priv:" be removed from the ALTO Cost Metrics and ALTO > > Endpoint Property Types registries? See > > > > https://www.iana.org/assignments/alto-protocol > > > > If so, should we add the note "Note: Identifiers prefixed with > > 'priv:' > > are reserved for Private Use (see RFC 7285, Section 10.8.2)" to the > > top of each registry? > > Please note the two different references to different sections of the > document for the two registries. > > Please add > > Note: Identifiers prefixed with 'priv:' are reserved for Private Use > (see RFC 7285, Section 10.6) > > to the ALTO Cost Metrics registry and > > Note: Identifiers prefixed with 'priv:' are reserved for Private Use > (see RFC 7285, Section 10.8.2) > > to the ALTO Endpoint Property Types registry. > > thanks > Sebastian ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
Re: [alto] [IANA #1230654] [Errata Verified] RFC7285 (6876)
Hi, On Fri, May 13, 2022 at 07:58:06PM +, Amanda Baber via RT wrote: > Hi all, > > This question relates to both 6874 and 6876: > > Should "priv:" be removed from the ALTO Cost Metrics and ALTO Endpoint > Property Types registries? See > > https://www.iana.org/assignments/alto-protocol > > If so, should we add the note "Note: Identifiers prefixed with 'priv:' > are reserved for Private Use (see RFC 7285, Section 10.8.2)" to the > top of each registry? Please note the two different references to different sections of the document for the two registries. Please add Note: Identifiers prefixed with 'priv:' are reserved for Private Use (see RFC 7285, Section 10.6) to the ALTO Cost Metrics registry and Note: Identifiers prefixed with 'priv:' are reserved for Private Use (see RFC 7285, Section 10.8.2) to the ALTO Endpoint Property Types registry. thanks Sebastian ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
Re: [alto] [IANA #1230654] [Errata Verified] RFC7285 (6876)
yes, I believe that is correct. On Fri, May 13, 2022 at 12:58 PM Amanda Baber via RT wrote: > Hi all, > > This question relates to both 6874 and 6876: > > Should "priv:" be removed from the ALTO Cost Metrics and ALTO Endpoint > Property Types registries? See > > https://www.iana.org/assignments/alto-protocol > > If so, should we add the note "Note: Identifiers prefixed with 'priv:' are > reserved for Private Use (see RFC 7285, Section 10.8.2)" to the top of each > registry? > > We'll need Martin to sign off on any registry changes. > > thanks, > > Amanda Baber > IANA Operations Manager > > On Thu May 12 22:09:51 2022, rfc-edi...@rfc-editor.org wrote: > > The following errata report has been verified for RFC7285, > > "Application-Layer Traffic Optimization (ALTO) Protocol". > > > > -- > > You may review the report below and at: > > https://www.rfc-editor.org/errata/eid6876 > > > > -- > > Status: Verified > > Type: Technical > > > > Reported by: Mohamed BOUCADAIR > > Date Reported: 2022-03-09 > > Verified by: Martin Duke (IESG) > > > > Section: 14.3 > > > > Original Text > > - > > +++ > > | Identifier | Intended Semantics | > > +++ > > | pid| See Section 7.1.1 | > > | priv: | Private use| > > +++ > > > > Table 4: ALTO Endpoint Property Types > > > > > > Corrected Text > > -- > > +++ > > | Identifier | Intended Semantics | > > +++ > > | pid| See Section 7.1.1 | > > +++ > > > > Table 4: ALTO Endpoint Property Types > > > > Note: Identifiers prefixed with "priv:" are > > reserved for Private Use (see Section 10.8.2.) > > > > > > Notes > > - > > priv: is not an identifier, but a prefix. > > > > -- > > RFC7285 (draft-ietf-alto-protocol-27) > > -- > > Title : Application-Layer Traffic Optimization (ALTO) > > Protocol > > Publication Date: September 2014 > > Author(s) : R. Alimi, Ed., R. Penno, Ed., Y. Yang, Ed., S. > > Kiesel, S. Previdi, W. Roome, S. Shalunov, R. Woundy > > Category: PROPOSED STANDARD > > Source : Application-Layer Traffic Optimization > > Area: Transport > > Stream : IETF > > Verifying Party : IESG > > ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] [IANA #1230654] [Errata Verified] RFC7285 (6876)
Hi all, This question relates to both 6874 and 6876: Should "priv:" be removed from the ALTO Cost Metrics and ALTO Endpoint Property Types registries? See https://www.iana.org/assignments/alto-protocol If so, should we add the note "Note: Identifiers prefixed with 'priv:' are reserved for Private Use (see RFC 7285, Section 10.8.2)" to the top of each registry? We'll need Martin to sign off on any registry changes. thanks, Amanda Baber IANA Operations Manager On Thu May 12 22:09:51 2022, rfc-edi...@rfc-editor.org wrote: > The following errata report has been verified for RFC7285, > "Application-Layer Traffic Optimization (ALTO) Protocol". > > -- > You may review the report below and at: > https://www.rfc-editor.org/errata/eid6876 > > -- > Status: Verified > Type: Technical > > Reported by: Mohamed BOUCADAIR > Date Reported: 2022-03-09 > Verified by: Martin Duke (IESG) > > Section: 14.3 > > Original Text > - > +++ > | Identifier | Intended Semantics | > +++ > | pid| See Section 7.1.1 | > | priv: | Private use| > +++ > > Table 4: ALTO Endpoint Property Types > > > Corrected Text > -- > +++ > | Identifier | Intended Semantics | > +++ > | pid| See Section 7.1.1 | > +++ > > Table 4: ALTO Endpoint Property Types > > Note: Identifiers prefixed with "priv:" are > reserved for Private Use (see Section 10.8.2.) > > > Notes > - > priv: is not an identifier, but a prefix. > > -- > RFC7285 (draft-ietf-alto-protocol-27) > -- > Title : Application-Layer Traffic Optimization (ALTO) > Protocol > Publication Date: September 2014 > Author(s) : R. Alimi, Ed., R. Penno, Ed., Y. Yang, Ed., S. > Kiesel, S. Previdi, W. Roome, S. Shalunov, R. Woundy > Category: PROPOSED STANDARD > Source : Application-Layer Traffic Optimization > Area: Transport > Stream : IETF > Verifying Party : IESG ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
