On 8 jul 2008, at 20.41, Keith Moore wrote:
1) I do understand where the current last 64 bits are EUId comes
from.
2) Someone (I think it was Keith Moore) said that if the scheme
doesn't work for servers AND hosts (i.e no difference) it's a bad
scheme. I sort of agree with that, but the
John C Klensin wrote:
Better text is welcome if we can agree on the principle. It
may also be that, if we are going to permit addresses, some
words in the Checklist about preferences for IPv4, IPv6, or
parallel examples would be in order.
The principle should be stay away from IP literals
*
* John C Klensin wrote:
*
* (iii) The IETF has indicated enough times that domain
* names, not literal addresses, should be used in both
* protocols and documents that doing anything else should
* reasonably require clear and strong justification.
*
John,
This
Date:Wed, 9 Jul 2008 09:41:03 -0700 (PDT)
From:The IESG [EMAIL PROTECTED]
Message-ID: [EMAIL PROTECTED]
| The IESG has received a request from an individual submitter to consider
| the following document:
|
| - 'IANA Considerations for the IPv4 and IPv6
--On Thursday, 10 July, 2008 08:50 -0700 Bob Braden
[EMAIL PROTECTED] wrote:
*
* John C Klensin wrote:
*
* (iii) The IETF has indicated enough times that domain
* names, not literal addresses, should be used in both
* protocols and documents that
On Thu, Jul 10, 2008 at 12:08 PM, Robert Elz [EMAIL PROTECTED] wrote:
This is the kind of thing we might have expected to see in a security
considerations section 15-20 years ago, when the network was a nice kind
friendly environment, where all the players would take great care not
to do
Kurt Erik Lindqvist wrote:
On 8 jul 2008, at 20.41, Keith Moore wrote:
[..]
I disagree that it doesn't work for servers. (Or it would be better
to say that I'd like to know why you think it doesn't work for servers.)
People have personal opinions, one likes this, the other likes that,
We recently deployed a new IETF Jabber server (ejabbered) and we would like
to load test it before the Dublin meeting. This coming Tuesday, July 15 at
10am PT (1PM ET and 5pm GMT) you are officially invited to log into the IETF
Jabber Hallway or various WG Chatrooms and chat with your fellow
Total of 179 messages in the last 7 days.
script run at: Fri Jul 11 00:53:02 EDT 2008
Messages | Bytes| Who
+--++--+
11.73% | 21 | 13.11% | 143970 | [EMAIL PROTECTED]
11.73% | 21 | 10.22% | 112236 | [EMAIL
A modified charter has been submitted for the Common Control and
Measurement Plane (ccamp) working group in the Routing Area of the IETF.
The IESG has not made any determination as yet. The modified charter is
provided below for informational purposes only. Please send your comments
to the IESG
The IESG has received a request from an individual submitter to consider
the following document:
- 'Guidelines for Using the Privacy Mechanism for SIP '
draft-munakata-sip-privacy-guideline-03.txt as an Informational RFC
The IESG plans to make a decision in the next few weeks, and solicits
The IESG has approved the following document:
- 'The Internet Assigned Number Authority (IANA) tel Uniform Resource
Identifier (URI) Parameter Registry '
draft-ietf-iptel-tel-reg-06.txt as a Proposed Standard
This document is the product of the IP Telephony Working Group.
The IESG
We recently deployed a new IETF Jabber server (ejabbered) and we would like
to load test it before the Dublin meeting. This coming Tuesday, July 15 at
10am PT (1PM ET and 5pm GMT) you are officially invited to log into the IETF
Jabber Hallway or various WG Chatrooms and chat with your fellow
A new Request for Comments is now available in online RFC libraries.
RFC 5260
Title: Sieve Email Filtering: Date and
Index Extensions
Author: N. Freed
Status: Standards Track
Date: July 2008
A new Request for Comments is now available in online RFC libraries.
RFC 5211
Title: An Internet Transition Plan
Author: J. Curran
Status: Informational
Date: July 2008
Mailbox:[EMAIL PROTECTED]
Pages:
15 matches
Mail list logo
