Title: RFC 3484 update?
On 23Jun05, on this list there began and ended a thread concerning ULAs, multicast, and RFC 3484. I agree with the contention espoused by some that RFC 3484 should be updated. Section 3.1 clearly states that with the presence of a multicast destination address, a compa
On Fri, 22 Jul 2005 14:20:37 +0930
Mark Smith <[EMAIL PROTECTED]> wrote:
> Hi,
>
> On Fri, 22 Jul 2005 10:32:48 +0900 (JST)
> Ryota Hirose <[EMAIL PROTECTED]> wrote:
>
> > Hi,
> >
> > >From: Iljitsch van Beijnum <[EMAIL PROTECTED]>
> > >Date: Thu, 21 Jul 2005 10:19:56 +0200
> >
> > > My common
Hi,
On Fri, 22 Jul 2005 10:32:48 +0900 (JST)
Ryota Hirose <[EMAIL PROTECTED]> wrote:
> Hi,
>
> >From: Iljitsch van Beijnum <[EMAIL PROTECTED]>
> >Date: Thu, 21 Jul 2005 10:19:56 +0200
>
> > My common sense tells me that the authors of RFC 2464 didn't consider
> > the case where the MTU would
Hi,
>From: Iljitsch van Beijnum <[EMAIL PROTECTED]>
>Date: Thu, 21 Jul 2005 10:19:56 +0200
> My common sense tells me that the authors of RFC 2464 didn't consider
> the case where the MTU would legitimately be larger than 1500 bytes.
> They did consider the case where router advertisements co
> >>
> >>The verification of temporary vs. public, home vs. care-of, CGA vs.
> >>not, are performed by a new function defined for this purpose:
> >>
> >> #include
> >>
> >>Not in6.h?
> >>
> >
> >
> > You mean
>>
>>The verification of temporary vs. public, home vs. care-of, CGA vs.
>>not, are performed by a new function defined for this purpose:
>>
>> #include
>>
>>Not in6.h?
>>
>
>
> You mean ip6.h?
> ip6.h is mainl
Hello Brian:
> > Title : IPv6 Socket API for source address selection
> > Author(s) : E. Nordmark, et al.
> > Filename: draft-chakrabarti-ipv6-addrselect-api-03.txt
>
> Hi Samita, Erik, and Julien,
>
> Didn't see this sent to the IPv6 ML, but sending comments
A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the IP Version 6 Working Group Working Group of
the IETF.
Title : A Method for Generating Link Scoped IPv6 Multicast
Addresses
Author(s) : J. Park, et al.
Actually, my proposal to Brian on the draft was exactly what you suggested,
mapping the name queries into the Solicited Node Address (SNA) range. I think
that is the best solution. I have another draft that suggests that the "dynamic
range" gets broken into 2 major sections: Global (DAG) scoped
On 21-jul-2005, at 1:01, Ryota Hirose wrote:
As I read it, RFC2464 says that the maximum *default* MTU is 1500,
and, anything larger than that must be manually configured. It
doesn't say that it is prohibited.
RFC2464 says as following:
This size may be reduced by a Router Ad
10 matches
Mail list logo
