Re: SCTP API draft (was Re: New "IP Version 6 Addressing Architecture" draft)

2000-07-24 Thread Jim Bound
I think I may have been misunderstood. Let me see if the response clears it up? >The discussion below raises concerns with our proposed draft for >an SCTP sockets API. SCTP is a reliable datagram transport developed >by SIGTRAN to carry telephony signaling information. >One distinctive feature

Re: SCTP API draft (was Re: New "IP Version 6 Addressing Architecture" draft)

2000-07-24 Thread Randall R. Stewart
Dear All: One note to all you readers.. this draft is a very very early first cut. We rushed it out to get it in to the drafts editor and thus it requires quite a bit of work yet :-> I did not get Jim's original email so I have a hard time reading the snippet below and making sense of it... I

SCTP API draft (was Re: New "IP Version 6 Addressing Architecture" draft)

2000-07-24 Thread La Monte Henry Piggy Yarroll
The discussion below raises concerns with our proposed draft for an SCTP sockets API. SCTP is a reliable datagram transport developed by SIGTRAN to carry telephony signaling information. One distinctive feature of SCTP is direct support for multi-homed hosts. SCTP has the notion of a "primary a

Proposed IPng Agenda for Pittsburgh IETF

2000-07-24 Thread Bob Hinden
Attached is the proposed agenda for the IPng w.g. sessions at the Pittsburgh IETF. The IPng working group will have two sessions. There will also be a joint IPng / Mobile IP session on Tuesday. The agenda for that session will be sent out separately. Please send us changes, additions, and c

Re: New "IP Version 6 Addressing Architecture" draft

2000-07-24 Thread Brian Haberman
JINMEI Tatuya / 神明達哉 wrote: > > > On Fri, 21 Jul 2000 08:46:37 -0400, > > "Brian Haberman" <[EMAIL PROTECTED]> said: > > > Yes, it is equivalent to the "local scope" defined in > > RFC 2365 and RFC 2730. It should be noted that those documents > > refer to IPv6 scope 3

Re: New "IP Version 6 Addressing Architecture" draft

2000-07-24 Thread Jim Bound
Mauro, >> but v4 mapped does not affect the ISV porting effort at all and in fact >> makes their job much easier if the platform they are porting to supports >> that paradigm. >you are absolutely right. my concern was about api issues. a modification >in the behaviour of af_inet6 passive socket,

Re: New "IP Version 6 Addressing Architecture" draft

2000-07-24 Thread itojun
I think most of the items are replied in reply to Brian. >> there's no way for the current API to recognize IPv4 traffic on top >> of AF_INET6 socket (appears as IPv4 mapped address), and native >> IPv6 traffic with IPv4 mapped address in the header). at least >> we

I-D ACTION:draft-ietf-ipngwg-addrconf-privacy-02.txt

2000-07-24 Thread Internet-Drafts
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the IPNG Working Group of the IETF. Title : Privacy Extensions for Stateless Address Autoconfiguration in IPv6 Author(s) : T. Nar