Re: [savi] WGLC: draft-ietf-savi-dhcp-22
"Leaf Yeh" <leaf.yeh.sdo@gmail.com> Tue, 22 April 2014 06:24 UTC
Return-Path: <leaf.yeh.sdo@gmail.com>
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 7C4FA1A00A5 for <savi@ietfa.amsl.com>; Mon, 21 Apr 2014 23:24:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] 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 QUsFMBa_q_vM for <savi@ietfa.amsl.com>; Mon, 21 Apr 2014 23:23:55 -0700 (PDT)
Received: from mail-pb0-x233.google.com (mail-pb0-x233.google.com [IPv6:2607:f8b0:400e:c01::233]) by ietfa.amsl.com (Postfix) with ESMTP id 6170D1A0089 for <savi@ietf.org>; Mon, 21 Apr 2014 23:23:55 -0700 (PDT)
Received: by mail-pb0-f51.google.com with SMTP id uo5so4540141pbc.24 for <savi@ietf.org>; Mon, 21 Apr 2014 23:23:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type:thread-index:content-language; bh=sFMMKXUskiz5eW2JcTp7XCv4sh6Otae0+7U7FIAJn0w=; b=uC+lNLKFv2/RexifGxlthqMb0eyO4RnrqZJyiPr1jDGJ54HR8uvz1tdwAl1LNgohVo l8iM38yayQJBQfOZmKXJBFn+PSgjTqnXGRzgEFcd5beifPDZpWVFiJBrcuDdSaOOtdWm AEPrGi5GHHkCfbVWeKZzRYe3FjJiDghZH/oeZKPcjyvR9ftWwcyXTUfGyVANQDTv8ylJ o6v8Bh+OvoLtjiMEoMs7wPfYuE5FmeFnmq+NQKcpqoTQ3I9u430LNJYI4XFjwaWGll3f YFF+eLI55a75tVRoZKBwbJqzGYtnqFlNpHbpmK/xrczKbgHtWD5giCK5zZz+cd0QQYGS oZTw==
X-Received: by 10.66.177.168 with SMTP id cr8mr7518451pac.128.1398147830237; Mon, 21 Apr 2014 23:23:50 -0700 (PDT)
Received: from PC ([218.241.103.137]) by mx.google.com with ESMTPSA id di3sm54674688pbc.11.2014.04.21.23.23.47 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Mon, 21 Apr 2014 23:23:49 -0700 (PDT)
From: Leaf Yeh <leaf.yeh.sdo@gmail.com>
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: <CF758A35.38C12%elevyabe@cisco.com>
Date: Tue, 22 Apr 2014 14:23:44 +0800
Message-ID: <53560af5.c3b3440a.7a58.1cfd@mx.google.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_001F_01CF5E36.7A34F690"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AQHPUxN2E7EPfIMXT02EsRAhu//xEJsWOt8AgAb/rjA=
Content-Language: zh-cn
Archived-At: http://mailarchive.ietf.org/arch/msg/savi/GHUkZ7HtxrBJMZ5E73fWvHBTLpM
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 06:24:01 -0000
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. J 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>; 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> Date: mardi 8 avril 2014 12:15 To: SAVI Mailing List <savi@ietf.org> Cc: "<draft-ietf-savi-dhcp@tools.ietf.org>" <draft-ietf-savi-dhcp@tools.ietf.org>, Ted Lemon <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)