[trill] Shepherd comments on draft-ietf-trill-arp-optimization - Document ready with a fi

"Susan Hares" <shares@ndzh.com> Fri, 02 October 2015 20:28 UTC

Return-Path: <shares@ndzh.com>
X-Original-To: trill@ietfa.amsl.com
Delivered-To: trill@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C3B5F1B2D67 for <trill@ietfa.amsl.com>; Fri, 2 Oct 2015 13:28:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -97.654
X-Spam-Level:
X-Spam-Status: No, score=-97.654 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DOS_OUTLOOK_TO_MX=2.845, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] 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 s9a4hB6FOmCS for <trill@ietfa.amsl.com>; Fri, 2 Oct 2015 13:28:57 -0700 (PDT)
Received: from hickoryhill-consulting.com (hhc-web3.hickoryhill-consulting.com [64.9.205.143]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D47211B2D60 for <trill@ietf.org>; Fri, 2 Oct 2015 13:28:55 -0700 (PDT)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=184.157.84.146;
From: "Susan Hares" <shares@ndzh.com>
To: <trill@ietf.org>
Date: Fri, 2 Oct 2015 16:28:51 -0400
Message-ID: <006b01d0fd50$f3d8d830$db8a8890$@ndzh.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_006C_01D0FD2F.6CC8BED0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdD9UNW7FHwZJGumSA+XAomACowYfg==
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com
Archived-At: <http://mailarchive.ietf.org/arch/msg/trill/SVmP0QNwY3UaVhbjkweULl1ZxLE>
Cc: 'Donald Eastlake' <d3e3e3@gmail.com>, 'Jon Hudson' <jon.hudson@gmail.com>
Subject: [trill] Shepherd comments on draft-ietf-trill-arp-optimization - Document ready with a fi
X-BeenThere: trill@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Developing a hybrid router/bridge." <trill.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/trill>, <mailto:trill-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/trill/>
List-Post: <mailto:trill@ietf.org>
List-Help: <mailto:trill-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/trill>, <mailto:trill-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Oct 2015 20:28:59 -0000

Draft: draft-ietf-trill-arp-optimization 

http://datatracker.ietf.org/doc/draft-ietf-trill-arp-optimization/

Status: Ready for WG LC, only minor edits needed



Minor Nits that must be fixed: 

1)      Use the right RFC2119 boiler plate and update "should" to "SHOULD"
plus "may" to "MAY"

 

Editorial issues: 

#1 Page 4 section 2 paragraph 2

From: 

/If the RBridge has extracted the sender's IP/MAC address pair from the
received data packet, it may save the information and use the IA APPsub-TLV
to distribute it to save the information and distribute it to other RBridges
through ESADI/ 

To: 

/If the RBridge has extracted the sender's IP/MAC address pair from the
received data packet (either ARP or ND), it may save the information and use
the IA APPsub-TLV to distribute it to save the information and distribute it
to other RBridges through ESADI/ 

Note: If my understanding of the data packet is wrong, would you please
clarify that instead in this paragraph. 

#2 section 3.1 paragraph 1 and 2 

Start the paragraph with: 

The processing for this is: 

.         If the sender's IP ..  (put the first paragraph in the first item
of a bulleted list) 

.         Else if the sender's IP has been saved (put the second paragraph
in a bulleted list

This will make the text easier to read. 

A few other textual changes in the same paragraph are: 

From: /The RBridge may use different strategies to do so for example, ask an
authoritative entity like directory servers or encapsulate and unicast the
ARP/ND message to the location where it believes the address is in use./

To: /The RBridge may use different strategies to do so.  For example, the
RBridge may ask an authoritative entity such as a directory server or an it
may encapsulate and unicast the ARP/ND location to the location where it
believes the address is in use.