Re: [mpls] colliding sub-TLVs for three MPLS wg drafts

Loa Andersson <loa@pi.nu> Sat, 06 November 2010 01:22 UTC

Message-ID: <4CD4ADCA.2090400@pi.nu>
Date: Sat, 06 Nov 2010 09:22:18 +0800
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6
MIME-Version: 1.0
To: "mpls-tp@ietf.org" <mpls-tp@ietf.org>, "mpls@ietf.org" <mpls@ietf.org>
References: <4CC84B41.9000506@pi.nu>
In-Reply-To: <4CC84B41.9000506@pi.nu>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: Re: [mpls] colliding sub-TLVs for three MPLS wg drafts
Precedence: list

Working Group,

just a quick reminder about this issue. Since I've not heard anything I
will start working towards an acceptable solution hear in Beijing.

However, the deadline to notify us about existing implementations and
deployments of the code points for the cc-cv-rdi draft is still
Thursday.

/Loa

On 2010-10-27 23:54, Loa Andersson wrote:
> Working Group,
>
> we have been working to progress several drafts to RFCs. Sometimes
> the process requires that we do early IANA allocations because some
> vendors has started to implement or even deploying equipment that
> relies on code points defined in the drafts.
>
> What has happened now is that we have two drafts
>
> draft-ietf-mpls-p2mp-lsp-ping
> draft-ietf-mpls-lsp-ping-enhanced-dsmap
>
> that has been comparatively stable for a long time, but on and
> off been waiting on each other. We have done a "two document"
> working group last call. We now have the documents in shape
> to request publication. Both documents are implemented and
> deployed.
>
> These documents request IANA allocation for 4 different sub-tlv's.
>
> We also have
>
> draft-ietf-mpls-tp-on-demand-cv
>
> for this document we requested early IANA allocation of two
> sub-tlv's. The code-points were granted recently.
>
> What has happened is that the code-points were assigned as
> early allocations as has been used when implementing
> draft-ietf-mpls-p2mp-lsp-ping.
>
> The easiest way out would be to assign new code-points to
> draft-ietf-mpls-tp-on-demand-cv and in the publication process
> assign the same code-pints to draft-ietf-mpls-p2mp-lsp-ping
> that has been used during the implementation.
>
> We therefore need to know
>
> 1. If anyone has implemented draft-ietf-mpls-tp-on-demand-cv
> using the code points assigned as an early allocation
> 2. If this implementation has been deployed.
> 3. If it possible to use new code points even if the first
> implementation uses the code points assigned through early
> allocation.
>
> We need your responses November 12, 2010 the latest.
>
> The working group chairs will also make sure that we do not
> any similar potential "double allocations" in waiting.
>
> /Loa

-- 


Loa Andersson                         email: loa.andersson@ericsson.com
Sr Strategy and Standards Manager            loa@pi.nu
Ericsson Inc                          phone: +46 10 717 52 13
                                              +46 767 72 92 13

[mpls] colliding sub-TLVs for three MPLS wg drafts Loa Andersson
Re: [mpls] colliding sub-TLVs for three MPLS wg d… Loa Andersson