RE: RFC7084

Wuyts Carl <Carl.Wuyts@technicolor.com> Tue, 10 December 2013 15:06 UTC

Return-Path: <Carl.Wuyts@technicolor.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 31ACD1AE109 for <ipv6@ietfa.amsl.com>; Tue, 10 Dec 2013 07:06:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.695
X-Spam-Level:
X-Spam-Status: No, score=-2.695 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, SUBJ_ALL_CAPS=1.506] 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 TPQ9zNZLmEAh for <ipv6@ietfa.amsl.com>; Tue, 10 Dec 2013 07:06:30 -0800 (PST)
Received: from na3sys009aog131.obsmtp.com (na3sys009aog131.obsmtp.com [74.125.149.247]) by ietfa.amsl.com (Postfix) with ESMTP id 735541A1F5D for <ipv6@ietf.org>; Tue, 10 Dec 2013 07:06:13 -0800 (PST)
Received: from MOPESEDGE01.eu.thmulti.com ([129.35.174.203]) (using TLSv1) by na3sys009aob131.postini.com ([74.125.148.12]) with SMTP ID DSNKUqct4Ers7YNSlhEHNvuZ6SFLkDoWM+AB@postini.com; Tue, 10 Dec 2013 07:06:25 PST
Received: from MOPESMAILHTC03.eu.thmulti.com (141.11.100.179) by mail3.technicolor.com (141.11.253.22) with Microsoft SMTP Server (TLS) id 8.3.298.1; Tue, 10 Dec 2013 16:01:24 +0100
Received: from MOPESMBX03.eu.thmulti.com ([169.254.2.32]) by MOPESMAILHTC03.eu.thmulti.com ([141.11.100.179]) with mapi id 14.03.0158.001; Tue, 10 Dec 2013 16:01:27 +0100
From: Wuyts Carl <Carl.Wuyts@technicolor.com>
To: Ole Troan <otroan@employees.org>
Subject: RE: RFC7084
Thread-Topic: RFC7084
Thread-Index: Ac705Oox+bAOGgDPSBCf3B3p1FF6cAAA4TqgACKmQYD///b6gP//7wHQgACJbgD//+7BAIAAEyMA///u8lAAAzNdAP//7pLg
Date: Tue, 10 Dec 2013 15:01:26 +0000
Message-ID: <96747494E3D74D41B20907035DB1E48DD1ED@MOPESMBX03.eu.thmulti.com>
References: <96747494E3D74D41B20907035DB1E48DC7BB@MOPESMBX03.eu.thmulti.com> <2D09D61DDFA73D4C884805CC7865E611303B0269@GAALPA1MSGUSR9L.ITServices.sbc.com> <96747494E3D74D41B20907035DB1E48DCD72@MOPESMBX03.eu.thmulti.com> <alpine.DEB.2.02.1312100803370.24602@uplift.swm.pp.se> <96747494E3D74D41B20907035DB1E48DCE42@MOPESMBX03.eu.thmulti.com> <52A7236A.30605@viagenie.ca> <96747494E3D74D41B20907035DB1E48DD168@MOPESMBX03.eu.thmulti.com> <52A72500.6020009@viagenie.ca> <96747494E3D74D41B20907035DB1E48DD181@MOPESMBX03.eu.thmulti.com> <B83C25D3-59EB-4BD3-AFEB-F2D9A2508B67@employees.org>
In-Reply-To: <B83C25D3-59EB-4BD3-AFEB-F2D9A2508B67@employees.org>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [141.11.249.10]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Dec 2013 15:06:32 -0000

Agree, but it does not mandate ia_na, does it ?


-----Original Message-----
From: Ole Troan [mailto:otroan@employees.org] 
Sent: dinsdag 10 december 2013 15:59
To: Wuyts Carl
Cc: Simon Perreault; 6man WG
Subject: Re: RFC7084

Carl,

> M=1 equals Managed flag = request ia_na or/and ia_pd.
> Please note a router is also acting as host.

that is wrong. the M-flag does not give a hint about prefix delegation.
the M flag is a hint from the network that stateful address assignment might be available.

cheers,
Ole

> -----Original Message-----
> From: Simon Perreault [mailto:simon.perreault@viagenie.ca] 
> Sent: dinsdag 10 december 2013 15:28
> To: Wuyts Carl; ipv6@ietf.org
> Subject: Re: RFC7084
> 
> Le 2013-12-10 09:25, Wuyts Carl a écrit :
>> M=1 should not be equal to force request ia_na.
> 
> What should M=1 mean then?
> 
>> what's the purpose of having separate options (ia_na and ia_pd)  if you're going to request both of them anyway ?
> 
> The answer to that seems simple to me: an end host would never request IA_PD. Only routers would.
> 
> Simon
> --
> DTN made easy, lean, and smart --> http://postellation.viagenie.ca
> NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
> STUN/TURN server               --> http://numb.viagenie.ca
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------