Re: [mpls] FW: FW: New Liaison Statement, "LS331 - Corrigendum 1 to Recommendation ITU-T G.8013/Y.1731: Global MEG_ID"

Hi,

the ITU-T ID draft does that this already, although well hidden. That is what I referred to as "formula" during my presentation. At the end of section 3 is says:

"The same substitution procedure applies to all identifiers specified
in RFC 6370 [RFC6370] except for the other alternatives mentioned in
this document."

But as announced, we'll spell this out in the next version of the document. 

Best,

Rolf

NEC Europe Limited | Registered Office: NEC House, 1 Victoria Road, London W3 6BL | Registered in England 2832014 

> -----Original Message-----
> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of
> Lou Berger
> Sent: Dienstag, 15. November 2011 02:16
> To: huubatwork@gmail.com
> Cc: mpls@ietf.org
> Subject: Re: [mpls] FW: FW: New Liaison Statement, "LS331 - Corrigendum
> 1 to Recommendation ITU-T G.8013/Y.1731: Global MEG_ID"
> 
> Huub,
> 	I guess I didn't make my self sufficiently clear.  Let me try
> again. If I understood the comments made in the meeting correctly, the
> statement made is that the usage of CC:ICC (ICC_GLOBAL_ID) is defined
> by the ITU-T and that the liaison referenced by Scott identifies the
> reference for this definition.  Is this correct?
> 
> Assuming this is correct, the referenced ITU-T document only covers
> usage of CC:ICC within the scope of a MEG_ID. So this raises the
> question of where is the ITU-T definition for usage of CC:ICC for MPLS
> LSPs & tunnels.  I surmised that such a definition does not exist, and
> therefor postulated that draft-ietf-mpls-tp-itu-t-identifiers will
> provide an LSP/Tunnel definition based on the ITU-T MEG_ID.
> 
> So, is this conclusion correct?
> 
> Much thanks,
> Lou
> 
> 
> On 11/14/2011 11:16 AM, Huub van Helvoort wrote:
> > Hello Lou,
> >
> > You wrote:
> >
> >> As the scope of this document (ITU-T G.8013/Y.1731) is just MEG IDs,
> >> I guess this means that draft-ietf-mpls-tp-itu-t-identifiers will
> >> need to explicitly define how to go from ICC-based MEG IDs to
> >> ICC_based LSPs&Tunnels, right?
> >
> > The draft-ietf-mpls-tp-itu-t-identifiers described how the Global_ID
> > can be based on CC and ICC.
> > RFC6370 defines how LSPs&Tunnels use the Global_ID to provide a
> global
> > unique number.
> >
> > Regards, huub.
> >
> >
> >
> >> On 11/14/2011 9:52 AM, Scott Mansfield wrote:
> >>> Greg and Huub,
> >>>
> >>> Looking at the text of liaison, the actual text of the corrigendum
> 1
> >>> is not attached to the liaison.  Currently the document is only
> >>> available to ITU-T TIES members since the document is still
> >>> "pre-published".
> >>>
> >>> Can you please provide the document?
> >>>
> >>> Regards,
> >>> -scott.
> >>>
> >>>> -----Original Message-----
> >>>> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On
> >>>> Behalf Of Scott Mansfield
> >>>> Sent: Sunday, November 13, 2011 8:36 PM
> >>>> To: mpls@ietf.org
> >>>> Subject: [mpls] FW: New Liaison Statement, "LS331 - Corrigendum 1
> >>>> to Recommendation ITU-T G.8013/Y.1731: Global MEG_ID"
> >>>>
> >>>> This is the liaison from the ITU-T that includes information about
> >>>> the Global MEG ID.  Uses the Country Code and the ICC to make the
> >>>> MEG ID globally unique.
> >>>>
> >>>> Regards,
> >>>> -scott.
> >>>>
> >>>>> -----Original Message-----
> >>>>> From: Liaison Statement Management Tool [mailto:lsmt@ietf.org]
> >>>>> Sent: Thursday, October 06, 2011 4:52 PM
> >>>>> To: rcallon@juniper.net; swallow@cisco.com; loa@pi.nu
> >>>>> Cc: yoichi.maeda@ttc.or.jp;
> >>>>> Steve.Trowbridge@alcatel-lucent.com; mpls@ietf.org;
> >>>>> lear@cisco.com; Scott Mansfield; huub.van.helvoort@huawei.com;
> >>>>> tsbsg15@itu.int; greg.jones@itu.int; hiroshi.ota@itu.int
> >>>>> Subject: New Liaison Statement, "LS331 - Corrigendum 1 to
> >>>>> Recommendation ITU-T G.8013/Y.1731: Global MEG_ID"
> >>>>>
> >>>>> Title: LS331 - Corrigendum 1 to Recommendation ITU-T
> >>>>> G.8013/Y.1731: Global MEG_ID Submission Date: 2011-10-06 URL of
> >>>>> the IETF Web page: /liaison/1100/
> >>>>>
> >>>>> From: ITU-T SG 15  (Greg Jones<greg.jones@itu.int>)
> >>>>> To: Multiprotocol Label Switching (rcallon@juniper.net,
> >>>>> swallow@cisco.com, loa@pi.nu)
> >>>>> Cc:
> >>>>> yoichi.maeda@ttc.or.jp,Steve.Trowbridge@alcatel-lucent.com,mpl
> >>>>> s@ietf.org,lear@cisco.com,scott.mansfield@ericsson.com
> >>>>> Reponse Contact:
> >>>>> tsbsg15@itu.int,greg.jones@itu.int,hiroshi.ota@itu.int
> >>>>> Technical Contact: huub.van.helvoort@huawei.com
> >>>>> Purpose: For information
> >>>>>
> >>>>> Body: The experts of Q10/15 would like to inform you that they
> >>>>> have agreed to a corrigendum for Recommendation ITU-T
> >>>>> G.8013/Y.1731 "OAM functions and mechanisms for Ethernet based
> >>>>> networks."
> >>>>> This corrigendum provides the definition of a globally
> >>>> unique MEG-ID
> >>>>> by using the Country Code (CC) and ITU-T Carrier Code (ICC).
> >>>>> Attach: TD477/PLEN, "Corrigendum 1 to Recommendation ITU-T
> >>>>> G.8013/Y.1731".
> >>>>> Attachment(s):
> >>>>>
> >>>>>      LS331 - Corrigendum 1 to Recommendation ITU-T
> >>>>> G.8013/Y.1731: Global MEG_ID - pdf body
> >>>>> https://datatracker.ietf.org/documents/LIAISON/file1279.pdf
> >>>>>
> >>>>>
> >>>>>
> >>>> _______________________________________________
> >>>> mpls mailing list
> >>>> mpls@ietf.org
> >>>> https://www.ietf.org/mailman/listinfo/mpls
> >>>>
> >>> _______________________________________________
> >>> mpls mailing list
> >>> mpls@ietf.org
> >>> https://www.ietf.org/mailman/listinfo/mpls
> >>>
> >>>
> >>>
> >>>
> >> _______________________________________________
> >> mpls mailing list
> >> mpls@ietf.org
> >> https://www.ietf.org/mailman/listinfo/mpls
> >
> >
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls