Hi Björn,
On 06/08/2012 03:16 AM, Bjoern Hoehrmann wrote:
I think the requirement in RFC 4395 section 2.6 applies here, there are
text fields in 'ni' and 'nih' addresses, so there needs to be some dis-
cussion about I18N and IRI issues, or a statement that there are none,
or something along
See draft-hoffman-tao-as-web-page-00, just published. I am the editor of that
draft, but the ideas in it come from the IESG. The IESG didn't pre-review the
draft, but it is based on what I was told was agreed to during the IESG
telechat on Thursday.
--Paul Hoffman
Looks like this didn't get through the first time.
From: Glen Zorn glenz...@gmail.com
To: ietf@ietf.org
Cc: glenz...@cmail.com
Subject: Re: Last Call: draft-hoffman-tao4677bis-15.txt (The Tao of
IETF: A Novice's Guide to the Internet Engineering Task Force) to
Informational RFC
Date: Sat,
A quick check of the Upcoming IETF Meetings calendar
(http://www.ietf.org/meeting/upcoming.html) shows that the next
meeting in Asia is scheduled for November 2015, while the last was
November 2011. How does a 4 year gap map to approximately once a
year?
this winter we are meeting in
The intended rotation cycle is still 1-1-1 for NA-EU-AP regions, but
it's all dependent on finding suitable and available venues and
willing hosts and sponsors. Changing the text of the document would
imply a change in policy or normal state of things which there
hasn't been.
Ole
Ole J.
On Sat, 2012-06-09 at 18:09 -0700, Ole Jacobsen wrote:
The intended rotation cycle is still 1-1-1 for NA-EU-AP regions, but
it's all dependent on finding suitable and available venues and
willing hosts and sponsors. Changing the text of the document would
imply a change in policy or normal
