Alex Campbell <alex.campb...@aviatnet.com> wrote:
> Hi,
> 
> I noticed the table in section 3 has been mangled - it has extra
> blank lines, entries in the wrong side of the table, and a missing
> pipe in the bottom right corner.

Thanks, now fixed.  The table now looks like this:

   +----------------------------------+--------------------------------+
   | YANG data node in                | IP-MIB object                  |
   | /if:interfaces/if:interface      |                                |
   +----------------------------------+--------------------------------+
   | ipv4                             | ipv4InterfaceEnableStatus      |
   | ipv4/enabled                     | ipv4InterfaceEnableStatus      |
   | ipv4/address                     | ipAddressEntry                 |
   | ipv4/address/ip                  | ipAddressAddrType              |
   |                                  | ipAddressAddr                  |
   | ipv4/neighbor                    | ipNetToPhysicalEntry           |
   | ipv4/neighbor/ip                 | ipNetToPhysicalNetAddressType  |
   |                                  | ipNetToPhysicalNetAddress      |
   | ipv4/neighbor/link-layer-address | ipNetToPhysicalPhysAddress     |
   | ipv4/neighbor/origin             | ipNetToPhysicalType            |
   | ipv6                             | ipv6InterfaceEnableStatus      |
   | ipv6/enabled                     | ipv6InterfaceEnableStatus      |
   | ipv6/forwarding                  | ipv6InterfaceForwarding        |
   | ipv6/address                     | ipAddressEntry                 |
   | ipv6/address/ip                  | ipAddressAddrType              |
   |                                  | ipAddressAddr                  |
   | ipv4/address/origin              | ipAddressOrigin                |
   | ipv6/address/status              | ipAddressStatus                |
   | ipv6/neighbor                    | ipNetToPhysicalEntry           |
   | ipv6/neighbor/ip                 | ipNetToPhysicalNetAddressType  |
   |                                  | ipNetToPhysicalNetAddress      |
   | ipv6/neighbor/link-layer-address | ipNetToPhysicalPhysAddress     |
   | ipv6/neighbor/origin             | ipNetToPhysicalType            |
   | ipv6/neighbor/state              | ipNetToPhysicalState           |
   +----------------------------------+--------------------------------+

           YANG Interface Data Nodes and Related IP-MIB Objects


/martin



> 
> Apart from that this draft looks good to me.
> ________________________________________
> From: netmod <netmod-boun...@ietf.org> on behalf of Kent Watsen 
> <kwat...@juniper.net>
> Sent: Wednesday, 29 November 2017 8:29 a.m.
> To: netmod@ietf.org
> Cc: netmod-cha...@ietf.org
> Subject: [netmod] WG Last Call: draft-ietf-netmod-rfc7277bis-00
> 
> All,
> 
> This starts a two-week working group last call on
> draft-ietf-netmod-rfc7277bis-00.
> 
> Please recall that this update's intention is to
> modify the YANG module to be in line with the NMDA
> guidelines [1].  Reviewing the diff between the two
> drafts [2] should reveal just this.
> 
> The working group last call ends on December 12.
> Please send your comments to the netmod mailing list.
> 
> Positive comments, e.g., "I've reviewed this document
> and believe it is ready for publication", are welcome!
> This is useful and important, even from authors.
> 
> [1] https://tools.ietf.org/html/draft-dsdt-nmda-guidelines-01
> [2] https://tools.ietf.org/rfcdiff?url2=draft-ietf-netmod-rfc7277bis-00.txt
> 
> Thank you,
> Netmod Chairs
> 
> _______________________________________________
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod
> 
> _______________________________________________
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod
> 

_______________________________________________
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

Reply via email to