[rfc-dist] RFC 4776 on Dynamic Host Configuration Protocol (DHCPv4 and DHCPv6) Option for Civic Addresses Configuration Information

rfc-editor@rfc-editor.org rfc-editor at rfc-editor.org
Fri Nov 17 18:05:16 PST 2006


A new Request for Comments is now available in online RFC libraries.

        
        RFC 4776

        Title:      Dynamic Host Configuration Protocol (DHCPv4 
                    and DHCPv6) Option for Civic Addresses 
                    Configuration Information 
        Author:     H. Schulzrinne
        Status:     Proposed Standard
        Date:       November 2006
        Mailbox:    hgs+geopriv at cs.columbia.edu
        Pages:      19
        Characters: 45495
        Obsoletes:  RFC4676
        See-Also:   

        I-D Tag:    draft-rfc4676bis-00.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4776.txt


RFC 4776 is being published to correct an error in the assignment of
the numeric value of the DHCPv6 option-code in RFC 4676 (Section 3.2).
This document obsoletes RFC 4676.

This document specifies a Dynamic Host Configuration Protocol (DHCPv4
and DHCPv6) option containing the civic location of the client or the
DHCP server.  The Location Configuration Information (LCI) includes
information about the country, administrative units such as states,
provinces, and cities, as well as street addresses, postal community
names, and building information.  The option allows multiple
renditions of the same address in different scripts and languages.  
[STANDARDS TRACK[

This document is a product of the Geographic Location/Privacy
Working Group of the IETF.

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol.  Distribution
of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...




More information about the rfc-dist mailing list