Re: [savi] WGLC: draft-ietf-savi-dhcp-22
"Guang Yao" <yaoguang@cernet.edu.cn> Tue, 22 April 2014 07:03 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 CD0F41A00CD for <savi@ietfa.amsl.com>; Tue, 22 Apr 2014 00:03:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.171
X-Spam-Level:
X-Spam-Status: No, score=-4.171 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_LETTER=-2, 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 0vGnIRlz4bBV for <savi@ietfa.amsl.com>; Tue, 22 Apr 2014 00:03:11 -0700 (PDT)
Received: from cernet.edu.cn (cernet.edu.cn [202.112.39.2]) by ietfa.amsl.com (Postfix) with ESMTP id BD5331A00D8 for <savi@ietf.org>; Tue, 22 Apr 2014 00:03:10 -0700 (PDT)
Received: from AndrewYaoPC (unknown [166.111.132.217]) by centos (Coremail) with SMTP id AQAAf3DbNgMbFFZTeeECAA--.151S2; Tue, 22 Apr 2014 15:02:51 +0800 (CST)
From: Guang Yao <yaoguang@cernet.edu.cn>
To: 'Leaf Yeh' <leaf.yeh.sdo@gmail.com>, "'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> <53560af5.c3b3440a.7a58.1cfd@mx.google.com> <001601cf5df4$b146bc00$13d43400$@cernet.edu.cn> <53561178.24d9440a.77a0.7bc6@mx.google.com>
In-Reply-To: <53561178.24d9440a.77a0.7bc6@mx.google.com>
Date: Tue, 22 Apr 2014 15:02:53 +0800
Message-ID: <003101cf5df8$e1f69560$a5e3c020$@cernet.edu.cn>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0032_01CF5E3B.F01CBB90"
X-Mailer: Microsoft Outlook 15.0
Thread-Index: AQJ+SCgfdpNGCy/MpS4Q3KK7ONbjpgGWxBw8Al/KbiQBgyP+yQLsKylnmXwxLUA=
Content-Language: zh-cn
X-CM-TRANSID: AQAAf3DbNgMbFFZTeeECAA--.151S2
X-Coremail-Antispam: 1UD129KBjvJXoWxKr4fGF18uw45Ar17tw4ktFb_yoWxGF18pa ykGFW3K34DJw1xuw4kW34Ivw4fZrW0kay7GFn7Jw10ya98WFySyr12k398Xr9rJr4kAa1S qa9F934DZw43ZrJanT9S1TB71UUUUUUqnTZGkaVYY2UrUUUUjbIjqfuFe4nvWSU5nxnvy2 9KBjDU0xBIdaVrnRJUUU9qb7Iv0xC_tr1lb4IE77IF4wAFF20E14v26r1j6r4UM7CY07I2 0VC2zVCF04k26cxKx2IYs7xG6rWj6s0DM7CIcVAFz4kK6r1j6r18M28lY4IEw2IIxxk0rw A2z4x0Y4vE2Ix0cI8IcVAFwI0_JFI_Gr1l84ACjcxK6xIIjxv20xvEc7CjxVAFwI0_Gr0_ Cr1l84ACjcxK6I8E87Iv67AKxVW8Jr0_Cr1UM28EF7xvwVC2z280aVCY1x0267AKxVWxJr 0_GcWle2I262IYc4CY6c8Ij28IcVAaY2xG8wAqx4xG67k08I80eVW5JVWrJwAqx4xG6c80 4VAFz4xC04v7Mc02F40Ew4AK048IF2xKxVWUJVW8JwAqx4xG6xAIxVCFxsxG0wAv7VC2z2 80aVAFwI0_Jr0_Gr1lOx8S6xCaFVCjc4AY6r1j6r4UM4x0Y48IcxkI7VAKI48JM4x0Y48I cxkI7VAKI48G6xCjnVAKz4kxMx8GjcxK6IxK0xIIj40E5I8CrwCY02Avz4vE14v_GF4l42 xK82IYc2Ij64vIr41lx2IqxVAqx4xG67AKxVWUGVWUWwC20s026x8GjcxK67AKxVWUGVWU WwC2zVAF1VAY17CE14v26r126r1DMIIYrxkI7VAKI48JMIIF0xvE2Ix0cI8IcVAFwI0_Jr 0_JF4lIxAIcVC0I7IYx2IY6xkF7I0E14v26r1j6r4UMIIF0xvE42xK8VAvwI8IcIk0rVWr Jr0_WFyUJwCI42IY6I8E87Iv67AKxVWUJVW8JwCI42IY6I8E87Iv6xkF7I0E14v26r4j6r 4UJbIYCTnIWIevJa73UjIFyTuYvjxU2pBTUUUUU
X-CM-SenderInfo: 51drw3xdqjquphuqv3oohg3hdfq/
Archived-At: http://mailarchive.ietf.org/arch/msg/savi/yDWXv-wWsjM_8GSydtoawqym9Bs
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: Tue, 22 Apr 2014 07:03:17 -0000
Well, I didn't read the sentence in RFC6620 you quoted. If considering this sentence, they are equivalent (since non-bound NA will be filtered on Validating port). Thank you for reminding! Guang From: savi [mailto:savi-bounces@ietf.org] On Behalf Of Leaf Yeh Sent: Tuesday, April 22, 2014 2:51 PM To: 'Guang Yao'; '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 Guang - Whenever we use DAD, the messages are not sent to the tentative node. Thus, SAVI-DHCP is actually different from RFC6620. I can't read the difference you mentioned here. :) Section 7.5.1.2 @ https://datatracker.ietf.org/doc/draft-ietf-savi-dhcp/?include_text=1 <quote>The messages MUST NOT be sent to the attachment from which the triggering packet is received.</quote> Section 3.2.3 of RFC6620 @ http://tools.ietf.org/html/rfc6620#section-3.2.3 <quote>The DAD_NS messages are not sent through any of the ports configured as Validating Ports. </quote> Best Regards, Leaf From: Guang Yao [mailto:yaoguang@cernet.edu.cn] Sent: Tuesday, April 22, 2014 2:33 PM To: 'Leaf Yeh'; 'Eric Levy- Abegnoli (elevyabe)'; '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 Leaf and Eric, Maybe there are some misunderstandings... In SAVI-DHCP, as I mentioned in the last letter, we use plain NS rather than DAD NS. Whenever we use DAD, the messages are not sent to the tentative node. Thus, SAVI-DHCP is actually different from RFC6620.Actually, I do think sending DAD NS to the tentative node will cause some problem. Best regards, Guang From: savi [mailto:savi-bounces@ietf.org] On Behalf Of Leaf Yeh Sent: Tuesday, April 22, 2014 2:24 PM To: 'Eric Levy- Abegnoli (elevyabe)'; '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 Eric - 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.). As for IPv6 address, I suppose the switch employs the same process as that described in section 3.2.3 of RFC6620, page 15 @ http://tools.ietf.org/html/rfc6620#section-3.2.3 <quote> 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 <http://tools.ietf.org/html/rfc6620#section-5.4.2> 5.4.2 <http://tools.ietf.org/html/rfc6620#section-5.4.2> of [RFC4862 <http://tools.ietf.org/html/rfc4862> ] for the IPAddr using the following default parameters: DupAddrDetectTransmits set to 2 (i.e., 2 Neighbor Solicitation messages for that address will be sent by the SAVI device) and RetransTimer set to T_WAIT milliseconds (i.e., the time between two Neighbor Solicitation messages is T_WAIT milliseconds). </quote> If you could agreed on the above in RFC6620, I guess you would have no doubt here for the IPv6 address. :) Best Regards, Leaf From: savi [mailto:savi-bounces@ietf.org] On Behalf Of Eric Levy- Abegnoli (elevyabe) 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)