[dhcwg] RE: SLPv2 DHCPv6 options (was: additional option for dhcpv6)
Richard Barr Hibbs <rbhibbs@pacbell.net> Mon, 04 February 2002 06:02 UTC
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA06364 for <dhcwg-archive@odin.ietf.org>; Mon, 4 Feb 2002 01:02:53 -0500 (EST)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id BAA29489 for dhcwg-archive@odin.ietf.org; Mon, 4 Feb 2002 01:02:54 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA28834; Mon, 4 Feb 2002 00:53:42 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA28816 for <dhcwg@optimus.ietf.org>; Mon, 4 Feb 2002 00:53:41 -0500 (EST)
Received: from mta6.snfc21.pbi.net (mta6.snfc21.pbi.net [206.13.28.240]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA06275 for <dhcwg@ietf.org>; Mon, 4 Feb 2002 00:53:39 -0500 (EST)
Received: from BarrH63p601 ([64.170.117.6]) by mta6.snfc21.pbi.net (iPlanet Messaging Server 5.1 (built May 7 2001)) with SMTP id <0GQZ003YEV1G82@mta6.snfc21.pbi.net> for dhcwg@ietf.org; Sun, 03 Feb 2002 21:53:40 -0800 (PST)
Date: Sun, 03 Feb 2002 21:52:43 -0800
From: Richard Barr Hibbs <rbhibbs@pacbell.net>
In-reply-to: <Pine.SOL.3.96.1020128183549.2579h-100000@qwer>
To: Erik Guttman <Erik.Guttman@Sun.COM>
Cc: dhcwg@ietf.org
Reply-to: rbhibbs@pacbell.net
Message-id: <JCELKJCFMDGAKJCIGGPNAEOMDJAA.rbhibbs@pacbell.net>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Content-type: text/plain; charset="us-ascii"
Content-transfer-encoding: 7bit
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
Content-Transfer-Encoding: 7bit
Subject: [dhcwg] RE: SLPv2 DHCPv6 options (was: additional option for dhcpv6)
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: <dhcwg.ietf.org>
X-BeenThere: dhcwg@ietf.org
Content-Transfer-Encoding: 7bit
Erik-- Thanks for the clarification! --Barr > -----Original Message----- > From: Erik Guttman > Sent: Monday, January 28, 2002 09:54 > > I can briefly clarify the SLP DHC options. These are being > revised from RFC 2610 in draft-guttman-svrloc-rfc2610bis-01.txt > I will add text to specify DHCPv6 options in the next revision. > [Snip!] > > Please note that it is possible for the DA option to be sent > without sending the SLP scope option. When an SLP agent is > configured with the DA option, it will request a SLPv2 DAAdvert > from the DA whose address is listed, in order to obtain information > about the DA, including which scopes the DA is configured with. > This is described in detail in draft-guttman-svrloc-rfc2608bis-02.txt > > The analogy to v4 option 78, SLP Directory Agent Option, will be > > 0 1 2 3 > 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | OPTION_SLPDA | option-len | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | | > | | > | DA Address #1 | > | | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > . . . . > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | | > | | > | DA Address #N | > | | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > > One or more DA addresses are supplied. The minimum length of the > option will be 36 bytes. The interpretation of this is field is > exactly the same as for option 78, except that it is used to > configure a SLP v2 agent with the IPv6 address of a SLPv2 DA. > [Snip!] > > Only one SLP Service Scope Option is sent to configure an SLP > agent. > > The analogy to v4 option 79, SLP Service Scope Option, will be > > 0 1 2 3 > 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | OPTION_SLPSCOPES | option-len | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | <Scope List> ... > +-------------------- > > This option includes zero or more bytes of UTF-8 string. Its > minimum length is 4 bytes. The interpretation of this field > is exactly as per DHCP option 79. > > I have no doubt that these options will eventually assigned > DHCPv6 option IDs as the rfc2610bis document proceeds. > _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg
- [dhcwg] additional option for dhcpv6 Vijay Bhaskar A K
- Re: [dhcwg] additional option for dhcpv6 Ted Lemon
- Re: [dhcwg] additional option for dhcpv6 Mark Stapp
- RE: [dhcwg] additional option for dhcpv6 Bernie Volz (EUD)
- Re: [dhcwg] additional option for dhcpv6 Vijay Bhaskar A K
- RE: [dhcwg] additional option for dhcpv6 Bernie Volz (EUD)
- RE: [dhcwg] additional option for dhcpv6 Vijayabhaskar A K
- RE: [dhcwg] additional option for dhcpv6 Jim Bound
- RE: [dhcwg] additional option for dhcpv6 Jim Bound
- RE: [dhcwg] additional option for dhcpv6 Bernie Volz (EUD)
- Re: [dhcwg] additional option for dhcpv6 Mark Stapp
- RE: [dhcwg] additional option for dhcpv6 Terrance Humphries
- Re: [dhcwg] additional option for dhcpv6 Vijay Bhaskar A K
- RE: [dhcwg] additional option for dhcpv6 Richard Barr Hibbs
- [dhcwg] SLPv2 DHCPv6 options (was: additional opt… Erik Guttman
- [dhcwg] RE: SLPv2 DHCPv6 options (was: additional… Richard Barr Hibbs