Hi Med, similar to the other case 6874, I think we should clarify that no policy change is intended, so:
Type: Editorial Reported by: Mohamed BOUCADAIR <[email protected]> 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 | +------------+--------------------+ Note: Identifiers prefixed with "priv:" are reserved for Private Use (see Section 10.8.2.) Table 4: ALTO Endpoint Property Types would that work for you? thanks Sebastian On Wed, Mar 09, 2022 at 01:23:35PM -0800, Chris Smiley wrote: > > Greetings, > > We are unable to verify this erratum that the submitter marked as editorial. > Please note that we have changed the “Type” of the following errata > report to “Technical”. As Stream Approver, please review and set the > Status and Type accordingly (see the definitions at > https://www.rfc-editor.org/errata-definitions/). > > You may review the report at: > https://www.rfc-editor.org/errata/eid6876 > > Please see https://www.rfc-editor.org/how-to-verify/ for further > information on how to verify errata reports. > > Further information on errata can be found at: > https://www.rfc-editor.org/errata.php. > > Thank you. > > RFC Editor/cs > > > > On Mar 8, 2022, at 10:21 PM, RFC Errata System <[email protected]> > > wrote: > > > > The following errata report has been submitted for RFC7285, > > "Application-Layer Traffic Optimization (ALTO) Protocol". > > > > -------------------------------------- > > You may review the report below and at: > > https://www.rfc-editor.org/errata/eid6876 > > > > -------------------------------------- > > Type: Editorial > > Reported by: Mohamed BOUCADAIR <[email protected]> > > > > 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 > > > > > > Notes > > ----- > > priv: is not an identifier, but a prefix. > > > > Instructions: > > ------------- > > This erratum is currently posted as "Reported". If necessary, please > > use "Reply All" to discuss whether it should be verified or > > rejected. When a decision is reached, the verifying party > > can log in to change the status and edit the report, if necessary. > > > > -------------------------------------- > > 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 [email protected] https://www.ietf.org/mailman/listinfo/alto
