IETF Logo Mail Archive

RE: RFC7084

"Hemant Singh (shemant)" <shemant@cisco.com> Tue, 10 December 2013 13:35 UTC

Return-Path: <shemant@cisco.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 73E2C1AE062 for <ipv6@ietfa.amsl.com>; Tue, 10 Dec 2013 05:35:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.995
X-Spam-Level:
X-Spam-Status: No, score=-7.995 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, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, SUBJ_ALL_CAPS=1.506, USER_IN_DEF_DKIM_WL=-7.5] autolearn=no
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 pMp6JyPW9i39 for <ipv6@ietfa.amsl.com>; Tue, 10 Dec 2013 05:34:58 -0800 (PST)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) by ietfa.amsl.com (Postfix) with ESMTP id A04001ACB4E for <ipv6@ietf.org>; Tue, 10 Dec 2013 05:34:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7484; q=dns/txt; s=iport; t=1386682493; x=1387892093; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=lcXZrLZsi/dEg1BLDhCnvqyGUYnXChlhHrxdhR1cJ84=; b=JRpipvUGXLTgVDIwSOnORU2ElK+bF4o4swqcHmjd1umesZPGP4bIX1Xv 6w4KawwRCiOrnNgL+3R8oEkWuFjzqoEqs3A+HfRTxEANMgWHoppJhfANN 7pyoc5LMVDzd+rA54xj7TIlb7AsldqOdAs/Bg/i2756jZz+ZTEqhxqmhi M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiAFAL8Xp1KtJV2Y/2dsb2JhbABZgkNEOFOCf7YbGIEDFmQQgiUBAQEEIwpMEAIBCA4DBAEBCx0DAgICMBQJCAEBBA4FCId6sR6PXBeOVCYLBgGCbDWBEwSqJ4Mpgio
X-IronPort-AV: E=Sophos;i="4.93,865,1378857600"; d="scan'208,217";a="5668516"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by alln-iport-4.cisco.com with ESMTP; 10 Dec 2013 13:34:53 +0000
Received: from xhc-rcd-x12.cisco.com (xhc-rcd-x12.cisco.com [173.37.183.86]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id rBADYr8X006320 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 10 Dec 2013 13:34:53 GMT
Received: from xmb-rcd-x06.cisco.com ([169.254.6.52]) by xhc-rcd-x12.cisco.com ([173.37.183.86]) with mapi id 14.03.0123.003; Tue, 10 Dec 2013 07:34:53 -0600
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: Erik Kline <ek@google.com>, "STARK, BARBARA H" <bs7652@att.com>
Subject: RE: RFC7084
Thread-Topic: RFC7084
Thread-Index: Ac705Oox+bAOGgDPSBCf3B3p1FF6cAAA4TqgAC3/b4AAAsQaoA==
Date: Tue, 10 Dec 2013 13:34:52 +0000
Message-ID: <75B6FA9F576969419E42BECB86CB1B891154028B@xmb-rcd-x06.cisco.com>
References: <96747494E3D74D41B20907035DB1E48DC7BB@MOPESMBX03.eu.thmulti.com> <2D09D61DDFA73D4C884805CC7865E611303B0269@GAALPA1MSGUSR9L.ITServices.sbc.com> <CAAedzxrNrwz9izxHS22mzZcUnPgQPAAkduuFD7LjE_ypB-4Ehg@mail.gmail.com>
In-Reply-To: <CAAedzxrNrwz9izxHS22mzZcUnPgQPAAkduuFD7LjE_ypB-4Ehg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.86.254.39]
Content-Type: multipart/alternative; boundary="_000_75B6FA9F576969419E42BECB86CB1B891154028Bxmbrcdx06ciscoc_"
MIME-Version: 1.0
Cc: "<ipv6@ietf.org>" <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 13:35:04 -0000

Erik,

From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Erik Kline
Sent: Tuesday, December 10, 2013 1:08 AM
To: STARK, BARBARA H
Cc: <ipv6@ietf.org>
Subject: Re: RFC7084


>Do these networks also support hosts plugging in directly?

Yes.  The host is a standalone CPE router.  The CPE is sitting behind a modem that bridges the RA of the access network to the CPE.  Thus the access network still controls the CPE behavior for DHCPv6 and IA_NA.

>Designing a network where DHCPv6 is a MUST would seem to me to be a violation of the stated node requirements, where it is merely a SHOULD.

DHCPv6 is also required for the CPE to acquire the IA_PD.   RFC 7084 does support the WAN interface being unnumbered (interface has only an IPv6 link-local address) or the WAN uses SLAAC to acquire its global IPv6 address(es).

Hemant

v2.31.3 | Report a Bug | By Email | System Status