Skip to main content

Dynamic Host Configuration Protocol (DHCPv4 and DHCPv6) Option for Civic Addresses Configuration Information
draft-ietf-geopriv-dhcp-civil-09

Yes

(Allison Mankin)
(Ted Hardie)

No Objection

(Alex Zinin)
(Bert Wijnen)
(Jon Peterson)
(Mark Townsley)
(Russ Housley)
(Sam Hartman)

Abstain


Note: This ballot was opened for revision 09 and is now closed.

Allison Mankin Former IESG member
Yes
Yes () Unknown

                            
Ted Hardie Former IESG member
Yes
Yes () Unknown

                            
Alex Zinin Former IESG member
No Objection
No Objection () Unknown

                            
Bert Wijnen Former IESG member
No Objection
No Objection () Unknown

                            
Bill Fenner Former IESG member
(was Discuss, No Objection) No Objection
No Objection (2006-02-16) Unknown
While re-reviewing in detail for the override vote, I found the following issues.  It made people upset for me to register them in what I thought was the correct way, so I will put them here.

HNO is not described in detail.  HNS is described as "House Number Suffix" in the table and "House Number" in the detailed description.  The paragraph talking about Building is labelled as "LMK" (making it the second paragraph labelled "LMK", since the one that's actually talking about "LMK" is also labelled such).

The description for the P.O. Box field says that it should contain the words "P.O. Box" or similar, but the example simply has a number.
Brian Carpenter Former IESG member
No Objection
No Objection (2005-06-06) Unknown
CAtype 1 (A1) should mention canton (CH)

Joel Halpern foun one error that will need to be fixed, probably in RFC  Editor interaction.  The last sentence of the IANA considerations  reads:
    The initial list of registrations is contained in .
There is a citation missing at the end?
Jon Peterson Former IESG member
No Objection
No Objection () Unknown

                            
Margaret Cullen Former IESG member
(was Discuss, No Objection) No Objection
No Objection (2006-02-16) Unknown
I have carefully reviewed this document in preparation for an override vote, and I have a couple of questions:

In the section describing the DHCPv6 format, the document says:

  The DHCPv6 [6] civic address option refers generally to the client as
  a whole.

The DHCPv4 section doesn't say this, though...  Are they different in this regard?

The document includes the following description of how addresses in the US will be represented:

  US (United States): The mapping to NENA designations is shown in
      parentheses.  A1 designates the state (STA), using the the two-
      letter state and possession abbreviations recommended by the
      United States Postal Service Publication 28 [20], Appendix B.  A2
      designates the county, parish (Louisiana) or borough (Alaska)
      (CNA).  A3 designates the civic community name, e.g., city or
      town.  It is also known as the municipal jurisdiction.  (MCN) The
      optional element A4 contains the community place name, such as
      "New bope Community" or "Urbanizacion" in Puerto Rico.  The civic
      community name (MCN) reflects the political boundaries.  These
      boundaries may differ from postal delivery assignments, the postal
      community name (PCN), for historical or practical reasons.

Minor nit:  s/. (MCN) The/ (MCN). The/  

Unfortunately, I can't figure out how I would represent my native home address using this system.

As a child I lived at:

11 Eisenhower Place
Wakefield, RI  02879

However, Wakefield is not a town.  The town is South Kingstown, RI (note that our town doesn't appear in our mailing address).  So, I think that Wakefield must be a Postal Community Name (PCN)?  Is that the same as the "community place name"?

Also, it seems downright silly not to include the U.S. zip code, even the 9-digit version if available, since there are so many systems that know how to map that to an approximate location, especially within a large city with multiple zip codes.
Mark Townsley Former IESG member
(was Discuss, No Objection) No Objection
No Objection () Unknown

                            
Russ Housley Former IESG member
No Objection
No Objection () Unknown

                            
Sam Hartman Former IESG member
No Objection
No Objection () Unknown

                            
Scott Hollenbeck Former IESG member
(was Discuss) No Objection
No Objection (2005-06-02) Unknown
Section 1: Looks like there are some spaces missing in "MUSTNOT", "SHALLNOT", and "SHOULDNOT".
David Kessens Former IESG member
(was Discuss) Abstain
Abstain (2005-11-21) Unknown
- the use of country codes seems possibly a bit misplaced as they are
  not really the determining factor on how an address is formed. Eg.
  some countries share the same formats. Basically, the country code
  is part of the address itself. The key should be the addressformat
  as registered with IANA. addressformat as registered with IANA.
  In addition, how does one define an address for a country or
  location that does not have a country code or different codes
  different pars of the country.

- We assume that five levels are sufficient for sub-national above the
  street level.

  Why ? I don't believe that Internet standards should be based on
  assumptions. Has this assumption been investigated and found to be
  correct ?