I've reviewed this document as part of the transport area directorate's
ongoing effort to review key IETF documents. These comments were written
primarily for the transport area directors, but are copied to the
document's authors for their information and to allow them to address
any issues
At 15:00 17-01-11, The IESG wrote:
The IESG has received a request from an individual submitter to consider
the following document:
- 'Special-Use Domain Names'
draft-cheshire-dnsext-special-names-01.txt as a Proposed Standard
Abstract
This document describes what it means to say that
On 2011-01-28, at 10:15, SM wrote:
Domain Name: EXAMPLE.COM
Registrar: RESERVED-INTERNET ASSIGNED NUMBERS AUTHORITY
Whois Server: whois.iana.org
Referral URL: http://res-dom.iana.org
Name Server: A.IANA-SERVERS.NET
Name Server: B.IANA-SERVERS.NET
Status:
Hello all,
2011/1/28 Magnus Westerlund magnus.westerl...@ericsson.com
I've reviewed this document as part of the transport area directorate's
ongoing effort to review key IETF documents. These comments were written
primarily for the transport area directors, but are copied to the
document's
28.01.2011 17:15, SM wrote:
At 15:00 17-01-11, The IESG wrote:
The IESG has received a request from an individual submitter to consider
the following document:
- 'Special-Use Domain Names'
draft-cheshire-dnsext-special-names-01.txt as a Proposed Standard
Abstract
This document describes
Hello all,
I am writing to comment draft-cheshire-dnsext-special-names-01, that
is currently in Last Call.
I've noticed that there is no clear definition of the created IANA
regsitry, as defined by RFC 5226. Among other, there is no clear
definition of registry format and initial values. I'd
On Tue, 18 Jan 2011, Eric Brunner-Williams wrote:
The -- violation
It is not a violation. Double hyphens have been permitted by the syntax
forever.
Tony.
--
f.anthony.n.finch d...@dotat.at http://dotat.at/
HUMBER THAMES DOVER WIGHT PORTLAND: NORTH BACKING WEST OR NORTHWEST, 5 TO 7,
There are label segments that have semantics.
The -- violation, prepended by something, ^xn, where ^ indicates
a label boundary, to indicate a (the current) IDN processing.
Bytes within a label with values in excess of 127.
Off hand I can't think of anything else (that is intentional). Along
