IETF Logo Mail Archive

Re: [v6ops] DAD again [was: draft-ietf-v6ops-host-addr-availability discussion]

"Templin, Fred L" <Fred.L.Templin@boeing.com> Mon, 16 November 2015 20:04 UTC

Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 789701A8949 for <v6ops@ietfa.amsl.com>; Mon, 16 Nov 2015 12:04:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.786
X-Spam-Level:
X-Spam-Status: No, score=-4.786 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.585, 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 qEOlwK6HYs1k for <v6ops@ietfa.amsl.com>; Mon, 16 Nov 2015 12:04:52 -0800 (PST)
Received: from blv-mbsout-01.boeing.com (blv-mbsout-01.boeing.com [130.76.32.231]) (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 372031A8948 for <v6ops@ietf.org>; Mon, 16 Nov 2015 12:04:52 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by blv-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id tAGK4s2u030761; Mon, 16 Nov 2015 12:04:54 -0800
Received: from XCH-PHX-513.sw.nos.boeing.com (xch-phx-513.sw.nos.boeing.com [10.57.37.30]) by blv-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id tAGK4nmq030727 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Mon, 16 Nov 2015 12:04:49 -0800
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.189]) by XCH-PHX-513.sw.nos.boeing.com ([169.254.13.120]) with mapi id 14.03.0235.001; Mon, 16 Nov 2015 12:04:45 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Hemant Singh (shemant)" <shemant@cisco.com>, "Mukom Akong T." <mukom.tamon@gmail.com>
Thread-Topic: [v6ops] DAD again [was: draft-ietf-v6ops-host-addr-availability discussion]
Thread-Index: AQHRFogofPNeczqv2U2vJopouDkBSJ6LeFYwgAa8AYCAAeLTIIAJg1aAgAFM4PCAAMIOAP//e67w
Date: Mon, 16 Nov 2015 20:04:44 +0000
Message-ID: <2134F8430051B64F815C691A62D9831832F4D137@XCH-BLV-504.nw.nos.boeing.com>
References: <8D175A1F-B1AE-44B4-838E-1C853B6C937D@cisco.com> <2134F8430051B64F815C691A62D9831832F391A7@XCH-BLV-504.nw.nos.boeing.com> <CAKD1Yr15C-uoxUw0kgWO-d=LmUK8qWGLS7vt+22W+k8xXtDY+g@mail.gmail.com> <2134F8430051B64F815C691A62D9831832F393F1@XCH-BLV-504.nw.nos.boeing.com> <2134F8430051B64F815C691A62D9831832F3941D@XCH-BLV-504.nw.nos.boeing.com> <563811DF.9020603@gmail.com> <2134F8430051B64F815C691A62D9831832F394F7@XCH-BLV-504.nw.nos.boeing.com> <563821EB.3040508@gmail.com> <2134F8430051B64F815C691A62D9831832F39A09@XCH-BLV-504.nw.nos.boeing.com> <56392B6D.8030703@gmail.com> <2134F8430051B64F815C691A62D9831832F3A88F@XCH-BLV-504.nw.nos.boeing.com> <2134F8430051B64F815C691A62D9831832F3A97F@XCH-BLV-504.nw.nos.boeing.com> <CAHDzDLBG8xZxUFsAuN-7WuruZcULF1QAS_ch=gD5rGQMZfskow@mail.gmail.com> <2134F8430051B64F815C691A62D9831832F3E8B0@XCH-BLV-504.nw.nos.boeing.com> <831e60e2122547bc8bdf167e76f664c9@XCH-RTP-005.cisco.com> <2134F8430051B64F815C691A62D9831832F4CE72@XCH-BLV-504.nw.nos.boeing.com> <e7bcbba7047f44aba6a355da51f3265b@XCH-RTP-005.cisco.com>
In-Reply-To: <e7bcbba7047f44aba6a355da51f3265b@XCH-RTP-005.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/FRrRi5BmbG-tAm7ziah9C2EAHcY>
Cc: "v6ops@ietf.org" <v6ops@ietf.org>
Subject: Re: [v6ops] DAD again [was: draft-ietf-v6ops-host-addr-availability discussion]
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Nov 2015 20:04:53 -0000

Hi Hemant,

> -----Original Message-----
> From: Hemant Singh (shemant) [mailto:shemant@cisco.com]
> Sent: Monday, November 16, 2015 11:52 AM
> To: Templin, Fred L; Mukom Akong T.
> Cc: v6ops@ietf.org
> Subject: RE: [v6ops] DAD again [was: draft-ietf-v6ops-host-addr-availability discussion]
> 
> Fred,
> 
> -----Original Message-----
> From: Templin, Fred L [mailto:Fred.L.Templin@boeing.com]
> Sent: Monday, November 16, 2015 11:42 AM
> To: Hemant Singh (shemant); Mukom Akong T.
> Cc: v6ops@ietf.org
> Subject: RE: [v6ops] DAD again [was: draft-ietf-v6ops-host-addr-availability discussion]
> 
> >- Node N receives a /64 prefix delegation for prefix P over interface eth0.
> >- N assigns P to the lo interface as a /64 route. This is done to black-hole
> >   unused portions of P.
> >- N configures address A from prefix P, and assigns it to eth0.
> 
> If A from prefix P is assigned to eth0, we have violated rfc3633 which says to not assign any IPv6 address on the port on which the
> node received the PD from.  Did I miss anything?

Section 12.1 of RFC3633 says:

   "the requesting router MUST
   NOT assign any delegated prefixes or subnets from the delegated
   prefix(es) to the link through which it received the DHCP message
   from the delegating router."

and what I am suggesting agrees with this requirement. I am talking
about assigning *addresses* (not prefixes or subnets), and the
document does not say that an address cannot be assigned to the
link through which the DHCP message was received.

Thanks - Fred
fred.l.templin@boeing.com

> Hemant
>

v2.23.0 | Report a Bug | By Email