Re: [mpls] Kathleen Moriarty's No Objection on draft-ietf-mpls-lsp-ping-relay-reply-10: (with COMMENT)

Lizhong Jin <lizho.jin@gmail.com> Tue, 29 September 2015 15:03 UTC

Return-Path: <lizho.jin@gmail.com>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 369D51B445D; Tue, 29 Sep 2015 08:03:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_FONT_LOW_CONTRAST=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Kx8jS2R1mAoH; Tue, 29 Sep 2015 08:03:10 -0700 (PDT)
Received: from mail-wi0-x231.google.com (mail-wi0-x231.google.com [IPv6:2a00:1450:400c:c05::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B5FC91B4458; Tue, 29 Sep 2015 08:03:09 -0700 (PDT)
Received: by wicge5 with SMTP id ge5so154831148wic.0; Tue, 29 Sep 2015 08:03:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=tAMchHoMbkxvNJ7VKa1WsSun7dakFSYC2ghBdw1FLRY=; b=io5lSDwlWAppZ6fN/SK8CrW+vHPxf4Mo6+Swh7x8ywg0z1c1gag2svqiCBPdeVaw7c IpL2ykJDaJUre8bZ2pTFEXSfEc9O1rsOaGwO61Y5I8HzEk2fMceTuixdJ+OuZZRz7nA0 cJUX4eoF1t4u5gO6y27c699ygawy/949HgTFO9GKtgAC/8d+F8CxGSFktjq+sECqIYmB hMR2rPXrcMXAk5inqN3LkFKB4HVIJ1fyIo1vcELYCBwwU/zxl/L1BIw/N8+n/hVJkdvK P5I+/u8WA9LopzUlidDrZzrIxkPoy5jBAOJiBhxwXdACKSyZwQ//9NLc3Y99hDcinW4A X+8w==
MIME-Version: 1.0
X-Received: by 10.180.206.83 with SMTP id lm19mr27259278wic.63.1443538988226; Tue, 29 Sep 2015 08:03:08 -0700 (PDT)
Received: by 10.194.236.164 with HTTP; Tue, 29 Sep 2015 08:03:08 -0700 (PDT)
In-Reply-To: <20150928144514.27528.79571.idtracker@ietfa.amsl.com>
References: <20150928144514.27528.79571.idtracker@ietfa.amsl.com>
Date: Tue, 29 Sep 2015 23:03:08 +0800
Message-ID: <CAH==cJzA_+AMYPRO0Fj3hmKAVZkMs4s1+-FLkUhNJ2iTEGJjnw@mail.gmail.com>
From: Lizhong Jin <lizho.jin@gmail.com>
To: Kathleen Moriarty <Kathleen.Moriarty.ietf@gmail.com>
Content-Type: multipart/alternative; boundary=001a11c26b789cdd9b0520e41caa
Archived-At: <http://mailarchive.ietf.org/arch/msg/mpls/_soFLolgwXrfHpCr8toAAnm7ZP0>
Cc: "mpls@ietf.org" <mpls@ietf.org>, draft-ietf-mpls-lsp-ping-relay-reply <draft-ietf-mpls-lsp-ping-relay-reply@ietf.org>, The IESG <iesg@ietf.org>, mpls-chairs <mpls-chairs@ietf.org>
Subject: Re: [mpls] Kathleen Moriarty's No Objection on draft-ietf-mpls-lsp-ping-relay-reply-10: (with COMMENT)
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mpls/>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Sep 2015 15:03:12 -0000

Hi, Kathleen
Thanks for the review. Please see inline below.

Regards
Lizhong

On Mon, Sep 28, 2015 at 10:45 PM, Kathleen Moriarty <
Kathleen.Moriarty.ietf@gmail.com> wrote:

> Kathleen Moriarty has entered the following ballot position for
> draft-ietf-mpls-lsp-ping-relay-reply-10: No Objection
>
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
>
>
> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
>
>
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-mpls-lsp-ping-relay-reply/
>
>
>
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> Thanks for your work on this draft.  The security review from 6 months
> ago hasn't been fully addressed in the draft and I think it would be
> helpful to do so.  There were responses given on list, but corresponding
> updates didn't happen for all of the comments.
>
> https://www.ietf.org/mail-archive/web/secdir/current/msg05301.html
>
> For the first comment, the response was that this mechanism does not
> deprecate use of "Echo Reply".  The language in the first paragraph of
> section 3 should be made clear on that point.
>
> [Lizhong] OK, how about to change the first paragraph in section3 as below.

 This new
   message is used to replace Echo Reply message which is sent from the
   replying LSR to a relay node or from a relay node to another relay
   node. Note that the reply message from any node to the initiator will

   still be Echo Reply.


> For the second comment:
>     s4.1: Is the outermost label allowed to be set to 255 to support the
>     “ping” mode or must it always be set to 1, 2, etc. to support
> “traceroute"
>     mode - as described in RFC 4379 s4.3?   I know s5 is just an example
>     but it really looks like this extension is just supposed to be for
> fault
>     isolation.
>
> The response via email says it is possible to set it to 255, could this
> be made clear in the draft?
>
[Lizhong] in section4, we added that LSP ping is possible as below:

If operator has knowledge of the relay nodes,
   the initiator could do LSP Ping by directly sending Echo Request with
   Relay Node Address Stack TLV containing the already known relay
   nodes.

Is the above enough? It seems a bit redundant to say TTL is set to 255 in

Ping mode here.


>
> The third comment was addressed, thank you.
>
> It was also good to see the security considerations cover path discovery
> as well as DoS related attacks.  Thanks for that!
>
>
>