Re: [Dhcpv6bis] a primary list of possible RFCs/drafts to merge

[Sheng Jiang <[e-mail]>]

Hi, Bernie,

Your reply is exactly what I expected. We could not take that much into one single document. That's why I call it primary list, which is just a kick off for us to figure out the real incorporating work.

Could you comment on one more document: RFC 6603 (update RFC3633) Prefix Exclude Option for DHCPv6-based Prefix Delegation?

Best regards,

Sheng

>-----Original Message-----
>From: Dhcpv6bis [mailto:[e-mail]] On Behalf Of Bernie
>Volz (volz)
>Sent: Thursday, December 12, 2013 12:47 PM
>To: Sheng Jiang; [e-mail]
>Subject: Re: [Dhcpv6bis] a primary list of possible RFCs/drafts to merge
>
>Thanks Sheng for the list. We will need to look over these in more detail,
>but ...
>
>IMHO ...
>
>We will NOT be doing most of these. In some cases, we may just add basic
>information and a reference (such as for DUID-UUID).
>
>I do think SOLMAX (RFC 7083) and Reconfigure REBIND (RFC 6644) are
>probably worth incorporating.
>
>(As I mentioned on the call) I did email Ralph about RFC 3736 and he agreed
>with me (as we had talked about it a while back) that a section on what's
>needed for a minimal DHCPv6 service ('other configuration' only). I attached
>that email from Ralph as it wasn't to the full group.
>
>RFC 6221 is an interesting question and that one needs review and some
>thought.
>
>RFC 6422, at least taking a quick look, I think was mislabeled as updates 3315
>(though there is some subtle change in server processing). But I think this
>stands on its own.
>
>RFC 4361 was another I think was incorrectly labeled as updates 3315 - what
>in it updates 3315? And similar for RFC 5494.
>
>Those that really update RFC 3315 will require some additional review to see
>what they change and whether to add some basic information and reference
>the document or whether to incorporate more of the changes.
>
>Simple option RFCs will be left as is and not included.
>
>---
>
>We will need to think about how to handle 'documenting' our conclusions on
>these? Do we want to create issues for each or groups of documents (i.e.,
>one for all the simple options that we are not including)? And perhaps a
>separate issue for those that specifically update 3315 so we can discuss and
>document our decision?
>
>- Bernie
>
>-----Original Message-----
>From: Dhcpv6bis [mailto:[e-mail]] On Behalf Of Sheng
>Jiang
>Sent: Wednesday, December 11, 2013 10:04 PM
>To: [e-mail]
>Subject: Re: [Dhcpv6bis] a primary list of possible RFCs/drafts to merge
>
>Oops... The text become unreadable after sent out though outlook email
>editor. Please see the attached two txt documents. Also resent the roughly
>filtered list here. There are 6 document officially "update" RFC3315.
>
>Rough filtered List
>
>RFC 3736 Stateless DHCPv6 Service
>
>RFC 4580 DHCPv6 Relay Agent Subscriber-ID Option
>
>RFC 4649 DHCPv6 Relay Agent Remote-ID Option
>
>RFC 4994 DHCPv6 Relay Agent Echo Request Option
>
>RFC 5007 DHCPv6 Leasequery
>
>RFC 5460 DHCPv6 Bulk Leasequery
>
>RFC 6221 (update RFC3315) Lightweight DHCPv6 Relay Agent
>
>RFC 6355 Definition of the UUID-Based DHCPv6 Unique Identifier
>(DUID-UUID)
>
>RFC 6422 (update RFC3315) Relay-Supplied DHCP Options
>
>RFC 6603 Prefix Exclude Option for DHCPv6-based Prefix Delegation
>
>RFC 6644 (update RFC3315) Rebind Capability in DHCPv6 Reconfigure
>Messages
>
>RFC 6939 Client Link-Layer Address Option in DHCPv6
>
>RFC 6977 Triggering DHCPv6 Reconfiguration from Relay Agents
>
>RFC 7083 (update RFC3315) Modification to Default Values of SOL_MAX_RT
>and INF_MAX_RT
>
>
>Another two documents that updated RFC3315
>
>RFC 4361 Node-specific Client Identifiers for DHCPv4
>
>RFC 5494 IANA Allocation Guidelines for the Address Resolution Protocol
>(ARP)
>
>Regards,
>
>Sheng
>
>>-----Original Message-----
>>From: Dhcpv6bis [mailto:[e-mail]] On Behalf Of Sheng
>>Jiang
>>Sent: Thursday, December 12, 2013 10:49 AM
>>To: [e-mail]
>>Subject: [Dhcpv6bis] a primary list of possible RFCs/drafts to merge
>>
>>Hi, all,
>>
>>The below is a primary list of possible RFCs/drafts to merge, also
>>available in attached txt. We should discuss them. For most of service
>>configuration options, it may be easy to filter them out. In a quick
>>glance, there are at least a few worthy out discussion.
>>
>>RFC 3736 Stateless DHCPv6 Service
>>RFC 4580 DHCPv6 Relay Agent Subscriber-ID Option RFC 4649 DHCPv6 Relay
>>Agent Remote-ID Option RFC 4994 DHCPv6 Relay Agent Echo Request
>Option
>>RFC 5007 DHCPv6 Leasequery RFC 5460 DHCPv6 Bulk Leasequery RFC 6221
>>Lightweight DHCPv6 Relay Agent RFC 6355 Definition of the UUID-Based
>>DHCPv6 Unique Identifier (DUID-UUID) RFC 6422 Relay-Supplied DHCP
>>Options RFC 6603 Prefix Exclude Option for DHCPv6-based Prefix
>>Delegation RFC 6644 Rebind Capability in DHCPv6 Reconfigure Messages
>>RFC 6939 Client Link-Layer Address Option in DHCPv6 RFC 6977 Triggering
>>DHCPv6 Reconfiguration from Relay Agents RFC 7083 Modification to
>>Default Values of SOL_MAX_RT and INF_MAX_RT
>>
>>Regards,
>>
>>Sheng
>>
>>3c. prepare a list of possible RFCs/drafts to merge
>>
>>RFC 3319 DHCPv6 Options for Session Initiation Protocol (SIP) Servers
>>RFC
>>3646 DNS Configuration options for DHCPv6 RFC 3736 Stateless DHCPv6
>>Service RFC 3898 Network Information Service (NIS) Configuration
>>Options for DHCPv6 RFC 4075 Simple Network Time Protocol (SNTP)
>>Configuration Option for DHCPv6 RFC 4242 Information Refresh Time
>>Option for DHCPv6 RFC 4280 DHCP Options for Broadcast and Multicast
>>Control Servers RFC 4580
>>DHCPv6 Relay Agent Subscriber-ID Option RFC 4649 DHCPv6 Relay Agent
>>Remote-ID Option RFC 4703 Resolution of Fully Qualified Domain Name
>>(FQDN) Conflicts among DHCP Clients RFC 4704 DHCPv6 Client Fully
>>Qualified Domain Name (FQDN) Option RFC 4776 DHCPv4 and DHCPv6
>Option
>>for Civic Addresses Configuration InformationRFC 4833 Timezone Options
>>for DHCP RFC 4994 DHCPv6 Relay Agent Echo Request Option RFC 5007
>>DHCPv6 Leasequery RFC 5192 DHCP Options for Protocol for Carrying
>>Authentication for Network Access (PANA) Authentication Agents RFC 5460
>>DHCPv6 Bulk Leasequery RFC 5678 DHCPv4 and DHCPv6 Options for IEEE
>>802.21 Mobility Services (MoS) Discovery RFC 5908 Network Time Protocol
>>(NTP) Server Option for DHCPv6 RFC 5970 DHCPv6 Options for Network
>Boot
>>RFC 6153
>>DHCPv4 and DHCPv6 Options for Access Network Discovery and Selection
>>Function (ANDSF) Discovery RFC 6221 Lightweight DHCPv6 Relay Agent RFC
>>6276 DHCPv6 Prefix Delegation for Network Mobility (NEMO) RFC 6334
>>DHCPv6 Option for Dual-Stack Lite RFC 6355 Definition of the UUID-Based
>>DHCPv6 Unique Identifier (DUID-UUID) RFC 6422 Relay-Supplied DHCP
>>Options RFC 6440 EAP Re-authentication Protocol (ERP) Local Domain Name
>>DHCPv6 Option RFC 6603 Prefix Exclude Option for DHCPv6-based Prefix
>>Delegation RFC 6607 Virtual Subnet Selection Options for DHCPv4 and
>>DHCPv6 RFC 6644 Rebind Capability in DHCPv6 Reconfigure Messages RFC
>>6653 DHCPv6 Prefix Delegation in Long-Term Evolution (LTE) Networks RFC
>>6784 Kerberos Options for DHCPv6 RFC 6939 Client Link-Layer Address
>>Option in DHCPv6 RFC 6977 Triggering DHCPv6 Reconfiguration from Relay
>>Agents RFC 7037 RADIUS Option for the DHCPv6 Relay Agent RFC 7083
>>Modification to Default Values of SOL_MAX_RT and INF_MAX_RT
>>
>>draft-ietf-dhc-topo-conf
>>draft-ietf-dhc-access-network-identifier
>>draft-ietf-dhc-dns-pd
>>draft-ietf-dhc-dhcpv6-unknown-msg
>>draft-ietf-dhc-sedhcpv6
>_______________________________________________
>Dhcpv6bis mailing list
>[e-mail]
>https://www.ietf.org/mailman/listinfo/dhcpv6bis