Re: New Version Notification for draft-matsushima-stateless-uplane-vepc-00.txt

Thanks for winding up a good old discussion on this specific GTP
topic. I have not yet read the I-D in a close detail but I have
some initial questions - so there might be some gaps in my
understanding of the I-D. Previously when similar architectures
were exercised the question of backward compatibility always came
up. One of the sticking points was the established practices to use
of GTP-U header extensions to carry subscriber specific data within
the core (i.e. between SGW/SGSN and PGW/GGSN). Have you thought 
of this? Another question/note I have is that now quite a bit of
tasks that used to belong to PGW/GGSN are now assigned to EPC-E
(like policy control). Has this been seen as an issue?

- Jouni




On Jul 10, 2013, at 7:12 PM, Ryuji Wakikawa <[email protected]> wrote:

> Hi 
> 
> We submit a new document.  Your comments are appreciated! 
> 
> thanks,
> ryuji
> 
> 
> Begin forwarded message:
> 
>> From: [email protected]
>> Subject: New Version Notification for draft-matsushima-stateless-uplane-vepc-00.txt
>> Date: July 10, 2013 9:09:44 AM PDT
>> To: Ryuji Wakikawa <[email protected]>, Satoru Matsushima <[email protected]>
>> 
>> 
>> A new version of I-D, draft-matsushima-stateless-uplane-vepc-00.txt
>> has been successfully submitted by Satoru Matsushima and posted to the
>> IETF repository.
>> 
>> Filename:	 draft-matsushima-stateless-uplane-vepc
>> Revision:	 00
>> Title:		 Stateless user-plane architecture for virtualized EPC (vEPC)
>> Creation date:	 2013-07-10
>> Group:		 Individual Submission
>> Number of pages: 19
>> URL:             http://www.ietf.org/internet-drafts/draft-matsushima-stateless-uplane-vepc-00.txt
>> Status:          http://datatracker.ietf.org/doc/draft-matsushima-stateless-uplane-vepc
>> Htmlized:        http://tools.ietf.org/html/draft-matsushima-stateless-uplane-vepc-00
>> 
>> 
>> Abstract:
>>  We envision a new mobile architecture for the future Evolved Packet
>>  Core (EPC).  The new architecture is designed to support the
>>  virtualization scheme called NFV (Network Function Virtualization).
>>  In our architecture, the user plane of EPC is decoupled from the
>>  control-plane and uses routing information to forward packets of
>>  mobile nodes.  Although the EPC control plane will run on hypervisor,
>>  our proposal does not modify the signaling of the EPC control plane.
>>  The benefits of our architecture are 1) scalability, 2) flexibility
>>  and 3) Manageability.  How to run the EPC control plane on NFV is out
>>  of our focus in this document.
>> 
>> 
>> 
>> 
>> The IETF Secretariat
>> 
> 
> _______________________________________________
> dmm mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/dmm