All,
This is the start of a 1-week WG Last Call on advancing:
Title : IPv6 Host to Router Load Sharing
Author(s) : R. Hinden, D. Thaler
Filename: draft-ietf-ipv6-host-load-sharing-03.txt
Pages : 6
Date: 2004-10-21
Dear All,
TAHI Projcet is organizing its 6th TAHI IPv6 Interoperability Test Event.
The event will be held from 24th - 28th January 2005 at the Makuhari messe of Chiba
Japan.
Registration will be avairable from 17 November 2004 at:
http://www.tahi.org/inop/6thinterop.html
Deadline to register
Fred,
Looking at all the discussion/arguments, I think we have
consensus about not adding the proposed code point to the
spec.
I agree with all others that it is not required in this
spec and it is not a good idea to add this code point at
this (DS) stage.
Regards
Mukesh
-Original
Pekka,
Sorry to have that missed. I somehow assumed that we needed no
modification after the consensus. My bad !
I will try to rephrase the text while addressing all the other
LC comments.
Regards
Mukesh
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf
On Fri, 2004-10-22 at 11:04, Suresh Krishnan wrote:
Can you give me more details or a pointer to such an attack? I will add
add some text and a reference to it.
There's a wealth of information about traffic analysis capabilities in
many books about WW-II-era codebreaking.
As a more modern
Dear All,
TAHI Projcet is organizing its 6th TAHI IPv6 Interoperability Test Event.
The event will be held from 24th - 28th January 2005 at the Makuhari messe of Chiba
Japan.
Registration will be avairable from 17 November 2004 at:
http://www.tahi.org/inop/6thinterop.html
Deadline to register
Hi
If M-Policy is 1, the host SHOULD invoke Host Configuration Behaviour
for address and other configuration information, regardless of the
change of the state variables. The host SHOULD NOT invoke
Information Configuration Behaviour regardless of O-Policy. Note,
On Fri, 29 Oct 2004, Soohong Daniel Park wrote:
If M-Policy is 1, the host SHOULD invoke Host Configuration Behaviour
for address and other configuration information, regardless of the
change of the state variables. The host SHOULD NOT invoke
Information Configuration Behaviour
Hi All,
We're having a discussion on URIs and IRIs in the IESG that has led
me to realize that the URL literal IPv6 address format described in
RFC 2732 does not contain any provision for including a zone ID. I
don't think that we could simply add a %zone-id to the end of the
IP address,
I don't know... I am far from a URL expert, but in discussions about
how to encode IPv6 literals in URIs and IRIs, the square brackets
don't seem to be enough. The percent sign also has to be encoded as
a %25 and/or changed to another character.
Does this apply to URLs, too?
Margaret
At 2:28
10 matches
Mail list logo
