From l3vpn-bounces@ietf.org Thu Nov 01 18:20:39 2007
Return-path: <l3vpn-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IniKA-0006TK-Ui; Thu, 01 Nov 2007 18:15:38 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IniK9-0006Pg-TE
	for l3vpn@ietf.org; Thu, 01 Nov 2007 18:15:37 -0400
Received: from mail-sin.bigfish.com ([207.46.51.74]
	helo=mail211-sin-R.bigfish.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IniJu-0004uT-Rs
	for l3vpn@ietf.org; Thu, 01 Nov 2007 18:15:33 -0400
Received: from mail211-sin (localhost.localdomain [127.0.0.1])
	by mail211-sin-R.bigfish.com (Postfix) with ESMTP id 3DD42E703D0
	for <l3vpn@ietf.org>; Thu,  1 Nov 2007 22:14:51 +0000 (UTC)
X-BigFish: V
X-MS-Exchange-Organization-Antispam-Report: OrigIP: 207.40.188.14; Service: EHS
Received: by mail211-sin (MessageSwitch) id 1193955291154866_8426;
	Thu,  1 Nov 2007 22:14:51 +0000 (UCT)
Received: from smtpgw6.it.sprintspectrum.com (smtpgw6.sprintspectrum.com
	[207.40.188.14])
	by mail211-sin.bigfish.com (Postfix) with ESMTP id 0263FA808C
	for <l3vpn@ietf.org>; Thu,  1 Nov 2007 22:14:49 +0000 (UTC)
Received: from mailhost.sprintspectrum.com (smtpgw7.it.sprintspectrum.com
	[207.40.65.55])
	by smtpgw6.it.sprintspectrum.com (8.12.11.Beta0/8.12.8) with ESMTP id
	lA1MExoB020259
	for <l3vpn@ietf.org>; Thu, 1 Nov 2007 17:14:59 -0500 (CDT)
Received: from plswg01a.ad.sprint.com (PLSWG01A.corp.sprint.com [10.214.11.47])
	by mailhost.sprintspectrum.com (Switch-3.2.5/Switch-3.2.5) with ESMTP
	id lA1MEwx4000874
	for <l3vpn@ietf.org>; Thu, 1 Nov 2007 17:14:58 -0500 (CDT)
Received: from PLSWB02C.ad.sprint.com ([208.10.70.215]) by
	plswg01a.ad.sprint.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 1 Nov 2007 17:14:58 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C81CD4.A389FE19"
Date: Thu, 1 Nov 2007 17:14:58 -0500
Message-ID: <6B1FF00C9F2BFD4EB894C686C440C2330FC576FE@PLSWB02C.ad.sprint.com>
In-Reply-To: <659DE65A3D2B0C49ACDE39BB0963154A067DCD89@PLSWB10C.ad.sprint.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: e2918 status
Thread-Index: AcgSkZ133b/+zvYkSlWS7jvde93HNQBxMPCwAAGZTJAAFD7HMAACIxoAAAAoJnAAABAjQAABNJCQAAkkZxAAASRUsAAAXyCgAAE9+oAAI0WFIAAAOu1QAACOiiAB0EWycAAFiPeQ
References: <659DE65A3D2B0C49ACDE39BB0963154A067DCD89@PLSWB10C.ad.sprint.com>
From: "Fiumano, Michael F [NTK]" <Michael.F.Fiumano@sprint.com>
To: "Magill, Bernie J [NTK]" <Bernard.Magill@sprint.com>,
	"Lipsit, William E [NTK]" <William.E.Lipsit@sprint.com>
X-OriginalArrivalTime: 01 Nov 2007 22:14:58.0208 (UTC)
	FILETIME=[A3849A00:01C81CD4]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1459dca363a7eac530b0f3f218abff0f
Cc: "Ryan, James A \[IT\]" <James.Ryan@sprint.com>, l3vpn@ietf.org, "Lemish,
	Mick L \[NTK\]" <michael.lemish@sprint.com>
Subject: RE: e2918 status
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l3vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>
Errors-To: l3vpn-bounces@ietf.org

This is a multi-part message in MIME format.

------_=_NextPart_001_01C81CD4.A389FE19
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

James, can you help us out here.  Bernie and Mick are the BizOps PMs.   =
They need to usher the project through the process.
I know we want to try and keep IT PMs out of it for a little while to =
actually help get the approach figured out, but this may force our hand.
Please help.

Thanks,
Michael Fiumano
Manager, IP Edge Development
Data Network Development
Desk: 703-689-5875   Cell: 703-598-2434
michael.f.fiumano@sprint.com



> _____________________________________________=20
> From: 	Magill, Bernie J [NTK] =20
> Sent:	Thursday, November 01, 2007 3:35 PM
> To:	Fiumano, Michael F [NTK]; Lipsit, William E [NTK]
> Cc:	Lemish, Mick L [NTK]
> Subject:	FW: e2918 status
> Importance:	High
>=20
> Michael and William,
>=20
> I need your help on the scope of E2918.  The scope is an issue and IT =
is having trouble figuring out LOEs for this project, due to the program =
unknowns and its growing complexity.  What is the true scope of E2918?  =
Can you help me work with the Planning team to properly define the scope =
of E2918?  I will then work to get it expedited and pushed through HLCE. =
 We need to take action on this soon, so we don> '> t slow down this =
program.  This program is also being pushed to a Director level as a =
scope concern, since Kathy Walker wants this program expedited.
>=20
> Give me a heads up if you have any questions.  Also, if you want more =
on the open concerns, see the email trail below> ...>=20
>=20
> Bernie Magill, PMP
> Manager, Program Management
> Network Business Operations
> SPRINT NEXTEL Corporation
> Mobile: (571) 436-9023
> Desk: (703) 433-3864
> I-Next: 6-333-3864
> Email: Bernard.Magill@sprint.com
>=20
>=20
> _____________________________________________
> From: Lemish, Mick L [NTK]=20
> Sent: Tuesday, October 23, 2007 9:53 AM
> To: Magill, Bernie J [NTK]
> Subject: FW: e2918 status
> Importance: High
>=20
> FYI> ...>=20
>=20
> Sounds like they didn> '> t put in the card what they really want =
(sounds much like the Pilot.) =20
>=20
> -----------=20
> Michael > "> Mick> ">  Lemish | Sr. Program Manager | Network Business =
Operations | Sprint Nextel Corp. | 703.926.3217(c) | =
michael.lemish@sprint.com
>=20
>=20
> _____________________________________________
> From: Alston, Gail [IT]=20
> Sent: Tuesday, October 23, 2007 9:51 AM
> To: Alemu, Blen B [NTK]; Eicher, Kari L [DEV]
> Cc: Castillo, Karin F [IT]; Lipsit, William E [NTK]; Kovacik, Paul A =
[DEV]; Lemish, Mick L [NTK]; Robertson, Keith K [IT]
> Subject: RE: e2918 status
> Importance: High
>=20
> While I do understand the importance of the project the way the =
sponsor William Lipsit described it yesterday, we do need to take a =
reality check.  The project now is vastly different from what was =
described during ICA.  Here is the approach description that we reviewed =
during ICA and that I entered into Portal:  At the time it was limited =
to enhancing the FMS and NRM reports created in E0165.
>=20
> 	Reporting requirements for FMS and NRM.
> 	User interface to allow the user to request the report instead of =
having to ask the development group to generate the report.
> 	Add DS3 fields to the report created in E0165.  Both FMS and NRM will =
need to enhance the E0165 reports.
>=20
> 	Look into the possibility of requesting Subex (NetProvision) =
capabilities.  Martin mentioned that this project should not need to =
fund IWNS needs.  During HLCE, revisit the possibility to make sure that =
there are no requirements
>=20
> Here are the points that will impact the schedule:
> 1) William mentioned a requirement to automate the migrations, however =
we need to get more specific about what the business requirements are. =20
> 2) The scope now is requesting a great deal of automation compared =
with the original scope of enhancing a couple of reports.
> 3) We need to identify the business process for performing the =
migrations before we know what needs to be automated.
> 4) There will be a need to coordinate updates between Subex, NRM and =
FMS, and possibly CIS.  Before we can provide an approach or LOE we need =
to have a better idea of the requirements for automating and timing of =
the updates between the support systems.  We are in danger of creating a =
real mess if this is not performed correctly.>=20
> 5) Subex is a new technology that is in the process of being deployed. =
 It has not been integrated with the rest of the support systems yet, so =
it is very difficult to provide an LOE for this area.
>=20
>=20
> Gail Alston
> 913-762-8723
>=20
>=20
> _____________________________________________
> From: Alemu, Blen B [NTK]=20
> Sent: Tuesday, October 23, 2007 8:33 AM
> To: Eicher, Kari L [DEV]
> Cc: Castillo, Karin F [IT]; Alston, Gail [IT]
> Subject: RE: e2918 status
>=20
> Kari/Gail,
>=20
> What is the implication of the change in the complexity of this CARD?  =
Does that mean even more time is needed to clarify the changes?
>=20
> Can you tell me exactly what we can expect as far as timelines on this =
CARD?
>=20
> Thank you.
>=20
> Blen.
>=20
>=20
>=20
>  -----Original Message-----
> From: 	Eicher, Kari L [DEV] =20
> Sent:	Monday, October 22, 2007 4:43 PM
> To:	Alemu, Blen B [NTK]
> Cc:	Castillo, Karin F [IT]; Alston, Gail [IT]
> Subject:	RE: e2918 status
>=20
> Blen,
>=20
> I have IM'ed with the assigned IT Solution Architect, Gail Alston, =
this afternoon.  Since she will be OOO later this week, she is unable to =
accommodate the expedited request.  Additionally, Gail spoke to the POC =
of E2918 and found out that the concept that was described during ICA =
has become very complex; apparently, the BRs have expanded and now the =
complexity of the concept has increased.
>=20
> Suggestions?
>=20
> Kari Eicher
> Enterprise Concept Estimation Team
> (913) 762-7094
>=20
>=20
> _____________________________________________=20
> From: 	Alemu, Blen B [NTK] =20
> Sent:	Monday, October 22, 2007 3:06 PM
> To:	Eicher, Kari L [DEV]
> Subject:	RE: e2918 status
>=20
> The HLCE schedule was based on the Project Start date (12/05/07) that =
was initially provided by the sponsor but now the executives are pushing =
for it to start ASAP.\
>=20
> Blen.
>=20
>=20
>=20
> 	 -----Original Message-----
> 	From: 	Eicher, Kari L [DEV] =20
> 	Sent:	Monday, October 22, 2007 3:53 PM
> 	To:	Alemu, Blen B [NTK]
> 	Subject:	RE: e2918 status
>=20
> 	Blen,
>=20
> 	Do you know why this wasn't submitted to HLCE earlier than last week?
>=20
> 	Thanks,
>=20
>=20
> 	Kari Eicher
> 	Enterprise Concept Estimation Team
> 	(913) 762-7094
>=20
>=20
> 	_____________________________________________=20
> 	From: 	Alemu, Blen B [NTK] =20
> 	Sent:	Monday, October 22, 2007 2:21 PM
> 	To:	Eicher, Kari L [DEV]
> 	Subject:	RE: e2918 status
>=20
> 	Kari,
>=20
> 	This project is being escalated at the Kathy Walker level.  Anything =
you can do to expedite this will be greatly appreciated.
>=20
> 	Thank you.
> 	Blen.
>=20
> 		 -----Original Message-----
> 		From: 	Eicher, Kari L [DEV] =20
> 		Sent:	Monday, October 22, 2007 11:00 AM
> 		To:	Alemu, Blen B [NTK]; Alston, Gail [IT]
> 		Cc:	Davis, Janet R [DEV]
> 		Subject:	RE: e2918 status
>=20
>=20
> 		Blen,
>=20
> 		Currently this concept is scheduled for Approach on 11/1/07 and =
Estimation on 11/9/07.  It was delayed one week in HLCE since the =
assigned Solution Architect, Gail Alston, will be OOO.
>=20
> 		Gail, do you have any suggestions?
>=20
> 		Thanks,
>=20
> 		Kari Eicher
> 		Enterprise Concept Estimation Team
> 		(913) 762-7094
>=20
>=20
> 		_____________________________________________=20
> 		From: 	Alemu, Blen B [NTK] =20
> 		Sent:	Monday, October 22, 2007 9:25 AM
> 		To:	Eicher, Kari L [DEV]; Davis, Janet R [DEV]
> 		Subject:	FW: e2918 status
>=20
> 		Kari/Janet,
>=20
> 		Is there any way to accelerate HLCE exit for this CARD?
>=20
> 		Blen.
>=20
> 		 -----Original Message-----
> 		From: 	Haskins, Eric D [NTK] =20
> 		Sent:	Monday, October 22, 2007 10:23 AM
> 		To:	Kupka, Leslie C [NTK]; Scott, Carla G [NTK]; Lunsford, Veronica =
[NTK]; Ames, Lori L [NTK]; Alemu, Blen B [NTK]
> 		Subject:	RE: e2918 status
>=20
> 		Leslie,
>=20
> 		Is there any opportunity to accelerate HLCE exit?=20
>=20
> 		Eric
>=20
> 		_____________________________________________
> 		From: Kupka, Leslie C [NTK]=20
> 		Sent: Monday, October 22, 2007 9:21 AM>=20
> 		To: Scott, Carla G [NTK]; Lunsford, Veronica [NTK]; Ames, Lori L =
[NTK]; Alemu, Blen B [NTK]
> 		Cc: Haskins, Eric D [NTK]
> 		Subject: RE: e2918 status
>=20
> 		Carla and Lori,
>=20
> 		Blen has confirmed the HLCE exit is scheduled for 11/2. I will note =
to watch closely and coordinate an expedited resourcing of NS core team. =
Please let me know if questions or concerns.
>=20
> 		Thanks to all,
>=20
> 		Leslie Kupka
>=20
> 		=
_________________________________________________________________________=
______________
> 		Leslie Kupka | Pipeline Management - Network Business Operations| =
Voice: 913.794.4109 | Mobile: 816.304.5766
>=20
>=20
>=20
> 		_____________________________________________=20
> 		From: 	Scott, Carla G [NTK] =20
> 		Sent:	Monday, October 22, 2007 8:19 AM
> 		To:	Lunsford, Veronica [NTK]; Kupka, Leslie C [NTK]; Ames, Lori L =
[NTK]; Alemu, Blen B [NTK]
> 		Cc:	Haskins, Eric D [NTK]
> 		Subject:	RE: e2918 status
>=20
> 		Thanks for the update.
>=20
> 		Yes, we need to get the core team assigned quickly > ->  at least to =
do the high level assessment for Kathy.
>=20
> 		Carla
>=20
> 		_____________________________________________
> 		From: Lunsford, Veronica [NTK]=20
> 		Sent: Sunday, October 21, 2007 11:38 PM
> 		To: Kupka, Leslie C [NTK]; Scott, Carla G [NTK]; Ames, Lori L [NTK]; =
Alemu, Blen B [NTK]
> 		Subject: RE: e2918 status
>=20
> 		Good evening,
>=20
> 		E2918/114367 was on the 10/15/07 1: N list at number 217.  It was =
listed under the concept number.
>=20
> 		Thank you,
>=20
> 		Veronica
> 		703-906-3278
> 		=20
> 		This message (including any attachments) contains confidential =
information intended for a specific individual and purpose, and is =
protected by law.  If you are not the intended recipient, you should =
delete this message.  Any disclosure, copying, or distribution of this =
message, or the taking of any action based on it, is strictly =
prohibited.
>=20
>=20
> 		_____________________________________________
> 		From: Kupka, Leslie C [NTK]=20
> 		Sent: Sunday, October 21, 2007 11:15 PM
> 		To: Scott, Carla G [NTK]; Ames, Lori L [NTK]; Alemu, Blen B [NTK]
> 		Cc: Lunsford, Veronica [NTK]
> 		Subject: RE: e2918 status
>=20
> 		Carla and Lori,
>=20
> 		RE: E2918 / 114367: IT Development support for 7500 Migrations: The =
referenced project is in OPX however, I did not find on the 1:N List of =
last week. It does have a concept exit of 12/5 so I will add to the 4Q07 =
Lock List. Resourcing will be triggered by exit from HLCE. Would you =
like me to expedite resource assignments after exiting HLCE?
>=20
> 		Veronica - Since the project is in OPX - did prioritization trigger =
the addition to OPX and it will show up this coming week on the 1:N?
> 		Blen - When do you forecast E2918 will exit HLCE? Is the 12/5 =
concept exit doable based on that?
>=20
> 		Please advise if questions or concerns.
> 		Thank you,
>=20
> 		Leslie Kupka
> 		=
_________________________________________________________________________=
______________
> 		Leslie Kupka | Pipeline Management - Network Business Operations| =
Voice: 913.794.4109 | Mobile: 816.304.5766
>=20
>=20
>=20
> 		_____________________________________________=20
> 		From: 	Scott, Carla G [NTK] =20
> 		Sent:	Friday, October 19, 2007 3:50 PM
> 		To:	Kupka, Leslie C [NTK]; Ames, Lori L [NTK]
> 		Subject:	e2918 status
>=20
> 		Hello,
>=20
> 		Can you tell me where e2918 is in the pipeline?
> 		Kathy W is asking for information, and I don> '> t believe we> '> ve =
assigned a core team yet (based on OPX2).
> 		Has it been estimated yet or do we know when the PM will be =
assigned?
>=20
> 		Thanks,
> 		Carla
> 		Carla Scott l Sprint Nextel l Network Services
> 		Strategy, Pipeline Plng & Customer Experience
> 		Desk: 913-794-4041  Mobile: 703-856-1363  164*100*12080
>=20

------_=_NextPart_001_01C81CD4.A389FE19
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7653.2">
<TITLE>RE: e2918 status</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">James, can you help =
us out here.&nbsp; Bernie and Mick are the BizOps PMs.&nbsp;&nbsp; They =
need to usher the project through the process.</FONT></P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">I know we want to try =
and keep IT PMs out of it for a little while to actually help get the =
approach figured out, but this may force our hand.</FONT></P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Please help.</FONT>
</P>

<P><FONT FACE=3D"Times New Roman">Thanks,</FONT>

<BR><FONT FACE=3D"Lucida Handwriting">Michael Fiumano</FONT>

<BR><FONT FACE=3D"Times New Roman">Manager, IP Edge Development</FONT>

<BR><FONT FACE=3D"Times New Roman">Data Network Development</FONT>

<BR><FONT FACE=3D"Times New Roman">Desk: 703-689-5875&nbsp;&nbsp; Cell: =
703-598-2434</FONT>

<BR><A HREF=3D"mailto:michael.f.fiumano@sprint.com"><U><FONT =
COLOR=3D"#0000FF" FACE=3D"Times New =
Roman">michael.f.fiumano@sprint.com</FONT></U></A>
</P>
<BR>
<BR>

<P><FONT SIZE=3D1 =
FACE=3D"Tahoma">_____________________________________________ </FONT>

<BR><B><FONT SIZE=3D1 FACE=3D"Tahoma">From: &nbsp;</FONT></B> <FONT =
SIZE=3D1 FACE=3D"Tahoma">Magill, Bernie J [NTK]&nbsp; </FONT>

<BR><B><FONT SIZE=3D1 FACE=3D"Tahoma">Sent:&nbsp;&nbsp;</FONT></B> <FONT =
SIZE=3D1 FACE=3D"Tahoma">Thursday, November 01, 2007 3:35 PM</FONT>

<BR><B><FONT SIZE=3D1 =
FACE=3D"Tahoma">To:&nbsp;&nbsp;&nbsp;&nbsp;</FONT></B> <FONT SIZE=3D1 =
FACE=3D"Tahoma">Fiumano, Michael F [NTK]; Lipsit, William E [NTK]</FONT>

<BR><B><FONT SIZE=3D1 =
FACE=3D"Tahoma">Cc:&nbsp;&nbsp;&nbsp;&nbsp;</FONT></B> <FONT SIZE=3D1 =
FACE=3D"Tahoma">Lemish, Mick L [NTK]</FONT>

<BR><B><FONT SIZE=3D1 =
FACE=3D"Tahoma">Subject:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</FONT>=
</B> <FONT SIZE=3D1 FACE=3D"Tahoma">FW: e2918 status</FONT>

<BR><B><FONT SIZE=3D1 =
FACE=3D"Tahoma">Importance:&nbsp;&nbsp;&nbsp;&nbsp;</FONT></B> <FONT =
SIZE=3D1 FACE=3D"Tahoma">High</FONT>
</P>

<P><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">Michael and =
William,</FONT>
</P>

<P><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">I need your help on =
the scope of E2918.&nbsp; The scope is an issue and IT is having trouble =
figuring out LOEs for this project, due to the program unknowns and its =
growing complexity.&nbsp;</FONT><B> <FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">What is the true scope of E2918?</FONT></B>&nbsp;<FONT =
COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial"> Can you help me work with the =
Planning team to properly define the scope of E2918?&nbsp; I will then =
work to get it expedited and pushed through HLCE.&nbsp; We need to take =
action on this soon, so we don&#8217;t slow down this program.&nbsp; =
This program is also being pushed to a Director level as a scope =
concern, since Kathy Walker wants this program expedited.</FONT></P>

<P><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">Give me a heads up if =
you have any questions.&nbsp; Also, if you want more on the open =
concerns, see the email trail below&#8230;</FONT>
</P>

<P><B><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Bernie Magill, =
PMP</FONT></B>

<BR><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Manager, Program =
Management</FONT>

<BR><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Network Business =
Operations</FONT>

<BR><B><FONT COLOR=3D"#000000" SIZE=3D2 FACE=3D"Arial">SPRINT NEXTEL =
Corporation</FONT></B>

<BR><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">Mobile: (571) =
436-9023</FONT>

<BR><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">Desk: (703) =
433-3864</FONT>

<BR><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">I-Next: =
6-333-3864</FONT>

<BR><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">Email: </FONT><A =
HREF=3D"mailto:Bernard.Magill@sprint.com"><U><FONT COLOR=3D"#0000FF" =
SIZE=3D2 FACE=3D"Arial">Bernard.Magill@sprint.com</FONT></U></A>
</P>
<BR>

<P><FONT SIZE=3D2 =
FACE=3D"Tahoma">_____________________________________________<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">From:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Lemish, Mick L [NTK]<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">Sent:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Tuesday, October 23, 2007 9:53 AM<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">To:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Magill, Bernie J [NTK]<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">Subject:</FONT></B><FONT =
SIZE=3D2 FACE=3D"Tahoma"> FW: e2918 status<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">Importance:</FONT></B><FONT =
SIZE=3D2 FACE=3D"Tahoma"> High</FONT>
</P>

<P><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">FYI&#8230;</FONT>
</P>

<P><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">Sounds like they =
didn&#8217;t put in the card what they really want (sounds much like the =
Pilot.)&nbsp; </FONT>
</P>

<P><FONT COLOR=3D"#800000" SIZE=3D2 =
FACE=3D"Arial">-----------</FONT><FONT COLOR=3D"#000080" FACE=3D"Times =
New Roman"><BR>
</FONT><FONT COLOR=3D"#800000" SIZE=3D2 FACE=3D"Tahoma">Michael =
&#8220;Mick&#8221; Lemish | Sr. Program Manager | Network Business =
Operations | Sprint Nextel Corp. | 703.926.3217(c) | </FONT><A =
HREF=3D"mailto:michael.lemish@sprint.com"><U><FONT COLOR=3D"#0000FF" =
SIZE=3D2 FACE=3D"Tahoma">michael.lemish@sprint.com</FONT></U></A></P>
<BR>

<P><FONT SIZE=3D2 =
FACE=3D"Tahoma">_____________________________________________<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">From:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Alston, Gail [IT]<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">Sent:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Tuesday, October 23, 2007 9:51 AM<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">To:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Alemu, Blen B [NTK]; Eicher, Kari L [DEV]<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">Cc:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Castillo, Karin F [IT]; Lipsit, William E [NTK]; =
Kovacik, Paul A [DEV]; Lemish, Mick L [NTK]; Robertson, Keith K [IT]<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">Subject:</FONT></B><FONT =
SIZE=3D2 FACE=3D"Tahoma"> RE: e2918 status<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">Importance:</FONT></B><FONT =
SIZE=3D2 FACE=3D"Tahoma"> High</FONT>
</P>

<P><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">While I do understand =
the importance of the project the way the sponsor William Lipsit =
described it yesterday, we do need to take a reality check.&nbsp; The =
project now is vastly different from what was described during =
ICA.&nbsp; Here is the approach description that we reviewed during ICA =
and that I entered into Portal:&nbsp; At the time it was limited to =
enhancing the FMS and NRM reports created in E0165.</FONT></P>
<UL><UL>
<P><B><FONT COLOR=3D"#FF0000" SIZE=3D2 FACE=3D"Arial">Reporting =
requirements for FMS and NRM.</FONT></B>

<BR><FONT COLOR=3D"#FF0000" SIZE=3D2 FACE=3D"Arial">User interface to =
allow the user to request the report instead of having to ask the =
development group to generate the report.</FONT></P>

<P><FONT COLOR=3D"#FF0000" SIZE=3D2 FACE=3D"Arial">Add DS3 fields to the =
report created in E0165.&nbsp; Both FMS and NRM will need to enhance the =
E0165 reports.</FONT>
</P>

<P><FONT COLOR=3D"#FF0000" SIZE=3D2 FACE=3D"Arial">Look into the =
possibility of requesting Subex (NetProvision) capabilities.&nbsp; =
Martin mentioned that this project should not need to fund IWNS =
needs.&nbsp; During HLCE, revisit the possibility to make sure that =
there are no requirements</FONT></P>
</UL></UL>
<P><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">Here are the points =
that will impact the schedule:</FONT>

<BR><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">1) William mentioned =
a requirement to automate the migrations, however we need to get more =
specific about what the business requirements are.&nbsp; </FONT></P>

<P><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">2) The scope now is =
requesting a great deal of automation compared with the original scope =
of enhancing a couple of reports.</FONT></P>

<P><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">3) We need to =
identify the business process for performing the migrations before we =
know what needs to be automated.</FONT>

<BR><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">4) There will be a =
need to coordinate updates between Subex, NRM and FMS, and possibly =
CIS.&nbsp; Before we can provide an approach or LOE we need to have a =
better idea of the requirements for automating and timing of the updates =
between the support systems.&nbsp; We are in danger of creating a real =
mess if this is not performed correctly.</FONT></P>

<P><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">5) Subex is a new =
technology that is in the process of being deployed.&nbsp; It has not =
been integrated with the rest of the support systems yet, so it is very =
difficult to provide an LOE for this area.</FONT></P>
<BR>

<P><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">Gail Alston</FONT>

<BR><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">913-762-8723</FONT>
</P>
<BR>

<P><FONT SIZE=3D2 =
FACE=3D"Tahoma">_____________________________________________<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">From:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Alemu, Blen B [NTK]<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">Sent:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Tuesday, October 23, 2007 8:33 AM<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">To:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Eicher, Kari L [DEV]<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">Cc:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Castillo, Karin F [IT]; Alston, Gail [IT]<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">Subject:</FONT></B><FONT =
SIZE=3D2 FACE=3D"Tahoma"> RE: e2918 status</FONT>
</P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Kari/Gail,</FONT>
</P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">What is the =
implication of the change in the complexity of this CARD?&nbsp; Does =
that mean even more time is needed to clarify the changes?</FONT></P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Can you tell me =
exactly what we can expect as far as timelines on this CARD?</FONT>
</P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Thank you.</FONT>
</P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Blen.</FONT>
</P>
<BR>
<BR>
<UL>
<P><FONT FACE=3D"Verdana"></FONT>&nbsp;<FONT SIZE=3D1 =
FACE=3D"Tahoma">-----Original Message-----</FONT>

<BR><B><FONT SIZE=3D1 FACE=3D"Tahoma">From: &nbsp;</FONT></B> <FONT =
SIZE=3D1 FACE=3D"Tahoma">Eicher, Kari L [DEV]&nbsp; </FONT>

<BR><B><FONT SIZE=3D1 FACE=3D"Tahoma">Sent:&nbsp;&nbsp;</FONT></B> <FONT =
SIZE=3D1 FACE=3D"Tahoma">Monday, October 22, 2007 4:43 PM</FONT>

<BR><B><FONT SIZE=3D1 =
FACE=3D"Tahoma">To:&nbsp;&nbsp;&nbsp;&nbsp;</FONT></B> <FONT SIZE=3D1 =
FACE=3D"Tahoma">Alemu, Blen B [NTK]</FONT>

<BR><B><FONT SIZE=3D1 =
FACE=3D"Tahoma">Cc:&nbsp;&nbsp;&nbsp;&nbsp;</FONT></B> <FONT SIZE=3D1 =
FACE=3D"Tahoma">Castillo, Karin F [IT]; Alston, Gail [IT]</FONT>

<BR><B><FONT SIZE=3D1 =
FACE=3D"Tahoma">Subject:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</FONT>=
</B> <FONT SIZE=3D1 FACE=3D"Tahoma">RE: e2918 status</FONT>
</P>

<P><FONT COLOR=3D"#0000FF" FACE=3D"Verdana">Blen,</FONT>
</P>

<P><FONT COLOR=3D"#0000FF" FACE=3D"Verdana">I have IM'ed with the =
assigned IT Solution Architect, Gail Alston, this afternoon.&nbsp; Since =
she will be OOO later this week, she is unable to accommodate the =
expedited request.&nbsp; Additionally, Gail spoke to the POC of E2918 =
and found out that the concept that was described during ICA has become =
very complex; apparently, the BRs have expanded and now the complexity =
of the concept has increased.</FONT></P>

<P><FONT COLOR=3D"#0000FF" FACE=3D"Verdana">Suggestions?</FONT>
</P>

<P><B><FONT COLOR=3D"#0000FF" FACE=3D"Verdana">Kari Eicher</FONT></B>

<BR><FONT COLOR=3D"#0000FF" FACE=3D"Verdana">Enterprise Concept =
Estimation Team</FONT>

<BR><FONT COLOR=3D"#0000FF" FACE=3D"Verdana">(913) 762-7094</FONT>
</P>
<BR>

<P><FONT SIZE=3D1 =
FACE=3D"Tahoma">_____________________________________________ </FONT>

<BR><B><FONT SIZE=3D1 FACE=3D"Tahoma">From: &nbsp;</FONT></B> <FONT =
SIZE=3D1 FACE=3D"Tahoma">Alemu, Blen B [NTK]&nbsp; </FONT>

<BR><B><FONT SIZE=3D1 FACE=3D"Tahoma">Sent:&nbsp;&nbsp;</FONT></B> <FONT =
SIZE=3D1 FACE=3D"Tahoma">Monday, October 22, 2007 3:06 PM</FONT>

<BR><B><FONT SIZE=3D1 =
FACE=3D"Tahoma">To:&nbsp;&nbsp;&nbsp;&nbsp;</FONT></B> <FONT SIZE=3D1 =
FACE=3D"Tahoma">Eicher, Kari L [DEV]</FONT>

<BR><B><FONT SIZE=3D1 =
FACE=3D"Tahoma">Subject:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</FONT>=
</B> <FONT SIZE=3D1 FACE=3D"Tahoma">RE: e2918 status</FONT>
</P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">The HLCE schedule was =
based on the Project Start date (12/05/07) that was initially provided =
by the sponsor but now the executives are pushing for it to start =
ASAP.\</FONT></P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Blen.</FONT>
</P>
<BR>
<BR>
<UL>
<P><FONT FACE=3D"Verdana"></FONT>&nbsp;<FONT SIZE=3D1 =
FACE=3D"Tahoma">-----Original Message-----</FONT>

<BR><B><FONT SIZE=3D1 FACE=3D"Tahoma">From: &nbsp;</FONT></B> <FONT =
SIZE=3D1 FACE=3D"Tahoma">Eicher, Kari L [DEV]&nbsp; </FONT>

<BR><B><FONT SIZE=3D1 FACE=3D"Tahoma">Sent:&nbsp;&nbsp;</FONT></B> <FONT =
SIZE=3D1 FACE=3D"Tahoma">Monday, October 22, 2007 3:53 PM</FONT>

<BR><B><FONT SIZE=3D1 =
FACE=3D"Tahoma">To:&nbsp;&nbsp;&nbsp;&nbsp;</FONT></B> <FONT SIZE=3D1 =
FACE=3D"Tahoma">Alemu, Blen B [NTK]</FONT>

<BR><B><FONT SIZE=3D1 =
FACE=3D"Tahoma">Subject:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</FONT>=
</B> <FONT SIZE=3D1 FACE=3D"Tahoma">RE: e2918 status</FONT>
</P>

<P><FONT COLOR=3D"#0000FF" FACE=3D"Verdana">Blen,</FONT>
</P>

<P><FONT COLOR=3D"#0000FF" FACE=3D"Verdana">Do you know why this wasn't =
submitted to HLCE earlier than last week?</FONT>
</P>

<P><FONT COLOR=3D"#0000FF" FACE=3D"Verdana">Thanks,</FONT>
</P>
<BR>

<P><B><FONT COLOR=3D"#0000FF" FACE=3D"Verdana">Kari Eicher</FONT></B>

<BR><FONT COLOR=3D"#0000FF" FACE=3D"Verdana">Enterprise Concept =
Estimation Team</FONT>

<BR><FONT COLOR=3D"#0000FF" FACE=3D"Verdana">(913) 762-7094</FONT>
</P>
<BR>

<P><FONT SIZE=3D1 =
FACE=3D"Tahoma">_____________________________________________ </FONT>

<BR><B><FONT SIZE=3D1 FACE=3D"Tahoma">From: &nbsp;</FONT></B> <FONT =
SIZE=3D1 FACE=3D"Tahoma">Alemu, Blen B [NTK]&nbsp; </FONT>

<BR><B><FONT SIZE=3D1 FACE=3D"Tahoma">Sent:&nbsp;&nbsp;</FONT></B> <FONT =
SIZE=3D1 FACE=3D"Tahoma">Monday, October 22, 2007 2:21 PM</FONT>

<BR><B><FONT SIZE=3D1 =
FACE=3D"Tahoma">To:&nbsp;&nbsp;&nbsp;&nbsp;</FONT></B> <FONT SIZE=3D1 =
FACE=3D"Tahoma">Eicher, Kari L [DEV]</FONT>

<BR><B><FONT SIZE=3D1 =
FACE=3D"Tahoma">Subject:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</FONT>=
</B> <FONT SIZE=3D1 FACE=3D"Tahoma">RE: e2918 status</FONT>
</P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Kari,</FONT>
</P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">This project is being =
escalated at the Kathy Walker level.&nbsp; Anything you can do to =
expedite this will be greatly appreciated.</FONT></P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Thank you.</FONT>

<BR><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Blen.</FONT>
</P>
<UL>
<P><FONT FACE=3D"Verdana"></FONT>&nbsp;<FONT SIZE=3D1 =
FACE=3D"Tahoma">-----Original Message-----</FONT>

<BR><B><FONT SIZE=3D1 FACE=3D"Tahoma">From: &nbsp;</FONT></B> <FONT =
SIZE=3D1 FACE=3D"Tahoma">Eicher, Kari L [DEV]&nbsp; </FONT>

<BR><B><FONT SIZE=3D1 FACE=3D"Tahoma">Sent:&nbsp;&nbsp;</FONT></B> <FONT =
SIZE=3D1 FACE=3D"Tahoma">Monday, October 22, 2007 11:00 AM</FONT>

<BR><B><FONT SIZE=3D1 =
FACE=3D"Tahoma">To:&nbsp;&nbsp;&nbsp;&nbsp;</FONT></B> <FONT SIZE=3D1 =
FACE=3D"Tahoma">Alemu, Blen B [NTK]; Alston, Gail [IT]</FONT>

<BR><B><FONT SIZE=3D1 =
FACE=3D"Tahoma">Cc:&nbsp;&nbsp;&nbsp;&nbsp;</FONT></B> <FONT SIZE=3D1 =
FACE=3D"Tahoma">Davis, Janet R [DEV]</FONT>

<BR><B><FONT SIZE=3D1 =
FACE=3D"Tahoma">Subject:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</FONT>=
</B> <FONT SIZE=3D1 FACE=3D"Tahoma">RE: e2918 status</FONT>
</P>
<BR>

<P><FONT COLOR=3D"#0000FF" FACE=3D"Verdana">Blen,</FONT>
</P>

<P><FONT COLOR=3D"#0000FF" FACE=3D"Verdana">Currently this concept is =
scheduled for Approach on 11/1/07 and Estimation on 11/9/07.&nbsp; It =
was delayed one week in HLCE since the assigned Solution Architect, Gail =
Alston, will be OOO.</FONT></P>

<P><FONT COLOR=3D"#0000FF" FACE=3D"Verdana">Gail, do you have any =
suggestions?</FONT>
</P>

<P><FONT COLOR=3D"#0000FF" FACE=3D"Verdana">Thanks,</FONT>
</P>

<P><B><FONT COLOR=3D"#0000FF" FACE=3D"Verdana">Kari Eicher</FONT></B>

<BR><FONT COLOR=3D"#0000FF" FACE=3D"Verdana">Enterprise Concept =
Estimation Team</FONT>

<BR><FONT COLOR=3D"#0000FF" FACE=3D"Verdana">(913) 762-7094</FONT>
</P>
<BR>

<P><FONT SIZE=3D1 =
FACE=3D"Tahoma">_____________________________________________ </FONT>

<BR><B><FONT SIZE=3D1 FACE=3D"Tahoma">From: &nbsp;</FONT></B> <FONT =
SIZE=3D1 FACE=3D"Tahoma">Alemu, Blen B [NTK]&nbsp; </FONT>

<BR><B><FONT SIZE=3D1 FACE=3D"Tahoma">Sent:&nbsp;&nbsp;</FONT></B> <FONT =
SIZE=3D1 FACE=3D"Tahoma">Monday, October 22, 2007 9:25 AM</FONT>

<BR><B><FONT SIZE=3D1 =
FACE=3D"Tahoma">To:&nbsp;&nbsp;&nbsp;&nbsp;</FONT></B> <FONT SIZE=3D1 =
FACE=3D"Tahoma">Eicher, Kari L [DEV]; Davis, Janet R [DEV]</FONT>

<BR><B><FONT SIZE=3D1 =
FACE=3D"Tahoma">Subject:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</FONT>=
</B> <FONT SIZE=3D1 FACE=3D"Tahoma">FW: e2918 status</FONT>
</P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Kari/Janet,</FONT>
</P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Is there any way to =
accelerate HLCE exit for this CARD?</FONT>
</P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Blen.</FONT>
</P>

<P><FONT FACE=3D"Arial"></FONT>&nbsp;<FONT SIZE=3D1 =
FACE=3D"Tahoma">-----Original Message-----</FONT>

<BR><B><FONT SIZE=3D1 FACE=3D"Tahoma">From: &nbsp;</FONT></B> <FONT =
SIZE=3D1 FACE=3D"Tahoma">Haskins, Eric D [NTK]&nbsp; </FONT>

<BR><B><FONT SIZE=3D1 FACE=3D"Tahoma">Sent:&nbsp;&nbsp;</FONT></B> <FONT =
SIZE=3D1 FACE=3D"Tahoma">Monday, October 22, 2007 10:23 AM</FONT>

<BR><B><FONT SIZE=3D1 =
FACE=3D"Tahoma">To:&nbsp;&nbsp;&nbsp;&nbsp;</FONT></B> <FONT SIZE=3D1 =
FACE=3D"Tahoma">Kupka, Leslie C [NTK]; Scott, Carla G [NTK]; Lunsford, =
Veronica [NTK]; Ames, Lori L [NTK]; Alemu, Blen B [NTK]</FONT>

<BR><B><FONT SIZE=3D1 =
FACE=3D"Tahoma">Subject:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</FONT>=
</B> <FONT SIZE=3D1 FACE=3D"Tahoma">RE: e2918 status</FONT>
</P>

<P><FONT COLOR=3D"#0000FF" FACE=3D"Arial">Leslie,</FONT>
</P>

<P><FONT COLOR=3D"#0000FF" FACE=3D"Arial">Is there any opportunity to =
accelerate HLCE exit? </FONT>
</P>

<P><FONT COLOR=3D"#0000FF" FACE=3D"Arial">Eric</FONT>
</P>

<P><FONT SIZE=3D2 =
FACE=3D"Tahoma">_____________________________________________<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">From:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Kupka, Leslie C [NTK]<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">Sent:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Monday, October 22, 2007 9:21 AM<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">To:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Scott, Carla G [NTK]; Lunsford, Veronica [NTK]; Ames, =
Lori L [NTK]; Alemu, Blen B [NTK]<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">Cc:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Haskins, Eric D [NTK]<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">Subject:</FONT></B><FONT =
SIZE=3D2 FACE=3D"Tahoma"> RE: e2918 status</FONT>
</P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Carla and =
Lori,</FONT>
</P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Blen has confirmed =
the</FONT><B><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial"> HLCE exit =
is s</FONT><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Microsoft Sans =
Serif">cheduled for 11/2</FONT></B><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Microsoft Sans Serif">. I will note to watch closely and =
coordinate an expedited resourcing of NS core team. Please let me know =
if questions or concerns.</FONT></P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Microsoft Sans Serif">Thanks =
to all,</FONT>
</P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Microsoft Sans Serif">Leslie =
Kupka</FONT>
</P>

<P><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Comic Sans =
MS">_____________________________________________________________________=
__________________</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Comic Sans MS">Leslie Kupka</FONT><FONT =
COLOR=3D"#FF0000" SIZE=3D2 FACE=3D"Comic Sans MS"></FONT> <FONT =
COLOR=3D"#000080" SIZE=3D2 FACE=3D"Comic Sans MS">|</FONT><FONT SIZE=3D2 =
FACE=3D"Comic Sans MS">=A0Pipeline Management - Network Business =
Operations</FONT><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Comic Sans =
MS">|</FONT> <FONT SIZE=3D2 FACE=3D"Comic Sans MS">Voice: =
913.794.4109</FONT><FONT COLOR=3D"#FF0000" SIZE=3D2 FACE=3D"Comic Sans =
MS"></FONT> <FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Comic Sans =
MS">|</FONT><FONT SIZE=3D2 FACE=3D"Comic Sans MS"> Mobile: =
816.304.5766</FONT>
</P>
<BR>
<BR>

<P><FONT SIZE=3D1 =
FACE=3D"Tahoma">_____________________________________________ </FONT>

<BR><B><FONT SIZE=3D1 FACE=3D"Tahoma">From: &nbsp;</FONT></B> <FONT =
SIZE=3D1 FACE=3D"Tahoma">Scott, Carla G [NTK]&nbsp; </FONT>

<BR><B><FONT SIZE=3D1 FACE=3D"Tahoma">Sent:&nbsp;&nbsp;</FONT></B> <FONT =
SIZE=3D1 FACE=3D"Tahoma">Monday, October 22, 2007 8:19 AM</FONT>

<BR><B><FONT SIZE=3D1 =
FACE=3D"Tahoma">To:&nbsp;&nbsp;&nbsp;&nbsp;</FONT></B> <FONT SIZE=3D1 =
FACE=3D"Tahoma">Lunsford, Veronica [NTK]; Kupka, Leslie C [NTK]; Ames, =
Lori L [NTK]; Alemu, Blen B [NTK]</FONT>

<BR><B><FONT SIZE=3D1 =
FACE=3D"Tahoma">Cc:&nbsp;&nbsp;&nbsp;&nbsp;</FONT></B> <FONT SIZE=3D1 =
FACE=3D"Tahoma">Haskins, Eric D [NTK]</FONT>

<BR><B><FONT SIZE=3D1 =
FACE=3D"Tahoma">Subject:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</FONT>=
</B> <FONT SIZE=3D1 FACE=3D"Tahoma">RE: e2918 status</FONT>
</P>

<P><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">Thanks for the =
update.</FONT>
</P>

<P><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">Yes, we need to get =
the core team assigned quickly &#8211; at least to do the high level =
assessment for Kathy.</FONT>
</P>

<P><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">Carla</FONT>
</P>

<P><FONT SIZE=3D2 =
FACE=3D"Tahoma">_____________________________________________<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">From:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Lunsford, Veronica [NTK]<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">Sent:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Sunday, October 21, 2007 11:38 PM<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">To:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Kupka, Leslie C [NTK]; Scott, Carla G [NTK]; Ames, Lori =
L [NTK]; Alemu, Blen B [NTK]<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">Subject:</FONT></B><FONT =
SIZE=3D2 FACE=3D"Tahoma"> RE: e2918 status</FONT>
</P>

<P><FONT COLOR=3D"#0000FF" FACE=3D"Book Antiqua">Good evening,</FONT>
</P>

<P><FONT COLOR=3D"#0000FF" FACE=3D"Book Antiqua">E2918/114367 was on the =
10/15/07 1: N list at number 217.&nbsp; It was listed under the concept =
number.</FONT>
</P>

<P><FONT COLOR=3D"#0000FF" FACE=3D"Book Antiqua">Thank you,</FONT>
</P>

<P><FONT COLOR=3D"#0000FF" FACE=3D"Book Antiqua">Veronica<I></I></FONT>

<BR><I><FONT COLOR=3D"#0000FF" FACE=3D"Book =
Antiqua">703-906-3278</FONT></I>

<BR><FONT COLOR=3D"#0000FF" FACE=3D"Book Antiqua">=A0</FONT>

<BR><FONT COLOR=3D"#FF0000" SIZE=3D1 FACE=3D"Arial">This message =
(including any attachments) contains confidential information intended =
for a specific individual and purpose, and is protected by law.=A0 If =
you are not the intended recipient, you should delete this message.=A0 =
Any disclosure, copying, or distribution of this message, or the taking =
of any action based on it, is strictly prohibited.</FONT></P>
<BR>

<P><FONT SIZE=3D2 =
FACE=3D"Tahoma">_____________________________________________<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">From:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Kupka, Leslie C [NTK]<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">Sent:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Sunday, October 21, 2007 11:15 PM<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">To:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Scott, Carla G [NTK]; Ames, Lori L [NTK]; Alemu, Blen B =
[NTK]<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">Cc:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Lunsford, Veronica [NTK]<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">Subject:</FONT></B><FONT =
SIZE=3D2 FACE=3D"Tahoma"> RE: e2918 status</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Carla and Lori,</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">RE: E</FONT><B><FONT SIZE=3D2 =
FACE=3D"Arial">2918 / 114367: IT Development support for 7500 =
Migrations:</FONT></B> <FONT SIZE=3D2 FACE=3D"Arial">The referenced =
project is in OPX however, I did not find on the 1:N List of last week. =
It does have a concept exit of 12/5 so I will add to the 4Q07 Lock List. =
Resourcing will be triggered by exit from HLCE. Would you like me to =
expedite resource assignments after exiting HLCE?</FONT></P>

<P><B><FONT SIZE=3D2 FACE=3D"Arial">Veronica -</FONT></B> <FONT SIZE=3D2 =
FACE=3D"Arial">Since the project is in OPX - did prioritization trigger =
the addition to OPX and it will show up this coming week on the =
1:N?</FONT></P>

<P><B><FONT SIZE=3D2 FACE=3D"Arial">Blen -</FONT></B> <FONT SIZE=3D2 =
FACE=3D"Arial">When do you forecast E2918 will exit HLCE? Is the 12/5 =
concept exit doable based on that?</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Please advise if questions or =
concerns.</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">Thank you,</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Leslie Kupka</FONT>

<BR><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Comic Sans =
MS">_____________________________________________________________________=
__________________</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Comic Sans MS">Leslie Kupka</FONT><FONT =
COLOR=3D"#FF0000" SIZE=3D2 FACE=3D"Comic Sans MS"></FONT> <FONT =
COLOR=3D"#000080" SIZE=3D2 FACE=3D"Comic Sans MS">|</FONT><FONT SIZE=3D2 =
FACE=3D"Comic Sans MS">=A0Pipeline Management - Network Business =
Operations</FONT><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Comic Sans =
MS">|</FONT> <FONT SIZE=3D2 FACE=3D"Comic Sans MS">Voice: =
913.794.4109</FONT><FONT COLOR=3D"#FF0000" SIZE=3D2 FACE=3D"Comic Sans =
MS"></FONT> <FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Comic Sans =
MS">|</FONT><FONT SIZE=3D2 FACE=3D"Comic Sans MS"> Mobile: =
816.304.5766</FONT>
</P>
<BR>
<BR>

<P><FONT SIZE=3D1 =
FACE=3D"Tahoma">_____________________________________________ </FONT>

<BR><B><FONT SIZE=3D1 FACE=3D"Tahoma">From: &nbsp;</FONT></B> <FONT =
SIZE=3D1 FACE=3D"Tahoma">Scott, Carla G [NTK]&nbsp; </FONT>

<BR><B><FONT SIZE=3D1 FACE=3D"Tahoma">Sent:&nbsp;&nbsp;</FONT></B> <FONT =
SIZE=3D1 FACE=3D"Tahoma">Friday, October 19, 2007 3:50 PM</FONT>

<BR><B><FONT SIZE=3D1 =
FACE=3D"Tahoma">To:&nbsp;&nbsp;&nbsp;&nbsp;</FONT></B> <FONT SIZE=3D1 =
FACE=3D"Tahoma">Kupka, Leslie C [NTK]; Ames, Lori L [NTK]</FONT>

<BR><B><FONT SIZE=3D1 =
FACE=3D"Tahoma">Subject:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</FONT>=
</B> <FONT SIZE=3D1 FACE=3D"Tahoma">e2918 status</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Hello,</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Can you tell me where e2918 is in the =
pipeline?</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">Kathy W is asking for information, and =
I don&#8217;t believe we&#8217;ve assigned a core team yet (based on =
OPX2).</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">Has it been estimated yet or do we =
know when the PM will be assigned?</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Thanks,</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">Carla</FONT>

<BR><B><FONT COLOR=3D"#808080" SIZE=3D2 FACE=3D"Arial">Carla Scott l =
Sprint Nextel l</FONT></B><FONT COLOR=3D"#808080" SIZE=3D2 =
FACE=3D"Arial"> Network Services</FONT>

<BR><FONT COLOR=3D"#808080" SIZE=3D1 FACE=3D"Arial">Strategy, Pipeline =
Plng &amp; Customer Experience</FONT>

<BR><FONT COLOR=3D"#808080" SIZE=3D1 FACE=3D"Arial">Desk: =
913-794-4041&nbsp; Mobile: 703-856-1363&nbsp; 164*100*12080</FONT>
</P>
</UL></UL></UL>
</BODY>
</HTML>
------_=_NextPart_001_01C81CD4.A389FE19--





From l3vpn-bounces@ietf.org Thu Nov 01 23:13:05 2007
Return-path: <l3vpn-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1InmrW-0006tg-FZ; Thu, 01 Nov 2007 23:06:22 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1InmrU-0006oK-Fu
	for l3vpn@ietf.org; Thu, 01 Nov 2007 23:06:20 -0400
Received: from outbound-va3.frontbridge.com ([216.32.180.16]
	helo=outbound5-va3-R.bigfish.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1InmrP-0008Lt-4d
	for l3vpn@ietf.org; Thu, 01 Nov 2007 23:06:15 -0400
Received: from outbound5-va3.bigfish.com (localhost.localdomain [127.0.0.1])
	by outbound5-va3-R.bigfish.com (Postfix) with ESMTP id ACA89188057E
	for <l3vpn@ietf.org>; Fri,  2 Nov 2007 02:59:46 +0000 (UTC)
Received: from mail3-va3-R.bigfish.com (si1-va3 [10.7.14.5])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by outbound5-va3.bigfish.com (Postfix) with ESMTP id AB3511B48049
	for <l3vpn@ietf.org>; Fri,  2 Nov 2007 02:59:46 +0000 (UTC)
Received: from mail3-va3 (localhost.localdomain [127.0.0.1])
	by mail3-va3-R.bigfish.com (Postfix) with ESMTP id 7E79D1AF8E22
	for <l3vpn@ietf.org>; Fri,  2 Nov 2007 03:06:14 +0000 (UTC)
X-BigFish: V
X-MS-Exchange-Organization-Antispam-Report: OrigIP: 207.40.188.14; Service: EHS
Received: by mail3-va3 (MessageSwitch) id 1193972774446078_18157;
	Fri,  2 Nov 2007 03:06:14 +0000 (UCT)
Received: from smtpgw6.it.sprintspectrum.com (smtpgw6.sprintspectrum.com
	[207.40.188.14])
	by mail3-va3.bigfish.com (Postfix) with ESMTP id 56DA91AF006D
	for <l3vpn@ietf.org>; Fri,  2 Nov 2007 03:06:14 +0000 (UTC)
Received: from mailhost.sprintspectrum.com (smtpgw8.it.sprintspectrum.com
	[207.40.65.56])
	by smtpgw6.it.sprintspectrum.com (8.12.11.Beta0/8.12.8) with ESMTP id
	lA236Dul029498
	for <l3vpn@ietf.org>; Thu, 1 Nov 2007 22:06:14 -0500 (CDT)
Received: from pdawg06a.ad.sprint.com (PDAWG06A.corp.sprint.com [10.122.2.33])
	by mailhost.sprintspectrum.com (Switch-3.2.5/Switch-3.2.5) with
	ESMTP id lA236DbQ009062
	for <l3vpn@ietf.org>; Thu, 1 Nov 2007 22:06:13 -0500 (CDT)
Received: from PLSWB02C.ad.sprint.com ([208.10.70.215]) by
	pdawg06a.ad.sprint.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 1 Nov 2007 22:06:13 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C81CFD.532B7F79"
Date: Thu, 1 Nov 2007 22:06:12 -0500
Message-ID: <6B1FF00C9F2BFD4EB894C686C440C2330FC576FF@PLSWB02C.ad.sprint.com>
In-Reply-To: <B63855F512D91449AA81FDF35C8CA08802A927@Sprocket.Soapstone.local>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: e2918 status
Thread-Index: AcgSkZ133b/+zvYkSlWS7jvde93HNQBxMPCwAAGZTJAAFD7HMAACIxoAAAAoJnAAABAjQAABNJCQAAkkZxAAASRUsAAAXyCgAAE9+oAAI0WFIAAAOu1QAACOiiAB0EWycAAFiPeQAAD3QNAACZIKoA==
References: <659DE65A3D2B0C49ACDE39BB0963154A067DCD89@PLSWB10C.ad.sprint.com>
	<6B1FF00C9F2BFD4EB894C686C440C2330FC576FE@PLSWB02C.ad.sprint.com>
	<B63855F512D91449AA81FDF35C8CA08802A927@Sprocket.Soapstone.local>
From: "Fiumano, Michael F [NTK]" <Michael.F.Fiumano@sprint.com>
To: <l3vpn@ietf.org>
X-OriginalArrivalTime: 02 Nov 2007 03:06:13.0606 (UTC)
	FILETIME=[53AAB860:01C81CFD]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 789c141a303c09204b537a4078e2a63f
Subject: RE: e2918 status
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l3vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>
Errors-To: l3vpn-bounces@ietf.org

This is a multi-part message in MIME format.

------_=_NextPart_001_01C81CFD.532B7F79
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Oops....forgive me all :)
=20

Thanks,=20
Michael Fiumano=20
Manager, IP Edge Development=20
Data Network Development=20
Desk: 703-689-5875   Cell: 703-598-2434=20
michael.f.fiumano@sprint.com <mailto:michael.f.fiumano@sprint.com> =20

=20



------_=_NextPart_001_01C81CFD.532B7F79
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:v =3D=20
"urn:schemas-microsoft-com:vml" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word" xmlns:st1 =3D=20
"urn:schemas-microsoft-com:office:smarttags"><HEAD><TITLE>RE: e2918 =
status</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3199" name=3DGENERATOR><!--[if !mso]>
<STYLE>v\:* {
	BEHAVIOR: url(#default#VML)
}
o\:* {
	BEHAVIOR: url(#default#VML)
}
w\:* {
	BEHAVIOR: url(#default#VML)
}
.shape {
	BEHAVIOR: url(#default#VML)
}
</STYLE>
<![endif]--><o:SmartTagType name=3D"City"=20
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"></o:SmartTagT=
ype><o:SmartTagType=20
name=3D"place"=20
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"></o:SmartTagT=
ype><!--[if !mso]>
<STYLE>st1\:* {
	BEHAVIOR: url(#default#ieooui)
}
</STYLE>
<![endif]-->
<STYLE>@font-face {
	font-family: Wingdings;
}
@font-face {
	font-family: Tahoma;
}
@font-face {
	font-family: Lucida Handwriting;
}
@font-face {
	font-family: Verdana;
}
@font-face {
	font-family: Microsoft Sans Serif;
}
@font-face {
	font-family: Comic Sans MS;
}
@font-face {
	font-family: Book Antiqua;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; }
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
	COLOR: blue; TEXT-DECORATION: underline
}
P {
	FONT-SIZE: 12pt; MARGIN-LEFT: 0in; MARGIN-RIGHT: 0in; FONT-FAMILY: =
"Times New Roman"; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto
}
SPAN.EmailStyle18 {
	COLOR: navy; FONT-FAMILY: Arial; mso-style-type: personal-reply
}
DIV.Section1 {
	page: Section1
}
OL {
	MARGIN-BOTTOM: 0in
}
UL {
	MARGIN-BOTTOM: 0in
}
</STYLE>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]--></HEAD>
<BODY lang=3DEN-US vLink=3Dblue link=3Dblue>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D234210503-02112007>Oops....forgive me all :)</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV><!-- =
Converted from text/rtf format -->
<P><FONT face=3D"Times New Roman">Thanks,</FONT> <BR><FONT=20
face=3D"Lucida Handwriting">Michael Fiumano</FONT> <BR><FONT=20
face=3D"Times New Roman">Manager, IP Edge Development</FONT> <BR><FONT=20
face=3D"Times New Roman">Data Network Development</FONT> <BR><FONT=20
face=3D"Times New Roman">Desk: 703-689-5875&nbsp;&nbsp; Cell: =
703-598-2434</FONT>=20
<BR><A href=3D"mailto:michael.f.fiumano@sprint.com"><U><FONT=20
face=3D"Times New Roman" =
color=3D#0000ff>michael.f.fiumano@sprint.com</FONT></U></A>=20
</P>
<DIV><FONT face=3DArial color=3D#0000ff =
size=3D2></FONT>&nbsp;</DIV><FONT face=3DArial=20
color=3D#0000ff size=3D2></FONT><BR></BODY></HTML>

------_=_NextPart_001_01C81CFD.532B7F79--





From l3vpn-bounces@ietf.org Mon Nov 12 17:40:11 2007
Return-path: <l3vpn-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Irhwo-0004SE-Tx; Mon, 12 Nov 2007 17:40:02 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Irhwn-0004P5-Kj
	for l3vpn@ietf.org; Mon, 12 Nov 2007 17:40:01 -0500
Received: from exprod7og102.obsmtp.com ([64.18.2.157])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Irhwn-00074a-6f
	for l3vpn@ietf.org; Mon, 12 Nov 2007 17:40:01 -0500
Received: from source ([66.129.224.36]) by exprod7ob102.postini.com
	([64.18.6.12]) with SMTP; Mon, 12 Nov 2007 14:39:10 PST
Received: from proton.jnpr.net ([10.10.2.37]) by gamma.jnpr.net with Microsoft
	SMTPSVC(6.0.3790.1830); Mon, 12 Nov 2007 14:38:54 -0800
Received: from [172.23.1.67] ([172.23.1.67] RDNS failed) by proton.jnpr.net
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 12 Nov 2007 17:38:52 -0500
Message-ID: <4738D5F5.8060205@juniper.net>
Date: Mon, 12 Nov 2007 17:38:45 -0500
From: Ron Bonica <rbonica@juniper.net>
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: l3vpn@ietf.org
X-Enigmail-Version: 0.93.0.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 12 Nov 2007 22:38:52.0630 (UTC)
	FILETIME=[CD0B4760:01C8257C]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Subject: Agenda for IETF 70
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l3vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>
Errors-To: l3vpn-bounces@ietf.org

Folks,

So far, the following people have requested agenda time:

T. Morin - draft-morin-l3vpn-mvpn-considerations-01
M. Napiera - draft-mnapierala-mvpn-part-reqt
B. Davies - draft-davie-tsvwg-rsvp-l3vpn
E. Rosen & R. Aggarwal - draft-ietf-l3vpn-2547bis-mcast
E. Rosen - TBD

Any others?

                      Ron




From l3vpn-bounces@ietf.org Mon Nov 12 18:15:38 2007
Return-path: <l3vpn-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IriVD-00044B-CW; Mon, 12 Nov 2007 18:15:35 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IriVC-00043i-QB
	for l3vpn@ietf.org; Mon, 12 Nov 2007 18:15:34 -0500
Received: from 28.2a.0540.static.theplanet.com ([64.5.42.40]
	helo=mail.zteusa.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IriVA-00023h-FA
	for l3vpn@ietf.org; Mon, 12 Nov 2007 18:15:34 -0500
Received: from ywu (host140.atlra.hyatthsiagx.com [208.48.21.140])
	by mail.zteusa.com (8.13.4/8.13.4/SuSE Linux 0.7) with ESMTP id
	lACNFjbl028878
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Mon, 12 Nov 2007 17:15:46 -0600
From: "Yingzhe Wu" <yingzhe.wu@zteusa.com>
To: "'Ron Bonica'" <rbonica@juniper.net>, <l3vpn@ietf.org>
References: <4738D5F5.8060205@juniper.net>
In-Reply-To: <4738D5F5.8060205@juniper.net>
Date: Mon, 12 Nov 2007 15:15:22 -0800
Message-ID: <001401c82581$e6784630$b368d290$@wu@zteusa.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcglfRMA8OEOlmiLQZKNoEFKYgDsyQAA7iXg
Content-Language: en-us
X-Spam-Score: 1.2 (+)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Cc: denghui@chinamobile.com
Subject: RE: Agenda for IETF 70
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l3vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>
Errors-To: l3vpn-bounces@ietf.org

Hi Ron,
There is a new draft from ZTEUSA at the following link:
http://www.ietf.org/internet-drafts/draft-wu-l3vpn-ipsec-gre-00.txt

Could you allocate a timeslot for this presentation?
And any comments on the reflector are welcome too.

Thanks,
Yingzhe
ZTE USA

-----Original Message-----
From: Ron Bonica [mailto:rbonica@juniper.net] 
Sent: Monday, November 12, 2007 2:39 PM
To: l3vpn@ietf.org
Subject: Agenda for IETF 70

Folks,

So far, the following people have requested agenda time:

T. Morin - draft-morin-l3vpn-mvpn-considerations-01
M. Napiera - draft-mnapierala-mvpn-part-reqt
B. Davies - draft-davie-tsvwg-rsvp-l3vpn
E. Rosen & R. Aggarwal - draft-ietf-l3vpn-2547bis-mcast
E. Rosen - TBD

Any others?

                      Ron





From l3vpn-bounces@ietf.org Wed Nov 14 01:54:42 2007
Return-path: <l3vpn-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IsC8y-0001z0-Hi; Wed, 14 Nov 2007 01:54:36 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IsC8v-0001se-TK
	for l3vpn@ietf.org; Wed, 14 Nov 2007 01:54:34 -0500
Received: from [221.130.253.133] (helo=cmccmta)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IsC8u-0005HI-AD
	for l3vpn@ietf.org; Wed, 14 Nov 2007 01:54:33 -0500
Received: from denghui ([10.1.6.121])
	by mail.chinamobile.com (Lotus Domino Release 6.5.5FP1)
	with SMTP id 2007111414540943-32761 ;
	Wed, 14 Nov 2007 14:54:09 +0800 
From: "Hui Deng" <denghui@chinamobile.com>
To: <l3vpn@ietf.org>
Date: Wed, 14 Nov 2007 14:53:57 +0800
Message-ID: <00d101c8268b$20d15b00$7906010a@denghui>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
Thread-Index: AcgmiyC3MpCOTWyuT9KvwmVv4b8aZg==
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
X-MIMETrack: Itemize by SMTP Server on jtgsml01/servers/cmcc(Release 6.5.5FP1
	| April 14, 2006) at 2007-11-14 14:54:09,
	Serialize by Router on cmccmta/servers/cmcc(Release 6.5.5FP1 | April 14,
	2006) at 2007-11-14 14:54:32,
	Serialize complete at 2007-11-14 14:54:32
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_00D2_01C826CE.2EF49B00"
X-Spam-Score: 0.7 (/)
X-Scan-Signature: 2b2ad76aced9b1d558e34a970a85c027
Subject: draft-wu-l3vpn-ipsec-gre-00
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l3vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>
Errors-To: l3vpn-bounces@ietf.org

This is a multi-part message in MIME format.

------=_NextPart_000_00D2_01C826CE.2EF49B00
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset="us-ascii"

Hello, all

 

Below is our new draft which posted recently,

 <http://www.ietf.org/internet-drafts/draft-wu-l3vpn-ipsec-gre-00.txt>
http://www.ietf.org/internet-drafts/draft-wu-l3vpn-ipsec-gre-00.txt

Abstract
   Provider-Provisioned Virtual Private Network (PPVPN)[RFC4110] uses
   some forms of IP tunneling schemes to tunnel VPN traffic.  Possible
   candidates are GRE, IP-in-IP, IPsec and MPLS.  The candidate
   tunneling scheme should provide multiplexing capability, as well as
   dynamic tunnel setup and maintenance capability.  Additionally,
   security is required if the VPN traffic is traversing public Internet
   or across Service Provider domains.  Each above candidate by itself
   is not sufficient to meet all these requirements.  This document
   describes a method of using IPsec signaling (i.e, IKE) to setup a GRE
   tunnel.  This IPsec GRE tunnel may be used as the candidate tunneling
   scheme in PPVPN network or remote access compulsory VPN.  This
   document also defines a way how the Key field in GRE header is used
   in IPsec GRE tunnel setup.

 

 

You are comments are really appreciated,

Many thanks for your help

 

Best regards,

 

-Hui

 

 


------=_NextPart_000_00D2_01C826CE.2EF49B00
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset="us-ascii"

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:&#23435;&#20307;;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"\@&#23435;&#20307;";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:10.5pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
pre
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:&#23435;&#20307;;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
 /* Page Definitions */
 @page Section1
	{size:595.3pt 841.9pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;
	layout-grid:15.6pt;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DZH-CN link=3Dblue vlink=3Dpurple =
style=3D'text-justify-trim:punctuation'>

<div class=3DSection1 style=3D'layout-grid:15.6pt'>

<p class=3DMsoNormal><font size=3D1 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
9.0pt;font-family:Arial'>Hello, all<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D1 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
9.0pt;font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D1 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
9.0pt;font-family:Arial'>Below is our new draft which posted =
recently,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D1 face=3DArial><span =
style=3D'font-size:9.0pt;
font-family:Arial'><a
href=3D"http://www.ietf.org/internet-drafts/draft-wu-l3vpn-ipsec-gre-00.t=
xt"><span
lang=3DEN-US>http://www.ietf.org/internet-drafts/draft-wu-l3vpn-ipsec-gre=
-00.txt</span></a></span></font><font
size=3D1 face=3DArial><span lang=3DEN-US =
style=3D'font-size:9.0pt;font-family:Arial'><o:p></o:p></span></font></p>=


<pre><font size=3D3 face=3D&#23435;&#20307;><span lang=3DEN-US =
style=3D'font-size:12.0pt'>Abstract<o:p></o:p></span></font></pre><pre><f=
ont
size=3D3 face=3D&#23435;&#20307;><span lang=3DEN-US =
style=3D'font-size:12.0pt'>&nbsp;&nbsp; Provider-Provisioned Virtual =
Private Network (PPVPN)[RFC4110] =
uses<o:p></o:p></span></font></pre><pre><font
size=3D3 face=3D&#23435;&#20307;><span lang=3DEN-US =
style=3D'font-size:12.0pt'>&nbsp;&nbsp; some forms of IP tunneling =
schemes to tunnel VPN traffic.&nbsp; =
Possible<o:p></o:p></span></font></pre><pre><font
size=3D3 face=3D&#23435;&#20307;><span lang=3DEN-US =
style=3D'font-size:12.0pt'>&nbsp;&nbsp; candidates are GRE, IP-in-IP, =
IPsec and MPLS.&nbsp; The =
candidate<o:p></o:p></span></font></pre><pre><font
size=3D3 face=3D&#23435;&#20307;><span lang=3DEN-US =
style=3D'font-size:12.0pt'>&nbsp;&nbsp; tunneling scheme should provide =
multiplexing capability, as well =
as<o:p></o:p></span></font></pre><pre><font
size=3D3 face=3D&#23435;&#20307;><span lang=3DEN-US =
style=3D'font-size:12.0pt'>&nbsp;&nbsp; dynamic tunnel setup and =
maintenance capability.&nbsp; =
Additionally,<o:p></o:p></span></font></pre><pre><font
size=3D3 face=3D&#23435;&#20307;><span lang=3DEN-US =
style=3D'font-size:12.0pt'>&nbsp;&nbsp; security is required if the VPN =
traffic is traversing public =
Internet<o:p></o:p></span></font></pre><pre><font
size=3D3 face=3D&#23435;&#20307;><span lang=3DEN-US =
style=3D'font-size:12.0pt'>&nbsp;&nbsp; or across Service Provider =
domains.&nbsp; Each above candidate by =
itself<o:p></o:p></span></font></pre><pre><font
size=3D3 face=3D&#23435;&#20307;><span lang=3DEN-US =
style=3D'font-size:12.0pt'>&nbsp;&nbsp; is not sufficient to meet all =
these requirements.&nbsp; This =
document<o:p></o:p></span></font></pre><pre><font
size=3D3 face=3D&#23435;&#20307;><span lang=3DEN-US =
style=3D'font-size:12.0pt'>&nbsp;&nbsp; describes a method of using =
IPsec signaling (i.e, IKE) to setup a =
GRE<o:p></o:p></span></font></pre><pre><font
size=3D3 face=3D&#23435;&#20307;><span lang=3DEN-US =
style=3D'font-size:12.0pt'>&nbsp;&nbsp; tunnel.&nbsp; This IPsec GRE =
tunnel may be used as the candidate =
tunneling<o:p></o:p></span></font></pre><pre><font
size=3D3 face=3D&#23435;&#20307;><span lang=3DEN-US =
style=3D'font-size:12.0pt'>&nbsp;&nbsp; scheme in PPVPN network or =
remote access compulsory VPN.&nbsp; =
This<o:p></o:p></span></font></pre><pre><font
size=3D3 face=3D&#23435;&#20307;><span lang=3DEN-US =
style=3D'font-size:12.0pt'>&nbsp;&nbsp; document also defines a way how =
the Key field in GRE header is =
used<o:p></o:p></span></font></pre><pre><font
size=3D3 face=3D&#23435;&#20307;><span lang=3DEN-US =
style=3D'font-size:12.0pt'>&nbsp;&nbsp; in IPsec GRE tunnel =
setup.<o:p></o:p></span></font></pre>

<p class=3DMsoNormal><font size=3D1 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
9.0pt;font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D1 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
9.0pt;font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D1 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
9.0pt;font-family:Arial'>You are comments are really =
appreciated,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D1 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
9.0pt;font-family:Arial'>Many thanks for your =
help<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D1 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
9.0pt;font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D1 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
9.0pt;font-family:Arial'>Best regards,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D1 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
9.0pt;font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D1 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
9.0pt;font-family:Arial'>-Hui<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D1 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
9.0pt;font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D1 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
9.0pt;font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

</div>

</body>

</html>

------=_NextPart_000_00D2_01C826CE.2EF49B00--






From l3vpn-bounces@ietf.org Thu Nov 15 06:26:45 2007
Return-path: <l3vpn-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Iscrn-0005T9-6E; Thu, 15 Nov 2007 06:26:39 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Iscrl-0005Qb-Na
	for l3vpn@ietf.org; Thu, 15 Nov 2007 06:26:37 -0500
Received: from wa-out-1112.google.com ([209.85.146.178])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Iscrh-0007Vx-W5
	for l3vpn@ietf.org; Thu, 15 Nov 2007 06:26:37 -0500
Received: by wa-out-1112.google.com with SMTP id k40so850200wah
	for <l3vpn@ietf.org>; Thu, 15 Nov 2007 03:26:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition;
	bh=DtAS2rngfqrTEibTI7OG6tyXV/Ld7IfA14weOW+NEoA=;
	b=Gw/pNEe07gUYdl9qMOmC6GnY0jvCbYmN+noBpMOvyFOA/m3NsiqT5Oc0HWDKTNYdyOjsSJtuUvrsKeGS5YDM9nBhAyE5FDeA25yDN5QOcvXESOEvkMDeA+4cjh7O7XhB1Ajn02mzJzEs04SP8z7CpwJOjJJWq4zOIeLCudw924g=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition;
	b=J0mVY8RK21+O7ytzUQvNRMGz7sG7Opa86JQgvyzTZtrmom4TEU/KxWiqVvJxXcyl2O96iJNL4Ou/Vn23CCVe+KHXQN0HC5VQw9snU9ehTzAcwvDgFFCj00Fv25ayMRNdhX+upaEVWGxoPUWGZDUG/vgox2B9F+o+gvxyqh8eyyY=
Received: by 10.114.88.1 with SMTP id l1mr590294wab.1195125992679;
	Thu, 15 Nov 2007 03:26:32 -0800 (PST)
Received: by 10.114.123.17 with HTTP; Thu, 15 Nov 2007 03:26:32 -0800 (PST)
Message-ID: <e360024e0711150326s4f95605ch5e115246823a1904@mail.gmail.com>
Date: Thu, 15 Nov 2007 19:26:32 +0800
From: "ma yc" <ycma610103@gmail.com>
To: l3vpn@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Subject: re:draft-wu-l3vpn-ipsec-gre-00
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l3vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>
Errors-To: l3vpn-bounces@ietf.org

Hi

Interesting draft. Please check my personal
view below.

1. I agree that GRE should be protected
by IPsec in some scenario. I just wonder
if it is necessary that GRE tunnels between
the same peer should be protected by different
IPsec tunnels. Is there any use case for such
deployment?

2. As per RFC 4301, the MUST supported selector
does not include GRE key. So i do not think any current
IPsec implementation supports that. To
mandate the implementations to support that,
GRE key need to be added as part of RFC 4301.

3. I am not so familiar with GRE, i have one question
about the header processing. Since all the fields after
protocol type are optional, how does a GRE implementation
tell the bits after protocol type is GRE key or checksum or
sequence number?

Thank you.
Regards
Yuanchen

>Hello, all
>
>
>
>Below is our new draft which posted recently,
>
>http://www.ietf.org/internet-drafts/draft-wu-l3vpn-ipsec-gre-00.txt




From l3vpn-bounces@ietf.org Thu Nov 15 14:50:20 2007
Return-path: <l3vpn-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Iskj4-0000gr-Hg; Thu, 15 Nov 2007 14:50:10 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Iskj3-0000fu-23
	for l3vpn@ietf.org; Thu, 15 Nov 2007 14:50:09 -0500
Received: from 28.2a.0540.static.theplanet.com ([64.5.42.40]
	helo=mail.zteusa.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Iskj0-0004N6-Lk
	for l3vpn@ietf.org; Thu, 15 Nov 2007 14:50:09 -0500
Received: from ywu (host10.atlra.hyatthsiagx.com [208.48.21.10])
	by mail.zteusa.com (8.13.4/8.13.4/SuSE Linux 0.7) with ESMTP id
	lAFJnm7E014077
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Thu, 15 Nov 2007 13:49:54 -0600
From: "Yingzhe Wu" <yingzhe.wu@zteusa.com>
To: "'ma yc'" <ycma610103@gmail.com>, <l3vpn@ietf.org>
References: <e360024e0711150326s4f95605ch5e115246823a1904@mail.gmail.com>
In-Reply-To: <e360024e0711150326s4f95605ch5e115246823a1904@mail.gmail.com>
Date: Thu, 15 Nov 2007 11:49:26 -0800
Message-ID: <002301c827c0$a809d580$f81d8080$@wu@zteusa.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acgnen+UKal55vatRsuShygRy/f3UAARVgdA
Content-Language: en-us
X-Spam-Score: 1.2 (+)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab
Cc: 
Subject: RE: draft-wu-l3vpn-ipsec-gre-00
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l3vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>
Errors-To: l3vpn-bounces@ietf.org

Hi YC,
Thanks a lot for your comments.
Please see inline for my reply.

BR/
Yingzhe

-----Original Message-----
From: ma yc [mailto:ycma610103@gmail.com] 
Sent: Thursday, November 15, 2007 3:27 AM
To: l3vpn@ietf.org
Subject: re:draft-wu-l3vpn-ipsec-gre-00

Hi

Interesting draft. Please check my personal
view below.

1. I agree that GRE should be protected
by IPsec in some scenario. I just wonder
if it is necessary that GRE tunnels between
the same peer should be protected by different
IPsec tunnels. Is there any use case for such
deployment?

YZ> The proposed GRE tunnel is per VPN. Different VPNs may have different
security requirements, hence it would be beneficial there is per-VPN based
differentiated security protection.

2. As per RFC 4301, the MUST supported selector
does not include GRE key. So i do not think any current
IPsec implementation supports that. To
mandate the implementations to support that,
GRE key need to be added as part of RFC 4301.

YZ> Yes, your observation is correct.

3. I am not so familiar with GRE, i have one question
about the header processing. Since all the fields after
protocol type are optional, how does a GRE implementation
tell the bits after protocol type is GRE key or checksum or
sequence number?

YZ> There are bit setting at the beginning of the GRE header to indicate a
particular field is present or not, such as Key, Checksum etc. While used in
this proposal, the 'K' bit must be set and 'C' bit must be cleared.

Thank you.
Regards
Yuanchen

>Hello, all
>
>
>
>Below is our new draft which posted recently,
>
>http://www.ietf.org/internet-drafts/draft-wu-l3vpn-ipsec-gre-00.txt





From l3vpn-bounces@ietf.org Mon Nov 19 14:15:52 2007
Return-path: <l3vpn-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IuC5k-0007Wj-M7; Mon, 19 Nov 2007 14:15:32 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IuC5K-0006VA-JV; Mon, 19 Nov 2007 14:15:06 -0500
Received: from ns1.neustar.com ([156.154.16.138])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IuC5H-0005xr-Mz; Mon, 19 Nov 2007 14:15:06 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id 5E46A327C0;
	Mon, 19 Nov 2007 19:15:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1IuC5F-0000AU-Ve; Mon, 19 Nov 2007 14:15:01 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1IuC5F-0000AU-Ve@stiedprstage1.ietf.org>
Date: Mon, 19 Nov 2007 14:15:01 -0500
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b280b4db656c3ca28dd62e5e0b03daa8
Cc: l3vpn@ietf.org
Subject: I-D ACTION:draft-ietf-l3vpn-2547bis-mcast-bgp-04.txt 
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l3vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>
Errors-To: l3vpn-bounces@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Layer 3 Virtual Private Networks Working Group of the IETF.

	Title		: BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs
	Author(s)	: R. Aggarwal, et al.
	Filename	: draft-ietf-l3vpn-2547bis-mcast-bgp-04.txt
	Pages		: 50
	Date		: 2007-11-19
	
This document describes the BGP encodings and procedures for
   exchanging the information elements required by Multicast in MPLS/BGP
   IP VPNs, as specified in [MVPN].

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-l3vpn-2547bis-mcast-bgp-04.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org 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-ietf-l3vpn-2547bis-mcast-bgp-04.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:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-l3vpn-2547bis-mcast-bgp-04.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.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2007-11-19134701.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-l3vpn-2547bis-mcast-bgp-04.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-l3vpn-2547bis-mcast-bgp-04.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2007-11-19134701.I-D@ietf.org>


--OtherAccess--

--NextPart--




From l3vpn-bounces@ietf.org Thu Nov 22 02:51:46 2007
Return-path: <l3vpn-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Iv6qU-00012g-Jn; Thu, 22 Nov 2007 02:51:34 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Iv6qT-00012b-S7
	for l3vpn@ietf.org; Thu, 22 Nov 2007 02:51:33 -0500
Received: from csnet1.cs.tsinghua.edu.cn ([166.111.68.226])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1Iv6qP-0005Xu-9L
	for l3vpn@ietf.org; Thu, 22 Nov 2007 02:51:33 -0500
Received: (qmail 7845 invoked by uid 0); 22 Nov 2007 08:11:25 -0000
Received: from unknown (HELO IBM-7B7FCA606E9) (qiminpeng@61.135.13.193)
	by csnet1.cs.tsinghua.edu.cn with SMTP; 22 Nov 2007 08:11:25 -0000
Date: Thu, 22 Nov 2007 15:49:30 +0800
From: "qiminpeng" <qiminpeng@csnet1.cs.tsinghua.edu.cn>
To: "l3vpn" <l3vpn@ietf.org>
Message-ID: <200711221549148437409@csnet1.cs.tsinghua.edu.cn>
X-mailer: Foxmail 6, 10, 201, 20 [cn]
Mime-Version: 1.0
Content-Type: multipart/alternative;
	boundary="=====003_Dragon765258851805_====="
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15
Subject: re: draft-wu-l3vpn-ipsec-gre-00
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l3vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>
Errors-To: l3vpn-bounces@ietf.org


This is a multi-part message in MIME format.

--=====003_Dragon765258851805_=====
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: 7bit

Hi
I'm interested in this draft. But I'm confused with a question below.
It is said that "the source GRE half key and destination GRE half key can be used in IKEv2 Traffic Selector negotiation".  In my humble opinion, it is just discribed how the GRE half key works in IKE protocol. I wonder how does it work in IPSec module. Is there any statement of this question? 
Thank you,
Regards
Minpeng Qi

>Hello, all
>
>
>
>Below is our new draft which posted recently,
>
>http://www.ietf.org/internet-drafts/draft-wu-l3vpn-ipsec-gre-00.txt

--=====003_Dragon765258851805_=====
Content-Type: text/html;
	charset="gb2312"
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=gb2312">
<META content="MSHTML 6.00.6000.16544" name=GENERATOR>
<STYLE>BLOCKQUOTE {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px; MARGIN-LEFT: 2em
}
OL {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
UL {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
</STYLE>
</HEAD>
<BODY style="FONT-SIZE: 10pt; FONT-FAMILY: verdana">
<DIV><FONT face=Verdana size=2>
<P>Hi<BR>I'm interested in this draft. But I'm confused with a question 
below.</P>
<P>It is said that "the source GRE half key and destination GRE half key can be 
used in IKEv2 Traffic Selector negotiation".&nbsp; In my humble opinion, it is 
just discribed how the GRE half key works in IKE protocol. I wonder how does it 
work in IPSec module. Is there any statement of this question? </P>
<P>Thank you,<BR>Regards</P>
<P>Minpeng Qi</P>
<P>&nbsp;</P>
<P></FONT><FONT face=Verdana size=2><FONT face=Verdana color=#c0c0c0 
size=2><FONT color=#000000>&gt;Hello, all<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt;Below 
is our new draft which posted recently,<BR>&gt;<BR>&gt;</FONT><A 
href="http://www.ietf.org/internet-drafts/draft-wu-l3vpn-ipsec-gre-00.txt">http://www.ietf.org/internet-drafts/draft-wu-l3vpn-ipsec-gre-00.txt</A><BR></FONT></P></DIV></FONT></BODY></HTML>

--=====003_Dragon765258851805_=====--






From l3vpn-bounces@ietf.org Thu Nov 22 07:33:32 2007
Return-path: <l3vpn-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IvBEs-0006di-3h; Thu, 22 Nov 2007 07:33:02 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IvBEr-0006dC-3R
	for l3vpn@ietf.org; Thu, 22 Nov 2007 07:33:01 -0500
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IvBEm-00071R-QC
	for l3vpn@ietf.org; Thu, 22 Nov 2007 07:33:01 -0500
X-IronPort-AV: E=Sophos;i="4.21,451,1188770400"; 
	d="scan'208,217";a="158514777"
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 22 Nov 2007 13:32:56 +0100
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id lAMCWujZ010878
	for <l3vpn@ietf.org>; Thu, 22 Nov 2007 13:32:56 +0100
Received: from xbh-ams-331.emea.cisco.com (xbh-ams-331.cisco.com
	[144.254.231.71])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id lAMCWuZZ029148
	for <l3vpn@ietf.org>; Thu, 22 Nov 2007 12:32:56 GMT
Received: from xfe-ams-332.cisco.com ([144.254.231.73]) by
	xbh-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 22 Nov 2007 13:32:56 +0100
Received: from [144.254.53.159] ([144.254.53.159]) by xfe-ams-332.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 22 Nov 2007 13:32:55 +0100
Mime-Version: 1.0 (Apple Message framework v752.3)
To: l3vpn@ietf.org
Message-Id: <5884FA6E-2E94-494E-90F7-0F0D82D4BC34@cisco.com>
Content-Type: multipart/alternative; boundary=Apple-Mail-16-531722938
References: <79E4059BC98EAF48BBE42FCF392DAA520953709E@emss09m07.us.lmco.com>
From: Francois Le Faucheur IMAP <flefauch@cisco.com>
Date: Thu, 22 Nov 2007 13:32:51 +0100
X-Mailer: Apple Mail (2.752.3)
X-OriginalArrivalTime: 22 Nov 2007 12:32:55.0605 (UTC)
	FILETIME=[CEB30650:01C82D03]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=15949; t=1195734776;
	x=1196598776; c=relaxed/simple; s=amsdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=flefauch@cisco.com;
	z=From:=20Francois=20Le=20Faucheur=20IMAP=20<flefauch@cisco.com>
	|Subject:=20Fwd=3A=20[Tsvwg]=20draft-davie-tsvwg-rsvp-l3vpn-01.txt=20-=20
	comments |Sender:=20;
	bh=O6zfhT5g8nASj/GDOqIo+KzF41TBlWtQtMvxFBG4f9A=;
	b=VcywqkdUeiLWVsOv4ccfg1onDgMnJho0ENpKeM0OOQszSaMqcLRxBcSzXUbhn3JoFIS2hVDP
	tK2VZ4elRxSI0hdy8Fy2jGQniwdfQaMpjSTMWVJHOgIVNt4ZtXLP2Gr5;
Authentication-Results: ams-dkim-1; header.From=flefauch@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim1002 verified; ); 
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 453b1bfcf0292bffe4cab90ba115f503
Subject: Fwd: [Tsvwg] draft-davie-tsvwg-rsvp-l3vpn-01.txt - comments
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l3vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>
Errors-To: l3vpn-bounces@ietf.org


--Apple-Mail-16-531722938
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=WINDOWS-1252;
	delsp=yes;
	format=flowed

This should be of interest to L3VPN WG since this draft will be =20
presented in L3VPN in Vancouver.
Francois

Begin forwarded message:

> From: "Yegenoglu, Ferit" <ferit.yegenoglu@lmco.com>
> Date: 21 November 2007 16:44:34 GMT+01:00
> To: tsvwg@ietf.org
> Subject: [Tsvwg] draft-davie-tsvwg-rsvp-l3vpn-01.txt - comments
>
> Hi Bruce, Francois, and Ashok,
>
>
> I enjoyed reading your new draft =93draft-davie-tsvwg-rsvp-=20
> l3vpn-01.txt.=94  We are working on some problems that can benefit =20
> from the solutions that your draft is proposing. I have the =20
> following comments/questions:
>
>
> 1)       As far as I can tell, your draft is also applicable to the =20=

> case where the aggregation region (per RFC 4804) is outside of the =20
> provider network, that is when the CE-PE interface is actually =20
> carrying aggregate RSVP messages. Can you confirm this? If this is =20
> correct I would suggest adding a note to that effect in your draft.
>
> 2)       In Section 3.1 (para. starting with =93As noted above=85=94), =
=20
> you are stating that the reason for not using the MPLS router alert =20=

> label is that not all deployed routers may support this. However, =20
> even if the routers were to support this capability, using the MPLS =20=

> router alert label would require that P routers along the PE-PE =20
> path also process RSVP messages, when they cannot do that because =20
> they lack VPN information. I would suggest adding this as another =20
> reason why MPLS router alert cannot be used.
>
> 3)       The VRF_ID identifies a VRF when sent by a PE router, a =20
> VPN context when sent by an ASBR, and possibly something else in a =20
> different application. It is merely a locally unique identifier, =20
> can we give it a more general name?
>
> 4)       How does an ASBR generate the =93pseudo VRF_ID=94? Ideally =
one =20
> would not want to generate a different pseudo VRF_ID for each RSVP =20
> session, but use a common identifier for sessions belonging to one =20
> VPN. One can get close to achieving this by noting that the VPN_ID =20
> carried inside the PATH message is unique within the router =20
> interface (IF_IN) through which the ASBR receives that PATH =20
> message. Therefore, if we use f(VPN_ID, IF_IN) as the pseudo VRF_ID =20=

> sent upstream by the ASBR (where f() is a one-to-one function), we =20
> can at least ensure that RSVP sessions belonging to the same VPN =20
> and arriving at the ASBR over the same interface use the same =20
> pseudo VRF_ID.
>
> 5)       Is there a reference for the approaches summarized in =20
> Appendix A.2 and A.3? =46rom the brief descriptions provided in your =20=

> draft I have a feeling that they may not work for the inter-AS =20
> Option B case as it may not be possible to uniquely identify =20
> sessions between two ASBRs.
>
>
> Regards,
>
> Ferit
>
>
>
>


--Apple-Mail-16-531722938
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=WINDOWS-1252

<HTML><BODY style=3D"word-wrap: break-word; -khtml-nbsp-mode: space; =
-khtml-line-break: after-white-space; ">This should be of interest to =
L3VPN WG since this draft will be presented in L3VPN in =
Vancouver.<DIV>Francois<BR><DIV><BR><DIV>Begin forwarded =
message:</DIV><BR class=3D"Apple-interchange-newline"><BLOCKQUOTE =
type=3D"cite"><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><FONT face=3D"Helvetica" =
size=3D"5" color=3D"#000000" style=3D"font: 18.0px Helvetica; color: =
#000000"><B>From: </B></FONT><FONT face=3D"Helvetica" size=3D"5" =
style=3D"font: 18.0px Helvetica">"Yegenoglu, Ferit" &lt;<A =
href=3D"mailto:ferit.yegenoglu@lmco.com">ferit.yegenoglu@lmco.com</A>&gt;<=
/FONT></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><FONT face=3D"Helvetica" =
size=3D"5" color=3D"#000000" style=3D"font: 18.0px Helvetica; color: =
#000000"><B>Date: </B></FONT><FONT face=3D"Helvetica" size=3D"5" =
style=3D"font: 18.0px Helvetica">21 November 2007 16:44:34 =
GMT+01:00</FONT></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><FONT face=3D"Helvetica" =
size=3D"5" color=3D"#000000" style=3D"font: 18.0px Helvetica; color: =
#000000"><B>To: </B></FONT><FONT face=3D"Helvetica" size=3D"5" =
style=3D"font: 18.0px Helvetica"><A =
href=3D"mailto:tsvwg@ietf.org">tsvwg@ietf.org</A></FONT></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><FONT face=3D"Helvetica" size=3D"5" color=3D"#000000" =
style=3D"font: 18.0px Helvetica; color: #000000"><B>Subject: =
</B></FONT><FONT face=3D"Helvetica" size=3D"5" style=3D"font: 18.0px =
Helvetica"><B>[Tsvwg] draft-davie-tsvwg-rsvp-l3vpn-01.txt - =
comments</B></FONT></DIV><DIV style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; =
"><BR></DIV> <SPAN class=3D"Apple-style-span" style=3D"border-collapse: =
separate; border-spacing: 0px 0px; color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 18px; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
text-align: auto; -khtml-text-decorations-in-effect: none; text-indent: =
0px; -apple-text-size-adjust: auto; text-transform: none; orphans: 2; =
white-space: normal; widows: 2; word-spacing: 0px; "><DIV =
class=3D"Section1"><P class=3D"MsoNormal"><FONT size=3D"2" =
face=3D"Arial"><SPAN style=3D"font-size:10.0pt; font-family:Arial; =
font-size: 13.3333px; "><SPAN class=3D"Apple-style-span" =
style=3D"font-family: Arial; font-size: 13.3333px; ">Hi Bruce, Francois, =
and Ashok,</SPAN></SPAN></FONT></P><DIV><FONT size=3D"2" =
face=3D"Arial"><SPAN style=3D"font-size:10.0pt; font-family:Arial; =
font-size: 13.3333px; "><SPAN class=3D"Apple-style-span" =
style=3D"font-family: Arial; font-size: 13.3333px; =
">=A0</SPAN></SPAN></FONT><BR class=3D"khtml-block-placeholder"></DIV><P =
class=3D"MsoNormal"><FONT size=3D"2" face=3D"Arial"><SPAN =
style=3D"font-size:10.0pt; font-family:Arial; font-size: 13.3333px; =
"><SPAN class=3D"Apple-style-span" style=3D"font-family: Arial; =
font-size: 13.3333px; ">I enjoyed reading your new draft =
=93draft-davie-tsvwg-rsvp-l3vpn-01.txt.=94 =A0We are working on some =
problems that can benefit from the solutions that your draft is =
proposing. I have the following =
comments/questions:</SPAN></SPAN></FONT></P><DIV><FONT size=3D"2" =
face=3D"Arial"><SPAN style=3D"font-size:10.0pt; font-family:Arial; =
font-size: 13.3333px; "><SPAN class=3D"Apple-style-span" =
style=3D"font-family: Arial; font-size: 13.3333px; =
">=A0</SPAN></SPAN></FONT><BR class=3D"khtml-block-placeholder"></DIV><P =
class=3D"MsoNormal" style=3D"margin-left:.5in;text-indent:-.25in; =
font-family: Times New Roman; font-size: 14.6667px; text-indent: -24px; =
"><FONT size=3D"2" face=3D"Arial"><SPAN =
style=3D"font-size:10.0pt;font-family:Arial; font-size: 13.3333px; =
text-indent: -24px; "><SPAN class=3D"Apple-style-span" =
style=3D"font-family: Arial; font-size: 13.3333px; text-indent: -24px; =
">1)</SPAN><FONT size=3D"1" face=3D"Times New Roman"><SPAN =
style=3D"font:7.0pt " times=3D"" new=3D"" roman";=3D"" font-family:=3D"" =
roman;=3D"" font-size:=3D"" 9.33333px;=3D"" text-indent:=3D"" =
-24px;=3D""><SPAN class=3D"Apple-style-span" style=3D"font-family: Times =
New Roman; font-size: 9.33333px; text-indent: -24px; ">=A0=A0=A0=A0=A0=A0 =
</SPAN></SPAN></FONT></SPAN></FONT><FONT size=3D"2" face=3D"Arial"><SPAN =
style=3D"font-size: 10.0pt;font-family:Arial; font-size: 13.3333px; =
text-indent: -24px; "><SPAN class=3D"Apple-style-span" =
style=3D"font-family: Arial; font-size: 13.3333px; text-indent: -24px; =
">As far as I can tell, your draft is also applicable to the case where =
the aggregation region (per RFC 4804) is outside of the provider =
network, that is when the CE-PE interface is actually carrying aggregate =
RSVP messages. Can you confirm this? If this is correct I would suggest =
adding a note to that effect in your draft.</SPAN></SPAN></FONT></P><P =
class=3D"MsoNormal" style=3D"margin-left:.5in;text-indent:-.25in; =
font-family: Times New Roman; font-size: 14.6667px; text-indent: -24px; =
"><FONT size=3D"2" face=3D"Arial"><SPAN =
style=3D"font-size:10.0pt;font-family:Arial; font-size: 13.3333px; =
text-indent: -24px; "><SPAN class=3D"Apple-style-span" =
style=3D"font-family: Arial; font-size: 13.3333px; text-indent: -24px; =
">2)</SPAN><FONT size=3D"1" face=3D"Times New Roman"><SPAN =
style=3D"font:7.0pt " times=3D"" new=3D"" roman";=3D"" font-family:=3D"" =
roman;=3D"" font-size:=3D"" 9.33333px;=3D"" text-indent:=3D"" =
-24px;=3D""><SPAN class=3D"Apple-style-span" style=3D"font-family: Times =
New Roman; font-size: 9.33333px; text-indent: -24px; ">=A0=A0=A0=A0=A0=A0 =
</SPAN></SPAN></FONT></SPAN></FONT><FONT size=3D"2" face=3D"Arial"><SPAN =
style=3D"font-size: 10.0pt;font-family:Arial; font-size: 13.3333px; =
text-indent: -24px; "><SPAN class=3D"Apple-style-span" =
style=3D"font-family: Arial; font-size: 13.3333px; text-indent: -24px; =
">In Section 3.1 (para. starting with =93As noted above=85=94), you are =
stating that the reason for not using the MPLS router alert label is =
that not all deployed routers may support this. However, even if the =
routers were to support this capability, using the MPLS router alert =
label would require that P routers along the PE-PE path also process =
RSVP messages, when they cannot do that because they lack VPN =
information. I would suggest adding this as another reason why MPLS =
router alert cannot be used.</SPAN></SPAN></FONT></P><P =
class=3D"MsoNormal" style=3D"margin-left:.5in;text-indent:-.25in; =
font-family: Times New Roman; font-size: 14.6667px; text-indent: -24px; =
"><FONT size=3D"2" face=3D"Arial"><SPAN =
style=3D"font-size:10.0pt;font-family:Arial; font-size: 13.3333px; =
text-indent: -24px; "><SPAN class=3D"Apple-style-span" =
style=3D"font-family: Arial; font-size: 13.3333px; text-indent: -24px; =
">3)</SPAN><FONT size=3D"1" face=3D"Times New Roman"><SPAN =
style=3D"font:7.0pt " times=3D"" new=3D"" roman";=3D"" font-family:=3D"" =
roman;=3D"" font-size:=3D"" 9.33333px;=3D"" text-indent:=3D"" =
-24px;=3D""><SPAN class=3D"Apple-style-span" style=3D"font-family: Times =
New Roman; font-size: 9.33333px; text-indent: -24px; ">=A0=A0=A0=A0=A0=A0 =
</SPAN></SPAN></FONT></SPAN></FONT><FONT size=3D"2" face=3D"Arial"><SPAN =
style=3D"font-size: 10.0pt;font-family:Arial; font-size: 13.3333px; =
text-indent: -24px; "><SPAN class=3D"Apple-style-span" =
style=3D"font-family: Arial; font-size: 13.3333px; text-indent: -24px; =
">The VRF_ID identifies a VRF when sent by a PE router, a VPN context =
when sent by an ASBR, and possibly something else in a different =
application. It is merely a locally unique identifier, can we give it a =
more general name?</SPAN></SPAN></FONT></P><P class=3D"MsoNormal" =
style=3D"margin-left:.5in;text-indent:-.25in; font-family: Times New =
Roman; font-size: 14.6667px; text-indent: -24px; "><FONT size=3D"2" =
face=3D"Arial"><SPAN style=3D"font-size:10.0pt;font-family:Arial; =
font-size: 13.3333px; text-indent: -24px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: Arial; font-size: =
13.3333px; text-indent: -24px; ">4)</SPAN><FONT size=3D"1" face=3D"Times =
New Roman"><SPAN style=3D"font:7.0pt " times=3D"" new=3D"" roman";=3D"" =
font-family:=3D"" roman;=3D"" font-size:=3D"" 9.33333px;=3D"" =
text-indent:=3D"" -24px;=3D""><SPAN class=3D"Apple-style-span" =
style=3D"font-family: Times New Roman; font-size: 9.33333px; =
text-indent: -24px; ">=A0=A0=A0=A0=A0=A0 =
</SPAN></SPAN></FONT></SPAN></FONT><FONT size=3D"2" face=3D"Arial"><SPAN =
style=3D"font-size: 10.0pt;font-family:Arial; font-size: 13.3333px; =
text-indent: -24px; "><SPAN class=3D"Apple-style-span" =
style=3D"font-family: Arial; font-size: 13.3333px; text-indent: -24px; =
">How does an ASBR generate the =93pseudo VRF_ID=94? Ideally one would =
not want to generate a different pseudo VRF_ID for each RSVP session, =
but use a common identifier for sessions belonging to one VPN. One can =
get close to achieving this by noting that the VPN_ID carried inside the =
PATH message is unique within the router interface (IF_IN) through which =
the ASBR receives that PATH message. Therefore, if we use f(VPN_ID, =
IF_IN) as the pseudo VRF_ID sent upstream by the ASBR (where f() is a =
one-to-one function), we can at least ensure that RSVP sessions =
belonging to the same VPN and arriving at the ASBR over the same =
interface use the same pseudo VRF_ID.</SPAN></SPAN></FONT></P><P =
class=3D"MsoNormal" style=3D"margin-left:.5in;text-indent:-.25in; =
font-family: Times New Roman; font-size: 14.6667px; text-indent: -24px; =
"><FONT size=3D"2" face=3D"Arial"><SPAN =
style=3D"font-size:10.0pt;font-family:Arial; font-size: 13.3333px; =
text-indent: -24px; "><SPAN class=3D"Apple-style-span" =
style=3D"font-family: Arial; font-size: 13.3333px; text-indent: -24px; =
">5)</SPAN><FONT size=3D"1" face=3D"Times New Roman"><SPAN =
style=3D"font:7.0pt " times=3D"" new=3D"" roman";=3D"" font-family:=3D"" =
roman;=3D"" font-size:=3D"" 9.33333px;=3D"" text-indent:=3D"" =
-24px;=3D""><SPAN class=3D"Apple-style-span" style=3D"font-family: Times =
New Roman; font-size: 9.33333px; text-indent: -24px; ">=A0=A0=A0=A0=A0=A0 =
</SPAN></SPAN></FONT></SPAN></FONT><FONT size=3D"2" face=3D"Arial"><SPAN =
style=3D"font-size: 10.0pt;font-family:Arial; font-size: 13.3333px; =
text-indent: -24px; "><SPAN class=3D"Apple-style-span" =
style=3D"font-family: Arial; font-size: 13.3333px; text-indent: -24px; =
">Is there a reference for the approaches summarized in Appendix A.2 and =
A.3? =46rom the brief descriptions provided in your draft I have a =
feeling that they may not work for the inter-AS Option B case as it may =
not be possible to uniquely identify sessions between two =
ASBRs.</SPAN></SPAN></FONT></P><DIV><FONT size=3D"2" face=3D"Arial"><SPAN =
style=3D"font-size:10.0pt; font-family:Arial; font-size: 13.3333px; =
"><SPAN class=3D"Apple-style-span" style=3D"font-family: Arial; =
font-size: 13.3333px; ">=A0</SPAN></SPAN></FONT><BR =
class=3D"khtml-block-placeholder"></DIV><P class=3D"MsoNormal"><FONT =
size=3D"2" face=3D"Arial"><SPAN style=3D"font-size:10.0pt; =
font-family:Arial; font-size: 13.3333px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: Arial; font-size: =
13.3333px; ">Regards,</SPAN></SPAN></FONT></P><P class=3D"MsoNormal"><FONT=
 size=3D"2" face=3D"Arial"><SPAN style=3D"font-size:10.0pt; =
font-family:Arial; font-size: 13.3333px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: Arial; font-size: =
13.3333px; ">Ferit</SPAN></SPAN></FONT></P><DIV style=3D"font-family: =
Times New Roman; font-size: 16px; "><FONT size=3D"3" face=3D"Times New =
Roman"><SPAN style=3D"font-size:12.0pt; font-family: Times New Roman; =
font-size: 16px; "><SPAN class=3D"Apple-style-span" style=3D"font-family: =
Times New Roman; font-size: 16px; ">=A0</SPAN></SPAN></FONT><BR =
class=3D"khtml-block-placeholder"></DIV><DIV><FONT size=3D"2" =
face=3D"Times New Roman"><SPAN style=3D"font-size: 11.0pt; font-family: =
Times New Roman; font-size: 14.6667px; "><SPAN class=3D"Apple-style-span" =
style=3D"font-family: Times New Roman; font-size: 14.6667px; =
">=A0</SPAN></SPAN></FONT><BR =
class=3D"khtml-block-placeholder"></DIV></DIV><BR =
class=3D"Apple-interchange-newline"></SPAN></BLOCKQUOTE></DIV><BR></DIV></=
BODY></HTML>=

--Apple-Mail-16-531722938--




From l3vpn-bounces@ietf.org Thu Nov 22 07:44:23 2007
Return-path: <l3vpn-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IvBPj-0004h0-LD; Thu, 22 Nov 2007 07:44:15 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IvBPi-0004bI-1V; Thu, 22 Nov 2007 07:44:14 -0500
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IvBPe-0007LD-3Y; Thu, 22 Nov 2007 07:44:13 -0500
X-IronPort-AV: E=Sophos;i="4.21,451,1188770400"; 
	d="scan'208,217";a="158515976"
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 22 Nov 2007 13:44:09 +0100
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id lAMCi90w014135; 
	Thu, 22 Nov 2007 13:44:09 +0100
Received: from xbh-ams-331.emea.cisco.com (xbh-ams-331.cisco.com
	[144.254.231.71])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id lAMCi9ZZ003295; 
	Thu, 22 Nov 2007 12:44:09 GMT
Received: from xfe-ams-332.cisco.com ([144.254.231.73]) by
	xbh-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 22 Nov 2007 13:44:09 +0100
Received: from [144.254.53.159] ([144.254.53.159]) by xfe-ams-332.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 22 Nov 2007 13:44:08 +0100
In-Reply-To: <79E4059BC98EAF48BBE42FCF392DAA520953709E@emss09m07.us.lmco.com>
References: <79E4059BC98EAF48BBE42FCF392DAA520953709E@emss09m07.us.lmco.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: multipart/alternative; boundary=Apple-Mail-17-532396255
Message-Id: <263F0482-8D45-4403-AA49-662886CD92F1@cisco.com>
From: Francois Le Faucheur IMAP <flefauch@cisco.com>
Date: Thu, 22 Nov 2007 13:44:04 +0100
To: "Yegenoglu, Ferit" <ferit.yegenoglu@lmco.com>
X-Mailer: Apple Mail (2.752.3)
X-OriginalArrivalTime: 22 Nov 2007 12:44:08.0646 (UTC)
	FILETIME=[5FDCEE60:01C82D05]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=11901; t=1195735449;
	x=1196599449; c=relaxed/simple; s=amsdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=flefauch@cisco.com;
	z=From:=20Francois=20Le=20Faucheur=20IMAP=20<flefauch@cisco.com>
	|Subject:=20Re=3A=20[Tsvwg]=20draft-davie-tsvwg-rsvp-l3vpn-01.txt=20-=20c
	omments |Sender:=20;
	bh=7Iy7czr4P7wdprkbImQJmY07YJM/mfsGWZU1DzGQ4pg=;
	b=c57k+A13cmLFxdayrdSao5YqsHttNvz7nU2sf+6Rf+GIiYtXotudZAZDgJXD3BJOepBUZzfh
	bdxhMYvL3CbefizMm8LmDiBiiigK8dbF+MJyM3mmKDutWO2/oFLN+PxT;
Authentication-Results: ams-dkim-1; header.From=flefauch@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim1002 verified; ); 
X-Spam-Score: -4.0 (----)
X-Scan-Signature: a069a8e8835d39ce36e425c148267a7b
Cc: Francois Le Faucheur IMAP <flefauch@cisco.com>,
	tsvwg tsvwg <tsvwg@ietf.org>, l3vpn@ietf.org
Subject: Re: [Tsvwg] draft-davie-tsvwg-rsvp-l3vpn-01.txt - comments
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l3vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>
Errors-To: l3vpn-bounces@ietf.org


--Apple-Mail-17-532396255
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=WINDOWS-1252;
	delsp=yes;
	format=flowed

Hi Ferit,

Thanks for your interest and comments. Thoughts on some of the points =20=

you bring up embedded below:

On 21 Nov 2007, at 16:44, Yegenoglu, Ferit wrote:

> Hi Bruce, Francois, and Ashok,
>
>
> I enjoyed reading your new draft =93draft-davie-tsvwg-rsvp-=20
> l3vpn-01.txt.=94  We are working on some problems that can benefit =20
> from the solutions that your draft is proposing. I have the =20
> following comments/questions:
>
>
> 1)       As far as I can tell, your draft is also applicable to the =20=

> case where the aggregation region (per RFC 4804) is outside of the =20
> provider network, that is when the CE-PE interface is actually =20
> carrying aggregate RSVP messages. Can you confirm this? If this is =20
> correct I would suggest adding a note to that effect in your draft.
This is correct. It is also applicable to RFC4804 sessions (as well =20
as RFC3175 sessions for that matter). We'll add a statement to that =20
effect.
>
> 5)       Is there a reference for the approaches summarized in =20
> Appendix A.2 and A.3?
we're not aware of references documenting these other approaches in =20
further details.

> =46rom the brief descriptions provided in your draft I have a feeling =20=

> that they may not work for the inter-AS Option B case as it may not =20=

> be possible to uniquely identify sessions between two ASBRs.
Right. Or perhaps more accurately, they would require further =20
extensions to operate in inter-AS Option B.

Francois

>
> Regards,
>
> Ferit
>
>
>
>


--Apple-Mail-17-532396255
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=WINDOWS-1252

<HTML><BODY style=3D"word-wrap: break-word; -khtml-nbsp-mode: space; =
-khtml-line-break: after-white-space; ">Hi Ferit,<DIV><BR =
class=3D"khtml-block-placeholder"></DIV><DIV>Thanks for your interest =
and comments. Thoughts on some of the points you bring up embedded =
below:=A0<DIV><BR><DIV><DIV>On 21 Nov 2007, at 16:44, Yegenoglu, Ferit =
wrote:</DIV><BR class=3D"Apple-interchange-newline"><BLOCKQUOTE =
type=3D"cite"><SPAN class=3D"Apple-style-span" style=3D"border-collapse: =
separate; border-spacing: 0px 0px; color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 18px; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
text-align: auto; -khtml-text-decorations-in-effect: none; text-indent: =
0px; -apple-text-size-adjust: auto; text-transform: none; orphans: 2; =
white-space: normal; widows: 2; word-spacing: 0px; "><DIV =
class=3D"Section1"><P class=3D"MsoNormal"><FONT size=3D"2" =
face=3D"Arial"><SPAN style=3D"font-size:10.0pt; font-family:Arial; =
font-size: 13.3333px; "><SPAN class=3D"Apple-style-span" =
style=3D"font-family: Arial; font-size: 13.3333px; ">Hi Bruce, Francois, =
and Ashok,</SPAN></SPAN></FONT></P><DIV><FONT size=3D"2" =
face=3D"Arial"><SPAN style=3D"font-size:10.0pt; font-family:Arial; =
font-size: 13.3333px; "><SPAN class=3D"Apple-style-span" =
style=3D"font-family: Arial; font-size: 13.3333px; =
">=A0</SPAN></SPAN></FONT><BR class=3D"khtml-block-placeholder"></DIV><P =
class=3D"MsoNormal"><FONT size=3D"2" face=3D"Arial"><SPAN =
style=3D"font-size:10.0pt; font-family:Arial; font-size: 13.3333px; =
"><SPAN class=3D"Apple-style-span" style=3D"font-family: Arial; =
font-size: 13.3333px; ">I enjoyed reading your new draft =
=93draft-davie-tsvwg-rsvp-l3vpn-01.txt.=94 =A0We are working on some =
problems that can benefit from the solutions that your draft is =
proposing. I have the following =
comments/questions:</SPAN></SPAN></FONT></P><DIV><FONT size=3D"2" =
face=3D"Arial"><SPAN style=3D"font-size:10.0pt; font-family:Arial; =
font-size: 13.3333px; "><SPAN class=3D"Apple-style-span" =
style=3D"font-family: Arial; font-size: 13.3333px; =
">=A0</SPAN></SPAN></FONT><BR class=3D"khtml-block-placeholder"></DIV><P =
class=3D"MsoNormal" style=3D"margin-left:.5in;text-indent:-.25in; =
font-family: Times New Roman; font-size: 14.6667px; text-indent: -24px; =
"><FONT size=3D"2" face=3D"Arial"><SPAN =
style=3D"font-size:10.0pt;font-family:Arial; font-size: 13.3333px; =
text-indent: -24px; "><SPAN class=3D"Apple-style-span" =
style=3D"font-family: Arial; font-size: 13.3333px; text-indent: -24px; =
">1)</SPAN><FONT size=3D"1" face=3D"Times New Roman"><SPAN =
style=3D"font:7.0pt " times=3D"" new=3D"" roman";=3D"" font-family:=3D"" =
roman;=3D"" font-size:=3D"" 9.33333px;=3D"" text-indent:=3D"" =
-24px;=3D""><SPAN class=3D"Apple-style-span" style=3D"font-family: Times =
New Roman; font-size: 9.33333px; text-indent: -24px; ">=A0=A0=A0=A0=A0=A0 =
</SPAN></SPAN></FONT></SPAN></FONT><FONT size=3D"2" face=3D"Arial"><SPAN =
style=3D"font-size: 10.0pt;font-family:Arial; font-size: 13.3333px; =
text-indent: -24px; "><SPAN class=3D"Apple-style-span" =
style=3D"font-family: Arial; font-size: 13.3333px; text-indent: -24px; =
">As far as I can tell, your draft is also applicable to the case where =
the aggregation region (per RFC 4804) is outside of the provider =
network, that is when the CE-PE interface is actually carrying aggregate =
RSVP messages. Can you confirm this? If this is correct I would suggest =
adding a note to that effect in your =
draft.</SPAN></SPAN></FONT></P></DIV></SPAN></BLOCKQUOTE><DIV>This is =
correct. It is also applicable to RFC4804 sessions (as well as RFC3175 =
sessions for that matter). We'll add a statement to that =
effect.=A0</DIV><BLOCKQUOTE type=3D"cite"><SPAN class=3D"Apple-style-span"=
 style=3D"border-collapse: separate; border-spacing: 0px 0px; color: =
rgb(0, 0, 0); font-family: Helvetica; font-size: 18px; font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; text-align: auto; =
-khtml-text-decorations-in-effect: none; text-indent: 0px; =
-apple-text-size-adjust: auto; text-transform: none; orphans: 2; =
white-space: normal; widows: 2; word-spacing: 0px; "><DIV =
class=3D"Section1"><P class=3D"MsoNormal" =
style=3D"margin-left:.5in;text-indent:-.25in; font-family: Times New =
Roman; font-size: 14.6667px; text-indent: -24px; "><FONT =
class=3D"Apple-style-span" face=3D"Arial" size=3D"4"><SPAN =
class=3D"Apple-style-span" style=3D"font-size: 13.3333px;"><BR =
class=3D"khtml-block-placeholder"></SPAN></FONT></P></DIV></SPAN></BLOCKQU=
OTE><BLOCKQUOTE type=3D"cite"><SPAN class=3D"Apple-style-span" =
style=3D"border-collapse: separate; border-spacing: 0px 0px; color: =
rgb(0, 0, 0); font-family: Helvetica; font-size: 18px; font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; text-align: auto; =
-khtml-text-decorations-in-effect: none; text-indent: 0px; =
-apple-text-size-adjust: auto; text-transform: none; orphans: 2; =
white-space: normal; widows: 2; word-spacing: 0px; "><DIV =
class=3D"Section1"><P class=3D"MsoNormal" =
style=3D"margin-left:.5in;text-indent:-.25in; font-family: Times New =
Roman; font-size: 14.6667px; text-indent: -24px; "><FONT size=3D"2" =
face=3D"Arial"><SPAN style=3D"font-size:10.0pt;font-family:Arial; =
font-size: 13.3333px; text-indent: -24px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: Arial; font-size: =
13.3333px; text-indent: -24px; ">5)</SPAN><FONT size=3D"1" face=3D"Times =
New Roman"><SPAN style=3D"font:7.0pt " times=3D"" new=3D"" roman";=3D"" =
font-family:=3D"" roman;=3D"" font-size:=3D"" 9.33333px;=3D"" =
text-indent:=3D"" -24px;=3D""><SPAN class=3D"Apple-style-span" =
style=3D"font-family: Times New Roman; font-size: 9.33333px; =
text-indent: -24px; ">=A0=A0=A0=A0=A0=A0 =
</SPAN></SPAN></FONT></SPAN></FONT><FONT size=3D"2" face=3D"Arial"><SPAN =
style=3D"font-size: 10.0pt;font-family:Arial; font-size: 13.3333px; =
text-indent: -24px; "><SPAN class=3D"Apple-style-span" =
style=3D"font-family: Arial; font-size: 13.3333px; text-indent: -24px; =
">Is there a reference for the approaches summarized in Appendix A.2 and =
A.3? <BR></SPAN></SPAN></FONT></P></DIV></SPAN></BLOCKQUOTE><DIV>we're =
not aware of references documenting these other approaches in further =
details.</DIV><BR><BLOCKQUOTE type=3D"cite"><SPAN =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
border-spacing: 0px 0px; color: rgb(0, 0, 0); font-family: Helvetica; =
font-size: 18px; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; text-align: auto; =
-khtml-text-decorations-in-effect: none; text-indent: 0px; =
-apple-text-size-adjust: auto; text-transform: none; orphans: 2; =
white-space: normal; widows: 2; word-spacing: 0px; "><DIV =
class=3D"Section1"><P class=3D"MsoNormal" =
style=3D"margin-left:.5in;text-indent:-.25in; font-family: Times New =
Roman; font-size: 14.6667px; text-indent: -24px; "><FONT size=3D"2" =
face=3D"Arial"><SPAN style=3D"font-size: 10.0pt;font-family:Arial; =
font-size: 13.3333px; text-indent: -24px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: Arial; font-size: =
13.3333px; text-indent: -24px; ">=46rom the brief descriptions provided =
in your draft I have a feeling that they may not work for the inter-AS =
Option B case as it may not be possible to uniquely identify sessions =
between two =
ASBRs.</SPAN></SPAN></FONT></P></DIV></SPAN></BLOCKQUOTE><DIV>Right. Or =
perhaps more accurately, they would require further extensions to =
operate in inter-AS Option B.</DIV><DIV><BR =
class=3D"khtml-block-placeholder"></DIV><DIV>Francois</DIV><BR><BLOCKQUOTE=
 type=3D"cite"><SPAN class=3D"Apple-style-span" style=3D"border-collapse: =
separate; border-spacing: 0px 0px; color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 18px; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
text-align: auto; -khtml-text-decorations-in-effect: none; text-indent: =
0px; -apple-text-size-adjust: auto; text-transform: none; orphans: 2; =
white-space: normal; widows: 2; word-spacing: 0px; "><DIV =
class=3D"Section1"><DIV><FONT size=3D"2" face=3D"Arial"><SPAN =
style=3D"font-size:10.0pt; font-family:Arial; font-size: 13.3333px; =
"><SPAN class=3D"Apple-style-span" style=3D"font-family: Arial; =
font-size: 13.3333px; ">=A0</SPAN></SPAN></FONT><BR =
class=3D"khtml-block-placeholder"></DIV><P class=3D"MsoNormal"><FONT =
size=3D"2" face=3D"Arial"><SPAN style=3D"font-size:10.0pt; =
font-family:Arial; font-size: 13.3333px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: Arial; font-size: =
13.3333px; ">Regards,</SPAN></SPAN></FONT></P><P class=3D"MsoNormal"><FONT=
 size=3D"2" face=3D"Arial"><SPAN style=3D"font-size:10.0pt; =
font-family:Arial; font-size: 13.3333px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: Arial; font-size: =
13.3333px; ">Ferit</SPAN></SPAN></FONT></P><DIV style=3D"font-family: =
Times New Roman; font-size: 16px; "><FONT size=3D"3" face=3D"Times New =
Roman"><SPAN style=3D"font-size:12.0pt; font-family: Times New Roman; =
font-size: 16px; "><SPAN class=3D"Apple-style-span" style=3D"font-family: =
Times New Roman; font-size: 16px; ">=A0</SPAN></SPAN></FONT><BR =
class=3D"khtml-block-placeholder"></DIV><DIV><FONT size=3D"2" =
face=3D"Times New Roman"><SPAN style=3D"font-size: 11.0pt; font-family: =
Times New Roman; font-size: 14.6667px; "><SPAN class=3D"Apple-style-span" =
style=3D"font-family: Times New Roman; font-size: 14.6667px; =
">=A0</SPAN></SPAN></FONT><BR =
class=3D"khtml-block-placeholder"></DIV></DIV><BR =
class=3D"Apple-interchange-newline"></SPAN></BLOCKQUOTE></DIV><BR></DIV></=
DIV></BODY></HTML>=

--Apple-Mail-17-532396255--




From l3vpn-bounces@ietf.org Sun Nov 25 20:04:37 2007
Return-path: <l3vpn-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IwSOW-0005wt-8y; Sun, 25 Nov 2007 20:04:16 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IwSOB-0005hZ-5o
	for l3vpn@ietf.org; Sun, 25 Nov 2007 20:03:55 -0500
Received: from [221.130.253.133] (helo=cmccmta)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IwSLw-0007ec-DA
	for l3vpn@ietf.org; Sun, 25 Nov 2007 20:01:37 -0500
Received: from denghui ([10.1.6.121])
	by mail.chinamobile.com (Lotus Domino Release 6.5.5FP1)
	with SMTP id 2007112609010150-6243 ; Mon, 26 Nov 2007 09:01:01 +0800 
From: "Hui Deng" <denghui@chinamobile.com>
To: "'qiminpeng'" <qiminpeng@csnet1.cs.tsinghua.edu.cn>,
	"'l3vpn'" <l3vpn@ietf.org>
Date: Mon, 26 Nov 2007 09:00:51 +0800
Message-ID: <000601c82fc7$ca10b8b0$7906010a@denghui>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
thread-index: Acgs34y0ik6tMn91Q8ixuL/8hbDHXgC58jcg
In-Reply-To: <200711221549148437409@csnet1.cs.tsinghua.edu.cn>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
X-MIMETrack: Itemize by SMTP Server on jtgsml01/servers/cmcc(Release 6.5.5FP1
	| April 14, 2006) at 2007-11-26 09:01:01,
	Serialize by Router on cmccmta/servers/cmcc(Release 6.5.5FP1 | April 14,
	2006) at 2007-11-26 09:01:37,
	Serialize complete at 2007-11-26 09:01:37
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0007_01C8300A.D83FDF90"
X-Spam-Score: 0.7 (/)
X-Scan-Signature: 025f8c5000216988bfe31585db759250
Cc: 
Subject: RE: draft-wu-l3vpn-ipsec-gre-00
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l3vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>
Errors-To: l3vpn-bounces@ietf.org

This is a multi-part message in MIME format.

------=_NextPart_000_0007_01C8300A.D83FDF90
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset="us-ascii"

Hi, Minpeng,

 

Thanks for your comments, 

As you said here, we do need extend IPsec to support gre key parse.

This is what we are proposing here, and is quite similar to MH type which is
defined in MIP6.

 

Many thanks

 

-Hui

 

 

  _____  

From: qiminpeng [mailto:qiminpeng@csnet1.cs.tsinghua.edu.cn] 
Sent: Thursday, November 22, 2007 3:50 PM
To: l3vpn
Subject: re: draft-wu-l3vpn-ipsec-gre-00

 

Hi
I'm interested in this draft. But I'm confused with a question below.

It is said that "the source GRE half key and destination GRE half key can be
used in IKEv2 Traffic Selector negotiation".  In my humble opinion, it is
just discribed how the GRE half key works in IKE protocol. I wonder how does
it work in IPSec module. Is there any statement of this question? 

Thank you,
Regards

Minpeng Qi

 

>Hello, all
>
>
>
>Below is our new draft which posted recently,
>
>http://www.ietf.org/internet-drafts/draft-wu-l3vpn-ipsec-gre-00.txt


------=_NextPart_000_0007_01C8300A.D83FDF90
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset="us-ascii"

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:&#23435;&#20307;;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Verdana;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:"\@&#23435;&#20307;";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:&#23435;&#20307;;}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;}
p
	{mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:12.0pt;
	font-family:&#23435;&#20307;;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:595.3pt 841.9pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DZH-CN link=3Dblue vlink=3Dblue>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D1 color=3Dnavy face=3DArial><span =
lang=3DEN-US
style=3D'font-size:9.0pt;font-family:Arial;color:navy'>Hi, =
Minpeng,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D1 color=3Dnavy face=3DArial><span =
lang=3DEN-US
style=3D'font-size:9.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p><=
/span></font></p>

<p class=3DMsoNormal><font size=3D1 color=3Dnavy face=3DArial><span =
lang=3DEN-US
style=3D'font-size:9.0pt;font-family:Arial;color:navy'>Thanks for your =
comments, <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D1 color=3Dnavy face=3DArial><span =
lang=3DEN-US
style=3D'font-size:9.0pt;font-family:Arial;color:navy'>As you said here, =
we do
need extend IPsec to support gre key parse.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D1 color=3Dnavy face=3DArial><span =
lang=3DEN-US
style=3D'font-size:9.0pt;font-family:Arial;color:navy'>This is what we =
are
proposing here, and is quite similar to MH type which is defined in =
MIP6.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D1 color=3Dnavy face=3DArial><span =
lang=3DEN-US
style=3D'font-size:9.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p><=
/span></font></p>

<p class=3DMsoNormal><font size=3D1 color=3Dnavy face=3DArial><span =
lang=3DEN-US
style=3D'font-size:9.0pt;font-family:Arial;color:navy'>Many =
thanks<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D1 color=3Dnavy face=3DArial><span =
lang=3DEN-US
style=3D'font-size:9.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p><=
/span></font></p>

<p class=3DMsoNormal><font size=3D1 color=3Dnavy face=3DArial><span =
lang=3DEN-US
style=3D'font-size:9.0pt;font-family:Arial;color:navy'>-Hui<o:p></o:p></s=
pan></font></p>

<p class=3DMsoNormal><font size=3D1 color=3Dnavy face=3DArial><span =
lang=3DEN-US
style=3D'font-size:9.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p><=
/span></font></p>

<p class=3DMsoNormal><font size=3D1 color=3Dnavy face=3DArial><span =
lang=3DEN-US
style=3D'font-size:9.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p><=
/span></font></p>

<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0cm 0cm =
0cm 4.0pt'>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D&#23435;&#20307;><span lang=3DEN-US style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Tahoma;font-weight:bold'>From:</spa=
n></font></b><font
size=3D2 face=3DTahoma><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:Tahoma'>
qiminpeng [mailto:qiminpeng@csnet1.cs.tsinghua.edu.cn] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Thursday, November =
22, 2007
3:50 PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> l3vpn<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> re:
draft-wu-l3vpn-ipsec-gre-00</span></font><span =
lang=3DEN-US><o:p></o:p></span></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D&#23435;&#20307;><span =
lang=3DEN-US =
style=3D'font-size:12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<div>

<p><font size=3D2 face=3DVerdana><span lang=3DEN-US =
style=3D'font-size:10.0pt;
font-family:Verdana'>Hi<br>
I'm interested in this draft. But I'm confused with a question =
below.<o:p></o:p></span></font></p>

<p><font size=3D2 face=3DVerdana><span lang=3DEN-US =
style=3D'font-size:10.0pt;
font-family:Verdana'>It is said that &quot;the source GRE half key and
destination GRE half key can be used in IKEv2 Traffic Selector
negotiation&quot;.&nbsp; In my humble opinion, it is just discribed how =
the GRE
half key works in IKE protocol. I wonder how does it work in IPSec =
module. Is
there any statement of this question? <o:p></o:p></span></font></p>

<p><font size=3D2 face=3DVerdana><span lang=3DEN-US =
style=3D'font-size:10.0pt;
font-family:Verdana'>Thank you,<br>
Regards<o:p></o:p></span></font></p>

<p><font size=3D2 face=3DVerdana><span lang=3DEN-US =
style=3D'font-size:10.0pt;
font-family:Verdana'>Minpeng Qi<o:p></o:p></span></font></p>

<p><font size=3D2 face=3DVerdana><span lang=3DEN-US =
style=3D'font-size:10.0pt;
font-family:Verdana'>&nbsp;<o:p></o:p></span></font></p>

<p><font size=3D2 color=3Dblack face=3DVerdana><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Verdana;color:black'>&gt;Hello, all<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;Below is our new draft which posted recently,<br>
&gt;<br>
&gt;</span></font><font size=3D2 color=3Dsilver face=3DVerdana><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Verdana;color:silver'><a
href=3D"http://www.ietf.org/internet-drafts/draft-wu-l3vpn-ipsec-gre-00.t=
xt">http://www.ietf.org/internet-drafts/draft-wu-l3vpn-ipsec-gre-00.txt</=
a></span></font><font
size=3D2 face=3DVerdana><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:Verdana'><o:p></o:p></span></font><=
/p>

</div>

</div>

</div>

</body>

</html>

------=_NextPart_000_0007_01C8300A.D83FDF90--






From l3vpn-bounces@ietf.org Mon Nov 26 10:52:22 2007
Return-path: <l3vpn-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IwgFt-0002po-Jz; Mon, 26 Nov 2007 10:52:17 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IwgFs-0002pj-V6
	for l3vpn@ietf.org; Mon, 26 Nov 2007 10:52:16 -0500
Received: from exprod7og101.obsmtp.com ([64.18.2.155])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IwgFm-0001DE-LG
	for l3vpn@ietf.org; Mon, 26 Nov 2007 10:52:16 -0500
Received: from source ([66.129.224.36]) by exprod7ob101.postini.com
	([64.18.6.12]) with SMTP; Mon, 26 Nov 2007 07:52:09 PST
Received: from proton.jnpr.net ([10.10.2.37]) by gamma.jnpr.net with Microsoft
	SMTPSVC(6.0.3790.1830); Mon, 26 Nov 2007 07:51:58 -0800
Received: from [172.23.1.172] ([172.23.1.172] RDNS failed) by proton.jnpr.net
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 26 Nov 2007 10:45:15 -0500
Message-ID: <474AEA07.4010102@juniper.net>
Date: Mon, 26 Nov 2007 10:45:11 -0500
From: Ron Bonica <rbonica@juniper.net>
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: l3vpn@ietf.org
X-Enigmail-Version: 0.93.0.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 26 Nov 2007 15:45:15.0266 (UTC)
	FILETIME=[56868E20:01C83043]
X-Spam-Score: -4.0 (----)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Subject: IETF 70 Agenda
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l3vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>
Errors-To: l3vpn-bounces@ietf.org

Folks,

The following is a proposed agenda for our meeting at IETF 70. If anyone
needs more or less time on the agenda, please email me privately.

                                Ron

Layer 3 Virtual Private Networks (Internet Area)

Wednesday, December 5, 2007
=========================

Chairs:
Rick Wilder <rick@rhwilder.net>
Ron Bonica  <rbonica@juniper.net>

Agenda:

09:00-09:10  Working Group Status and Charter - R. Bonica, R.Wilder

09:10-09:40 T. Morin - draft-morin-l3vpn-mvpn-considerations-01
09:40-10:00 M. Napiera - draft-mnapierala-mvpn-part-reqt
10:00-10:30 B. Davies - draft-davie-tsvwg-rsvp-l3vpn
10:30-11:00 E. Rosen & R. Aggarwal - draft-ietf-l3vpn-2547bis-mcast
11:00-11:30 E. Rosen - draft-rosen-l3vpn-mvpn-profiles-00





From l3vpn-bounces@ietf.org Mon Nov 26 20:28:48 2007
Return-path: <l3vpn-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IwpFg-0001M8-O3; Mon, 26 Nov 2007 20:28:40 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IwpFe-0001Ll-Km; Mon, 26 Nov 2007 20:28:38 -0500
Received: from exprod7og111.obsmtp.com ([64.18.2.175])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IwpFY-0004da-Oo; Mon, 26 Nov 2007 20:28:38 -0500
Received: from source ([66.129.224.36]) by exprod7ob111.postini.com
	([64.18.6.12]) with SMTP; Mon, 26 Nov 2007 17:28:10 PST
Received: from magenta.juniper.net ([172.17.27.123]) by emailsmtp55.jnpr.net
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 26 Nov 2007 17:28:17 -0800
Received: from juniper.net (sapphire.juniper.net [172.17.28.108])
	by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id lAR1SDE30787;
	Mon, 26 Nov 2007 17:28:13 -0800 (PST)
	(envelope-from yakov@juniper.net)
Message-Id: <200711270128.lAR1SDE30787@magenta.juniper.net>
To: Francois Le Faucheur IMAP <flefauch@cisco.com>
In-Reply-To: Your message of "Thu, 22 Nov 2007 13:44:04 +0100."
	<263F0482-8D45-4403-AA49-662886CD92F1@cisco.com> 
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <83248.1196126893.1@juniper.net>
Date: Mon, 26 Nov 2007 17:28:13 -0800
From: Yakov Rekhter <yakov@juniper.net>
X-OriginalArrivalTime: 27 Nov 2007 01:28:17.0353 (UTC)
	FILETIME=[C9796B90:01C83094]
X-Spam-Score: -4.0 (----)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Cc: l3vpn@ietf.org, "Yegenoglu, Ferit" <ferit.yegenoglu@lmco.com>,
	tsvwg tsvwg <tsvwg@ietf.org>
Subject: Re: [Tsvwg] draft-davie-tsvwg-rsvp-l3vpn-01.txt - comments 
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l3vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>
Errors-To: l3vpn-bounces@ietf.org

Francois,

> Hi Ferit,
> 
> Thanks for your interest and comments. Thoughts on some of the points 
> 
> you bring up embedded below:
> 
> On 21 Nov 2007, at 16:44, Yegenoglu, Ferit wrote:
> 
> > Hi Bruce, Francois, and Ashok,
> >
> >
> > I enjoyed reading your new draft =93draft-davie-tsvwg-rsvp-
> > l3vpn-01.txt.=94  We are working on some problems that can benefit 
> > from the solutions that your draft is proposing. I have the 
> > following comments/questions:
> >
> >
> > 1)       As far as I can tell, your draft is also applicable to the 
> > case where the aggregation region (per RFC 4804) is outside of the 
> > provider network, that is when the CE-PE interface is actually =20
> > carrying aggregate RSVP messages. Can you confirm this? If this is =20
> > correct I would suggest adding a note to that effect in your draft.
> This is correct. It is also applicable to RFC4804 sessions (as well =20
> as RFC3175 sessions for that matter). We'll add a statement to that =20
> effect.
> >
> > 5)  Is there a reference for the approaches summarized in 
> > Appendix A.2 and A.3?
> > we're not aware of references documenting these other approaches in 
> > further details.
> > From the brief descriptions provided in your draft I have a feeling 
> > that they may not work for the inter-AS Option B case as it may not 
> > be possible to uniquely identify sessions between two ASBRs.

> Right. Or perhaps more accurately, they would require further
> extensions to operate in inter-AS Option B.

Could you elaborate on what "further extensions" be required.

Yakov.




From l3vpn-bounces@ietf.org Wed Nov 28 15:02:27 2007
Return-path: <l3vpn-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IxT73-0002db-3o; Wed, 28 Nov 2007 15:02:25 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IxT71-0002cr-3B; Wed, 28 Nov 2007 15:02:23 -0500
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IxT70-0004G7-Jt; Wed, 28 Nov 2007 15:02:23 -0500
X-IronPort-AV: E=Sophos;i="4.23,225,1194217200"; d="scan'208";a="159053221"
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 28 Nov 2007 21:02:11 +0100
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id lASK2BKI004057; 
	Wed, 28 Nov 2007 21:02:11 +0100
Received: from xbh-ams-331.emea.cisco.com (xbh-ams-331.cisco.com
	[144.254.231.71])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id lASK1x3Z000354; 
	Wed, 28 Nov 2007 20:01:59 GMT
Received: from xfe-ams-331.emea.cisco.com ([144.254.231.72]) by
	xbh-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 28 Nov 2007 21:01:59 +0100
Received: from [144.254.53.159] ([144.254.53.159]) by
	xfe-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 28 Nov 2007 21:01:59 +0100
In-Reply-To: <200711270128.lAR1SDE30787@magenta.juniper.net>
References: <200711270128.lAR1SDE30787@magenta.juniper.net>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <2FF68529-97CD-4FC0-9400-E368C96328BA@cisco.com>
Content-Transfer-Encoding: 7bit
From: Francois Le Faucheur IMAP <flefauch@cisco.com>
Date: Wed, 28 Nov 2007 21:01:52 +0100
To: Yakov Rekhter <yakov@juniper.net>
X-Mailer: Apple Mail (2.752.3)
X-OriginalArrivalTime: 28 Nov 2007 20:01:59.0394 (UTC)
	FILETIME=[88ED7420:01C831F9]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2607; t=1196280131;
	x=1197144131; c=relaxed/simple; s=amsdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=flefauch@cisco.com;
	z=From:=20Francois=20Le=20Faucheur=20IMAP=20<flefauch@cisco.com>
	|Subject:=20Re=3A=20[Tsvwg]=20draft-davie-tsvwg-rsvp-l3vpn-01.txt=20-=20c
	omments=20 |Sender:=20;
	bh=2dXedyk0Pq6OlzmEq9f3VPJbOkjKTvu0E8AfiuNoUYE=;
	b=eBK8UYYggUA9zNeUW/4EXy2MzrfsOl6Y/dSIloMjtrcHQSjpciNvdHligeOWxDcvu6TD3dhP
	747w00fAnMWQjUyUHNU3DfoykENc/41yrw5jB47qRfxPW9JLGitZe7mD;
Authentication-Results: ams-dkim-1; header.From=flefauch@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim1002 verified; ); 
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
Cc: Francois Le Faucheur IMAP <flefauch@cisco.com>,
	Ferit Yegenoglu <ferit.yegenoglu@lmco.com>,
	tsvwg tsvwg <tsvwg@ietf.org>, l3vpn@ietf.org
Subject: Re: [Tsvwg] draft-davie-tsvwg-rsvp-l3vpn-01.txt - comments 
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l3vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>
Errors-To: l3vpn-bounces@ietf.org

Hi Yakov,

On 27 Nov 2007, at 02:28, Yakov Rekhter wrote:

> Francois,
>
>> Hi Ferit,
>>
>> Thanks for your interest and comments. Thoughts on some of the points
>>
>> you bring up embedded below:
>>
>> On 21 Nov 2007, at 16:44, Yegenoglu, Ferit wrote:
>>
>>> Hi Bruce, Francois, and Ashok,
>>>
>>>
>>> I enjoyed reading your new draft =93draft-davie-tsvwg-rsvp-
>>> l3vpn-01.txt.=94  We are working on some problems that can benefit
>>> from the solutions that your draft is proposing. I have the
>>> following comments/questions:
>>>
>>>
>>> 1)       As far as I can tell, your draft is also applicable to the
>>> case where the aggregation region (per RFC 4804) is outside of the
>>> provider network, that is when the CE-PE interface is actually =20
>>> carrying aggregate RSVP messages. Can you confirm this? If this  
>>> is =20
>>> correct I would suggest adding a note to that effect in your draft.
>> This is correct. It is also applicable to RFC4804 sessions (as  
>> well =20
>> as RFC3175 sessions for that matter). We'll add a statement to  
>> that =20
>> effect.
>>>
>>> 5)  Is there a reference for the approaches summarized in
>>> Appendix A.2 and A.3?
>>> we're not aware of references documenting these other approaches in
>>> further details.
>>> From the brief descriptions provided in your draft I have a feeling
>>> that they may not work for the inter-AS Option B case as it may not
>>> be possible to uniquely identify sessions between two ASBRs.
>
>> Right. Or perhaps more accurately, they would require further
>> extensions to operate in inter-AS Option B.
>
> Could you elaborate on what "further extensions" be required.

To make the approach described in Appendix A.3 work in inter-AS  
Option B, one avenue would be to get ASBR to :
	* readvertise VRF-labels (with "dummy addresses")
	* process RSVP messages and maintain RSVP states within VRF context
	* be able to do IP lookup inside VRF context in order to forward  
Path (as we discussed together) presumably maintaining VRF-like tables
	* swap dummy addresses inside Path message PHOP when forwarding them  
(for forwarding of Resv upstream)

Also, regarding Appendix A.3 approach, a method would have to be  
defined to allow the ingress-PE to pick the right VRF-label to apply  
when forwarding the Path message in the first place (eg in the  
simpler case of intra-AS: ingress-PE knows the egress-PE, but how  
exactly does ingress-PE pick the right VRF-label out of the multiple  
advertised by the egress-PE?).

Cheers

Francois


>
> Yakov.




