Re: [CCAMP] Request for early IANA Allocation of values for new flag and RRO sub-object in draft-ietf-ccamp-rsvp-te-srlg-collect-05

["Adrian Farrel" <[e-mail]>]

Hi,

Not sure whether Lou missed this or just didn't work over the weekend :-)

Anyway, yes, you need to supply a fully functional IANA Considerations section that tells IANA exactly what to do.

The easiest way to do this is:
- cut and paste the name of the registry
- cut and paste the name of the sub-registry
- cut and paste the table column headers
   (use the ASCII version of the registry)
- fill in the details

A

> -----Original Message-----
> From: OSCAR GONZALEZ DE DIOS [mailto:[e-mail]]
> Sent: 20 August 2014 17:45
> To: Lou Berger
> Cc: [e-mail]; [e-mail]; 'CCAMP'
> Subject: Re: [CCAMP] Request for early IANA Allocation of values for new flag
> and RRO sub-object in draft-ietf-ccamp-rsvp-te-srlg-collect-05
> 
> Hi Lou,
> 
>   I think we have a misunderstanding. You are referring in your mail to
> the Attributes TLV space (where a new entry should add  "Allowed on
> LSP_ATTRIBUTES", "Allowed on LSP_REQUIRED_ATTRIBUTES Reference”). We
> are
> referring to the Attribute Flags section of
> https://www.iana.org/assignments/rsvp-te-parameters/rsvp-te-
> parameters.xhtm
> l which compiles the flags of the Attribute Flags TLV.
> 
> The fields there are:
> 
> Bit No  Name    Attribute Flags Path    Attribute Flags Resv    RRO     Reference
> 
> 
> RFC 5420 says (textually):
> 
> "Each bit should be tracked with the following qualities:
> 
>    - Bit number
>    - Defining RFC
>    - Name of bit
>    - Whether there is meaning in the Attribute Flags TLV on a Path
>    - Whether there is meaning in the Attribute Flags TLV on a Resv
>    - Whether there is meaning in the RRO Attributes subobject
> “
> 
> I guess these are the columns we should include. Right?
> 
> Óscar
> 
> 
> 
> 
> El 01/08/14 13:16, "Lou Berger" <[e-mail]> escribió:
> 
> >Oscar,
> >    Thanks for the update.  I think you missed a couple of things that
> >were in my request to Adrian:
> >
> >1. For Attributes TLV Space, please provide all columns in the registry,
> >i.e.,  "Type", "Name", "Allowed on LSP_ATTRIBUTES", "Allowed on
> >LSP_REQUIRED_ATTRIBUTES Reference".
> >
> >2. Add "value 34 is suggested to align with exclude route" (I mistakenly
> >said ERO in my previous mail)
> >
> >Once these changes are submitted I can forward the early allocation
> >request.
> >
> >Thanks,
> >Lou
> >
> >On 8/1/2014 2:46 AM, OSCAR GONZALEZ DE DIOS wrote:
> >> Hi Adrian, Lou,
> >>
> >>   I have posted a new version of the draft
> >> draft-ietf-ccamp-rsvp-te-srlg-collect, in which it is highlighted in the
> >> IANA section the values whose early allocation is requested.
> >>
> >>   Should there be any issues with the IANA section, let the authors know
> >> asap.
> >>
> >>    Best Regards,
> >>
> >>       Óscar
> >>
> >>
> >>
> >> El 22/07/14 22:23, "Adrian Farrel" <[e-mail]> escribió:
> >>
> >>> Hi,
> >>>
> >>> I approve.
> >>>
> >>> Please check that the IANA section of the draft is nice and clean so
> >>>IANA
> >>> can make the right allocations with no ambiguity.
> >>> OR
> >>> Wait a few days for me to have time to check the draft.
> >>>
> >>> Thanks,
> >>> Adrian
> >>>
> >>>> -----Original Message-----
> >>>> From: Lou Berger [mailto:[e-mail]]
> >>>> Sent: 22 July 2014 23:18
> >>>> To: [e-mail]
> >>>> Cc: CCAMP
> >>>> Subject: Fwd: Request for early IANA Allocation of values for new flag
> >>>> and RRO
> >>>> sub-object in draft-ietf-ccamp-rsvp-te-srlg-collect-05
> >>>>
> >>>>
> >>>> Adrian,
> >>>> The WG chairs support the following early allocation request:
> >>>>
> >>>> 1) In the "Attributes TLV Space" section of the "Resource Reservation
> >>>> Protocol-Traffic Engineering (RSVP-TE) Parameters" registry located in
> >>>> https://www.iana.org/assignments/rsvp-te-
> >>>> <https://www.iana.org/assignments/rsvp-te-parameters/rsvp-te-
> >>>> parameters.xhtml>
> >>>> parameters/rsvp-te-parameters.xhtml
> >>>> <https://www.iana.org/assignments/rsvp-te-parameters/rsvp-te-
> >>>> parameters.xhtml>:
> >>>>
> >>>> Type (value to be assigned)
> >>>> Name SRLG Collection Flag
> >>>> Allowed on LSP_ATTRIBUTES yes
> >>>> Allowed on LSP_REQUIRED_ATTRIBUTES yes
> >>>>
> >>>> 2) In the Sub-object type ‒ 21 ROUTE_RECORD portion of the Resource
> >>>> Reservation Protocol (RSVP) Parameters registry located at
> >>>> http://www.iana.org/assignments/rsvp-parameters/rsvp-
> parameters.xhtml:
> >>>> Value: (value to be assigned) 34 is suggested to align with ERO
> >>>> Description: SRLG sub-object
> >>>>
> >>>> 3) In the "Error Codes and Globally-Defined Error Value Sub-Codes,
> >>>> Sub-Codes ‒ 2 Policy Control Failure" section of the "RSVP PARAMETERS"
> >>>> registry located at http://www.iana.org/assignments/rsvp-parameters.
> >>>> Value: (value to be assigned)
> >>>> Description: SRLG sub-object
> >>>>
> >>>> Do you approve this request -- so that we can submit the request (per
> >>>> stpe 5 of RFC7120)?
> >>>>
> >>>> Thank you,
> >>>> Lou (and Deborah)
> >>>>
> >>>>
> >>>> -------- Original Message --------
> >>>> Subject:     Request for early IANA Allocation of values for new flag
> >>>>and
> >>>> RRO sub-object in draft-ietf-ccamp-rsvp-te-srlg-collect-05
> >>>> Date:        Tue, 22 Jul 2014 15:19:35 +0000
> >>>> From:        OSCAR GONZALEZ DE DIOS
> >>>><[e-mail]>
> >>>> To:  Lou Berger <[e-mail]>, DEBORAH A BRUNGARD
> >>>> <[e-mail]>
> >>>> CC:  CCAMP <[e-mail]>
> >>>>
> >>>>
> >>>>
> >>>> Dear CCAMP WG Chairs,
> >>>>
> >>>> Following the procedure for Early IANA Allocation of Standards Track
> >>>> Code Points defined in Section 3.1 of RFC 7120, on behalf of the
> >>>>authors
> >>>> of the WG draft "RSVP-TE Extensions for Collecting SRLG Information",
> >>>> draft-ietf-ccamp-rsvp-te-srlg-collect-05, it is requested to CCAMP WG
> >>>> chairs the early allocation of the following values:
> >>>>
> >>>> --> Value for a new flag, named "SRLG Collection Flag" in the RSVP
> >>>> Attribute Bit Flags space. IANA has created a registry and manages the
> >>>> space of attributes bit flags of Attribute Flags TLV, as described in
> >>>> section 11.3 of [RFC5420], in the "Attributes TLV Space" section of
> >>>>the
> >>>> "Resource Reservation Protocol-Traffic Engineering (RSVP-TE)
> >>>>Parameters"
> >>>> registry located in
> >>>> https://www.iana.org/assignments/rsvp-te-parameters/rsvp-te-
> >>>> parameters.xhtml.
> >>>> The document "RSVP-TE Extensions for Collecting SRLG
> >>>> Information",draft-ietf-ccamp-rsvp-te-srlg-collect-05, introduces and
> >>>> defines a new Attribute Bit Flag, named "SRLG Collection Flag". It is
> >>>> requested that IANA makes an early assignment of the value of the
> >>>>"SRLG
> >>>> Collection Flag" from the Attribute Bit Flags.
> >>>>
> >>>> --> Type for a new RRO sub-object, named "SRLG sub-object " within the
> >>>> ROUTE_RECORD Object space. IANA has made assignments in the "Class
> >>>> Names, Class Numbers, and Class Types" section of the "RSVP
> >>>>PARAMETERS"
> >>>> registry located at http://www.iana.org/assignments/rsvp-parameters.
> >>>>It
> >>>> is requested that IANA makes an early assignment of the type of the
> >>>>new
> >>>> proposed RRO sub object in the document
> >>>> draft-ietf-ccamp-rsvp-te-srlg-collect-05 named "SRLG sub-object" from
> >>>> the ROUTE_RECORD portions of the mentioned registry.
> >>>>
> >>>> —> Value for a new Policy Control Failure Error sub code. IANA has
> >>>>made
> >>>> assignments in the "Error Codes and Globally-Defined Error Value
> >>>> Sub-Codes" section of the "RSVP
> >>>> PARAMETERS" registry located at
> >>>> http://www.iana.org/assignments/rsvp-parameters. We request that IANA
> >>>> makes an early assignment of a new error sub-code from the Policy
> >>>> Control Failure Sub-Codes registry.
> >>>>
> >>>> The main reason for the request of the early allocation is to
> >>>>facilitate
> >>>> interoperability of early implementations, as other WG documents have
> >>>> also new values in the same registry and clashes have been identified
> >>>> with the suggested values in the draft.
> >>>>
> >>>> Best Regards,
> >>>>
> >>>> Oscar
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>-----------------------------------------------------------------------
> >>>>-
> >>>>
> >>>> Este mensaje y sus adjuntos se dirigen exclusivamente a su
> >>>>destinatario,
> >>>> puede contener información privilegiada o confidencial y es para uso
> >>>> exclusivo de la persona o entidad de destino. Si no es usted. el
> >>>> destinatario indicado, queda notificado de que la lectura,
> >>>>utilización,
> >>>> divulgación y/o copia sin autorización puede estar prohibida en virtud
> >>>> de la legislación vigente. Si ha recibido este mensaje por error, le
> >>>> rogamos que nos lo comunique inmediatamente por esta misma vía y
> >>>>proceda
> >>>> a su destrucción.
> >>>>
> >>>> The information contained in this transmission is privileged and
> >>>> confidential information intended only for the use of the individual
> >>>>or
> >>>> entity named above. If the reader of this message is not the intended
> >>>> recipient, you are hereby notified that any dissemination,
> >>>>distribution
> >>>> or copying of this communication is strictly prohibited. If you have
> >>>> received this transmission in error, do not read it. Please
> >>>>immediately
> >>>> reply to the sender that you have received this communication in error
> >>>> and then delete it.
> >>>>
> >>>> Esta mensagem e seus anexos se dirigem exclusivamente ao seu
> >>>> destinatário, pode conter informação privilegiada ou confidencial e é
> >>>> para uso exclusivo da pessoa ou entidade de destino. Se não é vossa
> >>>> senhoria o destinatário indicado, fica notificado de que a leitura,
> >>>> utilização, divulgação e/ou cópia sem autorização pode estar proibida
> >>>>em
> >>>> virtude da legislação vigente. Se recebeu esta mensagem por erro,
> >>>> rogamos-lhe que nos o comunique imediatamente por esta mesma via e
> >>>> proceda a sua destruição
> >>>
> >>> _______________________________________________
> >>> CCAMP mailing list
> >>> [e-mail]
> >>> https://www.ietf.org/mailman/listinfo/ccamp
> >>
> >> ________________________________
> >>
> >> Este mensaje y sus adjuntos se dirigen exclusivamente a su
> >>destinatario, puede contener información privilegiada o confidencial y
> >>es para uso exclusivo de la persona o entidad de destino. Si no es
> >>usted. el destinatario indicado, queda notificado de que la lectura,
> >>utilización, divulgación y/o copia sin autorización puede estar
> >>prohibida en virtud de la legislación vigente. Si ha recibido este
> >>mensaje por error, le rogamos que nos lo comunique inmediatamente por
> >>esta misma vía y proceda a su destrucción.
> >>
> >> The information contained in this transmission is privileged and
> >>confidential information intended only for the use of the individual or
> >>entity named above. If the reader of this message is not the intended
> >>recipient, you are hereby notified that any dissemination, distribution
> >>or copying of this communication is strictly prohibited. If you have
> >>received this transmission in error, do not read it. Please immediately
> >>reply to the sender that you have received this communication in error
> >>and then delete it.
> >>
> >> Esta mensagem e seus anexos se dirigem exclusivamente ao seu
> >>destinatário, pode conter informação privilegiada ou confidencial e é
> >>para uso exclusivo da pessoa ou entidade de destino. Se não é vossa
> >>senhoria o destinatário indicado, fica notificado de que a leitura,
> >>utilização, divulgação e/ou cópia sem autorização pode estar proibida em
> >>virtude da legislação vigente. Se recebeu esta mensagem por erro,
> >>rogamos-lhe que nos o comunique imediatamente por esta mesma via e
> >>proceda a sua destruição
> >
> 
> 
> ________________________________
> 
> Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede
> contener información privilegiada o confidencial y es para uso exclusivo de la
> persona o entidad de destino. Si no es usted. el destinatario indicado, queda
> notificado de que la lectura, utilización, divulgación y/o copia sin autorización
> puede estar prohibida en virtud de la legislación vigente. Si ha recibido este
> mensaje por error, le rogamos que nos lo comunique inmediatamente por esta
> misma vía y proceda a su destrucción.
> 
> The information contained in this transmission is privileged and confidential
> information intended only for the use of the individual or entity named above. If
> the reader of this message is not the intended recipient, you are hereby notified
> that any dissemination, distribution or copying of this communication is strictly
> prohibited. If you have received this transmission in error, do not read it. Please
> immediately reply to the sender that you have received this communication in
> error and then delete it.
> 
> Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário,
> pode conter informação privilegiada ou confidencial e é para uso exclusivo da
> pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado,
> fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização
> pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem
> por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via
> e proceda a sua destruição