From exim@www1.ietf.org  Tue Aug  5 09:48:34 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA10945
	for <gsmp-archive@odin.ietf.org>; Tue, 5 Aug 2003 09:48:34 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19k2Ab-0007Mw-1B
	for gsmp-archive@odin.ietf.org; Tue, 05 Aug 2003 09:48:09 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h75Dm945028320
	for gsmp-archive@odin.ietf.org; Tue, 5 Aug 2003 09:48:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19k2Aa-0007Me-TA
	for gsmp-web-archive@optimus.ietf.org; Tue, 05 Aug 2003 09:48:08 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA10855
	for <gsmp-web-archive@ietf.org>; Tue, 5 Aug 2003 09:48:02 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19k2AX-00022P-00
	for gsmp-web-archive@ietf.org; Tue, 05 Aug 2003 09:48:05 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19k2AW-00022L-00
	for gsmp-web-archive@ietf.org; Tue, 05 Aug 2003 09:48:04 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19k2AV-0007Jw-0b; Tue, 05 Aug 2003 09:48:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19k2AM-0007I4-Us
	for gsmp@optimus.ietf.org; Tue, 05 Aug 2003 09:47:54 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA10843
	for <gsmp@ietf.org>; Tue, 5 Aug 2003 09:47:49 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19k2AL-000228-00
	for gsmp@ietf.org; Tue, 05 Aug 2003 09:47:53 -0400
Received: from h35s128a211n47.user.nortelnetworks.com ([47.211.128.35] helo=znsgs01r.nortelnetworks.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19k2AK-00021t-00
	for gsmp@ietf.org; Tue, 05 Aug 2003 09:47:52 -0400
Received: from zctfc040.europe.nortel.com (zctfc040.europe.nortel.com [47.164.129.95])
	by znsgs01r.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id h75DlJf00381
	for <gsmp@ietf.org>; Tue, 5 Aug 2003 14:47:19 +0100 (BST)
Received: from zctfc002.europe.nortel.com ([47.164.129.43]) by zctfc040.europe.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id NB6N20P5; Tue, 5 Aug 2003 15:47:18 +0200
Received: from nortelnetworks.com (ksundell-1.europe.nortel.com [47.167.132.215]) by zctfc002.europe.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id PQVT1TLR; Tue, 5 Aug 2003 15:47:19 +0200
Message-ID: <3F2FB58D.50803@nortelnetworks.com>
Date: Tue, 05 Aug 2003 15:47:57 +0200
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: Kenneth Sundell <ksundell@nortelnetworks.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2
X-Accept-Language: en-us
MIME-Version: 1.0
To: gsmp <gsmp@ietf.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [GSMP] Need consensus for support of protection in GSMP
Sender: gsmp-admin@ietf.org
Errors-To: gsmp-admin@ietf.org
X-BeenThere: gsmp@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/gsmp>,
	<mailto:gsmp-request@ietf.org?subject=unsubscribe>
List-Id: General Switch Management Protocol <gsmp.ietf.org>
List-Post: <mailto:gsmp@ietf.org>
List-Help: <mailto:gsmp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/gsmp>,
	<mailto:gsmp-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


Hi,

we had some discussions regarding recovery in Vienna (both at the 
working group meeting and off-line with the design teams). We had a 
tenetative decision among the editors to support protection only. I 
would like to check the consensus on the mailing list on that 
"decision", i.e. to support protection but not adding restoration to the 
protocol. We would leave restoration up to the GSMP controller.

Please give your thoughts to the list within two weeks from now.

Regards,
Ken





_______________________________________________
GSMP mailing list
GSMP@ietf.org
https://www1.ietf.org/mailman/listinfo/gsmp



From exim@www1.ietf.org  Tue Aug  5 10:01:28 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA11319
	for <gsmp-archive@odin.ietf.org>; Tue, 5 Aug 2003 10:01:28 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19k2N4-00087V-TC
	for gsmp-archive@odin.ietf.org; Tue, 05 Aug 2003 10:01:03 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h75E12WS031212
	for gsmp-archive@odin.ietf.org; Tue, 5 Aug 2003 10:01:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19k2N4-00087L-Py
	for gsmp-web-archive@optimus.ietf.org; Tue, 05 Aug 2003 10:01:02 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA11303
	for <gsmp-web-archive@ietf.org>; Tue, 5 Aug 2003 10:00:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19k2N2-0002AY-00
	for gsmp-web-archive@ietf.org; Tue, 05 Aug 2003 10:01:00 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19k2N2-0002AV-00
	for gsmp-web-archive@ietf.org; Tue, 05 Aug 2003 10:01:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19k2N3-00086F-6w; Tue, 05 Aug 2003 10:01:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19k2Md-00085V-W5
	for gsmp@optimus.ietf.org; Tue, 05 Aug 2003 10:00:36 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA11297
	for <gsmp@ietf.org>; Tue, 5 Aug 2003 10:00:30 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19k2Mb-0002AL-00
	for gsmp@ietf.org; Tue, 05 Aug 2003 10:00:33 -0400
Received: from tama5.ecl.ntt.co.jp ([129.60.39.102])
	by ietf-mx with esmtp (Exim 4.12)
	id 19k2Ma-0002A4-00
	for gsmp@ietf.org; Tue, 05 Aug 2003 10:00:33 -0400
Received: from vcs3.rdh.ecl.ntt.co.jp (vcs3.rdh.ecl.ntt.co.jp [129.60.39.110])
	by tama5.ecl.ntt.co.jp (8.12.8p1/8.12.8) with ESMTP id h75E0O1R021645;
	Tue, 5 Aug 2003 23:00:24 +0900 (JST)
Received: from nttmail3.ecl.ntt.co.jp (localhost [127.0.0.1])
	by vcs3.rdh.ecl.ntt.co.jp (8.12.8p1/8.12.8) with ESMTP id h75E0O8E010147;
	Tue, 5 Aug 2003 23:00:24 +0900 (JST)
Received: from eclscan3.m.ecl.ntt.co.jp (eclscan3.m.ecl.ntt.co.jp [129.60.5.69])
	by nttmail3.ecl.ntt.co.jp (8.12.8p1/8.12.8) with ESMTP id h75E0NeH026478;
	Tue, 5 Aug 2003 23:00:23 +0900 (JST)
Received: from iml.m.ecl.ntt.co.jp (localhost [127.0.0.1])
	by eclscan3.m.ecl.ntt.co.jp (8.9.3p2/3.7W) with ESMTP id XAA12946;
	Tue, 5 Aug 2003 23:00:23 +0900 (JST)
Received: from hornet.onlab.ntt.co.jp
	by iml.m.ecl.ntt.co.jp (8.9.3p2/3.7W) with ESMTP id XAA29345;
	Tue, 5 Aug 2003 23:00:22 +0900 (JST)
Received: (from okamoto@localhost)
	by hornet.onlab.ntt.co.jp (8.8.8+Sun/3.7W-07/02/99) id XAA29773;
	Tue, 5 Aug 2003 23:00:21 +0900 (JST)
X-Authentication-Warning: hornet.onlab.ntt.co.jp: okamoto set sender to okamoto.satoru@lab.ntt.co.jp using -f
Date: Tue, 5 Aug 2003 23:00:21 +0900
From: Satoru OKAMOTO <okamoto.satoru@lab.ntt.co.jp>
To: Kenneth Sundell <ksundell@nortelnetworks.com>
Cc: gsmp <gsmp@ietf.org>
Subject: Re: [GSMP] Need consensus for support of protection in GSMP
Message-ID: <20030805140021.GA29760%okamoto.satoru@lab.ntt.co.jp>
Reply-To: okamoto.satoru@lab.ntt.co.jp
References: <3F2FB58D.50803@nortelnetworks.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3F2FB58D.50803@nortelnetworks.com>
User-Agent: Mutt/1.4.1i-ja.1
Sender: gsmp-admin@ietf.org
Errors-To: gsmp-admin@ietf.org
X-BeenThere: gsmp@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/gsmp>,
	<mailto:gsmp-request@ietf.org?subject=unsubscribe>
List-Id: General Switch Management Protocol <gsmp.ietf.org>
List-Post: <mailto:gsmp@ietf.org>
List-Help: <mailto:gsmp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/gsmp>,
	<mailto:gsmp-request@ietf.org?subject=subscribe>

Hi Ken and all,
Yes. I agree with not adding restoration.

				Satoru Okamoto

On Tue, Aug 05, 2003 at 03:47:57PM +0200,
 Kenneth Sundell wrote:

> 
> Hi,
> 
> we had some discussions regarding recovery in Vienna (both at the 
> working group meeting and off-line with the design teams). We had a 
> tenetative decision among the editors to support protection only. I 
> would like to check the consensus on the mailing list on that 
> "decision", i.e. to support protection but not adding restoration to the 
> protocol. We would leave restoration up to the GSMP controller.
> 
> Please give your thoughts to the list within two weeks from now.
> 
> Regards,
> Ken

====================================================
Dr. Satoru Okamoto
Senior Research Engineer
Advanced IP Node Systems Research Group and 
Photonic Networking Research Group
Photonic Transport Network Laboratory
NTT Network Innovation Laboratories
Musashino-Office
  Room 1-2F, 9-11 Midori-Cho 3-Chome
  Musashino-Shi, Tokyo 180-8585 Japan
  Tel: +81-422-59-4353 Fax: +81-422-59-6387
Yokosuka-Office
  Room 807A, 1-1 Hikari-no-oka,
  Yokosuka-shi, Kanagawa 239-0847 Japan
  Tel: +81-46-859-8870  Fax: +81-46-859-3396    
E-mail: okamoto.satoru@lab.ntt.co.jp
====================================================


_______________________________________________
GSMP mailing list
GSMP@ietf.org
https://www1.ietf.org/mailman/listinfo/gsmp



From exim@www1.ietf.org  Tue Aug  5 12:54:28 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18767
	for <gsmp-archive@odin.ietf.org>; Tue, 5 Aug 2003 12:54:28 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19k54V-0007Ig-In
	for gsmp-archive@odin.ietf.org; Tue, 05 Aug 2003 12:54:03 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h75Gs3AH028060
	for gsmp-archive@odin.ietf.org; Tue, 5 Aug 2003 12:54:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19k54V-0007IV-E5
	for gsmp-web-archive@optimus.ietf.org; Tue, 05 Aug 2003 12:54:03 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18760
	for <gsmp-web-archive@ietf.org>; Tue, 5 Aug 2003 12:53:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19k54T-0003p3-00
	for gsmp-web-archive@ietf.org; Tue, 05 Aug 2003 12:54:01 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19k54S-0003p0-00
	for gsmp-web-archive@ietf.org; Tue, 05 Aug 2003 12:54:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19k54T-0007I4-1e; Tue, 05 Aug 2003 12:54:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19k54E-0007Hj-KH
	for gsmp@optimus.ietf.org; Tue, 05 Aug 2003 12:53:46 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18743
	for <gsmp@ietf.org>; Tue, 5 Aug 2003 12:53:40 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19k54C-0003ok-00
	for gsmp@ietf.org; Tue, 05 Aug 2003 12:53:44 -0400
Received: from zcars0m9.nortelnetworks.com ([47.129.242.157])
	by ietf-mx with esmtp (Exim 4.12)
	id 19k54C-0003oa-00
	for gsmp@ietf.org; Tue, 05 Aug 2003 12:53:44 -0400
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69])
	by zcars0m9.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id h75GrCR25487
	for <gsmp@ietf.org>; Tue, 5 Aug 2003 12:53:12 -0400 (EDT)
Received: by zcard309.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <NLVY9J7M>; Tue, 5 Aug 2003 12:53:12 -0400
Message-ID: <0D7FC1D8D861D511AEA70002A52CE5E604343F9A@zcard0ke.ca.nortel.com>
From: "Stephen Shew" <sdshew@nortelnetworks.com>
To: gsmp <gsmp@ietf.org>
Subject: RE: [GSMP] Need consensus for support of protection in GSMP
Date: Tue, 5 Aug 2003 12:53:10 -0400 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C35B72.0D48AA72"
Sender: gsmp-admin@ietf.org
Errors-To: gsmp-admin@ietf.org
X-BeenThere: gsmp@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/gsmp>,
	<mailto:gsmp-request@ietf.org?subject=unsubscribe>
List-Id: General Switch Management Protocol <gsmp.ietf.org>
List-Post: <mailto:gsmp@ietf.org>
List-Help: <mailto:gsmp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/gsmp>,
	<mailto:gsmp-request@ietf.org?subject=subscribe>

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C35B72.0D48AA72
Content-Type: text/plain

I agree that we should limit GSMP to protection support.  This is because
protection action is localized whereas restoration actions span multiple
switches.  Note that the definition of protection I'm using is an action
that does not change the endpoints of the connection whereas in restoration,
a new connection is used that replaces the failed connection (endpoints
change).  See G.841 "Types and Characteristics of SDH Network Protection
Architectures ".

-----Original Message-----
From: Sundell, Kenneth [ERK:AA50:EXCH] 
Sent: Tuesday, August 05, 2003 09:48
To: gsmp
Subject: [GSMP] Need consensus for support of protection in GSMP



Hi,

we had some discussions regarding recovery in Vienna (both at the 
working group meeting and off-line with the design teams). We had a 
tenetative decision among the editors to support protection only. I 
would like to check the consensus on the mailing list on that 
"decision", i.e. to support protection but not adding restoration to the 
protocol. We would leave restoration up to the GSMP controller.

Please give your thoughts to the list within two weeks from now.

Regards,
Ken





_______________________________________________
GSMP mailing list
GSMP@ietf.org
https://www1.ietf.org/mailman/listinfo/gsmp

------_=_NextPart_001_01C35B72.0D48AA72
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2656.31">
<TITLE>RE: [GSMP] Need consensus for support of protection in =
GSMP</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>I agree that we should limit GSMP to protection =
support.&nbsp; This is because protection action is localized whereas =
restoration actions span multiple switches.&nbsp; Note that the =
definition of protection I'm using is an action that does not change =
the endpoints of the connection whereas in restoration, a new =
connection is used that replaces the failed connection (endpoints =
change).&nbsp; See G.841 &quot;Types and Characteristics of SDH Network =
Protection Architectures &quot;.</FONT></P>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Sundell, Kenneth [ERK:AA50:EXCH] </FONT>
<BR><FONT SIZE=3D2>Sent: Tuesday, August 05, 2003 09:48</FONT>
<BR><FONT SIZE=3D2>To: gsmp</FONT>
<BR><FONT SIZE=3D2>Subject: [GSMP] Need consensus for support of =
protection in GSMP</FONT>
</P>
<BR>
<BR>

<P><FONT SIZE=3D2>Hi,</FONT>
</P>

<P><FONT SIZE=3D2>we had some discussions regarding recovery in Vienna =
(both at the </FONT>
<BR><FONT SIZE=3D2>working group meeting and off-line with the design =
teams). We had a </FONT>
<BR><FONT SIZE=3D2>tenetative decision among the editors to support =
protection only. I </FONT>
<BR><FONT SIZE=3D2>would like to check the consensus on the mailing =
list on that </FONT>
<BR><FONT SIZE=3D2>&quot;decision&quot;, i.e. to support protection but =
not adding restoration to the </FONT>
<BR><FONT SIZE=3D2>protocol. We would leave restoration up to the GSMP =
controller.</FONT>
</P>

<P><FONT SIZE=3D2>Please give your thoughts to the list within two =
weeks from now.</FONT>
</P>

<P><FONT SIZE=3D2>Regards,</FONT>
<BR><FONT SIZE=3D2>Ken</FONT>
</P>
<BR>
<BR>
<BR>
<BR>

<P><FONT =
SIZE=3D2>_______________________________________________</FONT>
<BR><FONT SIZE=3D2>GSMP mailing list</FONT>
<BR><FONT SIZE=3D2>GSMP@ietf.org</FONT>
<BR><FONT SIZE=3D2><A =
HREF=3D"https://www1.ietf.org/mailman/listinfo/gsmp" =
TARGET=3D"_blank">https://www1.ietf.org/mailman/listinfo/gsmp</A></FONT>=

</P>

</BODY>
</HTML>
------_=_NextPart_001_01C35B72.0D48AA72--

_______________________________________________
GSMP mailing list
GSMP@ietf.org
https://www1.ietf.org/mailman/listinfo/gsmp



From exim@www1.ietf.org  Wed Aug  6 15:56:34 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02409
	for <gsmp-archive@odin.ietf.org>; Wed, 6 Aug 2003 15:56:33 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19kUOE-0006xZ-NJ
	for gsmp-archive@odin.ietf.org; Wed, 06 Aug 2003 15:56:07 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h76Ju666026747
	for gsmp-archive@odin.ietf.org; Wed, 6 Aug 2003 15:56:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19kUOE-0006xK-Dp
	for gsmp-web-archive@optimus.ietf.org; Wed, 06 Aug 2003 15:56:06 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02402
	for <gsmp-web-archive@ietf.org>; Wed, 6 Aug 2003 15:56:02 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19kUOC-0006R8-00
	for gsmp-web-archive@ietf.org; Wed, 06 Aug 2003 15:56:04 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19kUOC-0006R4-00
	for gsmp-web-archive@ietf.org; Wed, 06 Aug 2003 15:56:04 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19kUO9-0006vL-Dh; Wed, 06 Aug 2003 15:56:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19kUNY-0006sw-DN
	for gsmp@optimus.ietf.org; Wed, 06 Aug 2003 15:55:24 -0400
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02370
	for <gsmp@odin.ietf.org>; Wed, 6 Aug 2003 15:55:20 -0400 (EDT)
Received: from apache by asgard.ietf.org with local (Exim 4.14)
	id 19kUM9-0000tX-OQ; Wed, 06 Aug 2003 15:53:57 -0400
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce:;
Cc: Internet Architecture Board <iab@iab.org>,
        RFC Editor <rfc-editor@rfc-editor.org>, <gsmp@ietf.org>
Message-Id: <E19kUM9-0000tX-OQ@asgard.ietf.org>
Date: Wed, 06 Aug 2003 15:53:57 -0400
Subject: [GSMP] Document Action: 'Requirements For Adding Optical Support
 To GSMPv3' to Informational RFC
Sender: gsmp-admin@ietf.org
Errors-To: gsmp-admin@ietf.org
X-BeenThere: gsmp@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/gsmp>,
	<mailto:gsmp-request@ietf.org?subject=unsubscribe>
List-Id: General Switch Management Protocol <gsmp.ietf.org>
List-Post: <mailto:gsmp@ietf.org>
List-Help: <mailto:gsmp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/gsmp>,
	<mailto:gsmp-request@ietf.org?subject=subscribe>

The IESG has approved the Internet-Draft 'Requirements For Adding Optical 
Support To GSMPv3' <draft-ietf-gsmp-reqs-06.txt> as an Informational RFC. 
This document is the product of the General Switch Management Protocol 
Working Group. The IESG contact persons are Bert Wijnen and Alex Zinin.

RFC-Editor notes:

1) Third paragraph of section 2.5 - expand DCN.
   OLD:
     used in legacy DCN environments that use OSI CLNP.
   NEW:
     used in legacy Data Communication Network (DCN) environments
     that use OSI CLNP.

2) For section 2.5 -  Add a final paragraph:

   The security risks of additional non-IP encapsulations MUST be
   described, since the mandatory to implement mechanism of IPsec
   is not available for these control channels, as in the RFC 3293
   Ethernet and ATM cases.  It is in scope to perform risk analysis
   and describe if mechanisms for link-level security mitigate the
   risk.


3) reword text in section 3.3

   OLD:
     A retransmission policy should be used if no reply is 
     received for a  message with "AckAll" set.
   NEW:
     A retransmission policy with a well-designed exponential
     backoff should be used if no reply is received for a
     message with "AckAll" set.


_______________________________________________
GSMP mailing list
GSMP@ietf.org
https://www1.ietf.org/mailman/listinfo/gsmp



From exim@www1.ietf.org  Wed Aug  6 16:17:30 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA03127
	for <gsmp-archive@odin.ietf.org>; Wed, 6 Aug 2003 16:17:29 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19kUiV-0007oI-Cx
	for gsmp-archive@odin.ietf.org; Wed, 06 Aug 2003 16:17:03 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h76KH3ik030016
	for gsmp-archive@odin.ietf.org; Wed, 6 Aug 2003 16:17:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19kUiV-0007o3-9C
	for gsmp-web-archive@optimus.ietf.org; Wed, 06 Aug 2003 16:17:03 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA03123
	for <gsmp-web-archive@ietf.org>; Wed, 6 Aug 2003 16:16:59 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19kUiT-0006eM-00
	for gsmp-web-archive@ietf.org; Wed, 06 Aug 2003 16:17:01 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19kUiS-0006eJ-00
	for gsmp-web-archive@ietf.org; Wed, 06 Aug 2003 16:17:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19kUiT-0007nI-AZ; Wed, 06 Aug 2003 16:17:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19kUiC-0007md-U2
	for gsmp@optimus.ietf.org; Wed, 06 Aug 2003 16:16:44 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA03110
	for <gsmp@ietf.org>; Wed, 6 Aug 2003 16:16:41 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19kUiB-0006dz-00
	for gsmp@ietf.org; Wed, 06 Aug 2003 16:16:43 -0400
Received: from mx03.forces.gc.ca ([131.137.245.203])
	by ietf-mx with esmtp (Exim 4.12)
	id 19kUiA-0006du-00
	for gsmp@ietf.org; Wed, 06 Aug 2003 16:16:42 -0400
Received: from asgard.ietf.org (asgard.ietf.org [132.151.6.40])
	by mx03.forces.gc.ca (DND-Mailer) with ESMTP id 40C32206607
	for <Allan.JER@forces.gc.ca>; Wed,  6 Aug 2003 16:14:58 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19kUNX-0000uo-Qf
	for ietf-announce-list@asgard.ietf.org; Wed, 06 Aug 2003 15:55:23 -0400
Received: from apache by asgard.ietf.org with local (Exim 4.14)
	id 19kUM9-0000tX-OQ; Wed, 06 Aug 2003 15:53:57 -0400
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce: ;
Cc: Internet Architecture Board <iab@iab.org>,
        RFC Editor <rfc-editor@rfc-editor.org>, <gsmp@ietf.org>
Message-Id: <E19kUM9-0000tX-OQ@asgard.ietf.org>
Date: Wed, 06 Aug 2003 15:53:57 -0400
Precedence: bulk
MIME-Version: 1.0
Subject: [GSMP] Document Action: 'Requirements For Adding Optical Support
 To GSMPv3' to Informational RFC
Sender: gsmp-admin@ietf.org
Errors-To: gsmp-admin@ietf.org
X-BeenThere: gsmp@ietf.org
X-Mailman-Version: 2.0.12
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/gsmp>,
	<mailto:gsmp-request@ietf.org?subject=unsubscribe>
List-Id: General Switch Management Protocol <gsmp.ietf.org>
List-Post: <mailto:gsmp@ietf.org>
List-Help: <mailto:gsmp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/gsmp>,
	<mailto:gsmp-request@ietf.org?subject=subscribe>

The IESG has approved the Internet-Draft 'Requirements For Adding Optical 
Support To GSMPv3' <draft-ietf-gsmp-reqs-06.txt> as an Informational RFC. 
This document is the product of the General Switch Management Protocol 
Working Group. The IESG contact persons are Bert Wijnen and Alex Zinin.

RFC-Editor notes:

1) Third paragraph of section 2.5 - expand DCN.
   OLD:
     used in legacy DCN environments that use OSI CLNP.
   NEW:
     used in legacy Data Communication Network (DCN) environments
     that use OSI CLNP.

2) For section 2.5 -  Add a final paragraph:

   The security risks of additional non-IP encapsulations MUST be
   described, since the mandatory to implement mechanism of IPsec
   is not available for these control channels, as in the RFC 3293
   Ethernet and ATM cases.  It is in scope to perform risk analysis
   and describe if mechanisms for link-level security mitigate the
   risk.


3) reword text in section 3.3

   OLD:
     A retransmission policy should be used if no reply is 
     received for a  message with "AckAll" set.
   NEW:
     A retransmission policy with a well-designed exponential
     backoff should be used if no reply is received for a
     message with "AckAll" set.



_______________________________________________
GSMP mailing list
GSMP@ietf.org
https://www1.ietf.org/mailman/listinfo/gsmp



From exim@www1.ietf.org  Fri Aug  8 05:30:31 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA05264
	for <gsmp-archive@odin.ietf.org>; Fri, 8 Aug 2003 05:30:31 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l3ZU-0003RM-Rr
	for gsmp-archive@odin.ietf.org; Fri, 08 Aug 2003 05:30:06 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h789U4Ea013220
	for gsmp-archive@odin.ietf.org; Fri, 8 Aug 2003 05:30:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l3ZU-0003R9-Ox
	for gsmp-web-archive@optimus.ietf.org; Fri, 08 Aug 2003 05:30:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA05261
	for <gsmp-web-archive@ietf.org>; Fri, 8 Aug 2003 05:29:58 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19l3ZR-0007Db-00
	for gsmp-web-archive@ietf.org; Fri, 08 Aug 2003 05:30:01 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19l3ZQ-0007DX-00
	for gsmp-web-archive@ietf.org; Fri, 08 Aug 2003 05:30:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l3ZR-0003QU-PS; Fri, 08 Aug 2003 05:30:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19l3Yl-0003Pk-JF
	for gsmp@optimus.ietf.org; Fri, 08 Aug 2003 05:29:20 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA05247
	for <gsmp@ietf.org>; Fri, 8 Aug 2003 05:29:13 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19l3Yi-0007DC-00
	for gsmp@ietf.org; Fri, 08 Aug 2003 05:29:16 -0400
Received: from psg.com ([147.28.0.62] ident=mailnull)
	by ietf-mx with esmtp (Exim 4.12)
	id 19l3Yh-0007D9-00
	for gsmp@ietf.org; Fri, 08 Aug 2003 05:29:15 -0400
Received: from [147.28.0.62] (helo=acm.org)
	by psg.com with esmtp (Exim 4.20)
	id 19l3Yh-000GP8-E7
	for gsmp@ietf.org; Fri, 08 Aug 2003 09:29:15 +0000
Date: Fri, 8 Aug 2003 18:26:28 +0900
Resent-Date: Fri, 8 Aug 2003 18:29:00 +0900
Content-Type: multipart/mixed; boundary=Apple-Mail-79-423361791
Mime-Version: 1.0 (Apple Message framework v552)
From: Avri Doria <avri@acm.org>
To: Avri Doria <avri@etri.re.kr>
Resent-To: gsmp@ietf.org
Resent-Message-Id: <63A28156-C982-11D7-8C8C-000393CC2112@acm.org>
Resent-From: Avri Doria <avri@acm.org>
Message-Id: <BE257488-C982-11D7-8C8C-000393CC2112@acm.org>
X-Mailer: Apple Mail (2.552)
Subject: [GSMP] Draft of minutes
Sender: gsmp-admin@ietf.org
Errors-To: gsmp-admin@ietf.org
X-BeenThere: gsmp@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/gsmp>,
	<mailto:gsmp-request@ietf.org?subject=unsubscribe>
List-Id: General Switch Management Protocol <gsmp.ietf.org>
List-Post: <mailto:gsmp@ietf.org>
List-Help: <mailto:gsmp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/gsmp>,
	<mailto:gsmp-request@ietf.org?subject=subscribe>


--Apple-Mail-79-423361791
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed
Content-Transfer-Encoding: 7bit

Please review:

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

--Apple-Mail-79-423361791
Content-Disposition: attachment;
	filename=gsmp-minutes.txt
Content-Type: text/plain;
	x-unix-mode=0644;
	name="gsmp-minutes.txt"
Content-Transfer-Encoding: 7bit


GSMP Working Group minutes IETF57

Notes taken by Jonathan Sadler.

The meeting was chaired by Kenneth Sundell and was scheduled for an
hour. 

Topics covered included:
 
- changes to the Base GSMP document including
  o  Triggered add
  o  Block add
  o  removal of technology specific content
- changes to the Packet spec
  o Label Type ranges updated
  o Stacking Section removed
  o Capability sets added
- changes to optical spec
  o reservation message for recovery
  o addition of technology specific block for recovery
  o add of new short message for data burst
  o discussion about terminology following what is being done
    in ccamp for GMPLS

Comment:  There are some difference developing between the
          docs.  There was an open meeting schedule for
          later in the IETF week to discuss the docs.
          Editors requested to attends with other being
          welcome.  Details of the discussions to be 
          discussed on the mailing list.  All provisional
          decisions to be discussed and confirmed on the
          WG mailing list.
          
- Discussion on Capability sets
  o each technology to have it own section and range of values
  o discussion of keeping it a fixed size or making variable.
    - opinions in favor of variable size especially for multi-layer
      support.
    - issue to be resolved on mailing list.
- Discussion of triggered add message
    o quiet room
    o WG list to be asked again if the message will do
- Discussion of bulk add message
    o predominant question of whether this form of the 
      message meets the requirements in the requirement
      document.  List to be inquired.
- Discussion of protection
    o 1+1 added as argument to Add Branch
    o other modes still need solution.
    o issue to be discussed on the list.

   
  
  

--Apple-Mail-79-423361791--


_______________________________________________
GSMP mailing list
GSMP@ietf.org
https://www1.ietf.org/mailman/listinfo/gsmp



From exim@www1.ietf.org  Thu Aug 28 12:59:54 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA00183
	for <gsmp-archive@odin.ietf.org>; Thu, 28 Aug 2003 12:59:54 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19sOaK-0005YJ-DU
	for gsmp-archive@odin.ietf.org; Thu, 28 Aug 2003 11:21:16 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h7SFLGVN021344
	for gsmp-archive@odin.ietf.org; Thu, 28 Aug 2003 11:21:16 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19sLSK-0004T5-Rs
	for gsmp-web-archive@optimus.ietf.org; Thu, 28 Aug 2003 08:00:48 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA05735
	for <gsmp-web-archive@ietf.org>; Thu, 28 Aug 2003 08:00:44 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19sLSJ-0004jM-00
	for gsmp-web-archive@ietf.org; Thu, 28 Aug 2003 08:00:47 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19sLSJ-0004jI-00
	for gsmp-web-archive@ietf.org; Thu, 28 Aug 2003 08:00:47 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19sJbP-0003fc-MT; Thu, 28 Aug 2003 06:02:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19sF12-0003Yy-Bm
	for gsmp@optimus.ietf.org; Thu, 28 Aug 2003 01:08:12 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA17811
	for <gsmp@ietf.org>; Thu, 28 Aug 2003 01:08:07 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19sF0y-00034U-00
	for gsmp@ietf.org; Thu, 28 Aug 2003 01:08:08 -0400
Received: from psg.com ([147.28.0.62] ident=mailnull)
	by ietf-mx with esmtp (Exim 4.12)
	id 19sF0x-00034I-00
	for gsmp@ietf.org; Thu, 28 Aug 2003 01:08:07 -0400
Received: from psg.com ([147.28.0.62])
	by psg.com with esmtp (Exim 4.22)
	id 19sF0x-000Gk9-Nb
	for gsmp@ietf.org; Thu, 28 Aug 2003 05:08:07 +0000
Date: Thu, 28 Aug 2003 14:07:40 +0900
Mime-Version: 1.0 (Apple Message framework v552)
Content-Type: text/plain; charset=US-ASCII; format=flowed
From: avri <avri@psg.com>
To: gsmp@ietf.org
Content-Transfer-Encoding: 7bit
Message-Id: <8C655C31-D915-11D7-9851-000393CC2112@psg.com>
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Subject: [GSMP] New tool
Sender: gsmp-admin@ietf.org
Errors-To: gsmp-admin@ietf.org
X-BeenThere: gsmp@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/gsmp>,
	<mailto:gsmp-request@ietf.org?subject=unsubscribe>
List-Id: General Switch Management Protocol <gsmp.ietf.org>
List-Post: <mailto:gsmp@ietf.org>
List-Help: <mailto:gsmp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/gsmp>,
	<mailto:gsmp-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi,

As those of you reading the list know there has been a little bit of 
consternation about:

a. the speed with which we are doing the work
b. the lack of participation

It occurred to me that part of the problem had to be with the WG 
chairs.  They, or rather we, were not doing enough to help the work 
move along and were not doing enough to keep the issues alive and in 
front of the group.

As I was getting ready to spend some more time focusing on the Base 
spec, it struck me that perhaps it would be good to try and assist the 
group in maintaining its focus and in tracking issues

I went searching among other working groups looking for methods and 
tools they employ to keep things organized and flowing.  From attending 
the WG chairs course I knew that issue tracking was important.  So I 
decided to borrow some stuff from the AAA group and have created a 
issues web page for the WG at:  psg.com/~avri/gsmp

(I will ask the secretariat to add this to the official web page)

It is not a sophisticated web page nor am i very happy with it, but I 
hope it will do as a start.  Over time I will add information and 
features and hope to make it nicer and work better.  Most important 
though I will use it to track the issues we need to deal with in order 
to finish the work we have before us.

In order to help me, I ask that folks with issues follow the directions 
in:
http://psg.com/~avri/gsmp/Issues-instructions.htm

That is, I ask that issues be submitted in a form that makes it easier 
to track.  For now at least, I will be doing all the maintenance by 
hand.

Hope this helps get us moving.

a.

PS.  If I got any of the original entries are wrong or you have 
something to add, please speak up.  I went through the recent email and 
added entries for the issues I had brought up on list.




_______________________________________________
GSMP mailing list
GSMP@ietf.org
https://www1.ietf.org/mailman/listinfo/gsmp



