Re: [savi] WGLC: draft-ietf-savi-dhcp-22

"Eric Levy- Abegnoli (elevyabe)" <elevyabe@cisco.com> Thu, 17 April 2014 12:09 UTC

Return-Path: <elevyabe@cisco.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 1CC581A010F for <savi@ietfa.amsl.com>; Thu, 17 Apr 2014 05:09:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.772
X-Spam-Level:
X-Spam-Status: No, score=-14.772 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 duxWtSIA7Dbp for <savi@ietfa.amsl.com>; Thu, 17 Apr 2014 05:09:17 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id ADDB91A0117 for <savi@ietf.org>; Thu, 17 Apr 2014 05:09:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7672; q=dns/txt; s=iport; t=1397736551; x=1398946151; h=from:to:cc:subject:date:message-id:in-reply-to: mime-version; bh=s0709BiIwx+T7+R0FWk6vtLxI2BTECUxNeMuJk9o2nY=; b=XfC5EXERLqfBUjhMXds2ZUN0BVyk3bHPrBsW/MHzXZhZtdelU6OcE/kP Z/NE8AZlC54WDNXa2ks5oLEwec9ykw7JXO08uRWjqk7Ku9I+PacYvmsux 4S0RUcKNDLVwllzbAJpQqk69sBLbFry0IxbJnIw4Ll5332bAShkkSYxKc 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AnoFALzDT1OtJA2H/2dsb2JhbABZgkJEO1e6U4h3gSUWdIIlAQIEbgsSAQgRAwECKCgRFAkIAgQBDQUbh00DEQ3DWQ2GcheMSYIIEQeEOASWfIFugTeLRYVQgzGCKw
X-IronPort-AV: E=Sophos; i="4.97,878,1389744000"; d="scan'208,217"; a="318399750"
Received: from alln-core-2.cisco.com ([173.36.13.135]) by rcdn-iport-2.cisco.com with ESMTP; 17 Apr 2014 12:09:10 +0000
Received: from xhc-rcd-x02.cisco.com (xhc-rcd-x02.cisco.com [173.37.183.76]) by alln-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s3HC9AMh000438 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 17 Apr 2014 12:09:10 GMT
Received: from xmb-rcd-x06.cisco.com ([169.254.6.41]) by xhc-rcd-x02.cisco.com ([173.37.183.76]) with mapi id 14.03.0123.003; Thu, 17 Apr 2014 07:09:10 -0500
From: "Eric Levy- Abegnoli (elevyabe)" <elevyabe@cisco.com>
To: Jean-Michel Combes <jeanmichel.combes@gmail.com>, SAVI Mailing List <savi@ietf.org>
Thread-Topic: [savi] WGLC: draft-ietf-savi-dhcp-22
Thread-Index: AQHPUxN2E7EPfIMXT02EsRAhu//xEJsWOt8A
Date: Thu, 17 Apr 2014 12:09:10 +0000
Message-ID: <CF758A35.38C12%elevyabe@cisco.com>
In-Reply-To: <CAA7e52osoEKeo=EqGF2=PTUrnxC=+8c+GkvF1v4DBQYELYQ6_A@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.3.2.130206
x-originating-ip: [10.49.80.39]
Content-Type: multipart/alternative; boundary="_000_CF758A3538C12elevyabeciscocom_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/savi/yrnOEmSivYVQ3rvJKVhA8tu9C9g
Cc: "<draft-ietf-savi-dhcp@tools.ietf.org>" <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: Thu, 17 Apr 2014 12:09:23 -0000

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.