IETF Logo Mail Archive

[dhcwg] Question on relay agent behavior in DHCPv6 prefix delegation

"Templin, Fred L" <Fred.L.Templin@boeing.com> Mon, 03 February 2014 16:49 UTC

Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC3C61A01AD for <dhcwg@ietfa.amsl.com>; Mon, 3 Feb 2014 08:49:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.837
X-Spam-Level:
X-Spam-Status: No, score=-2.837 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.535, 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 3V8hgiDp2uko for <dhcwg@ietfa.amsl.com>; Mon, 3 Feb 2014 08:49:25 -0800 (PST)
Received: from slb-mbsout-01.boeing.com (slb-mbsout-01.boeing.com [130.76.64.128]) by ietfa.amsl.com (Postfix) with ESMTP id ACA121A0165 for <dhcwg@ietf.org>; Mon, 3 Feb 2014 08:49:25 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by slb-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id s13GnPjw006847; Mon, 3 Feb 2014 08:49:25 -0800
Received: from XCH-PHX-109.sw.nos.boeing.com (xch-phx-109.sw.nos.boeing.com [130.247.25.36]) by slb-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id s13GnKU4006756 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK) for <dhcwg@ietf.org>; Mon, 3 Feb 2014 08:49:20 -0800
Received: from XCH-BLV-403.nw.nos.boeing.com (2002:82f7:193e::82f7:193e) by XCH-PHX-109.sw.nos.boeing.com (2002:82f7:1924::82f7:1924) with Microsoft SMTP Server (TLS) id 14.3.174.1; Mon, 3 Feb 2014 08:49:19 -0800
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.102]) by XCH-BLV-403.nw.nos.boeing.com ([169.254.3.123]) with mapi id 14.03.0174.001; Mon, 3 Feb 2014 08:49:19 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "dhcwg@ietf.org WG" <dhcwg@ietf.org>
Thread-Topic: Question on relay agent behavior in DHCPv6 prefix delegation
Thread-Index: Ac8g/+FYRMW3CqBVRFqGSM7aZaq32Q==
Date: Mon, 03 Feb 2014 16:49:19 +0000
Message-ID: <2134F8430051B64F815C691A62D983181C095B@XCH-BLV-504.nw.nos.boeing.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
Subject: [dhcwg] Question on relay agent behavior in DHCPv6 prefix delegation
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Feb 2014 16:49:27 -0000

Hi, RFC3633 says:

"14.  Relay agent behavior

   A relay agent forwards messages containing Prefix Delegation options
   in the same way as described in section 20, "Relay Agent Behavior" of
   RFC 3315.

   If a delegating router communicates with a requesting router through
   a relay agent, the delegating router may need a protocol or other
   out-of-band communication to add routing information for delegated
   prefixes into the provider edge router."

My question is, since the publication of RFC3633 has there been a
new RFC published that specifies "a protocol or other out-of-band
communication to add routing information"?

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

v2.23.0 | Report a Bug | By Email