[shara] RSIP [was RE: SHARA preliminary agenda posted]

["Dan Wing" <[e-mail]>]

 

> -----Original Message-----
> From: Laganier, Julien [mailto:[e-mail]] 
> Sent: Friday, November 06, 2009 12:04 AM
> To: Dan Wing
> Cc: [e-mail]
> Subject: RE: [shara] SHARA preliminary agenda posted
> 
> Hello Dan,
> 
> > > Hi Dan,
> > >
> > > There doesn't seem to be an A+P document on the agenda...
> > >
> > > When we talk about A+P, are we specifically discussing
> > > http://www.ietf.org/id/draft-ymbk-aplusp-05.txt?
> > 
> > No, by "A+P" we are generalizing to include solutions that
> > provide TCP/UDP ports to a subscriber, including so far:
> > 
> >   A+P, draft-ymbk-aplusp
> >   Port Range, draft-boucadair-port-range
> >   Port Range + IPv6, draft-boucadair-behave-ipv6-portrange
> >   SAM, draft-despres-softwire-mesh-sam
> >   Dual IVI, draft-xli-behave-divi
> 
> How about the RSIP [1,2,3,4] protocol?
> 
> [1] RFC 3102 (rfc3102) - Realm Specific IP: Framework
>     http://tools.ietf.org/html/rfc3102
> [2] RFC 3103 - Realm Specific IP: Protocol Specification
>     http://tools.ietf.org/html/rfc3103
> [3] RFC 3104 - RSIP Support for End-to-end IPsec
>     http://tools.ietf.org/html/rfc3104
> [4] RFC 3105 (rfc3105) - Finding an RSIP Server with SLP
>     http://tools.ietf.org/html/rfc3105

RSIP essentially borrows an IPv4 address from another network.  A+P isn't
doing that; it is using IPv4 addresses from the same access network as usual,
but instead of giving every host full use of an IPv4 address (any protocol,
all ports), it restricts the use to UDP, TCP, and ICMP, and a certain range of
UDP and TCP ports.  A+P doesn't borrow IPv4 addressees (or addresses and
ports) from far-away network domains.  Of course with tunneling such a thing
could be achieved with A+P - controlled only by where an A+P tunnel is
terminated.

-d