[mpls] draft-zheng-mpls-lsp-ping-yang-cfg
"Nobo Akiya" <nobo.akiya.dev@gmail.com> Fri, 27 March 2015 16:01 UTC
Return-Path: <nobo.akiya.dev@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 1AD241A86EB for <mpls@ietfa.amsl.com>; Fri, 27 Mar 2015 09:01:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.893
X-Spam-Level:
X-Spam-Status: No, score=-0.893 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, LOCALPART_IN_SUBJECT=1.107, SPF_PASS=-0.001] autolearn=no
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 glzp2RBiuyEm for <mpls@ietfa.amsl.com>; Fri, 27 Mar 2015 09:01:12 -0700 (PDT)
Received: from mail-wg0-x22d.google.com (mail-wg0-x22d.google.com [IPv6:2a00:1450:400c:c00::22d]) (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 14C771A1BBD for <mpls@ietf.org>; Fri, 27 Mar 2015 09:01:12 -0700 (PDT)
Received: by wgs2 with SMTP id 2so104303018wgs.1 for <mpls@ietf.org>; Fri, 27 Mar 2015 09:01:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:subject:date:message-id:mime-version:content-type :content-transfer-encoding:thread-index:content-language; bh=tcj1dn+ZZSQrBn549KhL1foDDtAyWM49Z4xI8iKqUj8=; b=WMjBjVelyUqHqyMKiOxY1ygP8+7T14AhXq+8SNIZgiJHiXTXEgfPFpy24k0bdzOU3u B9KOlKsDX3KlPdqGQ8Uha/CwRPm4PK2oHRx0ApPzW0sSpCAWZprYAQbaPvN3Cxv3FqRt moiUAU/U7If+2e+Hjzekkg8AF0dl3pBqrwmsXVSJODIRy8ElfupxoVu97bsiZJnkX4D8 Y/gGXlIkX+phaIvCObd4RcUv6tcwqPl9OKaaQS8TJwR9pjF77x+FNfUPS8+BAKxfnCwb ryLBPV4ZsS8oiV2OHyhW2jbmEbDcQkMYqRHPG3AWDlPctvnmM2QNzLCrWpTLzPvKgEd3 ao6Q==
X-Received: by 10.180.75.212 with SMTP id e20mr57160753wiw.26.1427472070788; Fri, 27 Mar 2015 09:01:10 -0700 (PDT)
Received: from NoboAkiyaPC ([2001:67c:370:160:9db3:57f0:1e4a:bc1f]) by mx.google.com with ESMTPSA id dq8sm3405748wib.9.2015.03.27.09.01.08 (version=TLSv1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 27 Mar 2015 09:01:10 -0700 (PDT)
From: Nobo Akiya <nobo.akiya.dev@gmail.com>
To: draft-zheng-mpls-lsp-ping-yang-cfg@tools.ietf.org
Date: Fri, 27 Mar 2015 11:01:03 -0500
Message-ID: <053c01d068a7$3bc640e0$b352c2a0$@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 15.0
Thread-Index: AdBopD4/IHhTgg/lSkyC3mZakt4iwA==
Content-Language: en-ca
Archived-At: <http://mailarchive.ietf.org/arch/msg/mpls/2dmkLlIebuo8iLkm7hR5qWK1vnw>
Cc: 'mpls' <mpls@ietf.org>
Subject: [mpls] draft-zheng-mpls-lsp-ping-yang-cfg
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: <http://www.ietf.org/mail-archive/web/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: Fri, 27 Mar 2015 16:01:15 -0000
Hi Authors, I went through the document [briefly] and had some comments. 1. In resultInfo, it is critical that we include Return Code and Return Subcode so that the users will know the nature of the error when problems are encountered. 2. Similar to the first comment, it is also important to include the source IP address of the received MPLS Echo Reply in the resultInfo, so that when a non-success MPLS Echo Reply is received back by the initiating node, users will know which network node sent that packet. 3. Frequency and ProbeCount is part of the Control Information, but the mechanism also allows the Schedule Parameters to specify when to start/stop. This will become ambiguous as the "operation" is done when MPLS Echo Request is sent ProbeCount times at the Frequency specified but the endTest can also defines the data/time when the operation should terminate. A clear description of the relationship/rule of them will be helpful. 4. The Control Information allows specifying of an outgoing interface but you'll also want to specify the nexthop address. 5. Being able to specify the TTL will be beneficial. 6. You'll also want to have some control over the ECMP, by being able to specify the destination IP address (i.e., 127/8) or inclusion of ELI/EL and the value of the EL. For the exact syntax, this is an aspect which will be helpful to talk to multiple vendors. For example, I know of an implementation which allows specifying of a _range_ of entropy set to be used, so that a single Ping operation sweeps the entropy set. Whether such capability is included in the yang definition or kept outside of it is a good discussion to have. 7. Before going too far forward with just the Ping, it'll be good to add the mechanism for Traceroute as well. Specifically how do we notify the information in the received DSMAP/DDMAP (with various Sub-TLVs of the DDMAP). 8. Related to comment 7, even the Ping operation may want to allow inclusion of a DSMAP/DDMAP. This will be useful when used together with a specific TTL value. Thanks! -Nobo
- [mpls] draft-zheng-mpls-lsp-ping-yang-cfg Nobo Akiya
- Re: [mpls] draft-zheng-mpls-lsp-ping-yang-cfg Gregory Mirsky