Re: [netmod] New Version Notification for draft-ding-netmod-arp-yang-model-00.txt

"dingxiaojian (A)" <> Wed, 01 November 2017 02:34 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id C731E13F83A for <>; Tue, 31 Oct 2017 19:34:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 8__ODQeLMh6z for <>; Tue, 31 Oct 2017 19:34:35 -0700 (PDT)
Received: from ( []) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id EC0D013F81F for <>; Tue, 31 Oct 2017 19:34:34 -0700 (PDT)
Received: from (EHLO ([]) by (MOS 4.3.7-GA FastPath queued) with ESMTP id DRU00022; Wed, 01 Nov 2017 02:34:33 +0000 (GMT)
Received: from ( by ( with Microsoft SMTP Server (TLS) id 14.3.361.1; Wed, 1 Nov 2017 02:33:31 +0000
Received: from ([]) by ([]) with mapi id 14.03.0361.001; Wed, 1 Nov 2017 10:33:28 +0800
From: "dingxiaojian (A)" <>
To: Alex Campbell <>
CC: "" <>
Thread-Topic: New Version Notification for draft-ding-netmod-arp-yang-model-00.txt
Thread-Index: AdNSuYxmkDPQfyT5S6yC51uqJHOFNw==
Date: Wed, 01 Nov 2017 02:33:28 +0000
Message-ID: <>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
x-originating-ip: []
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020202.59F932B9.0081, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: f878fea379253e5d24f6a6bdf13d3ffa
Archived-At: <>
Subject: Re: [netmod] New Version Notification for draft-ding-netmod-arp-yang-model-00.txt
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: NETMOD WG list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 01 Nov 2017 02:34:38 -0000

Hi Alex,

Thank you for your review of the draft and thoughtful comments, sincerely appreciated.
Sorry for the delay, please find my answers and notes in-line tagged DXJ>>.


发件人: Alex Campbell [] 
发送时间: 2017年10月27日 6:30
收件人: dingxiaojian (A) <>;
主题: Re: New Version Notification for draft-ding-netmod-arp-yang-model-00.txt

Hi Xiaojian,

* The published module ietf-ip (RFC 7277) overlaps the data being provided in this module.
  Especially your /arp/arp-tables and /arp/arp-static-tables seem to correspond to /interfaces-state/interface/ipv4/neighbor and /interfaces/interface/ipv4/neighbor from ietf-ip.
  I think we should avoid duplication of data where possible; can you refactor this module to augment what is already there?

DXJ>>  Thank you for remind us  of  RFC 7277. 
For / interfaces / interface / ipv4 / neighbor, it does describe entries of mappings from IPv4 addresses to link-layer addresses, which is similar to / arp / arp-static-tables in our draft. We will take your suggestion. 
For / interfaces-state / interface / ipv4 /neighbor, the list describes the ARP Cache. That is, we can only obtain ARP entries for an interface. However, in our / arp / arp-tables, we can not only obtain ARP entries for an interface, but also obtain ARP entries for a VPN (use vrf-name as the key).

* Data relating to a specific interface should be inside /interfaces/interface (and -state) (ietf-interfaces, RFC 7223) where it is possible and relevant.
  I don't see any reason to have a completely separate list with a leafref as a key, when you could use 'augment' to have the data as part of the interface itself.

  DXJ>> Good point. We take your suggestion. 'augment' can be used to refactor the module of possible / interfaces / interface in RFC 7223.

* ARP as a feature is not dependent on VRFs, but implementing this module requires the server to also implement ietf-network-instances.
  If the ARP-related data was under /interfaces(-state) then this draft wouldn't need to rely on ietf-network-instances.
  The network-instances draft already takes care of making sure each VRF has a separate list of interfaces.

  DXJ>> Good point. As discussed in the first part, vrf related entry is deleted in / arp / arp-static-tables.

From: netmod <> on behalf of dingxiaojian (A) <>
Sent: Thursday, 26 October 2017 10:27 p.m.
Subject: Re: [netmod] New Version Notification for draft-ding-netmod-arp-yang-model-00.txt

Hi all,

The ARP YANG module defined in this document has common properties that need to be configured.
It provides freedom for service providers to adapt this data model to different product implementations.

Please have a look and provide comments on the list.


A new version of I-D, draft-ding-netmod-arp-yang-model-00.txt
has been successfully submitted by Xiaojian Ding and posted to the IETF repository.

Name:           draft-ding-netmod-arp-yang-model
Revision:       00
Title:          YANG Data Model for ARP
Document date:  2017-10-26
Group:          Individual Submission
Pages:          16

   This document defines a YANG data model to describe Address
   Resolution Protocol (ARP) configurations.  It is intended this model
   be used by service providers who manipulate devices from different
   vendors in a standard way.

Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at

The IETF Secretariat

netmod mailing list