
From tena@huawei.com  Tue Dec  1 19:18:00 2009
Return-Path: <tena@huawei.com>
X-Original-To: opsawg@core3.amsl.com
Delivered-To: opsawg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A3C323A67E9 for <opsawg@core3.amsl.com>; Tue,  1 Dec 2009 19:18:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.494
X-Spam-Level: 
X-Spam-Status: No, score=-100.494 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  HTML_MESSAGE=0.001, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k48ZReVqB-2p for <opsawg@core3.amsl.com>; Tue,  1 Dec 2009 19:17:59 -0800 (PST)
Received: from szxga04-in.huawei.com (unknown [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id DA9423A67AE for <opsawg@ietf.org>; Tue,  1 Dec 2009 19:17:58 -0800 (PST)
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KU0007NN956Z7@szxga04-in.huawei.com> for opsawg@ietf.org; Wed, 02 Dec 2009 11:17:30 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KU000MXG956YT@szxga04-in.huawei.com> for opsawg@ietf.org; Wed, 02 Dec 2009 11:17:30 +0800 (CST)
Received: from z24109b ([10.70.39.142]) by szxml06-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KU0007SM9563O@szxml06-in.huawei.com> for opsawg@ietf.org; Wed, 02 Dec 2009 11:17:30 +0800 (CST)
Date: Wed, 02 Dec 2009 11:17:30 +0800
From: Tina TSOU <tena@huawei.com>
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
Message-id: <009301ca72fd$fb706560$8e27460a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Outlook Express 6.00.2900.3598
Content-type: multipart/alternative; boundary="Boundary_(ID_iFZYhOCDrU0Nix8VolN3OQ)"
X-Priority: 3
X-MSMail-priority: Normal
References: <002201ca701a$817f1390$8e27460a@china.huawei.com>
Cc: opsawg@ietf.org
Subject: Re: [OPSAWG] Network configuration in IP network
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Dec 2009 03:18:00 -0000

This is a multi-part message in MIME format.

--Boundary_(ID_iFZYhOCDrU0Nix8VolN3OQ)
Content-type: text/plain; charset=gb2312
Content-transfer-encoding: 7BIT

Hi Juergen,
The basic problem the document raises is that the cost of bootstrapping IP 
network nodes (i.e. provisioning an initial IP address and mask and associating 
it with a device identity) in a large-scale IP network so that they can be 
managed from a central point can be very high. Frequently the nodes themselves 
are reached through another operator's network. This is an operations problem, 
although it may require additional protocol solutions, so I thought it would be 
sensible to bring it to OAM Area first. A potential breakdown of the work we had 
in mind goes like this:

1) Survey of methods for plug-and-play bootstrapping of access nodes.

2x, y, z ...) Applicability of method x, y, z for plug-and-play bootstrapping of 
access nodes
   -- limitations on network topology
   -- other constraints on network deployment
   -- operational considerations.

3) If a new method is required: a description of the requirements.
    We're into BOF territory if we get this far, and maybe not in the OAM Area.



B. R.
Tina
http://tinatsou.weebly.com/contact.html


Begin forwarded message:


  From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
  Date: November 28, 2009 10:21:31 PM GMT+08:00
  To: Tina TSOU <tena@huawei.com>
  Cc: "opsawg@ietf.org" <opsawg@ietf.org>
  Subject: Re: [OPSAWG] Network configuration in IP network
  Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>


  On Sat, Nov 28, 2009 at 12:04:07PM +0100, Tina TSOU wrote:

    Hi all,

    Here are the updated slides for Network configuration in IP network.



    The I-D is below.



    Comments are very welcome.


  So what is the purpose of this document? Why did you post it?

  /js

  -- 
  Juergen Schoenwaelder           Jacobs University Bremen gGmbH
  Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
  Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>



  ----- Original Message ----- 
  From: Tina TSOU 
  To: opsawg@ietf.org 
  Sent: Saturday, November 28, 2009 7:04 PM
  Subject: [OPSAWG] Network configuration in IP network


  Hi all,
  Here are the updated slides for Network configuration in IP network.

  The I-D is below.

  Comments are very welcome.

  Have a nice weekend:)


  B. R.
  Tina

  http://tinatsou.weebly.com/contact.html

   
  ----- Original Message ----- 
  From: IETF I-D Submission Tool 
  To: internet-drafts@ietf.org 
  Cc: tena@huawei.com 
  Sent: Saturday, November 28, 2009 4:16 PM
  Subject: Manual Post Requested for draft-tsou-network-configuration-problem-statement


  Manual Posting Requested for following Internet-Draft:

  I-D Submission Tool URL: https://datatracker.ietf.org/idst/status.cgi?submission_id=19887


  Filename:    draft-tsou-network-configuration-problem-statement
  Version:    01
  Staging URL:    http://www.ietf.org/staging/draft-tsou-network-configuration-problem-statement-01.txt
  Title:    Network configuration problem statement
  Creation_date:    2009-11-28
  WG ID:    Individual Submission
  Number_of_pages: 8
  Abstract:
  With the network evolution to all IP, the network configuration needs to be enhanced because of large number of network devices and service tunnels. 
  The existing IP network management mainly depends on manual configuration. The cost will be very high if all these work are performed manually and it is a great burden for service providers to deploy and maintain such large scale IP networks. 
  This document discusses problems related to reducing network configuration workload and transmission tunnel setup between network devices and NMS (Network Management System).


  Submitter: Tina Tsou (tena@huawei.com)

  Author(s):
  Tina Tsou, tena@huawei.com



  B. R.
  Tina

  http://tinatsou.weebly.com/contact.html



------------------------------------------------------------------------------


  _______________________________________________
  OPSAWG mailing list
  OPSAWG@ietf.org
  https://www.ietf.org/mailman/listinfo/opsawg

--Boundary_(ID_iFZYhOCDrU0Nix8VolN3OQ)
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.2900.3627" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial>Hi Juergen,</FONT></DIV>
<DIV><FONT face=Arial>The basic problem the document raises is that the cost of 
bootstrapping IP <BR>network nodes (i.e. provisioning an initial IP address and 
mask and associating <BR>it with a device identity) in a large-scale IP network 
so that they can be <BR>managed from a central point can be very high. 
Frequently the nodes themselves <BR>are reached through another operator's 
network. This is an operations problem, <BR>although it may require additional 
protocol solutions, so I thought it would be <BR>sensible to bring it to OAM 
Area first. A potential breakdown of the work we had <BR>in mind goes like 
this:<BR><BR>1) Survey of methods for plug-and-play bootstrapping of access 
nodes.<BR><BR>2x, y, z ...) Applicability of method x, y, z for plug-and-play 
bootstrapping of <BR>access nodes<BR>&nbsp;&nbsp; -- limitations on network 
topology<BR>&nbsp;&nbsp; -- other constraints on network 
deployment<BR>&nbsp;&nbsp; -- operational considerations.<BR><BR>3) If a new 
method is required: a description of the requirements.<BR>&nbsp;&nbsp;&nbsp; 
We're into BOF territory if we get this far, and maybe not in the OAM 
Area.<BR></FONT></DIV>
<DIV><FONT face=Arial></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial>B. R.<BR>Tina<BR></FONT><A 
href="http://tinatsou.weebly.com/contact.html"><FONT 
face=Arial>http://tinatsou.weebly.com/contact.html</FONT></A><BR></DIV>
<DIV>
<DIV>&nbsp;</DIV>
<DIV>Begin forwarded message:</DIV><BR class=Apple-interchange-newline>
<BLOCKQUOTE type="cite">
  <DIV>
  <DIV style="MARGIN: 0px"><FONT style="FONT: 12px Helvetica; COLOR: #000000" 
  face=Helvetica color=#000000 size=3><B>From: </B></FONT><FONT 
  style="FONT: 12px Helvetica" face=Helvetica size=3>Juergen Schoenwaelder 
  &lt;<A href="">j.schoenwaelder@jacobs-university.de</A>&gt;</FONT></DIV>
  <DIV style="MARGIN: 0px"><FONT style="FONT: 12px Helvetica; COLOR: #000000" 
  face=Helvetica color=#000000 size=3><B>Date: </B></FONT><FONT 
  style="FONT: 12px Helvetica" face=Helvetica size=3>November 28, 2009 10:21:31 
  PM GMT+08:00</FONT></DIV>
  <DIV style="MARGIN: 0px"><FONT style="FONT: 12px Helvetica; COLOR: #000000" 
  face=Helvetica color=#000000 size=3><B>To: </B></FONT><FONT 
  style="FONT: 12px Helvetica" face=Helvetica size=3>Tina TSOU &lt;<A 
  href="">tena@huawei.com</A>&gt;</FONT></DIV>
  <DIV style="MARGIN: 0px"><FONT style="FONT: 12px Helvetica; COLOR: #000000" 
  face=Helvetica color=#000000 size=3><B>Cc: </B></FONT><FONT 
  style="FONT: 12px Helvetica" face=Helvetica size=3>"<A 
  href="">opsawg@ietf.org</A>" &lt;<A 
  href="">opsawg@ietf.org</A>&gt;</FONT></DIV>
  <DIV style="MARGIN: 0px"><FONT style="FONT: 12px Helvetica; COLOR: #000000" 
  face=Helvetica color=#000000 size=3><B>Subject: </B></FONT><FONT 
  style="FONT: 12px Helvetica" face=Helvetica size=3><B>Re: [OPSAWG] Network 
  configuration in IP network</B></FONT></DIV>
  <DIV style="MARGIN: 0px"><FONT style="FONT: 12px Helvetica; COLOR: #000000" 
  face=Helvetica color=#000000 size=3><B>Reply-To: </B></FONT><FONT 
  style="FONT: 12px Helvetica" face=Helvetica size=3>Juergen Schoenwaelder 
  &lt;<A href="">j.schoenwaelder@jacobs-university.de</A>&gt;</FONT></DIV>
  <DIV style="MIN-HEIGHT: 14px; MARGIN: 0px"><BR></DIV></DIV>
  <DIV>On Sat, Nov 28, 2009 at 12:04:07PM +0100, Tina TSOU wrote:<BR>
  <BLOCKQUOTE type="cite">Hi all,<BR></BLOCKQUOTE>
  <BLOCKQUOTE type="cite">Here are the updated slides for Network 
    configuration in IP network.<BR></BLOCKQUOTE>
  <BLOCKQUOTE type="cite"><BR></BLOCKQUOTE>
  <BLOCKQUOTE type="cite">The I-D is below.<BR></BLOCKQUOTE>
  <BLOCKQUOTE type="cite"><BR></BLOCKQUOTE>
  <BLOCKQUOTE type="cite">Comments are very welcome.<BR></BLOCKQUOTE><BR>So what 
  is the purpose of this document? Why did you post it?<BR><BR>/js<BR><BR>-- 
  <BR>Juergen Schoenwaelder 
  &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Jacobs University 
  Bremen gGmbH<BR>Phone: +49 421 200 3587 
  &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Campus Ring 1, 28759 Bremen, 
  Germany<BR>Fax: &nbsp;&nbsp;+49 421 200 3103 
  &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;<A 
  href="">http://www.jacobs-university.de/</A>&gt;<BR></DIV></BLOCKQUOTE><BR></DIV>
<BLOCKQUOTE 
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
  <DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
  <DIV 
  style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B> 
  <A title=tena@huawei.com href="mailto:tena@huawei.com">Tina TSOU</A> </DIV>
  <DIV style="FONT: 10pt arial"><B>To:</B> <A title=opsawg@ietf.org 
  href="mailto:opsawg@ietf.org">opsawg@ietf.org</A> </DIV>
  <DIV style="FONT: 10pt arial"><B>Sent:</B> Saturday, November 28, 2009 7:04 
  PM</DIV>
  <DIV style="FONT: 10pt arial"><B>Subject:</B> [OPSAWG] Network configuration 
  in IP network</DIV>
  <DIV><BR></DIV>
  <DIV><FONT face=Arial size=2>Hi all,</FONT></DIV>
  <DIV><FONT face=Arial size=2>Here are the updated slides for Network 
  configuration in IP network.</FONT></DIV>
  <DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
  <DIV><FONT face=Arial size=2>The I-D is below.</FONT></DIV>
  <DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
  <DIV><FONT face=Arial size=2>Comments are very welcome.</FONT></DIV>
  <DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
  <DIV><FONT face=Arial size=2>Have a nice weekend:)</FONT></DIV>
  <DIV><FONT face=Arial size=2>&nbsp;</DIV>
  <DIV>
  <DIV>&nbsp;</DIV>
  <DIV>B. R.<BR>Tina<BR></DIV>
  <DIV><A 
  href="http://tinatsou.weebly.com/contact.html">http://tinatsou.weebly.com/contact.html</A></DIV>
  <DIV><BR>&nbsp;</DIV>
  <DIV style="FONT: 10pt arial">----- Original Message ----- 
  <DIV style="BACKGROUND: #e4e4e4; font-color: black"><B>From:</B> <A 
  title=idsubmission@ietf.org href="mailto:idsubmission@ietf.org">IETF I-D 
  Submission Tool</A> </DIV>
  <DIV><B>To:</B> <A title=internet-drafts@ietf.org 
  href="mailto:internet-drafts@ietf.org">internet-drafts@ietf.org</A> </DIV>
  <DIV><B>Cc:</B> <A title=tena@huawei.com 
  href="mailto:tena@huawei.com">tena@huawei.com</A> </DIV>
  <DIV><B>Sent:</B> Saturday, November 28, 2009 4:16 PM</DIV>
  <DIV><B>Subject:</B> Manual Post Requested for 
  draft-tsou-network-configuration-problem-statement</DIV></DIV>
  <DIV><BR></DIV>Manual Posting Requested for following 
  Internet-Draft:<BR><BR>I-D Submission Tool URL: <A 
  href="https://datatracker.ietf.org/idst/status.cgi?submission_id=19887">https://datatracker.ietf.org/idst/status.cgi?submission_id=19887</A><BR><BR><BR>Filename: 
  &nbsp;&nbsp; draft-tsou-network-configuration-problem-statement<BR>Version: 
  &nbsp;&nbsp; 01<BR>Staging URL: &nbsp;&nbsp; <A 
  href="http://www.ietf.org/staging/draft-tsou-network-configuration-problem-statement-01.txt">http://www.ietf.org/staging/draft-tsou-network-configuration-problem-statement-01.txt</A><BR>Title: 
  &nbsp;&nbsp; Network configuration problem statement<BR>Creation_date: 
  &nbsp;&nbsp; 2009-11-28<BR>WG ID: &nbsp;&nbsp; Individual 
  Submission<BR>Number_of_pages: 8<BR>Abstract:<BR>With the network evolution to 
  all IP, the network configuration needs to be enhanced because of large number 
  of network devices and service tunnels. <BR>The existing IP network management 
  mainly depends on manual configuration. The cost will be very high if all 
  these work are performed manually and it is a great burden for service 
  providers to deploy and maintain such large scale IP networks. <BR>This 
  document discusses problems related to reducing network configuration workload 
  and transmission tunnel setup between network devices and NMS (Network 
  Management System).<BR><BR><BR>Submitter: Tina Tsou (<A 
  href="mailto:tena@huawei.com">tena@huawei.com</A>)<BR><BR>Author(s):<BR>Tina 
  Tsou, <A 
  href="mailto:tena@huawei.com">tena@huawei.com</A><BR><BR><BR></FONT></DIV>
  <DIV><FONT face=Arial size=2>B. R.<BR>Tina<BR></FONT></DIV>
  <DIV><FONT face=Arial size=2><A 
  href="http://tinatsou.weebly.com/contact.html">http://tinatsou.weebly.com/contact.html</A><BR></FONT></DIV>
  <P>
  <HR>

  <P></P>_______________________________________________<BR>OPSAWG mailing 
  list<BR>OPSAWG@ietf.org<BR>https://www.ietf.org/mailman/listinfo/opsawg<BR></BLOCKQUOTE></BODY></HTML>

--Boundary_(ID_iFZYhOCDrU0Nix8VolN3OQ)--

From tena@huawei.com  Tue Dec  1 19:38:15 2009
Return-Path: <tena@huawei.com>
X-Original-To: opsawg@core3.amsl.com
Delivered-To: opsawg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 80ED23A6774 for <opsawg@core3.amsl.com>; Tue,  1 Dec 2009 19:38:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.488
X-Spam-Level: 
X-Spam-Status: No, score=-99.488 tagged_above=-999 required=5 tests=[AWL=-1.006, BAYES_00=-2.599, FAKE_REPLY_C=2.012, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6dDZxA1Bhf0I for <opsawg@core3.amsl.com>; Tue,  1 Dec 2009 19:38:13 -0800 (PST)
Received: from szxga02-in.huawei.com (unknown [119.145.14.65]) by core3.amsl.com (Postfix) with ESMTP id 6A69E3A67AE for <opsawg@ietf.org>; Tue,  1 Dec 2009 19:38:13 -0800 (PST)
Received: from huawei.com (szxga02-in [172.24.2.6]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KU000BRLA37HD@szxga02-in.huawei.com> for opsawg@ietf.org; Wed, 02 Dec 2009 11:37:55 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KU00019FA37LF@szxga02-in.huawei.com> for opsawg@ietf.org; Wed, 02 Dec 2009 11:37:55 +0800 (CST)
Received: from z24109b ([10.70.39.142]) by szxml06-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KU000CVCA37W6@szxml06-in.huawei.com> for opsawg@ietf.org; Wed, 02 Dec 2009 11:37:55 +0800 (CST)
Date: Wed, 02 Dec 2009 11:37:54 +0800
From: Tina TSOU <tena@huawei.com>
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
Message-id: <00c101ca7300$d571f510$8e27460a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Outlook Express 6.00.2900.3598
Content-type: multipart/alternative; boundary="Boundary_(ID_9VqbVWiwE0C78qxt8xHTIg)"
X-Priority: 3
X-MSMail-priority: Normal
Cc: opsawg@ietf.org
Subject: Re: [OPSAWG] Network configuration in IP network
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Dec 2009 03:38:15 -0000

This is a multi-part message in MIME format.

--Boundary_(ID_9VqbVWiwE0C78qxt8xHTIg)
Content-type: text/plain; charset=gb2312
Content-transfer-encoding: 7BIT

Oops, I have to correct myself as below.

The basic problem the document raises is that the cost of bootstrapping IP 
network nodes (i.e. provisioning an initial IP address and mask and associating 
it with a device identity) in a large-scale IP network so that they can be 
managed from a central point can be very high. Frequently the nodes themselves 
are reached through another operator's network. This is an operations problem, 
although it may require additional protocol solutions, so I thought it would be 
sensible to bring it to OAM Area first. A potential breakdown of the work we had 
in mind goes like this:

1) Survey of methods for plug-and-play bootstrapping of network nodes.

2x, y, z ...) Applicability of method x, y, z for plug-and-play bootstrapping of 
network nodes
   -- limitations on network topology
   -- other constraints on network deployment
   -- operational considerations.

3) If a new method is required: a description of the requirements.
    We're into BOF territory if we get this far, and maybe not in the OAM Area.




B. R.
Tina
http://tinatsou.weebly.com/contact.html

  ----- Original Message ----- 
  From: Tina TSOU 
  To: Juergen Schoenwaelder 
  Cc: opsawg@ietf.org 
  Sent: Wednesday, December 02, 2009 11:17 AM
  Subject: Re: [OPSAWG] Network configuration in IP network


  Hi Juergen,
  The basic problem the document raises is that the cost of bootstrapping IP 
  network nodes (i.e. provisioning an initial IP address and mask and associating 
  it with a device identity) in a large-scale IP network so that they can be 
  managed from a central point can be very high. Frequently the nodes themselves 
  are reached through another operator's network. This is an operations problem, 
  although it may require additional protocol solutions, so I thought it would be 
  sensible to bring it to OAM Area first. A potential breakdown of the work we had 
  in mind goes like this:

  1) Survey of methods for plug-and-play bootstrapping of access nodes.

  2x, y, z ...) Applicability of method x, y, z for plug-and-play bootstrapping of 
  access nodes
     -- limitations on network topology
     -- other constraints on network deployment
     -- operational considerations.

  3) If a new method is required: a description of the requirements.
      We're into BOF territory if we get this far, and maybe not in the OAM Area.



  B. R.
  Tina
  http://tinatsou.weebly.com/contact.html


  Begin forwarded message:


    From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
    Date: November 28, 2009 10:21:31 PM GMT+08:00
    To: Tina TSOU <tena@huawei.com>
    Cc: "opsawg@ietf.org" <opsawg@ietf.org>
    Subject: Re: [OPSAWG] Network configuration in IP network
    Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>


    On Sat, Nov 28, 2009 at 12:04:07PM +0100, Tina TSOU wrote:

      Hi all,

      Here are the updated slides for Network configuration in IP network.



      The I-D is below.



      Comments are very welcome.


    So what is the purpose of this document? Why did you post it?

    /js

    -- 
    Juergen Schoenwaelder           Jacobs University Bremen gGmbH
    Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
    Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>



    ----- Original Message ----- 
    From: Tina TSOU 
    To: opsawg@ietf.org 
    Sent: Saturday, November 28, 2009 7:04 PM
    Subject: [OPSAWG] Network configuration in IP network


    Hi all,
    Here are the updated slides for Network configuration in IP network.

    The I-D is below.

    Comments are very welcome.

    Have a nice weekend:)


    B. R.
    Tina

    http://tinatsou.weebly.com/contact.html

     
    ----- Original Message ----- 
    From: IETF I-D Submission Tool 
    To: internet-drafts@ietf.org 
    Cc: tena@huawei.com 
    Sent: Saturday, November 28, 2009 4:16 PM
    Subject: Manual Post Requested for draft-tsou-network-configuration-problem-statement


    Manual Posting Requested for following Internet-Draft:

    I-D Submission Tool URL: https://datatracker.ietf.org/idst/status.cgi?submission_id=19887


    Filename:    draft-tsou-network-configuration-problem-statement
    Version:    01
    Staging URL:    http://www.ietf.org/staging/draft-tsou-network-configuration-problem-statement-01.txt
    Title:    Network configuration problem statement
    Creation_date:    2009-11-28
    WG ID:    Individual Submission
    Number_of_pages: 8
    Abstract:
    With the network evolution to all IP, the network configuration needs to be enhanced because of large number of network devices and service tunnels. 
    The existing IP network management mainly depends on manual configuration. The cost will be very high if all these work are performed manually and it is a great burden for service providers to deploy and maintain such large scale IP networks. 
    This document discusses problems related to reducing network configuration workload and transmission tunnel setup between network devices and NMS (Network Management System).


    Submitter: Tina Tsou (tena@huawei.com)

    Author(s):
    Tina Tsou, tena@huawei.com



    B. R.
    Tina

    http://tinatsou.weebly.com/contact.html



----------------------------------------------------------------------------


    _______________________________________________
    OPSAWG mailing list
    OPSAWG@ietf.org
    https://www.ietf.org/mailman/listinfo/opsawg

--Boundary_(ID_9VqbVWiwE0C78qxt8xHTIg)
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.2900.3627" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>Oops, I have to correct myself as 
below.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV>
<P class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN lang=EN-US>The basic 
problem the document raises is that the cost of bootstrapping IP <BR>network 
nodes (i.e. provisioning an initial IP address and mask and associating <BR>it 
with a device identity) in a large-scale IP network so that they can be 
<BR>managed from a central point can be very high. Frequently the nodes 
themselves <BR>are reached through another operator's network. This is an 
operations problem, <BR>although it may require additional protocol solutions, 
so&nbsp;I thought it would be <BR>sensible to bring it to OAM Area first. A 
potential breakdown of the work we had <BR>in mind goes like this:<BR><BR>1) 
Survey of methods for plug-and-play bootstrapping of network nodes.<BR><BR>2x, 
y, z ...) Applicability of method x, y, z for plug-and-play bootstrapping of 
<BR>network nodes<BR>&nbsp;&nbsp; -- limitations on network 
topology<BR>&nbsp;&nbsp; -- other constraints on network 
deployment<BR>&nbsp;&nbsp; -- operational considerations.<BR><BR>3) If a new 
method is required: a description of the requirements.<BR>&nbsp;&nbsp;&nbsp; 
We're into BOF territory if we get this far, and maybe not in the OAM Area.<SPAN 
style="mso-no-proof: yes"></SPAN></SPAN></P></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV>B. R.<BR>Tina<BR><A 
href="http://tinatsou.weebly.com/contact.html">http://tinatsou.weebly.com/contact.html</A><BR></DIV>
<BLOCKQUOTE dir=ltr 
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
  <DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
  <DIV 
  style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B> 
  <A title=tena@huawei.com href="mailto:tena@huawei.com">Tina TSOU</A> </DIV>
  <DIV style="FONT: 10pt arial"><B>To:</B> <A 
  title=j.schoenwaelder@jacobs-university.de 
  href="mailto:j.schoenwaelder@jacobs-university.de">Juergen Schoenwaelder</A> 
  </DIV>
  <DIV style="FONT: 10pt arial"><B>Cc:</B> <A title=opsawg@ietf.org 
  href="mailto:opsawg@ietf.org">opsawg@ietf.org</A> </DIV>
  <DIV style="FONT: 10pt arial"><B>Sent:</B> Wednesday, December 02, 2009 11:17 
  AM</DIV>
  <DIV style="FONT: 10pt arial"><B>Subject:</B> Re: [OPSAWG] Network 
  configuration in IP network</DIV>
  <DIV><BR></DIV>
  <DIV><FONT face=Arial>Hi Juergen,</FONT></DIV>
  <DIV><FONT face=Arial>The basic problem the document raises is that the cost 
  of bootstrapping IP <BR>network nodes (i.e. provisioning an initial IP address 
  and mask and associating <BR>it with a device identity) in a large-scale IP 
  network so that they can be <BR>managed from a central point can be very high. 
  Frequently the nodes themselves <BR>are reached through another operator's 
  network. This is an operations problem, <BR>although it may require additional 
  protocol solutions, so I thought it would be <BR>sensible to bring it to OAM 
  Area first. A potential breakdown of the work we had <BR>in mind goes like 
  this:<BR><BR>1) Survey of methods for plug-and-play bootstrapping of access 
  nodes.<BR><BR>2x, y, z ...) Applicability of method x, y, z for plug-and-play 
  bootstrapping of <BR>access nodes<BR>&nbsp;&nbsp; -- limitations on network 
  topology<BR>&nbsp;&nbsp; -- other constraints on network 
  deployment<BR>&nbsp;&nbsp; -- operational considerations.<BR><BR>3) If a new 
  method is required: a description of the requirements.<BR>&nbsp;&nbsp;&nbsp; 
  We're into BOF territory if we get this far, and maybe not in the OAM 
  Area.<BR></FONT></DIV>
  <DIV><FONT face=Arial></FONT>&nbsp;</DIV>
  <DIV><FONT face=Arial></FONT>&nbsp;</DIV>
  <DIV><FONT face=Arial>B. R.<BR>Tina<BR></FONT><A 
  href="http://tinatsou.weebly.com/contact.html"><FONT 
  face=Arial>http://tinatsou.weebly.com/contact.html</FONT></A><BR></DIV>
  <DIV>
  <DIV>&nbsp;</DIV>
  <DIV>Begin forwarded message:</DIV><BR class=Apple-interchange-newline>
  <BLOCKQUOTE type="cite">
    <DIV>
    <DIV style="MARGIN: 0px"><FONT style="FONT: 12px Helvetica; COLOR: #000000" 
    face=Helvetica color=#000000 size=3><B>From: </B></FONT><FONT 
    style="FONT: 12px Helvetica" face=Helvetica size=3>Juergen Schoenwaelder 
    &lt;<A href="">j.schoenwaelder@jacobs-university.de</A>&gt;</FONT></DIV>
    <DIV style="MARGIN: 0px"><FONT style="FONT: 12px Helvetica; COLOR: #000000" 
    face=Helvetica color=#000000 size=3><B>Date: </B></FONT><FONT 
    style="FONT: 12px Helvetica" face=Helvetica size=3>November 28, 2009 
    10:21:31 PM GMT+08:00</FONT></DIV>
    <DIV style="MARGIN: 0px"><FONT style="FONT: 12px Helvetica; COLOR: #000000" 
    face=Helvetica color=#000000 size=3><B>To: </B></FONT><FONT 
    style="FONT: 12px Helvetica" face=Helvetica size=3>Tina TSOU &lt;<A 
    href="">tena@huawei.com</A>&gt;</FONT></DIV>
    <DIV style="MARGIN: 0px"><FONT style="FONT: 12px Helvetica; COLOR: #000000" 
    face=Helvetica color=#000000 size=3><B>Cc: </B></FONT><FONT 
    style="FONT: 12px Helvetica" face=Helvetica size=3>"<A 
    href="">opsawg@ietf.org</A>" &lt;<A 
    href="">opsawg@ietf.org</A>&gt;</FONT></DIV>
    <DIV style="MARGIN: 0px"><FONT style="FONT: 12px Helvetica; COLOR: #000000" 
    face=Helvetica color=#000000 size=3><B>Subject: </B></FONT><FONT 
    style="FONT: 12px Helvetica" face=Helvetica size=3><B>Re: [OPSAWG] Network 
    configuration in IP network</B></FONT></DIV>
    <DIV style="MARGIN: 0px"><FONT style="FONT: 12px Helvetica; COLOR: #000000" 
    face=Helvetica color=#000000 size=3><B>Reply-To: </B></FONT><FONT 
    style="FONT: 12px Helvetica" face=Helvetica size=3>Juergen Schoenwaelder 
    &lt;<A href="">j.schoenwaelder@jacobs-university.de</A>&gt;</FONT></DIV>
    <DIV style="MIN-HEIGHT: 14px; MARGIN: 0px"><BR></DIV></DIV>
    <DIV>On Sat, Nov 28, 2009 at 12:04:07PM +0100, Tina TSOU wrote:<BR>
    <BLOCKQUOTE type="cite">Hi all,<BR></BLOCKQUOTE>
    <BLOCKQUOTE type="cite">Here are the updated slides for Network 
      configuration in IP network.<BR></BLOCKQUOTE>
    <BLOCKQUOTE type="cite"><BR></BLOCKQUOTE>
    <BLOCKQUOTE type="cite">The I-D is below.<BR></BLOCKQUOTE>
    <BLOCKQUOTE type="cite"><BR></BLOCKQUOTE>
    <BLOCKQUOTE type="cite">Comments are very welcome.<BR></BLOCKQUOTE><BR>So 
    what is the purpose of this document? Why did you post 
    it?<BR><BR>/js<BR><BR>-- <BR>Juergen Schoenwaelder 
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Jacobs 
    University Bremen gGmbH<BR>Phone: +49 421 200 3587 
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Campus Ring 1, 28759 Bremen, 
    Germany<BR>Fax: &nbsp;&nbsp;+49 421 200 3103 
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;<A 
    href="">http://www.jacobs-university.de/</A>&gt;<BR></DIV></BLOCKQUOTE><BR></DIV>
  <BLOCKQUOTE 
  style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
    <DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
    <DIV 
    style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B> 
    <A title=tena@huawei.com href="mailto:tena@huawei.com">Tina TSOU</A> </DIV>
    <DIV style="FONT: 10pt arial"><B>To:</B> <A title=opsawg@ietf.org 
    href="mailto:opsawg@ietf.org">opsawg@ietf.org</A> </DIV>
    <DIV style="FONT: 10pt arial"><B>Sent:</B> Saturday, November 28, 2009 7:04 
    PM</DIV>
    <DIV style="FONT: 10pt arial"><B>Subject:</B> [OPSAWG] Network configuration 
    in IP network</DIV>
    <DIV><BR></DIV>
    <DIV><FONT face=Arial size=2>Hi all,</FONT></DIV>
    <DIV><FONT face=Arial size=2>Here are the updated slides for Network 
    configuration in IP network.</FONT></DIV>
    <DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
    <DIV><FONT face=Arial size=2>The I-D is below.</FONT></DIV>
    <DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
    <DIV><FONT face=Arial size=2>Comments are very welcome.</FONT></DIV>
    <DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
    <DIV><FONT face=Arial size=2>Have a nice weekend:)</FONT></DIV>
    <DIV><FONT face=Arial size=2>&nbsp;</DIV>
    <DIV>
    <DIV>&nbsp;</DIV>
    <DIV>B. R.<BR>Tina<BR></DIV>
    <DIV><A 
    href="http://tinatsou.weebly.com/contact.html">http://tinatsou.weebly.com/contact.html</A></DIV>
    <DIV><BR>&nbsp;</DIV>
    <DIV style="FONT: 10pt arial">----- Original Message ----- 
    <DIV style="BACKGROUND: #e4e4e4; font-color: black"><B>From:</B> <A 
    title=idsubmission@ietf.org href="mailto:idsubmission@ietf.org">IETF I-D 
    Submission Tool</A> </DIV>
    <DIV><B>To:</B> <A title=internet-drafts@ietf.org 
    href="mailto:internet-drafts@ietf.org">internet-drafts@ietf.org</A> </DIV>
    <DIV><B>Cc:</B> <A title=tena@huawei.com 
    href="mailto:tena@huawei.com">tena@huawei.com</A> </DIV>
    <DIV><B>Sent:</B> Saturday, November 28, 2009 4:16 PM</DIV>
    <DIV><B>Subject:</B> Manual Post Requested for 
    draft-tsou-network-configuration-problem-statement</DIV></DIV>
    <DIV><BR></DIV>Manual Posting Requested for following 
    Internet-Draft:<BR><BR>I-D Submission Tool URL: <A 
    href="https://datatracker.ietf.org/idst/status.cgi?submission_id=19887">https://datatracker.ietf.org/idst/status.cgi?submission_id=19887</A><BR><BR><BR>Filename: 
    &nbsp;&nbsp; draft-tsou-network-configuration-problem-statement<BR>Version: 
    &nbsp;&nbsp; 01<BR>Staging URL: &nbsp;&nbsp; <A 
    href="http://www.ietf.org/staging/draft-tsou-network-configuration-problem-statement-01.txt">http://www.ietf.org/staging/draft-tsou-network-configuration-problem-statement-01.txt</A><BR>Title: 
    &nbsp;&nbsp; Network configuration problem statement<BR>Creation_date: 
    &nbsp;&nbsp; 2009-11-28<BR>WG ID: &nbsp;&nbsp; Individual 
    Submission<BR>Number_of_pages: 8<BR>Abstract:<BR>With the network evolution 
    to all IP, the network configuration needs to be enhanced because of large 
    number of network devices and service tunnels. <BR>The existing IP network 
    management mainly depends on manual configuration. The cost will be very 
    high if all these work are performed manually and it is a great burden for 
    service providers to deploy and maintain such large scale IP networks. 
    <BR>This document discusses problems related to reducing network 
    configuration workload and transmission tunnel setup between network devices 
    and NMS (Network Management System).<BR><BR><BR>Submitter: Tina Tsou (<A 
    href="mailto:tena@huawei.com">tena@huawei.com</A>)<BR><BR>Author(s):<BR>Tina 
    Tsou, <A 
    href="mailto:tena@huawei.com">tena@huawei.com</A><BR><BR><BR></FONT></DIV>
    <DIV><FONT face=Arial size=2>B. R.<BR>Tina<BR></FONT></DIV>
    <DIV><FONT face=Arial size=2><A 
    href="http://tinatsou.weebly.com/contact.html">http://tinatsou.weebly.com/contact.html</A><BR></FONT></DIV>
    <P>
    <HR>

    <P></P>_______________________________________________<BR>OPSAWG mailing 
    list<BR>OPSAWG@ietf.org<BR>https://www.ietf.org/mailman/listinfo/opsawg<BR></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

--Boundary_(ID_9VqbVWiwE0C78qxt8xHTIg)--

From j.schoenwaelder@jacobs-university.de  Tue Dec  1 21:57:53 2009
Return-Path: <j.schoenwaelder@jacobs-university.de>
X-Original-To: opsawg@core3.amsl.com
Delivered-To: opsawg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 64CAE3A6805 for <opsawg@core3.amsl.com>; Tue,  1 Dec 2009 21:57:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.922
X-Spam-Level: 
X-Spam-Status: No, score=-1.922 tagged_above=-999 required=5 tests=[AWL=0.327,  BAYES_00=-2.599, HELO_EQ_DE=0.35]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UwGcQeH2Zw1d for <opsawg@core3.amsl.com>; Tue,  1 Dec 2009 21:57:52 -0800 (PST)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by core3.amsl.com (Postfix) with ESMTP id 32C2B3A67EE for <opsawg@ietf.org>; Tue,  1 Dec 2009 21:57:51 -0800 (PST)
Received: from localhost (demetrius4.jacobs-university.de [212.201.44.49]) by hermes.jacobs-university.de (Postfix) with ESMTP id 1378AC0034; Wed,  2 Dec 2009 06:57:43 +0100 (CET)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius4.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id i4mlhJdIoQUF; Wed,  2 Dec 2009 06:57:41 +0100 (CET)
Received: from elstar.local (elstar.iuhb02.iu-bremen.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id D9653C0004; Wed,  2 Dec 2009 06:57:41 +0100 (CET)
Received: by elstar.local (Postfix, from userid 501) id 32DF9E401F1; Wed,  2 Dec 2009 06:57:41 +0100 (CET)
Date: Wed, 2 Dec 2009 06:57:41 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: Tina TSOU <tena@huawei.com>
Message-ID: <20091202055741.GA6374@elstar.local>
Mail-Followup-To: Tina TSOU <tena@huawei.com>, "opsawg@ietf.org" <opsawg@ietf.org>
References: <00c101ca7300$d571f510$8e27460a@china.huawei.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <00c101ca7300$d571f510$8e27460a@china.huawei.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: "opsawg@ietf.org" <opsawg@ietf.org>
Subject: Re: [OPSAWG] Network configuration in IP network
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Dec 2009 05:57:53 -0000

On Wed, Dec 02, 2009 at 04:37:54AM +0100, Tina TSOU wrote:
 
> The basic problem the document raises is that the cost of bootstrapping IP
> network nodes (i.e. provisioning an initial IP address and mask and associating
> it with a device identity) in a large-scale IP network so that they can be
> managed from a central point can be very high. Frequently the nodes themselves
> are reached through another operator's network. This is an operations problem,
> although it may require additional protocol solutions, so I thought it would be
> sensible to bring it to OAM Area first. A potential breakdown of the work we had
> in mind goes like this:
> 
> 1) Survey of methods for plug-and-play bootstrapping of network nodes.
> 
> 2x, y, z ...) Applicability of method x, y, z for plug-and-play bootstrapping of
> network nodes
>    -- limitations on network topology
>    -- other constraints on network deployment
>    -- operational considerations.
> 
> 3) If a new method is required: a description of the requirements.
>     We're into BOF territory if we get this far, and maybe not in the OAM Area.

So I probably have to wait until 1) and 2x, y, z) has been written to
fully understand the problem.

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>

From tena@huawei.com  Wed Dec  2 00:11:40 2009
Return-Path: <tena@huawei.com>
X-Original-To: opsawg@core3.amsl.com
Delivered-To: opsawg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 28C8D3A6A5F for <opsawg@core3.amsl.com>; Wed,  2 Dec 2009 00:11:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.601
X-Spam-Level: 
X-Spam-Status: No, score=-100.601 tagged_above=-999 required=5 tests=[AWL=1.113, BAYES_00=-2.599, HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CsIsxWIgBuHu for <opsawg@core3.amsl.com>; Wed,  2 Dec 2009 00:11:38 -0800 (PST)
Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id D717B3A6A5B for <opsawg@ietf.org>; Wed,  2 Dec 2009 00:11:36 -0800 (PST)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KU000F5KMQXHV@szxga03-in.huawei.com> for opsawg@ietf.org; Wed, 02 Dec 2009 16:11:21 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KU0004SBMQWRQ@szxga03-in.huawei.com> for opsawg@ietf.org; Wed, 02 Dec 2009 16:11:20 +0800 (CST)
Received: from z24109b ([10.70.39.142]) by szxml06-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KU000B2LMQWAE@szxml06-in.huawei.com> for opsawg@ietf.org; Wed, 02 Dec 2009 16:11:20 +0800 (CST)
Date: Wed, 02 Dec 2009 16:11:20 +0800
From: Tina TSOU <tena@huawei.com>
To: 'David Harrington' <ietfdbh@comcast.net>
Message-id: <003b01ca7327$07d3cbc0$8e27460a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Outlook Express 6.00.2900.3598
Content-type: multipart/alternative; boundary="Boundary_(ID_0imoPvMeNxauqrg1Lif/Cg)"
X-Priority: 3
X-MSMail-priority: Normal
Cc: opsawg@ietf.org
Subject: [OPSAWG] Network configuration in IP network
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Dec 2009 08:11:40 -0000

This is a multi-part message in MIME format.

--Boundary_(ID_0imoPvMeNxauqrg1Lif/Cg)
Content-type: text/plain; charset=gb2312
Content-transfer-encoding: 7BIT

Hi David,
Thank you for your reply. Comments are in line below.


B. R.
Tina


On Nov 29, 2009, at 12:06 AM, David Harrington wrote:

> Hi,
>
> I think the presentation and I-D need to demonstrate that there is a
> problem that needs solving, and the IETF is the right group to attempt
> solving it.
>
> I do not see anything in the presentation that demonstrates that the
> IETF needs to solve the LTE configuration problem. I do not see any
> discussion of existing IETF protocols that should be applied to this
> problem.
>
> The need for this extra information was discussed in some detail at
> the OPSAWG session in ietf76, but I don't see much of the requested
> information.
>
> In section 3.1, you say
> "   In a typical IP network, e.g., LTE IP backhaul network,".
> is an LTE IP backhaul network a typical IP network?
I should have refined as large scale IP infrastructure. LTE IP  
backhaul network is not a typical IP network, but it is a large scale  
IP infrastructure. We do not need example. It is everywhere.
>
>
> " In the existing configuration method,"
> is this list of steps true for all existing configuration methods?
I checked the Survey document.
>
>
> "Configuring
>   service tunnel from NMS is already defined which is not included in
>   this document."
> Where is this defined?
SNMP etc.
>
>
> How were the estimates in Figure 1 determined?

It is based on NGMN typical scenarios and it is not real network. This example should be 
deleted in next version to avoid misunderstanding.

> "The existing IP network management mainly depends on manual
>   configuration."
> What is the basis for this assertion? According to RFC3535 (IAB
> Network Management Workshop),
> "   Most devices have a builtin command line interface (CLI) for
>   configuration and troubleshooting purposes.  Network access to the
>   CLI has traditionally been through the TELNET protocol, while the
> SSH
>   protocol is gaining momentum to address security issues associated
>   with TELNET. "
> So I don't agree with your assertion. Remote access seems to be a
> major approach to configuration.

The words "remote access" should be refined to avoid misunderstanding. 
The real problem is to reduce the cost of IP network configuration in the 
process of IP management tunnel setup while traversing another vendor's device.  
The process of IP management tunnel setup includes provisioning an initial IP 
address or mask and associating it with a device identity in a large-scale IP network .
Regarding TELNET, it is configured manually so it is not high efficient. 

> I also think it is important to be clear about what "existing IP
> network management" means. There are many existing IP network
> management tools for tasks other than configuration, such as
> monitoring, logging, performance analysis, etc.

It should be "existing IP network configuration"

>
>
> The section on problems to be solved for network configuration should
> probably start with an acknowledgement of the work that has already
> been by the IETF about problems to be solved for configuration,
> including the 100+ RFCs that come up in a search for the term
> "configuration".
>
> As other SDO technologies build atop IP technologies, the IETF may
> need to consider large scale configuration requirements further, but I
> do not feel that this document, as written, is a valuable addition to
> the IETF work on configuring IP networks.

Agree with you. Yes, I should make the question clearly. We have done  
a lot of work for configuring IP network. We need to consider large  
scale infrastructure now. This document should be largely refined.
>
>
> David Harrington
> dbharrington@comcast.net
> ietfdbh@comcast.net
> dharrington@huawei.com
>
>
> ________________________________
>
> From: opsawg-bounces@ietf.org [mailto:opsawg-bounces@ietf.org]
> On Behalf Of Tina TSOU
> Sent: Saturday, November 28, 2009 6:04 AM
> To: opsawg@ietf.org
> Subject: [OPSAWG] Network configuration in IP network
> 
> 
> Hi all,
> Here are the updated slides for Network configuration in IP
> network.
> 
> The I-D is below.
> 
> Comments are very welcome.
> 
> Have a nice weekend:)
> 
> 
> B. R.
> Tina
> 
> http://tinatsou.weebly.com/contact.html
>
> 
> ----- Original Message -----
> From: IETF I-D Submission Tool <mailto:idsubmission@ietf.org>
>
> To: internet-drafts@ietf.org
> Cc: tena@huawei.com
> Sent: Saturday, November 28, 2009 4:16 PM
> Subject: Manual Post Requested for
> draft-tsou-network-configuration-problem-statement
>
> Manual Posting Requested for following Internet-Draft:
> 
> I-D Submission Tool URL:
> https://datatracker.ietf.org/idst/status.cgi?submission_id=19887
> 
> 
> Filename:
> draft-tsou-network-configuration-problem-statement
> Version:    01
> Staging URL:
> http://www.ietf.org/staging/draft-tsou-network-configuration-problem-s
> tatement-01.txt
> Title:    Network configuration problem statement
> Creation_date:    2009-11-28
> WG ID:    Individual Submission
> Number_of_pages: 8
> Abstract:
> With the network evolution to all IP, the network
> configuration needs to be enhanced because of large number of network
> devices and service tunnels.
> The existing IP network management mainly depends on manual
> configuration. The cost will be very high if all these work are
> performed manually and it is a great burden for service providers to
> deploy and maintain such large scale IP networks.
> This document discusses problems related to reducing network
> configuration workload and transmission tunnel setup between network
> devices and NMS (Network Management System).
> 
> 
> Submitter: Tina Tsou (tena@huawei.com)
> 
> Author(s):
> Tina Tsou, tena@huawei.com
> 
> 
> 
> B. R.
> Tina
> 
> http://tinatsou.weebly.com/contact.html
> 
>
>

--Boundary_(ID_0imoPvMeNxauqrg1Lif/Cg)
Content-type: text/html; charset=gb2312
Content-transfer-encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dgb2312">
<META content=3D"MSHTML 6.00.2900.3627" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hi David,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Thank you for your reply. Comments are =
in line=20
below.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>B. R.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Tina</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2></FONT><BR>On Nov 29, 2009, at 12:06 =
AM, David=20
Harrington wrote:<BR><BR>&gt; Hi,<BR>&gt;<BR>&gt; I think the =
presentation and=20
I-D need to demonstrate that there is a<BR>&gt; problem that needs =
solving, and=20
the IETF is the right group to attempt<BR>&gt; solving =
it.<BR>&gt;<BR>&gt; I do=20
not see anything in the presentation that demonstrates that the<BR>&gt; =
IETF=20
needs to solve the LTE configuration problem. I do not see any<BR>&gt;=20
discussion of existing IETF protocols that should be applied to =
this<BR>&gt;=20
problem.<BR>&gt;<BR>&gt; The need for this extra information was =
discussed in=20
some detail at<BR>&gt; the OPSAWG session in ietf76, but I don't see =
much of the=20
requested<BR>&gt; information.<BR>&gt;<BR>&gt; In section 3.1, you =
say<BR>&gt;=20
"&nbsp;&nbsp; In a typical IP network, e.g., LTE IP backhaul =
network,".<BR>&gt;=20
is an LTE IP backhaul network a typical IP network?<BR>I should have =
refined as=20
large scale IP infrastructure. LTE IP&nbsp; <BR>backhaul network is not =
a=20
typical IP network, but it is a large scale&nbsp; <BR>IP infrastructure. =
We do=20
not need example. It is everywhere.<BR>&gt;<BR>&gt;<BR>&gt; " In the =
existing=20
configuration method,"<BR>&gt; is this list of steps true for all =
existing=20
configuration methods?<BR>I checked the Survey =
document.<BR>&gt;<BR>&gt;<BR>&gt;=20
"Configuring<BR>&gt;&nbsp;&nbsp; service tunnel from NMS is already =
defined=20
which is not included in<BR>&gt;&nbsp;&nbsp; this document."<BR>&gt; =
Where is=20
this defined?<BR>SNMP etc.<BR>&gt;<BR>&gt;<BR>&gt; How were the =
estimates in=20
Figure 1 determined?<BR></DIV>
<DIV>It is based on NGMN typical scenarios and it is not real network. =
This=20
example should be </DIV>
<DIV>deleted in next version to avoid misunderstanding.</DIV>
<DIV><BR>&gt; "The existing IP network management mainly depends on=20
manual<BR>&gt;&nbsp;&nbsp; configuration."<BR>&gt; What is the basis for =
this=20
assertion? According to RFC3535 (IAB<BR>&gt; Network Management=20
Workshop),<BR>&gt; "&nbsp;&nbsp; Most devices have a builtin command =
line=20
interface (CLI) for<BR>&gt;&nbsp;&nbsp; configuration and =
troubleshooting=20
purposes.&nbsp; Network access to the<BR>&gt;&nbsp;&nbsp; CLI has =
traditionally=20
been through the TELNET protocol, while the<BR>&gt; =
SSH<BR>&gt;&nbsp;&nbsp;=20
protocol is gaining momentum to address security issues=20
associated<BR>&gt;&nbsp;&nbsp; with TELNET. "<BR>&gt; So I don't agree =
with your=20
assertion. Remote access seems to be a<BR>&gt; major approach to=20
configuration.</DIV>
<DIV>&nbsp;</DIV>
<DIV>The words "remote access" should be refined to avoid =
misunderstanding.=20
</DIV>
<DIV>The&nbsp;real problem is to reduce the cost of IP network =
configuration in=20
the </DIV>
<DIV>process of IP management tunnel=20
setup&nbsp;while&nbsp;traversing&nbsp;another vendor's =
device.&nbsp;&nbsp;</DIV>
<DIV>The process of IP management tunnel setup&nbsp;includes =
provisioning an=20
initial IP </DIV>
<DIV>address or mask and associating it with a device identity in a =
large-scale=20
IP network .</DIV>
<DIV>Regarding TELNET, it is&nbsp;configured manually&nbsp;so it is not =
high=20
efficient.&nbsp;</DIV><FONT face=3D=CB=CE=CC=E5 size=3D2></FONT>
<DIV><FONT face=3DArial size=3D2></FONT><BR>&gt; I also think it is =
important to be=20
clear about what "existing IP<BR>&gt; network management" means. There =
are many=20
existing IP network<BR>&gt; management tools for tasks other than =
configuration,=20
such as<BR>&gt; monitoring, logging, performance analysis, etc.</DIV>
<DIV>&nbsp;</DIV>
<DIV>It should be "existing IP network=20
configuration"<BR><BR>&gt;<BR>&gt;<BR>&gt; The section on problems to be =
solved=20
for network configuration should<BR>&gt; probably start with an =
acknowledgement=20
of the work that has already<BR>&gt; been by the IETF about problems to =
be=20
solved for configuration,<BR>&gt; including the 100+ RFCs that come up =
in a=20
search for the term<BR>&gt; "configuration".<BR>&gt;<BR>&gt; As other =
SDO=20
technologies build atop IP technologies, the IETF may<BR>&gt; need to =
consider=20
large scale configuration requirements further, but I<BR>&gt; do not =
feel that=20
this document, as written, is a valuable addition to<BR>&gt; the IETF =
work on=20
configuring IP networks.</DIV>
<DIV><FONT face=3DArial size=3D2></FONT><BR>Agree with you. Yes, I =
should make the=20
question clearly. We have done&nbsp; <BR>a lot of work for configuring =
IP=20
network. We need to consider large&nbsp; <BR>scale infrastructure now. =
This=20
document should be largely refined.<BR>&gt;<BR>&gt;<BR>&gt; David=20
Harrington<BR>&gt; <A=20
href=3D"mailto:dbharrington@comcast.net">dbharrington@comcast.net</A><BR>=
&gt; <A=20
href=3D"mailto:ietfdbh@comcast.net">ietfdbh@comcast.net</A><BR>&gt; <A=20
href=3D"mailto:dharrington@huawei.com">dharrington@huawei.com</A><BR>&gt;=
<BR>&gt;<BR>&gt;=20
________________________________<BR>&gt;<BR>&gt; From: <A=20
href=3D"mailto:opsawg-bounces@ietf.org">opsawg-bounces@ietf.org</A>=20
[mailto:opsawg-bounces@ietf.org]<BR>&gt; On Behalf Of Tina TSOU<BR>&gt; =
Sent:=20
Saturday, November 28, 2009 6:04 AM<BR>&gt; To: <A=20
href=3D"mailto:opsawg@ietf.org">opsawg@ietf.org</A><BR>&gt; Subject: =
[OPSAWG]=20
Network configuration in IP network<BR>&gt; <BR>&gt; <BR>&gt; Hi =
all,<BR>&gt;=20
Here are the updated slides for Network configuration in IP<BR>&gt;=20
network.<BR>&gt; <BR>&gt; The I-D is below.<BR>&gt; <BR>&gt; Comments =
are very=20
welcome.<BR>&gt; <BR>&gt; Have a nice weekend:)<BR>&gt; <BR>&gt; =
<BR>&gt; B.=20
R.<BR>&gt; Tina<BR>&gt; <BR>&gt; <A=20
href=3D"http://tinatsou.weebly.com/contact.html">http://tinatsou.weebly.c=
om/contact.html</A><BR>&gt;<BR>&gt;=20
<BR>&gt; ----- Original Message -----<BR>&gt; From: IETF I-D Submission =
Tool=20
&lt;<A=20
href=3D"mailto:idsubmission@ietf.org">mailto:idsubmission@ietf.org</A>&gt=
;<BR>&gt;<BR>&gt;=20
To: <A=20
href=3D"mailto:internet-drafts@ietf.org">internet-drafts@ietf.org</A><BR>=
&gt; Cc:=20
<A href=3D"mailto:tena@huawei.com">tena@huawei.com</A><BR>&gt; Sent: =
Saturday,=20
November 28, 2009 4:16 PM<BR>&gt; Subject: Manual Post Requested =
for<BR>&gt;=20
draft-tsou-network-configuration-problem-statement<BR>&gt;<BR>&gt; =
Manual=20
Posting Requested for following Internet-Draft:<BR>&gt; <BR>&gt; I-D =
Submission=20
Tool URL:<BR>&gt; <A=20
href=3D"https://datatracker.ietf.org/idst/status.cgi?submission_id=3D1988=
7">https://datatracker.ietf.org/idst/status.cgi?submission_id=3D19887</A>=
<BR>&gt;=20
<BR>&gt; <BR>&gt; Filename:<BR>&gt;=20
draft-tsou-network-configuration-problem-statement<BR>&gt;=20
Version:&nbsp;&nbsp;&nbsp; 01<BR>&gt; Staging URL:<BR>&gt; <A=20
href=3D"http://www.ietf.org/staging/draft-tsou-network-configuration-prob=
lem-s">http://www.ietf.org/staging/draft-tsou-network-configuration-probl=
em-s</A><BR>&gt;=20
tatement-01.txt<BR>&gt; Title:&nbsp;&nbsp;&nbsp; Network configuration =
problem=20
statement<BR>&gt; Creation_date:&nbsp;&nbsp;&nbsp; 2009-11-28<BR>&gt; WG =

ID:&nbsp;&nbsp;&nbsp; Individual Submission<BR>&gt; Number_of_pages: =
8<BR>&gt;=20
Abstract:<BR>&gt; With the network evolution to all IP, the =
network<BR>&gt;=20
configuration needs to be enhanced because of large number of =
network<BR>&gt;=20
devices and service tunnels.<BR>&gt; The existing IP network management =
mainly=20
depends on manual<BR>&gt; configuration. The cost will be very high if =
all these=20
work are<BR>&gt; performed manually and it is a great burden for service =

providers to<BR>&gt; deploy and maintain such large scale IP =
networks.<BR>&gt;=20
This document discusses problems related to reducing network<BR>&gt;=20
configuration workload and transmission tunnel setup between =
network<BR>&gt;=20
devices and NMS (Network Management System).<BR>&gt; <BR>&gt; <BR>&gt;=20
Submitter: Tina Tsou (<A=20
href=3D"mailto:tena@huawei.com">tena@huawei.com</A>)<BR>&gt; <BR>&gt;=20
Author(s):<BR>&gt; Tina Tsou, <A=20
href=3D"mailto:tena@huawei.com">tena@huawei.com</A><BR>&gt; <BR>&gt; =
<BR>&gt;=20
<BR>&gt; B. R.<BR>&gt; Tina<BR>&gt; <BR>&gt; <A=20
href=3D"http://tinatsou.weebly.com/contact.html">http://tinatsou.weebly.c=
om/contact.html</A><BR>&gt;=20
<BR>&gt;<BR>&gt;<BR></DIV></BODY></HTML>

--Boundary_(ID_0imoPvMeNxauqrg1Lif/Cg)--

From tena@huawei.com  Sun Dec  6 20:07:16 2009
Return-Path: <tena@huawei.com>
X-Original-To: opsawg@core3.amsl.com
Delivered-To: opsawg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9BC6A3A683F for <opsawg@core3.amsl.com>; Sun,  6 Dec 2009 20:07:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.414
X-Spam-Level: 
X-Spam-Status: No, score=-101.414 tagged_above=-999 required=5 tests=[AWL=1.184, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Td+ZgZB10mPp for <opsawg@core3.amsl.com>; Sun,  6 Dec 2009 20:07:15 -0800 (PST)
Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id 3DF213A67F9 for <opsawg@ietf.org>; Sun,  6 Dec 2009 20:07:15 -0800 (PST)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KU9005CMKRRUK@szxga03-in.huawei.com> for opsawg@ietf.org; Mon, 07 Dec 2009 12:07:04 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KU900LM0KRRP3@szxga03-in.huawei.com> for opsawg@ietf.org; Mon, 07 Dec 2009 12:07:03 +0800 (CST)
Received: from z24109b ([10.70.39.142]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KU9004KAKRRYX@szxml04-in.huawei.com> for opsawg@ietf.org; Mon, 07 Dec 2009 12:07:03 +0800 (CST)
Date: Mon, 07 Dec 2009 12:07:03 +0800
From: Tina TSOU <tena@huawei.com>
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
Message-id: <00a401ca76f2$bbaf1fe0$8e27460a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Outlook Express 6.00.2900.3598
Content-type: multipart/alternative; boundary="Boundary_(ID_9sJUPl/gAr5c7BnQTCjp7w)"
X-Priority: 3
X-MSMail-priority: Normal
References: <00c101ca7300$d571f510$8e27460a@china.huawei.com> <20091202055741.GA6374@elstar.local>
Cc: opsawg@ietf.org
Subject: Re: [OPSAWG] Network configuration in IP network
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Dec 2009 04:07:16 -0000

This is a multi-part message in MIME format.

--Boundary_(ID_9sJUPl/gAr5c7BnQTCjp7w)
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT

Hi Juergen,
draft-tsou-network-configuration-problem-statement-00 was presented to the
OPSAWG in Hiroshima, but the question came back: what am I asking the OPSAWG
to do? Having thought about it a bit, I've decided that I'm really looking
for a protocol that would function like BOOTP or DHCP, but would work for
routers being added in a large-scale network deployment. I'm continuing to
investigate the issue, but since DHCP belongs to Internet Area, it seems logical
that any further discussions take place in that Area.
I will keep you updated.


B. R.
Tina
http://tinatsou.weebly.com/contact.html

  ----- Original Message ----- 
  From: Juergen Schoenwaelder 
  To: Tina TSOU 
  Cc: opsawg@ietf.org 
  Sent: Wednesday, December 02, 2009 1:57 PM
  Subject: Re: [OPSAWG] Network configuration in IP network


  On Wed, Dec 02, 2009 at 04:37:54AM +0100, Tina TSOU wrote:
   
  > The basic problem the document raises is that the cost of bootstrapping IP
  > network nodes (i.e. provisioning an initial IP address and mask and associating
  > it with a device identity) in a large-scale IP network so that they can be
  > managed from a central point can be very high. Frequently the nodes themselves
  > are reached through another operator's network. This is an operations problem,
  > although it may require additional protocol solutions, so I thought it would be
  > sensible to bring it to OAM Area first. A potential breakdown of the work we had
  > in mind goes like this:
  > 
  > 1) Survey of methods for plug-and-play bootstrapping of network nodes.
  > 
  > 2x, y, z ...) Applicability of method x, y, z for plug-and-play bootstrapping of
  > network nodes
  >    -- limitations on network topology
  >    -- other constraints on network deployment
  >    -- operational considerations.
  > 
  > 3) If a new method is required: a description of the requirements.
  >     We're into BOF territory if we get this far, and maybe not in the OAM Area.

  So I probably have to wait until 1) and 2x, y, z) has been written to
  fully understand the problem.

  /js

  -- 
  Juergen Schoenwaelder           Jacobs University Bremen gGmbH
  Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
  Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>

--Boundary_(ID_9sJUPl/gAr5c7BnQTCjp7w)
Content-type: text/html; charset=iso-8859-1
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=iso-8859-1">
<META content="MSHTML 6.00.2900.3627" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial>Hi Juergen,</FONT></DIV>
<DIV><FONT face=Arial>draft-tsou-network-configuration-problem-statement-00 was 
presented to the<BR>OPSAWG in Hiroshima, but the question came back: 
what&nbsp;am I&nbsp;asking the OPSAWG<BR>to do? Having thought about it a bit, 
I've decided that&nbsp;I'm really looking<BR>for a protocol that would function 
like BOOTP or DHCP, but would work for<BR>routers being added in a large-scale 
network deployment.&nbsp;I'm continuing to<BR>investigate the issue, but since 
DHCP belongs to Internet Area, it seems logical<BR>that any further discussions 
take place in that Area.</FONT></DIV>
<DIV><FONT face=Arial>I will keep you updated.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV>B. R.<BR>Tina<BR><A 
href="http://tinatsou.weebly.com/contact.html">http://tinatsou.weebly.com/contact.html</A><BR></DIV>
<BLOCKQUOTE 
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
  <DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
  <DIV 
  style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B> 
  <A title=j.schoenwaelder@jacobs-university.de 
  href="mailto:j.schoenwaelder@jacobs-university.de">Juergen Schoenwaelder</A> 
  </DIV>
  <DIV style="FONT: 10pt arial"><B>To:</B> <A title=tena@huawei.com 
  href="mailto:tena@huawei.com">Tina TSOU</A> </DIV>
  <DIV style="FONT: 10pt arial"><B>Cc:</B> <A title=opsawg@ietf.org 
  href="mailto:opsawg@ietf.org">opsawg@ietf.org</A> </DIV>
  <DIV style="FONT: 10pt arial"><B>Sent:</B> Wednesday, December 02, 2009 1:57 
  PM</DIV>
  <DIV style="FONT: 10pt arial"><B>Subject:</B> Re: [OPSAWG] Network 
  configuration in IP network</DIV>
  <DIV><BR></DIV>On Wed, Dec 02, 2009 at 04:37:54AM +0100, Tina TSOU 
  wrote:<BR>&nbsp;<BR>&gt; The basic problem the document raises is that the 
  cost of bootstrapping IP<BR>&gt; network nodes (i.e. provisioning an initial 
  IP address and mask and associating<BR>&gt; it with a device identity) in a 
  large-scale IP network so that they can be<BR>&gt; managed from a central 
  point can be very high. Frequently the nodes themselves<BR>&gt; are reached 
  through another operator's network. This is an operations problem,<BR>&gt; 
  although it may require additional protocol solutions, so I thought it would 
  be<BR>&gt; sensible to bring it to OAM Area first. A potential breakdown of 
  the work we had<BR>&gt; in mind goes like this:<BR>&gt; <BR>&gt; 1) Survey of 
  methods for plug-and-play bootstrapping of network nodes.<BR>&gt; <BR>&gt; 2x, 
  y, z ...) Applicability of method x, y, z for plug-and-play bootstrapping 
  of<BR>&gt; network nodes<BR>&gt;&nbsp;&nbsp;&nbsp; -- limitations on network 
  topology<BR>&gt;&nbsp;&nbsp;&nbsp; -- other constraints on network 
  deployment<BR>&gt;&nbsp;&nbsp;&nbsp; -- operational considerations.<BR>&gt; 
  <BR>&gt; 3) If a new method is required: a description of the 
  requirements.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp; We're into BOF territory if we 
  get this far, and maybe not in the OAM Area.<BR><BR>So I probably have to wait 
  until 1) and 2x, y, z) has been written to<BR>fully understand the 
  problem.<BR><BR>/js<BR><BR>-- <BR>Juergen 
  Schoenwaelder&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Jacobs University Bremen gGmbH<BR>Phone: +49 421 200 
  3587&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Campus Ring 1, 28759 
  Bremen, Germany<BR>Fax:&nbsp;&nbsp; +49 421 200 
  3103&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;<A 
  href="http://www.jacobs-university.de/">http://www.jacobs-university.de/</A>&gt;</BLOCKQUOTE></BODY></HTML>

--Boundary_(ID_9sJUPl/gAr5c7BnQTCjp7w)--

From tena@huawei.com  Tue Dec 15 03:29:25 2009
Return-Path: <tena@huawei.com>
X-Original-To: opsawg@core3.amsl.com
Delivered-To: opsawg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E58FA3A672E for <opsawg@core3.amsl.com>; Tue, 15 Dec 2009 03:29:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -96.477
X-Spam-Level: 
X-Spam-Status: No, score=-96.477 tagged_above=-999 required=5 tests=[AWL=3.133, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=0.001,  RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eyHsm2DzmmUb for <opsawg@core3.amsl.com>; Tue, 15 Dec 2009 03:29:24 -0800 (PST)
Received: from szxga02-in.huawei.com (unknown [119.145.14.65]) by core3.amsl.com (Postfix) with ESMTP id 319A33A680B for <opsawg@ietf.org>; Tue, 15 Dec 2009 03:29:24 -0800 (PST)
Received: from huawei.com (szxga02-in [172.24.2.6]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KUO007NFYKCCY@szxga02-in.huawei.com> for opsawg@ietf.org; Tue, 15 Dec 2009 19:29:00 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KUO000OUYKBGS@szxga02-in.huawei.com> for opsawg@ietf.org; Tue, 15 Dec 2009 19:29:00 +0800 (CST)
Received: from [192.168.5.102] ([121.35.199.159]) by szxml01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KUO00GNCYK5X7@szxml01-in.huawei.com>; Tue, 15 Dec 2009 19:28:54 +0800 (CST)
Date: Tue, 15 Dec 2009 19:28:46 +0800
From: Tina TSOU <tena@huawei.com>
To: young <young@h3c.com>
Message-id: <CD43B1FE-4C68-4BAE-B0D8-D88E6AE54DFF@huawei.com>
MIME-version: 1.0
X-Mailer: Apple Mail (2.930.3)
Content-type: multipart/alternative; boundary="Boundary_(ID_GfTlomFP3zdLJxgWBD9fIg)"
Cc: opsawg@ietf.org
Subject: Re: [OPSAWG] Network configuration in large scale IP infrastructure
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Dec 2009 11:29:26 -0000

--Boundary_(ID_GfTlomFP3zdLJxgWBD9fIg)
Content-type: text/plain; charset=UTF-8; format=flowed; delsp=yes
Content-transfer-encoding: quoted-printable

Hi Yang,
Thank you for your suggestion.

I have gone through RFC 5415. Section 3.3 has some relationship with =20
my problems. But the precondition is IP reachable between WTP and AC. =20=

This reachability should be pre-configured, especially when there are =20=

one or more L3 devices in the middle of the WTP and AC.

DHCP is used in this document to discover AC IP addresses, but the =20
precondition should be that there is a Layer 3 tunnel between DHCP =20
relay and AC. It is not clear in this document how this tunnel is setup.

The problem I hope to solve in the large scale IP infrastructure is =20
plug & play for all the L2/L3 devices in the network (the first step) =20=

and the service can be auto configured in the future.

The scope of the problem can be narrowed from the bearer network =20
device to network edge, e.g., low-end router/packet transport device/=20
LAN Switch. It can be complement to the existing zero configuration/=20
plug and play in CAPWAP or xDSL. In xDSL case, for example, modem can =20=

be implemented by zero configuration. If my problem is solved, DSLAM =20
can achieve plug and play as well.



B. R.
Tina
http://tinatsou.weebly.com/contact.html

> ----- Original Message -----
> From: young
> To: 'Tina TSOU'
> Cc: opsawg@ietf.org ; 'Juergen Schoenwaelder'
> Sent: Monday, December 07, 2009 1:46 PM
> Subject: =E7=AD=94=E5=A4=8D: [OPSAWG] Network configuration in IP =
network
>
>     Hi, Tina:
>
>     I suggest you go through the CAPWAP (RFC5415) to check whether
>     it is able to meet your most requirement.
>     It may help us to understand the problem to resolve and narrow =20
> the scope
> of the problem.
>
>     At present, please ignore the RFC5415 only support 802.16, =20
> 802.11, and no support
> on the LTE.
>
>     Regards=E3=80=80
> =E3=80=80=E3=80=80Richard
>
> -----=E9=82=AE=E4=BB=B6=E5=8E=9F=E4=BB=B6-----
> =E5=8F=91=E4=BB=B6=E4=BA=BA: opsawg-bounces@ietf.org =
[mailto:opsawg-bounces@ietf.org] =20
> =E4=BB=A3=E8=A1=A8 Tina TSOU
> =E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4: 2009=E5=B9=B412=E6=9C=887=E6=97=A5=
 12:07
> =E6=94=B6=E4=BB=B6=E4=BA=BA: Juergen Schoenwaelder
> =E6=8A=84=E9=80=81: opsawg@ietf.org
> =E4=B8=BB=E9=A2=98: Re: [OPSAWG] Network configuration in IP network
>
> Hi Juergen,
> draft-tsou-network-configuration-problem-statement-00 was presented =20=

> to the
> OPSAWG in Hiroshima, but the question came back: what am I asking =20
> the OPSAWG
> to do? Having thought about it a bit, I've decided that I'm really =20
> looking
> for a protocol that would function like BOOTP or DHCP, but would =20
> work for
> routers being added in a large-scale network deployment. I'm =20
> continuing to
> investigate the issue, but since DHCP belongs to Internet Area, it =20
> seems logical
> that any further discussions take place in that Area.
> I will keep you updated.
>
>
> B. R.
> Tina
> http://tinatsou.weebly.com/contact.html
> ----- Original Message -----
> From: Juergen Schoenwaelder
> To: Tina TSOU
> Cc: opsawg@ietf.org
> Sent: Wednesday, December 02, 2009 1:57 PM
> Subject: Re: [OPSAWG] Network configuration in IP network
>
> On Wed, Dec 02, 2009 at 04:37:54AM +0100, Tina TSOU wrote:
>
> > The basic problem the document raises is that the cost of =20
> bootstrapping IP
> > network nodes (i.e. provisioning an initial IP address and mask =20
> and associating
> > it with a device identity) in a large-scale IP network so that =20
> they can be
> > managed from a central point can be very high. Frequently the =20
> nodes themselves
> > are reached through another operator's network. This is an =20
> operations problem,
> > although it may require additional protocol solutions, so I =20
> thought it would be
> > sensible to bring it to OAM Area first. A potential breakdown of =20
> the work we had
> > in mind goes like this:
> >
> > 1) Survey of methods for plug-and-play bootstrapping of network =20
> nodes.
> >
> > 2x, y, z ...) Applicability of method x, y, z for plug-and-play =20
> bootstrapping of
> > network nodes
> >    -- limitations on network topology
> >    -- other constraints on network deployment
> >    -- operational considerations.
> >
> > 3) If a new method is required: a description of the requirements.
> >     We're into BOF territory if we get this far, and maybe not in =20=

> the OAM Area.
>
> So I probably have to wait until 1) and 2x, y, z) has been written to
> fully understand the problem.
>
> /js
>
> --=20
> Juergen Schoenwaelder           Jacobs University Bremen gGmbH
> Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
> Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>
>

--Boundary_(ID_GfTlomFP3zdLJxgWBD9fIg)
Content-type: text/html; charset=UTF-8
Content-transfer-encoding: quoted-printable

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"color: rgb(0, 0, 0); font-family: =
Arial; font-size: 10px; "><div style=3D"text-align: left; font-size: =
12pt; margin-top: 0cm; margin-right: 0cm; margin-bottom: 0pt; =
margin-left: 0cm; font-family: 'Times New Roman'; "><span lang=3D"EN-US" =
style=3D"font-size: 10pt; font-family: Arial; =
"></span></div></span></blockquote>Hi Yang,<div>Thank you for your =
suggestion.</div><div><br></div><div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal =
normal normal 13px/normal Arial; ">I have gone through RFC 5415. Section =
3.3&nbsp;has some relationship with my problems.&nbsp;But the =
precondition is IP reachable between WTP and AC. This =
reachability&nbsp;should be pre-configured, especially when there are =
one or more&nbsp;L3 devices&nbsp;in the middle of the WTP and =
AC.</div><p style=3D"margin: 0.0px 0.0px 0.0px 0.0px; font: 16.0px =
Helvetica">&nbsp;</p><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; font: normal normal normal =
13px/normal Arial; ">DHCP is&nbsp;used in this document to discover AC =
IP addresses, but the precondition should be that there is a Layer 3 =
tunnel between DHCP&nbsp;relay and AC. It is not clear in this document =
how&nbsp;this tunnel is setup.&nbsp;</div><p style=3D"margin: 0.0px =
0.0px 0.0px 0.0px; font: 13.0px Arial">&nbsp;</p><div style=3D"margin-top:=
 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: =
normal normal normal 13px/normal Arial; ">The problem I hope to solve in =
the large scale IP infrastructure is plug &amp; play for all the L2/L3 =
devices in the network (the first step) and the service can be auto =
configured in the future.</div><p style=3D"margin: 0.0px 0.0px 0.0px =
0.0px; font: 13.0px Arial">&nbsp;</p><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal =
normal normal 13px/normal Arial; ">The scope of the problem can =
be&nbsp;narrowed from the bearer network device to network edge, e.g., =
low-end router/packet transport device/LAN Switch. It&nbsp;can =
be&nbsp;complement to the existing zero configuration/plug and play in =
CAPWAP or xDSL. In xDSL case, for example, modem can be implemented by =
zero configuration. If my problem is solved, DSLAM can achieve plug and =
play as well.</div></div><div><br></div><div><br><div><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div><br><div =
apple-content-edited=3D"true"><div style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; =
"><div><div><div><div><div><div><div><div><div><div><div><div><div><div><d=
iv><div><div><div><div><div><div><div><div><div><div><div><div><div><div><=
div><div><div><div><div><div><div><div><div><div><div>B. =
R.</div><div>Tina</div><div><a =
href=3D"http://tinatsou.weebly.com/contact.html">http://tinatsou.weebly.co=
m/contact.html</a></div><div><br></div></div></div></div></div></div></div=
></div></div></div></div></div></div></div></div></div></div></div></div><=
/div></div></div></div></div></div></div></div></div></div></div></div></d=
iv></div></div></div></div></div></div></div></div></div></div></div></div=
><div><blockquote type=3D"cite"><span class=3D"Apple-style-span" =
style=3D"color: rgb(0, 0, 0); "><div lang=3D"ZH-CN" vlink=3D"blue" =
link=3D"blue" bgcolor=3D"white"><blockquote dir=3D"ltr" =
style=3D"padding-right: 0px; padding-left: 5px; margin-left: 5px; =
border-left-color: rgb(0, 0, 0); border-left-width: 2px; =
border-left-style: solid; margin-right: 0px; "><div style=3D"font: =
normal normal normal 10pt/normal arial; ">----- Original Message =
-----<div style=3D"background-image: initial; background-repeat: =
initial; background-attachment: initial; -webkit-background-clip: =
initial; -webkit-background-origin: initial; background-color: rgb(228, =
228, 228); "><b>From:</b>&nbsp;<a title=3D"young@h3c.com" =
href=3D"mailto:young@h3c.com" style=3D"color: blue; text-decoration: =
underline; ">young</a></div><div><b>To:</b>&nbsp;<a =
title=3D"tena@huawei.com" href=3D"mailto:tena@huawei.com" style=3D"color: =
blue; text-decoration: underline; ">'Tina =
TSOU'</a></div><div><b>Cc:</b>&nbsp;<a title=3D"opsawg@ietf.org" =
href=3D"mailto:opsawg@ietf.org" style=3D"color: blue; text-decoration: =
underline; ">opsawg@ietf.org</a>&nbsp;;&nbsp;<a =
title=3D"j.schoenwaelder@jacobs-university.de" =
href=3D"mailto:j.schoenwaelder@jacobs-university.de" style=3D"color: =
blue; text-decoration: underline; ">'Juergen =
Schoenwaelder'</a></div><div><b>Sent:</b>&nbsp;Monday, December 07, 2009 =
1:46 PM</div><div><b>Subject:</b>&nbsp;=E7=AD=94=E5=A4=8D: [OPSAWG] =
Network configuration in IP network</div></div><div><br></div><div =
class=3D"Section1"><div style=3D"font-size: 12pt; margin-top: 0cm; =
margin-right: 0cm; margin-bottom: 0pt; margin-left: 0cm; font-family: =
'Times New Roman'; "><font face=3D"=E5=AE=8B=E4=BD=93" color=3D"blue" =
size=3D"2"><span lang=3D"EN-US" style=3D"font-size: 10.5pt; color: blue; =
font-family: =E5=AE=8B=E4=BD=93; ">&nbsp;&nbsp;&nbsp; Hi, =
Tina:</span></font></div><p class=3D"MsoNormal" style=3D"font-size: =
12pt; margin-top: 0cm; margin-right: 0cm; margin-bottom: 0pt; =
margin-left: 0cm; font-family: 'Times New Roman'; "><font face=3D"=E5=AE=8B=
=E4=BD=93" color=3D"blue" size=3D"2"><span lang=3D"EN-US" =
style=3D"font-size: 10.5pt; color: blue; font-family: =E5=AE=8B=E4=BD=93; =
"></span></font>&nbsp;</p><div style=3D"font-size: 12pt; margin-top: =
0cm; margin-right: 0cm; margin-bottom: 0pt; margin-left: 0cm; =
font-family: 'Times New Roman'; "><font face=3D"=E5=AE=8B=E4=BD=93" =
color=3D"blue" size=3D"2"><span lang=3D"EN-US" style=3D"font-size: =
10.5pt; color: blue; font-family: =E5=AE=8B=E4=BD=93; =
">&nbsp;&nbsp;&nbsp; I suggest you go through the CAPWAP (RFC5415) to =
check whether</span></font></div><div style=3D"font-size: 12pt; =
margin-top: 0cm; margin-right: 0cm; margin-bottom: 0pt; margin-left: =
0cm; font-family: 'Times New Roman'; "><font face=3D"=E5=AE=8B=E4=BD=93" =
color=3D"blue" size=3D"2"><span lang=3D"EN-US" style=3D"font-size: =
10.5pt; color: blue; font-family: =E5=AE=8B=E4=BD=93; =
">&nbsp;&nbsp;&nbsp; it is able to meet your most =
requirement.</span></font></div><div style=3D"font-size: 12pt; =
margin-top: 0cm; margin-right: 0cm; margin-bottom: 0pt; margin-left: =
0cm; font-family: 'Times New Roman'; "><font face=3D"=E5=AE=8B=E4=BD=93" =
color=3D"blue" size=3D"2"><span lang=3D"EN-GB" style=3D"font-size: =
10.5pt; color: blue; font-family: =E5=AE=8B=E4=BD=93; =
">&nbsp;&nbsp;&nbsp; It may help us to understand the problem to resolve =
and narrow the scope</span></font></div><div style=3D"text-indent: 21pt; =
font-size: 12pt; margin-top: 0cm; margin-right: 0cm; margin-bottom: 0pt; =
margin-left: 0cm; font-family: 'Times New Roman'; "><font face=3D"=E5=AE=8B=
=E4=BD=93" color=3D"blue" size=3D"2"><span lang=3D"EN-GB" =
style=3D"font-size: 10.5pt; color: blue; font-family: =E5=AE=8B=E4=BD=93; =
">of the problem.</span></font></div><p class=3D"MsoNormal" =
style=3D"text-indent: 21pt; font-size: 12pt; margin-top: 0cm; =
margin-right: 0cm; margin-bottom: 0pt; margin-left: 0cm; font-family: =
'Times New Roman'; "><font face=3D"=E5=AE=8B=E4=BD=93" color=3D"blue" =
size=3D"2"><span lang=3D"EN-GB" style=3D"font-size: 10.5pt; color: blue; =
font-family: =E5=AE=8B=E4=BD=93; "></span></font>&nbsp;</p><div =
style=3D"font-size: 12pt; margin-top: 0cm; margin-right: 0cm; =
margin-bottom: 0pt; margin-left: 0cm; font-family: 'Times New Roman'; =
"><font face=3D"=E5=AE=8B=E4=BD=93" color=3D"blue" size=3D"2"><span =
lang=3D"EN-US" style=3D"font-size: 10.5pt; color: blue; font-family: =
=E5=AE=8B=E4=BD=93; ">&nbsp;&nbsp; &nbsp;At present, please ignore the =
RFC5415 only support 802.16, 802.11, and no =
support</span></font></div><div style=3D"text-indent: 21pt; font-size: =
12pt; margin-top: 0cm; margin-right: 0cm; margin-bottom: 0pt; =
margin-left: 0cm; font-family: 'Times New Roman'; "><font face=3D"=E5=AE=8B=
=E4=BD=93" color=3D"blue" size=3D"2"><span lang=3D"EN-US" =
style=3D"font-size: 10.5pt; color: blue; font-family: =E5=AE=8B=E4=BD=93; =
">on the</span></font><font face=3D"=E5=AE=8B=E4=BD=93" color=3D"blue" =
size=3D"2"><span lang=3D"EN-US" style=3D"font-size: 10.5pt; color: blue; =
font-family: =E5=AE=8B=E4=BD=93; ">&nbsp;</span></font><font =
face=3D"=E5=AE=8B=E4=BD=93" color=3D"blue" size=3D"2"><span lang=3D"EN-US"=
 style=3D"font-size: 10.5pt; color: blue; font-family: =E5=AE=8B=E4=BD=93;=
 ">LTE.</span></font></div><p class=3D"MsoNormal" style=3D"font-size: =
12pt; margin-top: 0cm; margin-right: 0cm; margin-bottom: 0pt; =
margin-left: 0cm; font-family: 'Times New Roman'; "><font face=3D"=E5=AE=8B=
=E4=BD=93" color=3D"blue" size=3D"2"><span lang=3D"EN-GB" =
style=3D"font-size: 10.5pt; color: blue; font-family: =E5=AE=8B=E4=BD=93; =
">&nbsp;&nbsp;&nbsp;</span></font></p><div style=3D"font-size: 12pt; =
margin-top: 0cm; margin-right: 0cm; margin-bottom: 0pt; margin-left: =
0cm; font-family: 'Times New Roman'; "><font face=3D"=E5=AE=8B=E4=BD=93" =
color=3D"blue" size=3D"2"><span lang=3D"EN-US" style=3D"font-size: =
10.5pt; color: blue; font-family: =E5=AE=8B=E4=BD=93; =
">&nbsp;&nbsp;&nbsp; Regards=E3=80=80</span></font></div><div =
style=3D"font-size: 12pt; margin-top: 0cm; margin-right: 0cm; =
margin-bottom: 0pt; margin-left: 0cm; font-family: 'Times New Roman'; =
"><font face=3D"=E5=AE=8B=E4=BD=93" color=3D"blue" size=3D"2"><span =
style=3D"font-size: 10.5pt; color: blue; font-family: =E5=AE=8B=E4=BD=93; =
">=E3=80=80=E3=80=80</span></font><font face=3D"=E5=AE=8B=E4=BD=93" =
color=3D"blue" size=3D"2"><span lang=3D"EN-GB" style=3D"font-size: =
10.5pt; color: blue; font-family: =E5=AE=8B=E4=BD=93; =
">Richard</span></font></div><p class=3D"MsoNormal" style=3D"font-size: =
12pt; margin-top: 0cm; margin-right: 0cm; margin-bottom: 0pt; =
margin-left: 0cm; font-family: 'Times New Roman'; "><font face=3D"=E5=AE=8B=
=E4=BD=93" color=3D"blue" size=3D"2"><span lang=3D"EN-US" =
style=3D"font-size: 10.5pt; color: blue; font-family: =E5=AE=8B=E4=BD=93; =
"></span></font>&nbsp;</p><div style=3D"font-size: 12pt; margin-top: =
0cm; margin-right: 0cm; margin-bottom: 0pt; margin-left: 0cm; =
font-family: 'Times New Roman'; "><font face=3D"=E5=AE=8B=E4=BD=93" =
size=3D"2"><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: =
=E5=AE=8B=E4=BD=93; ">-----=E9=82=AE=E4=BB=B6=E5=8E=9F=E4=BB=B6-----<br><b=
><span style=3D"font-weight: bold; ">=E5=8F=91=E4=BB=B6=E4=BA=BA:</span></=
b>&nbsp;<a href=3D"mailto:opsawg-bounces@ietf.org" style=3D"color: blue; =
text-decoration: underline; ">opsawg-bounces@ietf.org</a>&nbsp;[<a =
href=3D"mailto:opsawg-bounces@ietf.org" style=3D"color: blue; =
text-decoration: underline; =
">mailto:opsawg-bounces@ietf.org</a>]&nbsp;<b><span style=3D"font-weight: =
bold; ">=E4=BB=A3=E8=A1=A8&nbsp;</span></b>Tina TSOU<br><b><span =
style=3D"font-weight: bold; =
">=E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4:</span></b>&nbsp;2009=E5=B9=B412=E6=
=9C=887=E6=97=A5 12:07<br><b><span style=3D"font-weight: bold; =
">=E6=94=B6=E4=BB=B6=E4=BA=BA:</span></b>&nbsp;Juergen =
Schoenwaelder<br><b><span style=3D"font-weight: bold; =
">=E6=8A=84=E9=80=81:</span></b>&nbsp;<a href=3D"mailto:opsawg@ietf.org" =
style=3D"color: blue; text-decoration: underline; =
">opsawg@ietf.org</a><br><b><span style=3D"font-weight: bold; =
">=E4=B8=BB=E9=A2=98:</span></b>&nbsp;Re: [OPSAWG] Network configuration =
in IP network</span></font></div><p class=3D"MsoNormal" =
style=3D"font-size: 12pt; margin-top: 0cm; margin-right: 0cm; =
margin-bottom: 0pt; margin-left: 0cm; font-family: 'Times New Roman'; =
"><font face=3D"Times New Roman" size=3D"3"><span lang=3D"EN-US" =
style=3D"font-size: 12pt; "></span></font>&nbsp;</p><div><div =
style=3D"font-size: 12pt; margin-top: 0cm; margin-right: 0cm; =
margin-bottom: 0pt; margin-left: 0cm; font-family: 'Times New Roman'; =
"><font face=3D"Arial" size=3D"3"><span lang=3D"EN-US" style=3D"font-size:=
 12pt; font-family: Arial; ">Hi =
Juergen,</span></font></div></div><div><div style=3D"font-size: 12pt; =
margin-top: 0cm; margin-right: 0cm; margin-bottom: 0pt; margin-left: =
0cm; font-family: 'Times New Roman'; "><font face=3D"Arial" =
size=3D"3"><span lang=3D"EN-US" style=3D"font-size: 12pt; font-family: =
Arial; ">draft-tsou-network-configuration-problem-statement-00 was =
presented to the<br>OPSAWG in Hiroshima, but the question came back: =
what&nbsp;am I&nbsp;asking the OPSAWG<br>to do? Having thought about it =
a bit, I've decided that&nbsp;I'm really looking<br>for a protocol that =
would function like BOOTP or DHCP, but would work for<br>routers being =
added in a large-scale network deployment.&nbsp;I'm continuing =
to<br>investigate the issue, but since DHCP belongs to Internet Area, it =
seems logical<br>that any further discussions take place in that =
Area.</span></font></div></div><div><div style=3D"font-size: 12pt; =
margin-top: 0cm; margin-right: 0cm; margin-bottom: 0pt; margin-left: =
0cm; font-family: 'Times New Roman'; "><font face=3D"Arial" =
size=3D"3"><span lang=3D"EN-US" style=3D"font-size: 12pt; font-family: =
Arial; ">I will keep you updated.</span></font></div></div><div><p =
class=3D"MsoNormal" style=3D"font-size: 12pt; margin-top: 0cm; =
margin-right: 0cm; margin-bottom: 0pt; margin-left: 0cm; font-family: =
'Times New Roman'; "><font face=3D"Times New Roman" size=3D"3"><span =
lang=3D"EN-US" style=3D"font-size: 12pt; =
"></span></font>&nbsp;</p></div><div><p class=3D"MsoNormal" =
style=3D"font-size: 12pt; margin-top: 0cm; margin-right: 0cm; =
margin-bottom: 0pt; margin-left: 0cm; font-family: 'Times New Roman'; =
"><font face=3D"Times New Roman" size=3D"3"><span lang=3D"EN-US" =
style=3D"font-size: 12pt; "></span></font>&nbsp;</p></div><div><div =
style=3D"font-size: 12pt; margin-top: 0cm; margin-right: 0cm; =
margin-bottom: 0pt; margin-left: 0cm; font-family: 'Times New Roman'; =
"><font face=3D"Times New Roman" size=3D"3"><span lang=3D"EN-US" =
style=3D"font-size: 12pt; ">B. R.<br>Tina<br><a =
href=3D"http://tinatsou.weebly.com/contact.html" style=3D"color: blue; =
text-decoration: underline; =
">http://tinatsou.weebly.com/contact.html</a></span></font></div></div><bl=
ockquote style=3D"border-right-width: medium; border-right-style: none; =
border-right-color: initial; padding-right: 0cm; border-top-width: =
medium; border-top-style: none; border-top-color: initial; padding-left: =
4pt; padding-bottom: 0cm; margin-top: 5pt; margin-right: 0cm; =
margin-bottom: 5pt; margin-left: 3.75pt; border-left-color: black; =
border-left-width: 1.5pt; border-left-style: solid; padding-top: 0cm; =
border-bottom-width: medium; border-bottom-style: none; =
border-bottom-color: initial; "><div><div style=3D"font-size: 12pt; =
margin-top: 0cm; margin-right: 0cm; margin-bottom: 0pt; margin-left: =
0cm; font-family: 'Times New Roman'; "><font face=3D"Arial" =
size=3D"2"><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: =
Arial; ">----- Original Message -----</span></font></div></div><div><div =
style=3D"background-image: initial; background-repeat: initial; =
background-attachment: initial; -webkit-background-clip: initial; =
-webkit-background-origin: initial; background-color: rgb(228, 228, =
228); font-size: 12pt; margin-top: 0cm; margin-right: 0cm; =
margin-bottom: 0pt; margin-left: 0cm; font-family: 'Times New Roman'; =
"><b><font face=3D"Arial" size=3D"2"><span lang=3D"EN-US" =
style=3D"font-weight: bold; font-size: 10pt; font-family: Arial; =
">From:</span></font></b><font face=3D"Arial" size=3D"2"><span =
lang=3D"EN-US" style=3D"font-size: 10pt; font-family: Arial; ">&nbsp;<a =
title=3D"j.schoenwaelder@jacobs-university.de" =
href=3D"mailto:j.schoenwaelder@jacobs-university.de" style=3D"color: =
blue; text-decoration: underline; ">Juergen =
Schoenwaelder</a></span></font></div></div><div><div style=3D"font-size: =
12pt; margin-top: 0cm; margin-right: 0cm; margin-bottom: 0pt; =
margin-left: 0cm; font-family: 'Times New Roman'; "><b><font =
face=3D"Arial" size=3D"2"><span lang=3D"EN-US" style=3D"font-weight: =
bold; font-size: 10pt; font-family: Arial; ">To:</span></font></b><font =
face=3D"Arial" size=3D"2"><span lang=3D"EN-US" style=3D"font-size: 10pt; =
font-family: Arial; ">&nbsp;<a title=3D"tena@huawei.com" =
href=3D"mailto:tena@huawei.com" style=3D"color: blue; text-decoration: =
underline; ">Tina TSOU</a></span></font></div></div><div><div =
style=3D"font-size: 12pt; margin-top: 0cm; margin-right: 0cm; =
margin-bottom: 0pt; margin-left: 0cm; font-family: 'Times New Roman'; =
"><b><font face=3D"Arial" size=3D"2"><span lang=3D"EN-US" =
style=3D"font-weight: bold; font-size: 10pt; font-family: Arial; =
">Cc:</span></font></b><font face=3D"Arial" size=3D"2"><span =
lang=3D"EN-US" style=3D"font-size: 10pt; font-family: Arial; ">&nbsp;<a =
title=3D"opsawg@ietf.org" href=3D"mailto:opsawg@ietf.org" style=3D"color: =
blue; text-decoration: underline; =
">opsawg@ietf.org</a></span></font></div></div><div><div =
style=3D"font-size: 12pt; margin-top: 0cm; margin-right: 0cm; =
margin-bottom: 0pt; margin-left: 0cm; font-family: 'Times New Roman'; =
"><b><font face=3D"Arial" size=3D"2"><span lang=3D"EN-US" =
style=3D"font-weight: bold; font-size: 10pt; font-family: Arial; =
">Sent:</span></font></b><font face=3D"Arial" size=3D"2"><span =
lang=3D"EN-US" style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;Wednesday, December 02, 2009 1:57 =
PM</span></font></div></div><div><div style=3D"font-size: 12pt; =
margin-top: 0cm; margin-right: 0cm; margin-bottom: 0pt; margin-left: =
0cm; font-family: 'Times New Roman'; "><b><font face=3D"Arial" =
size=3D"2"><span lang=3D"EN-US" style=3D"font-weight: bold; font-size: =
10pt; font-family: Arial; ">Subject:</span></font></b><font face=3D"Arial"=
 size=3D"2"><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: =
Arial; ">&nbsp;Re: [OPSAWG] Network configuration in IP =
network</span></font></div></div><div><p class=3D"MsoNormal" =
style=3D"font-size: 12pt; margin-top: 0cm; margin-right: 0cm; =
margin-bottom: 0pt; margin-left: 0cm; font-family: 'Times New Roman'; =
"><font face=3D"Times New Roman" size=3D"3"><span lang=3D"EN-US" =
style=3D"font-size: 12pt; "></span></font>&nbsp;</p></div><div =
style=3D"font-size: 12pt; margin-top: 0cm; margin-right: 0cm; =
margin-bottom: 0pt; margin-left: 0cm; font-family: 'Times New Roman'; =
"><font face=3D"Times New Roman" size=3D"3"><span lang=3D"EN-US" =
style=3D"font-size: 12pt; ">On Wed, Dec 02, 2009 at 04:37:54AM +0100, =
Tina TSOU wrote:<br>&nbsp;<br>> The basic problem the document raises is =
that the cost of bootstrapping IP<br>> network nodes (i.e. provisioning =
an initial IP address and mask and associating<br>> it with a device =
identity) in a large-scale IP network so that they can be<br>> managed =
from a central point can be very high. Frequently the nodes =
themselves<br>> are reached through another operator's network. This is =
an operations problem,<br>> although it may require additional protocol =
solutions, so I thought it would be<br>> sensible to bring it to OAM =
Area first. A potential breakdown of the work we had<br>> in mind goes =
like this:<br>>&nbsp;<br>> 1) Survey of methods for plug-and-play =
bootstrapping of network nodes.<br>>&nbsp;<br>> 2x, y, z ...) =
Applicability of method x, y, z for plug-and-play bootstrapping of<br>> =
network nodes<br>>&nbsp;&nbsp;&nbsp; -- limitations on network =
topology<br>>&nbsp;&nbsp;&nbsp; -- other constraints on network =
deployment<br>>&nbsp;&nbsp;&nbsp; -- operational =
considerations.<br>>&nbsp;<br>> 3) If a new method is required: a =
description of the requirements.<br>>&nbsp;&nbsp;&nbsp;&nbsp; We're into =
BOF territory if we get this far, and maybe not in the OAM =
Area.<br><br>So I probably have to wait until 1) and 2x, y, z) has been =
written to<br>fully understand the =
problem.<br><br>/js<br><br>--&nbsp;<br>Juergen =
Schoenwaelder&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Jacobs University Bremen gGmbH<br>Phone: +49 421 200 =
3587&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Campus Ring 1, =
28759 Bremen, Germany<br>Fax:&nbsp;&nbsp; +49 421 200 =
3103&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;<a =
href=3D"http://www.jacobs-university.de/" style=3D"color: blue; =
text-decoration: underline; =
">http://www.jacobs-university.de/</a>></span></font></div><div><font =
class=3D"Apple-style-span" face=3D"'Times New Roman'" size=3D"4"><span =
class=3D"Apple-style-span" style=3D"font-size: =
16px;"><br></span></font></div></blockquote></div></blockquote></div></spa=
n></blockquote></div></div></div></div></div></body></html>=

--Boundary_(ID_GfTlomFP3zdLJxgWBD9fIg)--

From sob@harvard.edu  Thu Dec 17 04:58:33 2009
Return-Path: <sob@harvard.edu>
X-Original-To: opsawg@core3.amsl.com
Delivered-To: opsawg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6D0B03A67CF for <opsawg@core3.amsl.com>; Thu, 17 Dec 2009 04:58:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level: 
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qyVQ4VKUZ3hT for <opsawg@core3.amsl.com>; Thu, 17 Dec 2009 04:58:32 -0800 (PST)
Received: from newdev.eecs.harvard.edu (newdev.eecs.harvard.edu [140.247.60.212]) by core3.amsl.com (Postfix) with ESMTP id B3FB83A672E for <opsawg@ietf.org>; Thu, 17 Dec 2009 04:58:32 -0800 (PST)
Received: by newdev.eecs.harvard.edu (Postfix, from userid 501) id 433B32E4A83; Thu, 17 Dec 2009 07:58:18 -0500 (EST)
To: opsawg@ietf.org
Message-Id: <20091217125818.433B32E4A83@newdev.eecs.harvard.edu>
Date: Thu, 17 Dec 2009 07:58:18 -0500 (EST)
From: sob@harvard.edu (Scott O. Bradner)
Subject: [OPSAWG] poll on making draft-sfv-mpls-tp-fault a MPLS wg document
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Dec 2009 12:58:33 -0000

this may be of interest to OPSAWG

Scott

---------------
All,

this is to start a two week poll on making

http://www.ietf.org/id/draft-sfv-mpls-tp-fault-01.txt

an MPLS working group document.

Send a mail to the mpls-tp@ietf.org mailing list,
indicating "yes/support" or "no/do not support".

Comments on the content of the draft should be sent to the same
mailing list with a different subject line.

The poll ends Friday 15 Jan, 2010.

/Loa
-- 
