[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PWE3] Comments on draft-nitinb-mpls-tp-lsp-ping-bfd-procedures-02
- To: Greg Mirsky <gregimirsky at gmail.com>, Rahul Aggarwal <rahul at juniper.net>, David Ward <dward at juniper.net>, "Thomas D. Nadeau" <tom.nadeau at bt.com>, "mpls at ietf.org" <mpls at ietf.org>, "mpls-tp at ietf.org" <mpls-tp at ietf.org>, "ccamp at ietf.org" <ccamp at ietf.org>, pwe3 <pwe3 at ietf.org>
- Subject: Re: [PWE3] Comments on draft-nitinb-mpls-tp-lsp-ping-bfd-procedures-02
- From: Nitin Bahadur <nitinb at juniper.net>
- Date: Wed, 17 Feb 2010 23:28:42 -0800
- Accept-language: en-US
- Acceptlanguage: en-US
- Delivered-to: pwe3 at core3.amsl.com
- In-reply-to: <787be2781002171259x1c9a3536k7dafabed3ab99f66 at mail.gmail.com>
- List-archive: <http://www.ietf.org/mail-archive/web/pwe3>
- List-help: <mailto:pwe3-request@ietf.org?subject=help>
- List-id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
- List-post: <mailto:pwe3@ietf.org>
- List-subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
- List-unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
- Thread-index: AcqwFBO+zMuQ18V2SDiRtp4XiQfBkAAV+tHV
- Thread-topic: Comments on draft-nitinb-mpls-tp-lsp-ping-bfd-procedures-02
- User-agent: Microsoft-Entourage/13.3.0.091002
Hi Greg,
Thanks for reading the draft in detail. See inline below for responses to your comments.
On 2/17/10 12:59 PM, "Greg Mirsky" <gregimirsky at gmail.com> wrote:
Dear Authors and All,
below are my comments to the document:
* Abstract - "widely deployed" to replace "widely deployment"
NB> Will fix that.
* Section 2.1, Figure 2 - Section 3 RFC 5586 states that if ACH TLVs might be present then ACH TLV Header must be present. The Length of ACH TLV Header may set to zero in no ACH TLVs are actually present in the given packet. Said that I turn to figure 2 that presents LSP Ping packet with ACH format. The ACH TLV Header is not presented in the format even though presence of ACH TLVs is indicated. I think that proper LSP Ping with ACH format will look as:
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MPLS Label stack |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| GAL |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 0 0 1|Version| Reserved | LSP-Ping Channel Type |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ACH TLV Header |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ACH TLVs |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| LSP-Ping payload |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
NB> You are right. I will fix that.
* Section 2.3 discusses optional use of Source Address TLV but the sentence "Only 1 source address TLV MUST be present in a LSP-Ping packet." may be interpreted as the Source Address TLV is mandatory. I propose to change "MUST" to "MAY" in the sentence
NB> Sure...will rephrase to avoid confusion.
* Figure 3 - same comments regarding ACH TLV Header in the format as for Figure 2
NB> Will fix.
Thanks for your useful comments Greg.
Nitin