Re: [savi] WGLC: draft-ietf-savi-dhcp-22
"Guang Yao" <yaoguang@cernet.edu.cn> Mon, 21 April 2014 02:35 UTC
Return-Path: <yaoguang@cernet.edu.cn>
X-Original-To: savi@ietfa.amsl.com
Delivered-To: savi@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 662331A016D for <savi@ietfa.amsl.com>; Sun, 20 Apr 2014 19:35:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.171
X-Spam-Level:
X-Spam-Status: No, score=-2.171 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.272] 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 kcnPd7h-vEqK for <savi@ietfa.amsl.com>; Sun, 20 Apr 2014 19:35:17 -0700 (PDT)
Received: from cernet.edu.cn (cernet.edu.cn [202.112.39.2]) by ietfa.amsl.com (Postfix) with ESMTP id 44FF71A0173 for <savi@ietf.org>; Sun, 20 Apr 2014 19:35:16 -0700 (PDT)
Received: from AndrewYaoPC (unknown [101.5.139.26]) by centos (Coremail) with SMTP id AQAAf3BL3wTQg1RTWXoCAA--.76S2; Mon, 21 Apr 2014 10:34:56 +0800 (CST)
From: Guang Yao <yaoguang@cernet.edu.cn>
To: "'Eric Levy- Abegnoli (elevyabe)'" <elevyabe@cisco.com>, 'Jean-Michel Combes' <jeanmichel.combes@gmail.com>, 'SAVI Mailing List' <savi@ietf.org>
References: <CAA7e52osoEKeo=EqGF2=PTUrnxC=+8c+GkvF1v4DBQYELYQ6_A@mail.gmail.com> <CF758A35.38C12%elevyabe@cisco.com>
In-Reply-To:
Date: Mon, 21 Apr 2014 10:34:58 +0800
Message-ID: <000e01cf5d0a$4a279d40$de76d7c0$@cernet.edu.cn>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_000F_01CF5D4D.584D2730"
X-Mailer: Microsoft Outlook 15.0
Thread-Index: AQGWxBw8aOCAcInCS57YaewRMqhY0JuMhGCwgAAHJdA=
Content-Language: zh-cn
X-CM-TRANSID: AQAAf3BL3wTQg1RTWXoCAA--.76S2
X-Coremail-Antispam: 1UD129KBjvJXoWxXryUCFWUurWrKF1kJw18Zrb_yoW7Jr1Dpa yDJFW3J34kGw1xW397Xw4xZrZ7urWFkFW2yF1DG3W0y3Z8uFyrtFy2kr1Yvry7Grn3Aa1Y vF4q934kA343Z3DanT9S1TB71UUUUUUqnTZGkaVYY2UrUUUUjbIjqfuFe4nvWSU5nxnvy2 9KBjDU0xBIdaVrnRJUUUB0b7Iv0xC_Kw4lb4IE77IF4wAFF20E14v26r1j6r4UM7CY07I2 0VC2zVCF04k26cxKx2IYs7xG6rWj6s0DM7CIcVAFz4kK6r1j6r18M28lY4IEw2IIxxk0rw A2z4x0Y4vE2Ix0cI8IcVAFwI0_JFI_Gr1l84ACjcxK6xIIjxv20xvEc7CjxVAFwI0_Gr0_ Cr1l84ACjcxK6I8E87Iv67AKxVW8Jr0_Cr1UM28EF7xvwVC2z280aVCY1x0267AKxVW8Jr 0_Cr1UM2AIxVAIcxkEcVAq07x20xvEncxIr21l5I8CrVAYj202j2C_Xr0_Wr1l5I8CrVAq jxCE14ACF2xKxwAqx4xG64kEw2xG04xIwI0_Jr0_Gr1l5I8CrVCF0I0E4I0vr24lYx0E2I x0cI8IcVAFwI0_Jr0_Jr4lYx0Ex4A2jsIE14v26r1j6r4UMcvjeVCFs4IE7xkEbVWUJVW8 JwACjcxG0xvY0x0EwIxGrwACjcxG0xvY0x0EwIxGrVCF72vEw4AK0wCjr7xvwVCIw2I0I7 xG6c02F41l42xK82IYc2Ij64vIr41lx2IqxVAqx4xG67AKxVWUGVWUWwC20s026x8GjcxK 67AKxVWUGVWUWwC2zVAF1VAY17CE14v26r126r1DMIIYrxkI7VAKI48JMIIF0xvE2Ix0cI 8IcVAFwI0_Jr0_JF4lIxAIcVC0I7IYx2IY6xkF7I0E14v26r1j6r4UMIIF0xvE42xK8VAv wI8IcIk0rVWrJr0_WFyUJwCI42IY6I8E87Iv67AKxVWUJVW8JwCI42IY6I8E87Iv6xkF7I 0E14v26r4j6r4UJbIYCTnIWIevJa73UjIFyTuYvjxUgWxRDUUUU
X-CM-SenderInfo: 51drw3xdqjquphuqv3oohg3hdfq/
Archived-At: http://mailarchive.ietf.org/arch/msg/savi/w-nP7JGvWrVtC8mkbPCaxIRa5G0
X-Mailman-Approved-At: Tue, 22 Apr 2014 02:46:15 -0700
Cc: draft-ietf-savi-dhcp@tools.ietf.org, 'Ted Lemon' <mellon@fugue.com>
Subject: Re: [savi] WGLC: draft-ietf-savi-dhcp-22
X-BeenThere: savi@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mailing list for the SAVI working group at IETF <savi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/savi>, <mailto:savi-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/savi/>
List-Post: <mailto:savi@ietf.org>
List-Help: <mailto:savi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/savi>, <mailto:savi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Apr 2014 02:35:21 -0000
Hi, Eric Before we begin modifying the SAVI-DHCP, we find some related text in RFC6620: 1. " MLD Considerations The FCFS SAVI device MUST join the solicited node multicast group for all the addresses with a state other than NO_BIND. This is needed to make sure that the FCFS SAVI device will receive the DAD_NS for those addresses. Please note that it may not be enough to rely on the host behind the Validating Port to do so, since the node may move, and after a while, the packets for that particular solicited node multicast group will no longer be forwarded to the FCFS SAVI device. Therefore, the FCFS SAVI device MUST join the solicited node multicast groups for all the addresses that are in a state other than NO_BIND. " 2. "Upon the reception through a Validating Port (VP) of a DATA packet containing IPAddr as the source address, the SAVI device SHOULD execute the process of sending Neighbor Solicitation messages of the Duplicate Address Detection process as described in Section 5.4.2 of [RFC4862] " Maybe such designs also violate your comments? Thank you very much! Best regards, Guang From: Guang Yao [mailto:yaoguang@cernet.edu.cn] Sent: Monday, April 21, 2014 10:20 AM To: 'Eric Levy- Abegnoli (elevyabe)'; 'Jean-Michel Combes'; 'SAVI Mailing List' Cc: '<draft-ietf-savi-dhcp@tools.ietf.org>'; 'Ted Lemon' Subject: RE: [savi] WGLC: draft-ietf-savi-dhcp-22 Hi, Eric Thank you very much for the comments! 1. For the first one, considering the whole "data snooping process" is actually a "conditional should"(s7.1), the DHCP lease query process is actually no more than a "conditional should". The "MUST" just specifies if the data snooping process is to be implemented, the lease query process will be a MUST. Besides, it seems there is no good alternative method to set up bindings without DHCP lease query; however, if DHCP lease query cannot be performed, the whole data snooping process is meaningless. Thus, we choose "MUST" on DHCP lease query process. 2. We fully accept the second comment and will revise the doc accordingly. Best regards, Guang From: Eric Levy- Abegnoli (elevyabe) [mailto:elevyabe@cisco.com] Sent: Thursday, April 17, 2014 8:09 PM To: Jean-Michel Combes; SAVI Mailing List Cc: <draft-ietf-savi-dhcp@tools.ietf.org <mailto:draft-ietf-savi-dhcp@tools.ietf.org> >; Ted Lemon Subject: Re: [savi] WGLC: draft-ietf-savi-dhcp-22 Hi, In general, the document looks good. I spot a few substantial issues listed below: 1) There seem to be a requirement in several places of the document (see below) to send LEASEQUERY to the DHCP server. That is certainly useful to do so, but switches are sometimes pure layer-2 switches, and don't implement a DHCP stack not they have a layer-3 address to source traffic from. Even when the switches have a layer-3 leg, setting then to reach out the DHCP server is not a trivial operation, and not one which is typically done on layer-2 access switches. Whenever the LEASEQUERY is mandated, I'd rather have it as a SHOULD, with some alternate behavior (delete the entry for instance). Section 6.4.2.2, paragrap 2.1: the SAVI device MUST send a LEASEQUERY [RFC5007] Section 7.5.2.1 IPv4 address: Send a DHCPLEASEQUERY [RFC4388] IPv6 address: Send a LEASEQUERY [RFC5007] 2) Section 7.1 & 7.2 "To perform this process, the SAVI device MUST join the Solicited Node Multicast group of the source address of triggering IPv6 data packet whenever performing duplicate detection." * I don't think a layer-2 switch can and need to join the Solicited Node Multicast group of the source address. It does not have a layer-3 stack on top of every link it is bridging/switching. It has to snoop ND traffic, like it snoops DHCP traffic. Section 7.5.1.2 * I wonder what would be the end-result if the switch send a DAD or and ARP and the legitimate owner interpret it as "someone already has the address" (always possible depending on its current state). That would seriously break DAD or ACD (rfc5227). I think we need a way to distinguish between the packets issued by the switch and normal DAD or ACD packets. (some field in the header? But that would be a protocol change.). Eric From: Jean-Michel Combes <jeanmichel.combes@gmail.com <mailto:jeanmichel.combes@gmail.com> > Date: mardi 8 avril 2014 12:15 To: SAVI Mailing List <savi@ietf.org <mailto:savi@ietf.org> > Cc: "<draft-ietf-savi-dhcp@tools.ietf.org <mailto:draft-ietf-savi-dhcp@tools.ietf.org> >" <draft-ietf-savi-dhcp@tools.ietf.org <mailto:draft-ietf-savi-dhcp@tools.ietf.org> >, Ted Lemon <mellon@fugue.com <mailto:mellon@fugue.com> > Subject: [savi] WGLC: draft-ietf-savi-dhcp-22 Folks, As it has been deeply modified since the last WGLC (version -06), this is a new two weeks WGLC for the following document: "SAVI Solution for DHCP" (http://tools.ietf.org/html/draft-ietf-savi-dhcp-22). Please, don't hesitate to give your opinion (i.e., agreement/disagreement to move forward the document, comments, etc.)! Thanks in advance. Best regards, JMC.
- [savi] WGLC: draft-ietf-savi-dhcp-22 Jean-Michel Combes
- Re: [savi] WGLC: draft-ietf-savi-dhcp-22 Jean-Michel Combes
- Re: [savi] WGLC: draft-ietf-savi-dhcp-22 Eric Levy- Abegnoli (elevyabe)
- Re: [savi] WGLC: draft-ietf-savi-dhcp-22 Guang Yao
- Re: [savi] WGLC: draft-ietf-savi-dhcp-22 Leaf Yeh
- Re: [savi] WGLC: draft-ietf-savi-dhcp-22 Guang Yao
- Re: [savi] WGLC: draft-ietf-savi-dhcp-22 Leaf Yeh
- Re: [savi] WGLC: draft-ietf-savi-dhcp-22 Guang Yao
- Re: [savi] WGLC: draft-ietf-savi-dhcp-22 Eric Levy- Abegnoli (elevyabe)
- Re: [savi] WGLC: draft-ietf-savi-dhcp-22 Guang Yao
- Re: [savi] WGLC: draft-ietf-savi-dhcp-22 Guang Yao
- Re: [savi] WGLC: draft-ietf-savi-dhcp-22 Guang Yao
- Re: [savi] WGLC: draft-ietf-savi-dhcp-22 Ted Lemon
- Re: [savi] WGLC: draft-ietf-savi-dhcp-22 Ted Lemon
- Re: [savi] WGLC: draft-ietf-savi-dhcp-22 Pascal Thubert (pthubert)
- Re: [savi] WGLC: draft-ietf-savi-dhcp-22 Eric Levy- Abegnoli (elevyabe)
- Re: [savi] WGLC: draft-ietf-savi-dhcp-22 Eric Levy- Abegnoli (elevyabe)
- Re: [savi] WGLC: draft-ietf-savi-dhcp-22 Ted Lemon
- Re: [savi] WGLC: draft-ietf-savi-dhcp-22 Eric Levy- Abegnoli (elevyabe)
- Re: [savi] WGLC: draft-ietf-savi-dhcp-22 Leaf Yeh
- Re: [savi] WGLC: draft-ietf-savi-dhcp-22 Leaf Yeh
- Re: [savi] WGLC: draft-ietf-savi-dhcp-22 Ted Lemon
- Re: [savi] WGLC: draft-ietf-savi-dhcp-22 Guang Yao
- Re: [savi] WGLC: draft-ietf-savi-dhcp-22 Pascal Thubert (pthubert)
- Re: [savi] WGLC: draft-ietf-savi-dhcp-22 Guang Yao
- Re: [savi] WGLC: draft-ietf-savi-dhcp-22 Jun Bi
- Re: [savi] WGLC: draft-ietf-savi-dhcp-22 Guang Yao
- Re: [savi] WGLC: draft-ietf-savi-dhcp-22 Ted Lemon
- Re: [savi] WGLC: draft-ietf-savi-dhcp-22 Jun Bi
- Re: [savi] WGLC: draft-ietf-savi-dhcp-22 Fred Baker (fred)
- Re: [savi] WGLC: draft-ietf-savi-dhcp-22 Fred Baker (fred)