[RAM] PASH: Another SHIM6 proxying draft, in addition to pshim6

[Pekka Nikander <[e-mail]>]

Another new draft, http://www.ietf.org/internet-drafts/draft-nikander- 
ram-pash-00.txt , outlines how to proxy SHIM6 in a slightly different  
way than PSHIM6; it also discusses HIP proxying.  It is not as  
detailed as PSHIM6; instead it tries to show that it is indeed  
possible to use SHIM6 (and HIP) in a LISP-like way.  However, it is  
important to remember that SHIM6 and especially HIP provide much more  
than LISP does; see e.g. Markus Stenberg's recent message.

 From a deployment point of view the biggest difference between  
PSHIM6 and PASH seems to be that PASH outlines scenarios that require  
less machinery between the legacy hosts and the network than PSHIM6  
does; PSHIM6 also includes some discussion about that in Section 7.   
The generix draft [1] tries to generalise the different approaches,  
but unfortunately as of today it may be still too scanty to be really  
comprehensible, at least if the reader is not willing to think hard.   
However, I hope that the PASH (and PSHIM6) help to digest the generix  
message.

The more architectural message here is that there indeed seems to be  
pretty independent dimensions of where to implement id/loc split:  
where to implement it vertically (in the stack), and where to  
implement it horizontally (in the host/network).  A third (though not  
independent) dimension is the nature and routability/resolvability of  
identifiers, along the lines of LISP 1, 1.5, 2, and 3 deployment  
scenarios.

--Pekka Nikander

[1] http://www.ietf.org/internet-drafts/draft-nikander-ram-generix- 
proxying-00.txt


On 28 Feb 2007, at 13:45, marcelo bagnulo braun wrote:

> Hi,
>
> i have included in this draft some level of detail on how to do  
> proxies in shim6, in order to support unmodified hosts, allow some  
> middle boxes to perform egress path selection and provide PI  
> identifiers, so that we can have an idea of how this would look  
> like in the shim approach
>
> Comments are welcome
>
> Regards, marcelo
>
> Inicio mensaje reenviado:
>
>> De: [e-mail]
>> Fecha: 27 de febrero de 2007 21:50:02 GMT+01:00
>> Para: [e-mail]
>> Cc: Asunto: I-D ACTION:draft-bagnulo-pshim6-00.txt
>> Responder a: [e-mail]
>>
>> A New Internet-Draft is available from the on-line Internet-Drafts
>> directories.
>>
>>
>> 	Title		: Proxy Shim6 (P-Shim6)
>> 	Author(s)	: M. Bagnulo
>> 	Filename	: draft-bagnulo-pshim6-00.txt
>> 	Pages		: 22
>> 	Date		: 2007-2-27
>> 	
>>    This draft discusses extensions to the shim6 architecture to  
>> support
>>    shim6 proxies that would allow the provision of the following
>>    capabilities:
>>    o  Provide Upper Layer Identifier portability.
>>    o  Provide Traffic Engineering policy enforcement.
>>    o  Off-load of the shim6 context management from the actual  
>> peers of
>>       the communication.
>>
>>
>> A URL for this Internet-Draft is:
>> http://www.ietf.org/internet-drafts/draft-bagnulo-pshim6-00.txt
>>
>> To remove yourself from the I-D Announcement list, send a message to
>> [e-mail] with the word unsubscribe in the  
>> body of
>> the message.
>> You can also visit https://www1.ietf.org/mailman/listinfo/I-D- 
>> announce
>> to change your subscription settings.
>>
>> Internet-Drafts are also available by anonymous FTP. Login with the
>> username "anonymous" and a password of your e-mail address. After
>> logging in, type "cd internet-drafts" and then
>> "get draft-bagnulo-pshim6-00.txt".
>>
>> A list of Internet-Drafts directories can be found in
>> http://www.ietf.org/shadow.html
>> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>>
>> Internet-Drafts can also be obtained by e-mail.
>>
>> Send a message to:
>> 	[e-mail].
>> In the body type:
>> 	"FILE /internet-drafts/draft-bagnulo-pshim6-00.txt".
>> 	
>> NOTE:	The mail server at ietf.org can return the document in
>> 	MIME-encoded form by using the "mpack" utility.  To use this
>> 	feature, insert the command "ENCODING mime" before the "FILE"
>> 	command.  To decode the response(s), you will need "munpack" or
>> 	a MIME-compliant mail reader.  Different MIME-compliant mail readers
>> 	exhibit different behavior, especially when dealing with
>> 	"multipart" MIME messages (i.e. documents which have been split
>> 	up into multiple messages), so check your local documentation on
>> 	how to manipulate these messages.
>>
>> Below is the data which will enable a MIME compliant mail reader
>> implementation to automatically retrieve the ASCII version of the
>> Internet-Draft.
>> Content-Type: text/plain
>> Content-ID: <[e-mail]>
>>
>> _______________________________________________
>> I-D-Announce mailing list
>> [e-mail]
>> https://www1.ietf.org/mailman/listinfo/i-d-announce
>
>
> _______________________________________________
> RAM mailing list
> [e-mail]
> https://www1.ietf.org/mailman/listinfo/ram
>


_______________________________________________
RAM mailing list
[e-mail]
https://www1.ietf.org/mailman/listinfo/ram