Re: [mpls-tp] poll to adopt draft-nitinb-mpls-tp-on-demand-cv as a working group document

Hi Haiyan,

On 7/1/10 6:53 PM, "Zhang Haiyan" <zhanghaiyan@huawei.com> wrote:

> No/ do not support.
> 
> Several comments need clarification:
> 
> 1) We do not see how the content of the draft satisfies "on-demand-cv" as
> claimed in the title. We only see "LSP-Ping" and "LSP Traceroute" in the main
> part of the draft.

> In the introduction part we also see the "on-demand Connectivity Verification,
> Route Tracing and Adjacency functions".
> Could the authors clarify the "on-demand CV"?

I agree that the text needs a little working to make it clear how on-demand
CV, Route tracing and Adjaceny are achieved. The current text is based
around the solution (lsp-ping), rather than the requirement (cv,
route-tracing). The authors will fix this in the next revision.

> 2) Could the authors clarify the purpose of describing "LSP-Ping with IP
> encapsulation" and "LSP Traceroute with IP encapsulation"?

Thanks for asking. As per Section 2.1.4 of RFC 5860

" It MUST be possible to deploy the OAM functionality in any of these
   environments.  As a result, it MUST be possible to operate OAM
   functions with or without relying on IP capabilities, and it MUST be
   possible to choose to make use of IP capabilities when these are
   present."

To ensure that the above requirement was met, we added the sections on
LSP-ping with IP encap.

> The draft seems to be just a regular extension of MPLS LSP ping, not
> particular for MPLS-TP. Shouldn't it be a draft with the name
> "mpls-lsp-ping-extensions"?

Godo question. It is true that the extensions apply equally well to regular
MPLS LSPs. As per the MPLS-TP Joint Working Team guidelines, all drafts that
address mpls-tp requirement/solutions should have a mpls-tp name (for
simplicity for IETF WG chairs and their ITU counter-parts).

Hope that helps.
Nitin

> ----- Original Message -----
> From: "Loa Andersson" <loa@pi.nu>
> To: <mpls-tp@ietf.org>; <mpls@ietf.org>; "MPLS-TP ad hoc team"
> <ahmpls-tp@lists.itu.int>
> Sent: Monday, June 21, 2010 8:07 PM
> Subject: [mpls-tp] poll to adopt draft-nitinb-mpls-tp-on-demand-cv as a
> working group document
> 
> 
>> 
>> Working Group,
>> 
>> this email is to start poll to adopt
>> draft-nitinb-mpls-tp-on-demand-cv-00.txt
>> as an MPLS working group draft.
>> 
>> After recent experience, the chairs would like to remind you all
>> what it means to conduct a poll to adopt a draft as a working group
>> draft.
>> 
>> - Please recall that the IETF does not "vote." Polls of a working
>>   group are to gather information to help the chairs make their
>>   decisions. Voting is not part of the normal working methods of
>>   an IETF working group.
>> 
>> - The "rough consensus" process used in the working group assumes
>>   that people expressing opinions are also participating in the
>>   development of standards documents.
>> 
>> - Subscription to the list specifically to express an opinion is
>>   noticed by the chairs who has access to information on the new list
>>   members. Such behavior is not part of the normal working methods.
>> 
>> - The purpose of a poll for adoption is to help the chairs understand
>>   the level of support for a document (i.e. who has read it, who
>>   believes it is a good starting point for working group work, who
>>   will contribute to the work) and whether there are any significant
>>   technical issues. Statements of objection must be backed up by
>>   proper technical reasons.
>> 
>> So please respond to this poll indicating whether you support the
>> adoption of this draft or stating your technical issues.
>> 
>> Please also not that this draft has after a discussion with the
>> working group chairs been renamed, it was earlier know as
>> draft-nitinb-mpls-tp-lsp-ping-extensions-01.
>> 
>> This poll ends eob July 5.
>> 
>> 
>> Loa and George
>> mpls wg co-chairs
>> 
>> -- 
>> 
>> 
>> 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-tp mailing list
>> mpls-tp@ietf.org
>> https://www.ietf.org/mailman/listinfo/mpls-tp
> _______________________________________________
> mpls-tp mailing list
> mpls-tp@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls-tp