[lac-discuss-en] Fwd: [governance] IETF standard to reserve ".local"?

[Carlton Samuels]

This is important!
CAS
==================================================

---------- Forwarded message ----------
From: Stephane Bortzmeyer <bortzmeyer at internatif.org>
Date: Wed, Nov 25, 2009 at 10:03 AM
Subject: [governance] IETF standard to reserve ".local"?
To: governance at lists.cpsr.org


For information, here is the Last Call inside IETF for the approval of
a new RFC which would reserve ".local" as a TLD, without bothering to
go through the long and expensive ICANN process.

Do note the section 3.1, which basically states that ICANN can be
ignored:

  Note that this use of the ".local." suffix falls under IETF/IANA
  jurisdiction, not ICANN jurisdiction. DNS is an IETF network
  protocol, governed by protocol rules defined by the IETF. These IETF
  protocol rules dictate character set, maximum name length, packet
  format, etc. ICANN determines additional rules that apply when the
  IETF's DNS protocol is used on the public Internet. In contrast,
  private uses of the DNS protocol on isolated private networks are not
  governed by ICANN. Since this change is a change to the core DNS
  protocol rules, it affects everyone, not just those machines using
  the ICANN-governed Internet. Hence this change falls into the
  category of an IETF protocol rule, not an ICANN usage rule.

  This allocation of responsibility is formally established in
  "Memorandum of Understanding Concerning the Technical Work of the
  Internet Assigned Numbers Authority" [RFC 2860]. Exception (a) of
  clause 4.3 states that the IETF has the authority to instruct IANA
  to reserve pseudo-TLDs as required for protocol design purposes.
  For example, "Reserved Top Level DNS Names" [RFC 2606] defines
  the following pseudo-TLDs:

     .test
     .example
     .invalid
     .localhost
____________________________________________________________
You received this message as a subscriber on the list:
    governance at lists.cpsr.org
To be removed from the list, send any message to:
    governance-unsubscribe at lists.cpsr.org

For all list information and functions, see:
    http://lists.cpsr.org/lists/info/governance


---------- Forwarded message ----------
From: The IESG <iesg-secretary at ietf.org>
To: IETF-Announce <ietf-announce at ietf.org>
Date: Wed, 18 Nov 2009 06:07:17 -0800 (PST)
Subject: Last Call: draft-cheshire-dnsext-multicastdns (Multicast DNS) to
Informational RFC
The IESG has received a request from an individual submitter to consider
the following document:

- 'Multicast DNS '
  <draft-cheshire-dnsext-multicastdns-08.txt> as an Informational RFC

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send substantive comments to the
ietf at ietf.org mailing lists by 2009-12-16. Exceptionally,
comments may be sent to iesg at ietf.org instead. In either case, please
retain the beginning of the Subject line to allow automated sorting.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-cheshire-dnsext-multicastdns-08.txt


IESG discussion can be tracked via
https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=7426&rfc_flag=0

_______________________________________________
IETF-Announce mailing list
IETF-Announce at ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce