From mib-doctors-bounces@ietf.org Wed Apr 04 00:16:15 2007
Return-path: <mib-doctors-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HYwut-0004P9-5m; Wed, 04 Apr 2007 00:16:15 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HYwur-0004MD-Vd
	for mib-doctors@ietf.org; Wed, 04 Apr 2007 00:16:13 -0400
Received: from elasmtp-banded.atl.sa.earthlink.net ([209.86.89.70])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HYwuq-0004SD-Gc
	for mib-doctors@ietf.org; Wed, 04 Apr 2007 00:16:13 -0400
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
	s=dk20050327; d=mindspring.com;
	b=N0VSCUnKOON3GhgeVFUqi78vm+4/TrbPDELzyqEnL9EZe/C7olVv3YL+a0Sz5s6L;
	h=Received:Message-ID:From:To:Subject:Date:MIME-Version:Content-Type:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE:X-ELNK-Trace:X-Originating-IP;
Received: from [66.167.249.181] (helo=JoanPC)
	by elasmtp-banded.atl.sa.earthlink.net with asmtp (Exim 4.34)
	id 1HYwuk-0002NB-62
	for mib-doctors@ietf.org; Wed, 04 Apr 2007 00:16:06 -0400
Message-ID: <009701c7766f$aed04280$6501a8c0@JoanPC>
From: "Joan Cucchiara" <jcucchiara@mindspring.com>
To: "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>
Date: Wed, 4 Apr 2007 00:14:04 -0400
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-ELNK-Trace: 4d68bbe9cb71969ea344cf2d1a8e60840a9da525759e26540169b7ab79c462b9dc48a411070f075a2601a10902912494350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 66.167.249.181
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 21be852dc93f0971708678c18d38c096
Subject: [MIB-DOCTORS] Is the following an Editorial Change?
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mib-doctors>,
	<mailto:mib-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mib-doctors>
List-Post: <mailto:mib-doctors@ietf.org>
List-Help: <mailto:mib-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mib-doctors>,
	<mailto:mib-doctors-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0584208496=="
Errors-To: mib-doctors-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0584208496==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0094_01C7764E.276D9C50"

This is a multi-part message in MIME format.

------=_NextPart_000_0094_01C7764E.276D9C50
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


Hello,

I'm reviewing a draft MIB which has some tables which sparse augment=20
tables in an RFC MIB.

One of these sparse augmenting tables contains a TruthValue object such
that if the object is true(1), then the DESCRIPTION clauses of some of =
the
objects in the BASE table are changed.

These redefinitions of the BASE table objects are in the draft MIB in
the text of the document (not in a MIB Module).

Here is an example which appears in the text of the new draft:
mplsTunnelEgressLSRId  <---- object from the BASE table in the RFC MIB.

      This object continues to map to the field in the RSVP-TE Session
      Object that occupies the space used by the IPv4 Tunnel Endpoint
      Address [RFC3209], but for a P2MP tunnel, this object does not
      identify an address of the egress of the tunnel. Instead it
      contains the P2MP ID value that identifies the identifier of the
      set of destinations for the P2MP tunnel and is carried in the P2MP
      Session Object [P2MP-TE]. The Description clause for this object
      can be read as follows.

         "Identity of the egress LSR associated with this tunnel
          instance.

          When an entry in the mplsTeP2mpTunnelTable is present
          corresponding to this entry in the mplsTunnelTable and when
          the mplsTeP2mpTunnel object in that table entry is present
          with the value true(1), this object contains the P2MP ID that
          identifies the set of destinations of this tunnel and that is
          signaled in the P2MP ID field of the P2MP Session Object if
          the MPLS signaling protocol for this tunnel indicated by
          mplsTunnelSignallingProto in MPLS-TE-STD-MIB is rsvp(2)."

      The destinations of the P2MP tunnel are found in the new
      mplsTeP2mpTunnelDestTable.

Currently, I believe that this is "not legal" and I should advise the =
authors of the
draft MIB, to rework the RFC (as painful as this may be), but wanted to =
get some=20
advice on this myself.

Thank you,
   Joan




------=_NextPart_000_0094_01C7764E.276D9C50
Content-Type: text/html;
	charset="iso-8859-1"
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=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.2912" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Hello,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>I'm reviewing a draft MIB which has =
some tables=20
which sparse augment </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>tables in an RFC MIB.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>One of these sparse augmenting tables =
contains a=20
TruthValue object such</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>that if the object is true(1), then the =
DESCRIPTION=20
clauses of some of the</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>objects in the BASE table are =
changed.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>These redefinitions of the BASE table =
objects are=20
in the draft MIB in</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>the text of the document (not in&nbsp;a =
MIB=20
Module).</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Here is an example which appears in the =
text of the=20
new draft:</FONT></DIV>
<DIV>mplsTunnelEgressLSRId&nbsp; &lt;---- object from the BASE table in =
the RFC=20
MIB.<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; This object continues to map =
to the=20
field in the RSVP-TE Session<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Object =
that=20
occupies the space used by the IPv4 Tunnel=20
Endpoint<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Address [RFC3209], but for a =
P2MP=20
tunnel, this object does not<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; identify =
an=20
address of the egress of the tunnel. Instead=20
it<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; contains the P2MP ID value that =
identifies=20
the identifier of the<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; set of =
destinations for=20
the P2MP tunnel and is carried in the =
P2MP<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
Session Object [P2MP-TE]. The Description clause for this=20
object<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; can be read as=20
follows.<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
"Identity of=20
the egress LSR associated with this=20
tunnel<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
instance.<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
When an=20
entry in the mplsTeP2mpTunnelTable is=20
present<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
corresponding=20
to this entry in the mplsTunnelTable and=20
when<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the=20
mplsTeP2mpTunnel object in that table entry is=20
present<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; with =
the value=20
true(1), this object contains the P2MP ID=20
that<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
identifies the=20
set of destinations of this tunnel and that=20
is<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; signaled in =
the=20
P2MP ID field of the P2MP Session Object=20
if<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the MPLS =
signaling=20
protocol for this tunnel indicated=20
by<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
mplsTunnelSignallingProto in MPLS-TE-STD-MIB is=20
rsvp(2)."<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The destinations of the =
P2MP=20
tunnel are found in the new<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
mplsTeP2mpTunnelDestTable.<BR><BR><FONT face=3DArial size=3D2>Currently, =
I believe=20
that this is "not legal" and I should advise the authors of =
the</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>draft MIB, to rework the RFC (as =
painful as this=20
may be), but wanted to get some </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>advice on this myself.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Thank you,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp; Joan</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></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV></BODY></HTML>

------=_NextPart_000_0094_01C7764E.276D9C50--



--===============0584208496==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
MIB-DOCTORS mailing list
MIB-DOCTORS@ietf.org
https://www1.ietf.org/mailman/listinfo/mib-doctors

--===============0584208496==--





From mib-doctors-bounces@ietf.org Mon Apr 09 06:01:15 2007
Return-path: <mib-doctors-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HaqgV-0000tv-9V; Mon, 09 Apr 2007 06:01:15 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HaqgU-0000tq-0Q
	for mib-doctors@ietf.org; Mon, 09 Apr 2007 06:01:14 -0400
Received: from co300216-co-outbound.net.avaya.com ([198.152.13.100]
	helo=co300216-co-outbound.avaya.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HaqgS-0003uH-BD
	for mib-doctors@ietf.org; Mon, 09 Apr 2007 06:01:13 -0400
Received: from unknown (HELO IS0004AVEXU1.global.avaya.com) ([135.64.105.51])
	by co300216-co-outbound.avaya.com with ESMTP;
	09 Apr 2007 06:01:06 -0400
X-IronPort-AV: i="4.14,387,1170651600"; 
	d="scan'208,217"; a="1244572:sNHT14892954"
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [MIB-DOCTORS] Is the following an Editorial Change?
Date: Mon, 9 Apr 2007 13:00:24 +0300
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F0CA034DA@is0004avexu1.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [MIB-DOCTORS] Is the following an Editorial Change?
Thread-Index: Acd2cAFRalNG8u89SAyJLqYwjR8blAEHNNNA
References: <009701c7766f$aed04280$6501a8c0@JoanPC>
From: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>
To: "Joan Cucchiara" <jcucchiara@mindspring.com>,
	"MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 223e3c753032a50d5dc4443c921c3fcd
Cc: 
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mib-doctors>,
	<mailto:mib-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mib-doctors>
List-Post: <mailto:mib-doctors@ietf.org>
List-Help: <mailto:mib-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mib-doctors>,
	<mailto:mib-doctors-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1334630004=="
Errors-To: mib-doctors-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1334630004==
content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C77A8D.E4724E8C"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C77A8D.E4724E8C
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

If I understand well, this looks to me like a semantic change that is
not backwards compatible. Does this reflect a change in the protocol? If
so how is backwards compatibility ensured in the protocol?=20
=20
MIB-wise, for the case where the TruthValue object is true(1) why not
point to a new object for the respective case instead of changing the
semantics of the objects already defined in the RFC? The price is adding
a new object, but the change would be incremental, thus acceptable,
wouldn't it?=20
=20
Dan
=20
=20
=20
=20


  _____ =20

	From: Joan Cucchiara [mailto:jcucchiara@mindspring.com]=20
	Sent: Wednesday, April 04, 2007 7:14 AM
	To: MIB Doctors (E-mail)
	Subject: [MIB-DOCTORS] Is the following an Editorial Change?
=09
=09
	=20
	Hello,
	=20
	I'm reviewing a draft MIB which has some tables which sparse
augment=20
	tables in an RFC MIB.
	=20
	One of these sparse augmenting tables contains a TruthValue
object such
	that if the object is true(1), then the DESCRIPTION clauses of
some of the
	objects in the BASE table are changed.
	=20
	These redefinitions of the BASE table objects are in the draft
MIB in
	the text of the document (not in a MIB Module).
	=20
	Here is an example which appears in the text of the new draft:
	mplsTunnelEgressLSRId  <---- object from the BASE table in the
RFC MIB.
=09
	      This object continues to map to the field in the RSVP-TE
Session
	      Object that occupies the space used by the IPv4 Tunnel
Endpoint
	      Address [RFC3209], but for a P2MP tunnel, this object does
not
	      identify an address of the egress of the tunnel. Instead
it
	      contains the P2MP ID value that identifies the identifier
of the
	      set of destinations for the P2MP tunnel and is carried in
the P2MP
	      Session Object [P2MP-TE]. The Description clause for this
object
	      can be read as follows.
=09
	         "Identity of the egress LSR associated with this tunnel
	          instance.
=09
	          When an entry in the mplsTeP2mpTunnelTable is present
	          corresponding to this entry in the mplsTunnelTable and
when
	          the mplsTeP2mpTunnel object in that table entry is
present
	          with the value true(1), this object contains the P2MP
ID that
	          identifies the set of destinations of this tunnel and
that is
	          signaled in the P2MP ID field of the P2MP Session
Object if
	          the MPLS signaling protocol for this tunnel indicated
by
	          mplsTunnelSignallingProto in MPLS-TE-STD-MIB is
rsvp(2)."
=09
	      The destinations of the P2MP tunnel are found in the new
	      mplsTeP2mpTunnelDestTable.
=09
	Currently, I believe that this is "not legal" and I should
advise the authors of the
	draft MIB, to rework the RFC (as painful as this may be), but
wanted to get some=20
	advice on this myself.
	=20
	Thank you,
	   Joan
	=20
	=20
	=20
	=20


------_=_NextPart_001_01C77A8D.E4724E8C
Content-Type: text/html;
	charset="us-ascii"
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=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.2963" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><SPAN class=3D454485209-09042007><FONT face=3DArial color=3D#0000ff =

size=3D2><STRONG><EM>If I understand well, this looks to me like a =
semantic change=20
that is not backwards compatible. Does this reflect a change in the =
protocol? If=20
so how is backwards compatibility ensured in the protocol?=20
</EM></STRONG></FONT></SPAN></DIV>
<DIV><SPAN class=3D454485209-09042007><STRONG><EM><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></EM></STRONG></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D454485209-09042007><STRONG><EM><FONT face=3DArial =
color=3D#0000ff=20
size=3D2>MIB-wise, for the case where the TruthValue object is true(1) =
why not=20
point to a new object for the respective case instead of changing the =
semantics=20
of the objects already&nbsp;defined in the RFC? The price is adding a =
new=20
object, but the change would be incremental, thus acceptable, wouldn't =
it?=20
</FONT></EM></STRONG></SPAN></DIV>
<DIV><SPAN class=3D454485209-09042007><STRONG><EM><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></EM></STRONG></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D454485209-09042007><STRONG><EM><FONT face=3DArial =
color=3D#0000ff=20
size=3D2>Dan</FONT></EM></STRONG></SPAN></DIV>
<DIV><SPAN class=3D454485209-09042007><STRONG><EM><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></EM></STRONG></SPAN>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> Joan Cucchiara=20
  [mailto:jcucchiara@mindspring.com] <BR><B>Sent:</B> Wednesday, April =
04, 2007=20
  7:14 AM<BR><B>To:</B> MIB Doctors (E-mail)<BR><B>Subject:</B> =
[MIB-DOCTORS] Is=20
  the following an Editorial Change?<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>Hello,</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>I'm reviewing a draft MIB which has =
some tables=20
  which sparse augment </FONT></DIV>
  <DIV><FONT face=3DArial size=3D2>tables in an RFC MIB.</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>One of these sparse augmenting tables =
contains a=20
  TruthValue object such</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2>that if the object is true(1), then =
the=20
  DESCRIPTION clauses of some of the</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2>objects in the BASE table are=20
  changed.</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>These redefinitions of the BASE table =
objects are=20
  in the draft MIB in</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2>the text of the document (not =
in&nbsp;a MIB=20
  Module).</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>Here is an example which appears in =
the text of=20
  the new draft:</FONT></DIV>
  <DIV>mplsTunnelEgressLSRId&nbsp; &lt;---- object from the BASE table =
in the=20
  RFC MIB.<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; This object continues =
to map to=20
  the field in the RSVP-TE Session<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Object that=20
  occupies the space used by the IPv4 Tunnel=20
  Endpoint<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Address [RFC3209], but for =
a P2MP=20
  tunnel, this object does not<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
identify an=20
  address of the egress of the tunnel. Instead=20
  it<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; contains the P2MP ID value that=20
  identifies the identifier of the<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; set =
of=20
  destinations for the P2MP tunnel and is carried in the=20
  P2MP<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Session Object [P2MP-TE]. The=20
  Description clause for this object<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
can be=20
  read as =
follows.<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  "Identity of the egress LSR associated with this=20
  tunnel<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
instance.<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
When=20
  an entry in the mplsTeP2mpTunnelTable is=20
  present<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  corresponding to this entry in the mplsTunnelTable and=20
  when<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the=20
  mplsTeP2mpTunnel object in that table entry is=20
  present<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; with =
the=20
  value true(1), this object contains the P2MP ID=20
  that<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
identifies the=20
  set of destinations of this tunnel and that=20
  is<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; signaled =
in the=20
  P2MP ID field of the P2MP Session Object=20
  if<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the MPLS=20
  signaling protocol for this tunnel indicated=20
  by<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  mplsTunnelSignallingProto in MPLS-TE-STD-MIB is=20
  rsvp(2)."<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The destinations of =
the P2MP=20
  tunnel are found in the new<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  mplsTeP2mpTunnelDestTable.<BR><BR><FONT face=3DArial =
size=3D2>Currently, I believe=20
  that this is "not legal" and I should advise the authors of =
the</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2>draft MIB, to rework the RFC (as =
painful as this=20
  may be), but wanted to get some </FONT></DIV>
  <DIV><FONT face=3DArial size=3D2>advice on this myself.</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>Thank you,</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp; Joan</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></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial =
size=3D2></FONT>&nbsp;</DIV></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C77A8D.E4724E8C--


--===============1334630004==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
MIB-DOCTORS mailing list
MIB-DOCTORS@ietf.org
https://www1.ietf.org/mailman/listinfo/mib-doctors

--===============1334630004==--




From mib-doctors-bounces@ietf.org Mon Apr 09 11:04:07 2007
Return-path: <mib-doctors-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HavPb-00036v-M1; Mon, 09 Apr 2007 11:04:07 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HavPa-00035n-Ls
	for mib-doctors@ietf.org; Mon, 09 Apr 2007 11:04:06 -0400
Received: from rwcrmhc15.comcast.net ([204.127.192.85])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HavPZ-000185-1c
	for mib-doctors@ietf.org; Mon, 09 Apr 2007 11:04:06 -0400
Received: from harrington73653
	(c-24-128-104-207.hsd1.nh.comcast.net[24.128.104.207])
	by comcast.net (rwcrmhc15) with SMTP
	id <20070409150403m15007j460e>; Mon, 9 Apr 2007 15:04:03 +0000
From: "David B Harrington" <dbharrington@comcast.net>
To: "'Romascanu, Dan \(Dan\)'" <dromasca@avaya.com>,
	"'Joan Cucchiara'" <jcucchiara@mindspring.com>,
	"'MIB Doctors \(E-mail\)'" <mib-doctors@ietf.org>
References: <009701c7766f$aed04280$6501a8c0@JoanPC>
	<AAB4B3D3CF0F454F98272CBE187FDE2F0CA034DA@is0004avexu1.global.avaya.com>
Subject: RE: [MIB-DOCTORS] Is the following an Editorial Change?
Date: Mon, 9 Apr 2007 11:03:34 -0400
Message-ID: <0aa501c77ab8$3f598130$0600a8c0@china.huawei.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
In-Reply-To: <AAB4B3D3CF0F454F98272CBE187FDE2F0CA034DA@is0004avexu1.global.avaya.com>
Thread-Index: Acd2cAFRalNG8u89SAyJLqYwjR8blAEHNNNAAAoybqA=
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8a961490db2a74c7613bf0201229f176
Cc: 
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mib-doctors>,
	<mailto:mib-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mib-doctors>
List-Post: <mailto:mib-doctors@ietf.org>
List-Help: <mailto:mib-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mib-doctors>,
	<mailto:mib-doctors-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0153025082=="
Errors-To: mib-doctors-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0153025082==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0AA6_01C77A96.B847E130"

This is a multi-part message in MIME format.

------=_NextPart_000_0AA6_01C77A96.B847E130
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit

Hi,
 
I looked at the change fairly quickly, and have not done a thorough
analysis.
 
My impression is that the original object is a union for EgressIDs.
The TruthValue serves as the discriminator in a discriminated union.
When true, the EgressId should be interpreted as a specific type of
EgressId.
So on my quick analysis, it appeared this was not illegal according to
SMIv2 rules.
 
The description that says it changes the DESCRIPTION clause would make
it illegal because it changes the semantics, but I think that is a
document wordsmithing problem, not a real SMIv2 legality problem.
 
I have concerns it may be a bad design however.
I am not sure that when the Truthvalue is true, the EgressId ALWAYS
represents a P2MP ID.
If not, there is potential for conflicting values among multiple
types, and the MIB only has a binary discriminator.
It does strike me that this is redefining the original purpose of the
field, to cover a case not considered originally.
 
David Harrington
dharrington@huawei.com
dbharrington@comcast.net
ietfdbh@comcast.net



  _____  

From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com] 
Sent: Monday, April 09, 2007 6:00 AM
To: Joan Cucchiara; MIB Doctors (E-mail)
Subject: RE: [MIB-DOCTORS] Is the following an Editorial Change?


If I understand well, this looks to me like a semantic change that is
not backwards compatible. Does this reflect a change in the protocol?
If so how is backwards compatibility ensured in the protocol? 
 
MIB-wise, for the case where the TruthValue object is true(1) why not
point to a new object for the respective case instead of changing the
semantics of the objects already defined in the RFC? The price is
adding a new object, but the change would be incremental, thus
acceptable, wouldn't it? 
 
Dan
 
 
 
 


  _____  

From: Joan Cucchiara [mailto:jcucchiara@mindspring.com] 
Sent: Wednesday, April 04, 2007 7:14 AM
To: MIB Doctors (E-mail)
Subject: [MIB-DOCTORS] Is the following an Editorial Change?


 
Hello,
 
I'm reviewing a draft MIB which has some tables which sparse augment 
tables in an RFC MIB.
 
One of these sparse augmenting tables contains a TruthValue object
such
that if the object is true(1), then the DESCRIPTION clauses of some of
the
objects in the BASE table are changed.
 
These redefinitions of the BASE table objects are in the draft MIB in
the text of the document (not in a MIB Module).
 
Here is an example which appears in the text of the new draft:
mplsTunnelEgressLSRId  <---- object from the BASE table in the RFC
MIB.

      This object continues to map to the field in the RSVP-TE Session
      Object that occupies the space used by the IPv4 Tunnel Endpoint
      Address [RFC3209], but for a P2MP tunnel, this object does not
      identify an address of the egress of the tunnel. Instead it
      contains the P2MP ID value that identifies the identifier of the
      set of destinations for the P2MP tunnel and is carried in the
P2MP
      Session Object [P2MP-TE]. The Description clause for this object
      can be read as follows.

         "Identity of the egress LSR associated with this tunnel
          instance.

          When an entry in the mplsTeP2mpTunnelTable is present
          corresponding to this entry in the mplsTunnelTable and when
          the mplsTeP2mpTunnel object in that table entry is present
          with the value true(1), this object contains the P2MP ID
that
          identifies the set of destinations of this tunnel and that
is
          signaled in the P2MP ID field of the P2MP Session Object if
          the MPLS signaling protocol for this tunnel indicated by
          mplsTunnelSignallingProto in MPLS-TE-STD-MIB is rsvp(2)."

      The destinations of the P2MP tunnel are found in the new
      mplsTeP2mpTunnelDestTable.

Currently, I believe that this is "not legal" and I should advise the
authors of the
draft MIB, to rework the RFC (as painful as this may be), but wanted
to get some 
advice on this myself.
 
Thank you,
   Joan
 
 
 
 


------=_NextPart_000_0AA6_01C77A96.B847E130
Content-Type: text/html;
	charset="US-ASCII"
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=3Dus-ascii">
<META content=3D"MSHTML 6.00.6000.16414" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D781464414-09042007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Hi,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D781464414-09042007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D781464414-09042007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>I looked at the change fairly quickly, and have =
not done a=20
thorough analysis.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D781464414-09042007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D781464414-09042007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>My impression is that the original object is a =
union for=20
EgressIDs.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D781464414-09042007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>The TruthValue serves as the discriminator in a =

discriminated union.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D781464414-09042007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>When true, the EgressId should be interpreted =
as a specific=20
type of EgressId.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D781464414-09042007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>So on my quick analysis, it appeared this was =
not illegal=20
according to SMIv2 rules.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D781464414-09042007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D781464414-09042007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>The description that says it changes the =
DESCRIPTION clause=20
would make it illegal because it changes the semantics, but I think that =
is a=20
document wordsmithing problem, not a real&nbsp;SMIv2 legality=20
problem.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D781464414-09042007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D781464414-09042007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>I have concerns it may be a bad design=20
however.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D781464414-09042007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>I am not sure that when the Truthvalue is true, =
the=20
EgressId ALWAYS represents a P2MP ID.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D781464414-09042007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>If not, there is potential for conflicting =
values among=20
multiple types, and the MIB only has a binary =
discriminator.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D781464414-09042007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>It does strike me that this is redefining the =
original=20
purpose of the field, to cover a case not considered=20
originally.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D781464414-09042007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D781464414-09042007><!-- =
Converted from text/plain format -->
<P><FONT size=3D2>David=20
Harrington<BR>dharrington@huawei.com<BR>dbharrington@comcast.net<BR>ietfd=
bh@comcast.net<BR></FONT></P></SPAN></DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> Romascanu, Dan (Dan)=20
  [mailto:dromasca@avaya.com] <BR><B>Sent:</B> Monday, April 09, 2007 =
6:00=20
  AM<BR><B>To:</B> Joan Cucchiara; MIB Doctors =
(E-mail)<BR><B>Subject:</B> RE:=20
  [MIB-DOCTORS] Is the following an Editorial =
Change?<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV><SPAN class=3D454485209-09042007><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2><STRONG><EM>If I understand well, this looks to me like a =
semantic=20
  change that is not backwards compatible. Does this reflect a change in =
the=20
  protocol? If so how is backwards compatibility ensured in the =
protocol?=20
  </EM></STRONG></FONT></SPAN></DIV>
  <DIV><SPAN class=3D454485209-09042007><STRONG><EM><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2></FONT></EM></STRONG></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D454485209-09042007><STRONG><EM><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2>MIB-wise, for the case where the TruthValue object is true(1) =
why not=20
  point to a new object for the respective case instead of changing the=20
  semantics of the objects already&nbsp;defined in the RFC? The price is =
adding=20
  a new object, but the change would be incremental, thus acceptable, =
wouldn't=20
  it? </FONT></EM></STRONG></SPAN></DIV>
  <DIV><SPAN class=3D454485209-09042007><STRONG><EM><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2></FONT></EM></STRONG></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D454485209-09042007><STRONG><EM><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2>Dan</FONT></EM></STRONG></SPAN></DIV>
  <DIV><SPAN class=3D454485209-09042007><STRONG><EM><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2></FONT></EM></STRONG></SPAN>&nbsp;</DIV>
  <DIV>&nbsp;</DIV>
  <DIV>&nbsp;</DIV>
  <DIV>&nbsp;</DIV><BR>
  <BLOCKQUOTE dir=3Dltr=20
  style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
    <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft>
    <HR tabIndex=3D-1>
    <FONT face=3DTahoma size=3D2><B>From:</B> Joan Cucchiara=20
    [mailto:jcucchiara@mindspring.com] <BR><B>Sent:</B> Wednesday, April =
04,=20
    2007 7:14 AM<BR><B>To:</B> MIB Doctors (E-mail)<BR><B>Subject:</B>=20
    [MIB-DOCTORS] Is the following an Editorial =
Change?<BR></FONT><BR></DIV>
    <DIV></DIV>
    <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
    <DIV><FONT face=3DArial size=3D2>Hello,</FONT></DIV>
    <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
    <DIV><FONT face=3DArial size=3D2>I'm reviewing a draft MIB which has =
some tables=20
    which sparse augment </FONT></DIV>
    <DIV><FONT face=3DArial size=3D2>tables in an RFC MIB.</FONT></DIV>
    <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
    <DIV><FONT face=3DArial size=3D2>One of these sparse augmenting =
tables contains=20
    a TruthValue object such</FONT></DIV>
    <DIV><FONT face=3DArial size=3D2>that if the object is true(1), then =
the=20
    DESCRIPTION clauses of some of the</FONT></DIV>
    <DIV><FONT face=3DArial size=3D2>objects in the BASE table are=20
    changed.</FONT></DIV>
    <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
    <DIV><FONT face=3DArial size=3D2>These redefinitions of the BASE =
table objects=20
    are in the draft MIB in</FONT></DIV>
    <DIV><FONT face=3DArial size=3D2>the text of the document (not =
in&nbsp;a MIB=20
    Module).</FONT></DIV>
    <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
    <DIV><FONT face=3DArial size=3D2>Here is an example which appears in =
the text of=20
    the new draft:</FONT></DIV>
    <DIV>mplsTunnelEgressLSRId&nbsp; &lt;---- object from the BASE table =
in the=20
    RFC MIB.<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; This object continues =
to map=20
    to the field in the RSVP-TE =
Session<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Object=20
    that occupies the space used by the IPv4 Tunnel=20
    Endpoint<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Address [RFC3209], but =
for a P2MP=20
    tunnel, this object does not<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
identify an=20
    address of the egress of the tunnel. Instead=20
    it<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; contains the P2MP ID value that =

    identifies the identifier of the<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
set of=20
    destinations for the P2MP tunnel and is carried in the=20
    P2MP<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Session Object [P2MP-TE]. The =

    Description clause for this object<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
can be=20
    read as =
follows.<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    "Identity of the egress LSR associated with this=20
    tunnel<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
instance.<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
When=20
    an entry in the mplsTeP2mpTunnelTable is=20
    present<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    corresponding to this entry in the mplsTunnelTable and=20
    when<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the=20
    mplsTeP2mpTunnel object in that table entry is=20
    present<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
with the=20
    value true(1), this object contains the P2MP ID=20
    that<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
identifies=20
    the set of destinations of this tunnel and that=20
    is<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
signaled in the=20
    P2MP ID field of the P2MP Session Object=20
    if<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the =
MPLS=20
    signaling protocol for this tunnel indicated=20
    by<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    mplsTunnelSignallingProto in MPLS-TE-STD-MIB is=20
    rsvp(2)."<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The destinations of =
the P2MP=20
    tunnel are found in the new<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    mplsTeP2mpTunnelDestTable.<BR><BR><FONT face=3DArial =
size=3D2>Currently, I=20
    believe that this is "not legal" and I should advise the authors of=20
    the</FONT></DIV>
    <DIV><FONT face=3DArial size=3D2>draft MIB, to rework the RFC (as =
painful as=20
    this may be), but wanted to get some </FONT></DIV>
    <DIV><FONT face=3DArial size=3D2>advice on this myself.</FONT></DIV>
    <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
    <DIV><FONT face=3DArial size=3D2>Thank you,</FONT></DIV>
    <DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp; Joan</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></FONT>&nbsp;</DIV>
    <DIV><FONT face=3DArial=20
size=3D2></FONT>&nbsp;</DIV></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_0AA6_01C77A96.B847E130--




--===============0153025082==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
MIB-DOCTORS mailing list
MIB-DOCTORS@ietf.org
https://www1.ietf.org/mailman/listinfo/mib-doctors

--===============0153025082==--






From mib-doctors-bounces@ietf.org Mon Apr 09 11:41:25 2007
Return-path: <mib-doctors-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Havzh-0007eP-TD; Mon, 09 Apr 2007 11:41:25 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Havzg-0007e7-92
	for mib-doctors@ietf.org; Mon, 09 Apr 2007 11:41:24 -0400
Received: from nj300815-nj-outbound.net.avaya.com ([198.152.12.100]
	helo=nj300815-nj-outbound.avaya.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Havzf-0007cU-1F
	for mib-doctors@ietf.org; Mon, 09 Apr 2007 11:41:24 -0400
Received: from 51.105.64.135.in-addr.arpa (HELO IS0004AVEXU1.global.avaya.com)
	([135.64.105.51])
	by nj300815-nj-outbound.avaya.com with ESMTP; 09 Apr 2007 11:41:18 -0400
X-IronPort-AV: i="4.14,388,1170651600"; 
	d="scan'208,217"; a="1441152:sNHT12156834"
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [MIB-DOCTORS] Is the following an Editorial Change?
Date: Mon, 9 Apr 2007 18:41:02 +0300
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F0CA0350C@is0004avexu1.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [MIB-DOCTORS] Is the following an Editorial Change?
Thread-Index: Acd2cAFRalNG8u89SAyJLqYwjR8blAEHNNNAAAoybqAAAeZ1kA==
References: <009701c7766f$aed04280$6501a8c0@JoanPC>
	<AAB4B3D3CF0F454F98272CBE187FDE2F0CA034DA@is0004avexu1.global.avaya.com>
	<0aa501c77ab8$3f598130$0600a8c0@china.huawei.com>
From: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>
To: "David B Harrington" <dbharrington@comcast.net>,
	"Joan Cucchiara" <jcucchiara@mindspring.com>,
	"MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 34d35111647d654d033d58d318c0d21a
Cc: 
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mib-doctors>,
	<mailto:mib-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mib-doctors>
List-Post: <mailto:mib-doctors@ietf.org>
List-Help: <mailto:mib-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mib-doctors>,
	<mailto:mib-doctors-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1748178019=="
Errors-To: mib-doctors-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1748178019==
content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C77ABD.7A2AF98A"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C77ABD.7A2AF98A
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

=20
=20
This was exactly my impression as well, and this is why I was wondering
how do two entities supporting one the older version and the other the
new version of the protocol interoperate on the wire.=20
=20
Dan
=20


  _____ =20

	From: David B Harrington [mailto:dbharrington@comcast.net]=20
=09
	=20
	It does strike me that this is redefining the original purpose
of the field, to cover a case not considered originally.
	=20
	David Harrington
	dharrington@huawei.com
	dbharrington@comcast.net
	ietfdbh@comcast.net
=09


	=20


------_=_NextPart_001_01C77ABD.7A2AF98A
Content-Type: text/html;
	charset="us-ascii"
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=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.2963" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><STRONG><EM><FONT face=3DArial color=3D#0000ff=20
size=3D2></FONT></EM></STRONG>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV><SPAN class=3D314113915-09042007><STRONG><EM><FONT face=3DArial =
color=3D#0000ff=20
size=3D2>This was exactly my impression as well, and this is why I was =
wondering=20
how do two entities supporting one the older version and the other the =
new=20
version of the protocol interoperate on the wire.=20
</FONT></EM></STRONG></SPAN></DIV>
<DIV><SPAN class=3D314113915-09042007><STRONG><EM><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></EM></STRONG></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D314113915-09042007><STRONG><EM><FONT face=3DArial =
color=3D#0000ff=20
size=3D2>Dan</FONT></EM></STRONG></SPAN></DIV>
<DIV><SPAN class=3D314113915-09042007></SPAN>&nbsp;</DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> David B Harrington=20
  [mailto:dbharrington@comcast.net] <BR></FONT></DIV>
  <DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff=20
  size=3D2></FONT>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D781464414-09042007><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>It does strike me that this is redefining the =
original=20
  purpose of the field, to cover a case not considered=20
  originally.</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D781464414-09042007><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D781464414-09042007><!-- =
Converted from text/plain format -->
  <P><FONT size=3D2>David=20
  =
Harrington<BR>dharrington@huawei.com<BR>dbharrington@comcast.net<BR>ietfd=
bh@comcast.net<BR></FONT></P></SPAN></DIV><BR><SPAN=20
  class=3D314113915-09042007><STRONG><EM><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2>&nbsp;</FONT></EM></STRONG></SPAN></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C77ABD.7A2AF98A--


--===============1748178019==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
MIB-DOCTORS mailing list
MIB-DOCTORS@ietf.org
https://www1.ietf.org/mailman/listinfo/mib-doctors

--===============1748178019==--




From mib-doctors-bounces@ietf.org Tue Apr 10 18:13:59 2007
Return-path: <mib-doctors-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HbOb9-00033N-6e; Tue, 10 Apr 2007 18:13:59 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HbOb8-00033C-IB
	for mib-doctors@ietf.org; Tue, 10 Apr 2007 18:13:58 -0400
Received: from elasmtp-junco.atl.sa.earthlink.net ([209.86.89.63])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HbOb4-0006ck-Pe
	for mib-doctors@ietf.org; Tue, 10 Apr 2007 18:13:58 -0400
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
	s=dk20050327; d=mindspring.com;
	b=loI94OHLVGTBF1ExIKkjG6EYWi1ooOU48s3OqPPV18cyEubFJPgkah/XG51fAPkC;
	h=Received:Message-ID:From:To:References:Subject:Date:MIME-Version:Content-Type:X-Priority:X-MSMail-Priority:X-Mailer:X-MIMEOLE:X-ELNK-Trace:X-Originating-IP;
Received: from [66.167.249.181] (helo=JoanPC)
	by elasmtp-junco.atl.sa.earthlink.net with asmtp (Exim 4.34)
	id 1HbOb3-0006T1-IJ; Tue, 10 Apr 2007 18:13:54 -0400
Message-ID: <011c01c77bbd$3f10f5e0$6501a8c0@JoanPC>
From: "Joan Cucchiara" <jcucchiara@mindspring.com>
To: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>,
	"David B Harrington" <dbharrington@comcast.net>,
	"MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>
References: <009701c7766f$aed04280$6501a8c0@JoanPC>
	<AAB4B3D3CF0F454F98272CBE187FDE2F0CA034DA@is0004avexu1.global.avaya.com>
	<0aa501c77ab8$3f598130$0600a8c0@china.huawei.com>
	<AAB4B3D3CF0F454F98272CBE187FDE2F0CA0350C@is0004avexu1.global.avaya.com>
Subject: Re: [MIB-DOCTORS] Is the following an Editorial Change?
Date: Tue, 10 Apr 2007 18:11:53 -0400
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-ELNK-Trace: 4d68bbe9cb71969ea344cf2d1a8e60840a9da525759e2654e5ca403402287360f19bf517696bedbcc6b317bf5bc479bb350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 66.167.249.181
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97c820c82c68af374c4e382a80dc5017
Cc: 
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mib-doctors>,
	<mailto:mib-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mib-doctors>
List-Post: <mailto:mib-doctors@ietf.org>
List-Help: <mailto:mib-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mib-doctors>,
	<mailto:mib-doctors-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0939311513=="
Errors-To: mib-doctors-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0939311513==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0119_01C77B9B.B7AE4FB0"

This is a multi-part message in MIME format.

------=_NextPart_000_0119_01C77B9B.B7AE4FB0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Dan and David,

Thank you for your comments.  The original protocol did not define =
point-2-multipoint because the
working group agreed to do this in subsequent documents (as an extension =
to the protocol). =20
I don't know if anything in the original protocol was invalidated due to =
adding the point-2-multipoint
extension.

Wrt the new MIB I agree with the approach of having new objects, since, =
as Dan points out,=20
there appears to be the potential for interoperability using the same =
objects from the original RFC. =20
This approach might make some of the objects in the original =
(point-2-point) MIB meaningless=20
but that should be acceptable as long as it is documented.  In fact, I =
could advise the authors
to  show what objects from the RFC MIB need to be supported in the =
conformance=20
section of the new MIB.

-Joan

  ----- Original Message -----=20
  From: Romascanu, Dan (Dan)=20
  To: David B Harrington ; Joan Cucchiara ; MIB Doctors (E-mail)=20
  Sent: Monday, April 09, 2007 11:41 AM
  Subject: RE: [MIB-DOCTORS] Is the following an Editorial Change?




  This was exactly my impression as well, and this is why I was =
wondering how do two entities supporting one the older version and the =
other the new version of the protocol interoperate on the wire.=20

  Dan




-------------------------------------------------------------------------=
---
    From: David B Harrington [mailto:dbharrington@comcast.net]=20


    It does strike me that this is redefining the original purpose of =
the field, to cover a case not considered originally.

    David Harrington
    dharrington@huawei.com
    dbharrington@comcast.net
    ietfdbh@comcast.net



     
------=_NextPart_000_0119_01C77B9B.B7AE4FB0
Content-Type: text/html;
	charset="iso-8859-1"
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=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.2912" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Dan and David,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Thank you for your comments.&nbsp; The =
original=20
protocol did not define point-2-multipoint because the</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>working group agreed to do this in =
subsequent=20
documents (as an extension to the protocol).&nbsp; </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I&nbsp;don't know if anything&nbsp;in =
the original=20
protocol was invalidated due to adding the =
point-2-multipoint</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>extension.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Wrt the new MIB =
I&nbsp;agree&nbsp;with&nbsp;the=20
approach of having new objects, since, as Dan points out, </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>there appears to be the potential =
</FONT><FONT=20
face=3DArial size=3D2>for interoperability using the same objects from =
the original=20
RFC.&nbsp; </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>This approach might make </FONT><FONT =
face=3DArial=20
size=3D2>some of the objects in the original (point-2-point) =
</FONT><FONT=20
face=3DArial size=3D2>MIB meaningless </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>but that should be </FONT><FONT =
face=3DArial=20
size=3D2>acceptable as long as it is documented.&nbsp; In fact, I=20
could&nbsp;advise the authors</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>to&nbsp;&nbsp;show what objects from =
the RFC MIB=20
need to be supported in </FONT><FONT face=3DArial size=3D2>the =
</FONT><FONT=20
face=3DArial size=3D2>conformance </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>section of the new MIB.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>-Joan</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
  <DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
  <DIV=20
  style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
  <A title=3Ddromasca@avaya.com =
href=3D"mailto:dromasca@avaya.com">Romascanu, Dan=20
  (Dan)</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A =
title=3Ddbharrington@comcast.net=20
  href=3D"mailto:dbharrington@comcast.net">David B Harrington</A> ; <A=20
  title=3Djcucchiara@mindspring.com =
href=3D"mailto:jcucchiara@mindspring.com">Joan=20
  Cucchiara</A> ; <A title=3Dmib-doctors@ietf.org=20
  href=3D"mailto:mib-doctors@ietf.org">MIB Doctors (E-mail)</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Monday, April 09, 2007 =
11:41=20
  AM</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> RE: [MIB-DOCTORS] Is =
the=20
  following an Editorial Change?</DIV>
  <DIV><BR></DIV>
  <DIV><STRONG><EM><FONT face=3DArial color=3D#0000ff=20
  size=3D2></FONT></EM></STRONG>&nbsp;</DIV>
  <DIV>&nbsp;</DIV>
  <DIV><SPAN class=3D314113915-09042007><STRONG><EM><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2>This was exactly my impression as well, and this is why I was =
wondering=20
  how do two entities supporting one the older version and the other the =
new=20
  version of the protocol interoperate on the wire.=20
  </FONT></EM></STRONG></SPAN></DIV>
  <DIV><SPAN class=3D314113915-09042007><STRONG><EM><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2></FONT></EM></STRONG></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D314113915-09042007><STRONG><EM><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2>Dan</FONT></EM></STRONG></SPAN></DIV>
  <DIV><SPAN class=3D314113915-09042007></SPAN>&nbsp;</DIV><BR>
  <BLOCKQUOTE dir=3Dltr=20
  style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
    <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft>
    <HR tabIndex=3D-1>
    <FONT face=3DTahoma size=3D2><B>From:</B> David B Harrington=20
    [mailto:dbharrington@comcast.net] <BR></FONT></DIV>
    <DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff=20
    size=3D2></FONT>&nbsp;</DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D781464414-09042007><FONT =
face=3DArial=20
    color=3D#0000ff size=3D2>It does strike me that this is redefining =
the original=20
    purpose of the field, to cover a case not considered=20
    originally.</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D781464414-09042007><FONT =
face=3DArial=20
    color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D781464414-09042007><!-- =
Converted from text/plain format -->
    <P><FONT size=3D2>David Harrington<BR><A=20
    =
href=3D"mailto:dharrington@huawei.com">dharrington@huawei.com</A><BR><A=20
    =
href=3D"mailto:dbharrington@comcast.net">dbharrington@comcast.net</A><BR>=
<A=20
    =
href=3D"mailto:ietfdbh@comcast.net">ietfdbh@comcast.net</A><BR></FONT></P=
></SPAN></DIV><BR><SPAN=20
    class=3D314113915-09042007><STRONG><EM><FONT face=3DArial =
color=3D#0000ff=20
    =
size=3D2>&nbsp;</FONT></EM></STRONG></SPAN></BLOCKQUOTE></BLOCKQUOTE></BO=
DY></HTML>

------=_NextPart_000_0119_01C77B9B.B7AE4FB0--



--===============0939311513==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
MIB-DOCTORS mailing list
MIB-DOCTORS@ietf.org
https://www1.ietf.org/mailman/listinfo/mib-doctors

--===============0939311513==--





From mib-doctors-bounces@ietf.org Thu Apr 12 07:49:09 2007
Return-path: <mib-doctors-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HbxnZ-0006lR-7b; Thu, 12 Apr 2007 07:49:09 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HbxnX-0006kx-BF; Thu, 12 Apr 2007 07:49:07 -0400
Received: from co300216-co-outbound.net.avaya.com ([198.152.13.100]
	helo=co300216-co-outbound.avaya.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HbxnW-0005lc-EK; Thu, 12 Apr 2007 07:49:07 -0400
Received: from unknown (HELO IS0004AVEXU1.global.avaya.com) ([135.64.105.51])
	by co300216-co-outbound.avaya.com with ESMTP;
	12 Apr 2007 07:49:04 -0400
X-IronPort-AV: i="4.14,400,1170651600"; d="scan'208"; a="2716171:sNHT10351074"
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
Received: from 300815erh2.post.avaya.com ([198.152.6.49]) by
	IS0004AVEXU1.global.avaya.com with Microsoft
	SMTPSVC(5.0.2195.6713); Thu, 29 Mar 2007 14:20:54 +0200
MIME-Version: 1.0
Received: from co300216-co-outbound.avaya.com
	(co300216-co-outbound.net.avaya.com [198.152.13.100]) by
	300815erh2.post.avaya.com (Switch-3.1.8/Switch-3.1.7) with
	ESMTP id l2TCKrQ3029018 for <dromasca@avaya.com>;
	Thu, 29 Mar 2007 08:20:53 -0400
Content-Type: text/plain;
	charset="windows-1256"
Content-Transfer-Encoding: quoted-printable
Received: from lists.ietf.org (HELO megatron.ietf.org) ([156.154.16.145]) by
	co300216-co-ierwest.avaya.com with ESMTP; 29 Mar 2007 08:23:58 -0400
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by
	megatron.ietf.org with esmtp (Exim 4.43) id 1HWtcQ-0000At-2E;
	Thu, 29 Mar 2007 08:20:42 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with
	esmtp (Exim 4.43) id 1HWtcO-00009p-HE;
	Thu, 29 Mar 2007 08:20:40 -0400
Received: from co300216-co-outbound.net.avaya.com ([198.152.13.100]
	helo=co300216-co-outbound.avaya.com) by ietf-mx.ietf.org with
	esmtp (Exim 4.43) id 1HWtcM-0000zj-Op;
	Thu, 29 Mar 2007 08:20:40 -0400
Received: from unknown (HELO IS0004AVEXU1.global.avaya.com) ([135.64.105.51])
	by co300216-co-outbound.avaya.com with ESMTP;
	29 Mar 2007 08:23:42 -0400
Received: from 300216erh2.post.avaya.com ([198.152.7.49]) by
	IS0004AVEXU1.global.avaya.com with Microsoft
	SMTPSVC(5.0.2195.6713); Tue, 27 Mar 2007 15:03:25 +0200
Received: from de307622-de-outbound.net.avaya.com
	(de307622-de-outbound.net.avaya.com [198.152.71.100]) by
	300216erh2.post.avaya.com (Switch-3.1.8/Switch-3.1.7) with
	ESMTP id l2RD2hjf000420 for <dromasca@avaya.com>;
	Tue, 27 Mar 2007 07:03:23 -0600
Received: from megatron.ietf.org ([156.154.16.145]) by
	de307622-de-ieremea.avaya.com with ESMTP; 27 Mar 2007 09:03:22 -0400
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by
	megatron.ietf.org with esmtp (Exim 4.43) id 1HWBKP-0002cd-5Q;
	Tue, 27 Mar 2007 09:03:09 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with
	esmtp (Exim 4.43) id 1HWBKN-0002bm-7r;
	Tue, 27 Mar 2007 09:03:07 -0400
Received: from co300216-co-outbound.net.avaya.com ([198.152.13.100]
	helo=co300216-co-outbound.avaya.com) by ietf-mx.ietf.org with
	esmtp (Exim 4.43) id 1HWBKK-0000I7-Jc;
	Tue, 27 Mar 2007 09:03:07 -0400
Received: from unknown (HELO IS0004AVEXU1.global.avaya.com) ([135.64.105.51])
	by co300216-co-outbound.avaya.com with ESMTP;
	27 Mar 2007 09:05:31 -0400
content-class: urn:content-classes:message
Date: Thu, 12 Apr 2007 14:48:23 +0300
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F0CA56A62@is0004avexu1.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Minutes of the OPS Area open meetings in Prague - FINAL VERSION?
Thread-Index: AcdwcCfEZyJt5bMOTaeTKpD3N4xYIQ==
From: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>
To: <ops-area@ietf.org>, <ops-nm@ietf.org>, <mib-doctors@ietf.org>,
	"IETF MIBs" <ietfmibs@lists.ietf.org>, <aaa-doctors@ietf.org>,
	<nmrg@ibr.cs.tu-bs.de>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 8cb9b411340046bf4080a729180a0672
Cc: 
Subject: [MIB-DOCTORS] Minutes of the OPS Area open meetings in Prague -
	FINAL VERSION? 
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mib-doctors>,
	<mailto:mib-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mib-doctors>
List-Post: <mailto:mib-doctors@ietf.org>
List-Help: <mailto:mib-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mib-doctors>,
	<mailto:mib-doctors-request@ietf.org?subject=subscribe>
Errors-To: mib-doctors-bounces@ietf.org

Unless I missed some mails during my vacation, I did not record any =
further feedback to this version.=20

Going once ...
Going twice ...
(but not later than this weekend, please)

Dan

-------------------------------------------------------------------------=
------


Meeting 1 - Monday March 19, 2007 15:20 to 17:20=20

1. Meeting Administrivia

2. Introduction of new Area Director - Ron Bonica=20

Dan - thanking David Kessens for his years of service as Area Director

3. Mini-BOF A: - Manageability and Operational Guidelines - David =
Harrington=20

http://www3.ietf.org/proceedings/07mar/slides/opsarea-1.ppt

Discussions about the structure of the document - should the protocol =
evaluation be part of the document?=20

4. Mini-BOF B: COPS push mode policy configuration - Tom Taylor and Tina =
Tsou =20

http://www3.ietf.org/proceedings/07mar/slides/opsarea-3.ppt

Sharon Chisholm: why COPS? because COPS is (apparently) going away=20
Unidentified : working at the ITU-T, still some interest=20
Kevin Johnson: in the draft, not quite clear if a new message was used.
Tom: draft proposes a new message but could also use a flag, which is =
the less violent solution. Discussion of the collision of handles
Dbh: there are two questions to answer.
question 1: is COPS going away? Worth it? Little update in the industry. =
Should this be part of the manageability work (his mini-BOF)? Should we =
move COPS to experimental or not recommended? question 2: technical =
decision whether change is the right one?
Scott Bradner: Answer Dave's first question. some enthusiasm for COPS at =
the  beginning, then faded away. Interest in ITU. The ITU-T is using a =
few protocols including DIAMETER and COPS from the IETF that require =
some extensions. If another non-IETF group wants to use COPS, why stand =
in their way?
Dave: "I can agree with that; somebody once said that the IETF doesn't =
produce standards, but technologies; other organizations produce =
standards"
Dan (to Tom): what is your preferred solution?=20
Tom: A standard document with the COPS update . ITU and IETF would =
progress this in parallel (approve in ITU-T as an annex), and then have =
IETF (tweak and) approve it, and then update ITU-T to reference the RFC.
Scott: This parallel approach has been problematic in the past. It =
should either be done in ITU or in IETF, but not both.
Tina: I think this can be done
Dan: another approach is that the ITU-T can publish an Informational =
document. I do not want to take a position at this point. ITU should =
also consider what happens
Dave Partain: I think there will be little energy to do this in the =
IETF, so it should be done in ITU.
Bert: I do not know if COPS-PR is being used or not; I know I do not =
want to spend time working on COPS-PR. Is anybody interested in working =
on it (including review any work done by ITU?)
Tom: Does anybody work for an organization that uses COPS-PR?=20
One person raised their hands (Tina Tsou from Huawei)
Tom: Is there any interest in working on COPS-PR extensions?=20
Dan: these questions should be asked on the OPS lists and ITU lists.
Should it be standards track? - the authors would like it so.=20
Action item - Tom to address the ops-area list with query to determine =
status of implementation and deployment of COPS and COPS-PR and level of =
interest in participating in such a work

5. Mini-BOF C: Best Current Practices in Operations and Management - =
David Harrington =20

http://www3.ietf.org/proceedings/07mar/slides/opsarea-2.ppt

Proposal to create operation capabilities working group, modeled on the =
experience of opsec WG
Would bring in operators experience
Framework document and operational guidelines as principal output
Is opsec a success story?=20
Straw poll indicates interest - continue discussion after the next item

6. Improved Efficiency of the OPS Area - proposal for the formation of a =
OPS Area WG - ADs=20

David and Dan - create structure for OPS area, similar to the one =
existing in TSV and Routing
Should it be merged with OPS and management capabilities WG as suggested =
by David H.?=20
TSV chair - success in Transport due to multiple small items, no =
dominant item
Straw poll indicates interest - nobody believes it's a bad idea, =
continue discussions in net meeting


7. Open Microphone=20



Meeting 2 - Wednesday March 21, 2007 - 13:00 to 16:10=20

1. Meeting Administrivia ADs (total: 5 min)=20

2. Mini-BOF D: NE/facilities/lines/protocols/services data modeling - =
Michael Alexander=20

http://www3.ietf.org/proceedings/07mar/slides/opsarea-4.ppt

Scott Bradner - very complex, IETF not good history in this type of =
thing
Pekka - benefit would go to NMS vendors?
response - benefit to equipment vendors to get devices into NMSs
Pekka - simpler version may be helpful, clean terminology would be =
helpful potential but current scope too big, maybe more fit to the IRTF
Margret Wassermann - interesting, but what gets standardized?
response - focus on meta models only
xx - sim  (info model) underway for 4 years - achieved meta view, now =
time to distribute to groups to use
response - this proposal is much simpler than sim

Chair: suggest create list & discuss issues raised in meeting, only one =
opposed

3. MIB-Doctor-sponsored MIB-document-writing template: David Harrington=20

http://www3.ietf.org/proceedings/07mar/slides/opsarea-8.ppt

No discussions

4. Mini-BOF E: MIB module editing in XML : Emile Stephan =20

http://www3.ietf.org/proceedings/07mar/slides/opsarea-5.ppt

Sharon - do you actually have tools to translate XML to MIBs?
response - I'm proposing to edit the MIB in XML and use XSL =
transformation.
Sharon - do you do SMI verification?
Emile: Shows that the tool captures mistakes.
Bill Fenner - wrong way to model MIB in XML - better to have element =
that is syntax or XML schema for writing a MIB
response - I'm using XML in a very loose way, but this is better than =
nothing. Please make better proposal.
Juergen - The opening argument in the beginning you wanted to move to =
data model. The main issue is not syntactic problem to get there.
response -  I asked for a BOF in order to discuss and have proposals of =
how to move forward

chair - does not feel that it's a standards problem at this time but =
maybe should be discussed with tools people

5. Mini-BOF F: Japanese Data Model Standards: Tomoyuki Iijima=20

http://www3.ietf.org/proceedings/07mar/slides/opsarea-6.ppt

- proposed goal for NGO
Sharon - why select VLANs?
response - well used technology in enterprise space
chair - MIB modules are used for VLAN config in enterprises - good to =
see comparison between SNMP & netconf=20

chair - In Chicago we will have one or two BOFs for data modeling. This =
contribution belongs to this space. Encourage to continue the work, =
update the I-D and bring proposals to the NGO work.


6. Mini-BOF G: OWL techniques for MIB to XML documents and schema =
translation - Bob Natale=20

http://www3.ietf.org/proceedings/07mar/slides/opsarea-7.ppt

Andy Bierman - there are issues beyond mere translations - suggests that =
experts in a protocol would need to be involved in determining if =
conversion can even be done
Scott Bradner - how fill in holes (beyond what MIB covers)
bob - would need to have collaborative process for each MIB
=09
chair - good to invite WS-CIM folk to join discussion
Sharon xx - may be mismatch between MIBs and service-orientated =
interface - also may be too high a data bandwidth generated for SOA/WS  =
management stations
Bob - yes an issue
Sharon - how much interest in WS community
Bob - much need among user & developer communities=20
Dan Romascanu (from floor) - not sure that this fits the base role of =
the IETF - make net work better
Bob - this will help the operators run the network better
Eugene - spent years in WS area - high level seems to be good - but WS =
seems to rely on different fundamental information needs than what is in =
MIBs - also some groups in this area do not like each  other (OAIS & =
DMTF for example).  The other is political. Are the two standard bodies =
can really work together in the long term?
xx - good idea & he is optimistic that this would be useful - but there =
are valid concerns about level of impact on the other communities

chair - open list for discussion, consensus in the room


7. Late Submission - requirements to tunneling protocols OAM - KIKUCHI =
Yutaka=20

Pekka - why is this tunnel specific? Only reordering is
response - Our main objective is to measure tunnel quality.
Chair - Maybe the next version of the draft you may need to better =
clarify what is tunnel quality, to emphasis the difference between =
interface and tunnel interface
Scott Bradner - if you prepend seq # you change packet size you may have =
to fragment
Response - I used GRE sequence number (32 bits). Good, if you prepend =
sequence number you may get into segmentation situation.

chair -We'll continue to discuss this on the list, gauge interest and =
answer the questions. I forwarded this to IPPM and benchmarking WG.

Tries to sense the interest in the room: 4-5 hands. Is this not =
relevant? None


8. Open microphone =20

Margaret: The topics today were interesting. But interesting is not good =
enough. We have really bad history of trying to standardize management =
approaches that were not really needed by service providers. We much =
work only on what users really need.
Dan: We split the OPS session to two days. Today's is more the 'new'
issues. We need more feedback from operators. Work in the past lead to =
NETCONF etc.
Dave K.: We haven't allowed BOFs for the last few IETF being strict to =
ensure that ideas that are not really required will not go forward.
However we felt that we may miss some good ideas from going forward.
Bob: To answer Margaret. I wanted to stress in my presentation that =
there are operators and users that need the data models. What do you =
want that shows this need.
Margaret: I want them to be here and participate. If we don' t have =
multiple sources of input.
David Partain: I'd like to address Margaret point. There has been a lot =
of discussions on data modeling. This is a real problem, since everyone =
wants to use NETCOM but there is not any data models. Our users want =
NETCONF. I think this is fair to characterizing it as real need.
Margeret: Are you the customer of the data model
David: Me and my customer.
Ron B.: Maybe we should go to the operators and ask what are the most =
critical problems and start from that, i.e. solve this first. When he =
was a operator he would not have seen the issue as a lack of a data =
model - rather why does pager go off - should keep doing this kind of =
thing but should try to get closer to user=E2=80=99s actual perceived =
needs
Andy: I don't believe it is possible to have a protocol independent data =
model. We don't have the expertise in web verbs etc. You should do the =
work. I agree with Scott that we don't have a way to fill in the holes.
Dave H: Addressing Margaret point. I'm going to have a workgroup meeting =
to understand their needs. Are there any operators  in the rooms? ~ 5 =
hands. on Monday he proposed an ops nm WG to get operators involved - =
looking for volunteers to help ops area better understand operator =
needs, also - operations & managements guidelines doc - also ooking for =
volunteers for that
Bob: We might have minimum basic requirements for conversion of MIBs. =
But most MIBs should be map-able.
Dave K.: Is the experiment with the mini-BOF useful? Around 30 hands
Who thinks this is not useful? None
Dan: Regarding Dave H suggestion for two working groups, I suggest that =
we unite it into one working group.
Dave H: I think these are two different problems and should be done by =
two different contributor groups. Protocol designers and Operators.
Dan: I agree, but work generates feedback and input generates work. My =
concern that split of resources and that there will not be enough =
interest if we split it to two.
Dave K: From the operator part we don't want to be too lonely=85 The =
important thing is to have a good charter for the working group.
Ron B: New WG chair. Applause to Dave K. I work for Juniper. I was an =
operator in the VBNS network. Looking forward to work with you all.

_______________________________________________
MIB-DOCTORS mailing list
MIB-DOCTORS@ietf.org
https://www1.ietf.org/mailman/listinfo/mib-doctors



From mib-doctors-bounces@ietf.org Thu Apr 12 08:01:38 2007
Return-path: <mib-doctors-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hbxzd-0005vV-LT; Thu, 12 Apr 2007 08:01:38 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hbxza-0005qQ-Te; Thu, 12 Apr 2007 08:01:34 -0400
Received: from nj300815-nj-outbound.net.avaya.com ([198.152.12.100]
	helo=nj300815-nj-outbound.avaya.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HbxzZ-0002e8-N0; Thu, 12 Apr 2007 08:01:34 -0400
Received: from 51.105.64.135.in-addr.arpa (HELO IS0004AVEXU1.global.avaya.com)
	([135.64.105.51])
	by nj300815-nj-outbound.avaya.com with ESMTP; 12 Apr 2007 07:59:32 -0400
X-IronPort-AV: i="4.14,400,1170651600"; d="scan'208"; a="2705580:sNHT26971566"
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 12 Apr 2007 14:59:32 +0300
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F0CA56A74@is0004avexu1.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Operations and Management Area Open Hour Calls
Thread-Index: Acd8+gfH6aOrb3XeSmirednYz/Np7Q==
From: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>
To: <ops-area@ietf.org>, <ops-nm@ietf.org>, <ops-dir@ops.ietf.org>,
	<ops-chairs@ietf.org>, <mib-doctors@ietf.org>, <aaa-doctors@ietf.org>,
	"IETF MIBs" <ietfmibs@lists.ietf.org>, <nmrg@ibr.cs.tu-bs.de>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Cc: 
Subject: [MIB-DOCTORS] Operations and Management Area Open Hour Calls
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mib-doctors>,
	<mailto:mib-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mib-doctors>
List-Post: <mailto:mib-doctors@ietf.org>
List-Help: <mailto:mib-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mib-doctors>,
	<mailto:mib-doctors-request@ietf.org?subject=subscribe>
Errors-To: mib-doctors-bounces@ietf.org



Ron Bonica and Dan Romascanu are holding Open Hours to discuss issues
related to the IETF Operations and Management Area on the first and
third Tuesday of each month at noon-1PM PT / 3-4PM ET / 9-10PM CET.=20

All WG chairs, document editors, contributors, participants and in
general all interested to talk with us about the area and IETF business
are invited to ask for a meeting slot using the space below, and/or to
write us directly at rbonica@juniper.net or dromasca@avaya.com. An
e-mail will be sent in response to acknowledge the time slot and provide
a telephone bridge number to be used in the call.=20

The next OPS area open slots are:=20


* Tue 4/17

   PT                CET
   12-12:30pm        9-9:30pm =20
   12:30-1pm         9:30-10pm =20

Ron and Dan

_______________________________________________
MIB-DOCTORS mailing list
MIB-DOCTORS@ietf.org
https://www1.ietf.org/mailman/listinfo/mib-doctors



From mib-doctors-bounces@ietf.org Sat Apr 14 07:01:15 2007
Return-path: <mib-doctors-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hcg0J-0007kE-Rr; Sat, 14 Apr 2007 07:01:15 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hcg0H-0007jv-IA; Sat, 14 Apr 2007 07:01:13 -0400
Received: from nj300815-nj-outbound.net.avaya.com ([198.152.12.100]
	helo=nj300815-nj-outbound.avaya.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Hcg0G-0005as-4E; Sat, 14 Apr 2007 07:01:13 -0400
Received: from 51.105.64.135.in-addr.arpa (HELO IS0004AVEXU1.global.avaya.com)
	([135.64.105.51])
	by nj300815-nj-outbound.avaya.com with ESMTP; 14 Apr 2007 07:01:11 -0400
X-IronPort-AV: i="4.14,410,1170651600"; d="scan'208"; a="3555052:sNHT8998032"
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Sat, 14 Apr 2007 14:00:54 +0300
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F0CA56F76@is0004avexu1.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: UPDATED Agenda and Package for April 19, 2007 Telechat 
Thread-Index: Acd+Dru/+5xz8MzKRO28VbP1qZRp3wAdKqfA
From: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>
To: <ops-area@ietf.org>, <mib-doctors@ietf.org>,
	"IETF MIBs" <ietfmibs@lists.ietf.org>, <aaa-doctors@ietf.org>,
	"capwap" <capwap@frascone.com>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 187ae6c2eea74946c0ab707161f6256d
Cc: 
Subject: [MIB-DOCTORS] FW: UPDATED Agenda and Package for April 19,
	2007 Telechat 
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mib-doctors>,
	<mailto:mib-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mib-doctors>
List-Post: <mailto:mib-doctors@ietf.org>
List-Help: <mailto:mib-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mib-doctors>,
	<mailto:mib-doctors-request@ietf.org?subject=subscribe>
Errors-To: mib-doctors-bounces@ietf.org

Please find below the preliminary agenda of the 4/19 IESG telechat.
Please have a look at the documents proposed for approval and let me
know if there are any comments or concerns until 4/18 COB the latest.=20

Note that the agenda includes one MIB document proposed for standards
and three CAPWAP initial submission documents that are proposed to be
published as informational RFCs.=20

Thanks and Regards,

Dan
=20



=20

     =20
2. Protocol Actions
	Reviews should focus on these questions: "Is this document a
	reasonable basis on which to build the salient part of the
Internet
	infrastructure? If not, what changes would make it so?"


2.1 WG Submissions
2.1.1 New Item
  o draft-ietf-simple-presence-rules-09.txt
    Presence Authorization Rules (Proposed Standard) - 1 of 5=20
    Token: Jon Peterson
  o draft-ietf-ips-isns-mib-11.txt
    Definitions of Managed Objects for iSNS (Internet Storage Name
Service)=20
    (Proposed Standard) - 2 of 5=20
    Note: PROTO Shepherd: David Black (Black_David@emc.com). MIB Doctor:
Bert=20
    Wijnen (bwijnen@lucent.com). Initial expert review: Keith McCloghrie

    (kzm@cisco.com)=20
    Token: Lars Eggert
  o draft-ietf-rmt-fec-bb-revised-06.txt
    Forward Error Correction (FEC) Building Block (Proposed Standard) -
3
of 5=20
    Token: Magnus Westerlund
  o draft-ietf-16ng-ipv6-over-ipv6cs-09.txt
    IPv6 Over the IP Specific part of the Packet Convergence sublayer in
802.16=20
    Networks (Proposed Standard) - 4 of 5=20
    Note: NOTE: There are some LC and IEEE-review comments pending=20
    Token: Jari Arkko
  o draft-ietf-behave-tcp-06.txt
    NAT Behavioral Requirements for TCP (BCP) - 5 of 5=20
    Token: Magnus Westerlund

2.1.2 Returning Item
  o draft-ietf-pkix-lightweight-ocsp-profile-08.txt
    Lightweight OCSP Profile for High Volume Environments (Proposed
Standard) -=20
    1 of 1=20
    Token: Russ Housley


2.2 Individual Submissions
2.2.1 New Item
  o draft-siemborski-imap-sasl-initial-response-06.txt
    IMAP Extension for SASL Initial Client Response (Proposed Standard)
-
1 of=20
    1=20
    Token: Chris Newman

2.2.2 Returning Item
NONE

3. Document Actions

3.1 WG Submissions
	Reviews should focus on these questions: "Is this document a
reasonable
	contribution to the area of Internet engineering which it
covers? If
	not, what changes would make it so?"

3.1.1 New Item
  o draft-ietf-16ng-ipv6-link-model-analysis-03.txt
    Analysis of IPv6 Link Models for 802.16 based Networks
(Informational)
- 1=20
    of 2=20
    Note: PROTO Shepherd is Soohong Daniel Park=20
    &lt;soohong.park@samsung.com&gt;=20
    Token: Jari Arkko
  o draft-ietf-trill-routing-reqs-02.txt
    TRILL Routing Requirements in Support of RBridges (Informational) -
2
of 2=20
    Token: Mark Townsley

3.1.2 Returning Item
  o Five-document ballot:  - 1 of 1
     - draft-ietf-hip-base-07.txt
       Host Identity Protocol (Experimental)=20
     - draft-ietf-hip-esp-05.txt
       Using ESP transport format with HIP (Experimental)=20
     - draft-ietf-hip-registration-02.txt
       Host Identity Protocol (HIP) Registration Extension
(Experimental)

     - draft-ietf-hip-mm-05.txt
       End-Host Mobility and Multihoming with the Host Identity Protocol

       (Experimental)=20
     - draft-ietf-hip-rvs-05.txt
       Host Identity Protocol (HIP) Rendezvous Extension (Experimental)=20
    Token: Mark Townsley


3.2 Individual Submissions Via AD
	Reviews should focus on these questions: "Is this document a
reasonable
	contribution to the area of Internet engineering which it
covers? If
	not, what changes would make it so?"

3.2.1 New Item
  o draft-allen-sipping-poc-p-answer-state-header-05.txt
    The P-Answer-State Header Extension to the Session Initiation
Protocol
for=20
    the Open Mobile Alliance Push-to-talk over Cellular (Informational)
-
1 of=20
    1=20
    Note: SIPPING RFC 3427 Expert Reviewer is Gonzalo Camarillo;
dependency of=20
    OMA=20
    Token: Jon Peterson

3.2.2 Returning Item
NONE
3.3 Independent Submissions Via RFC Editor
	The IESG will use RFC 3932 responses: 1) The IESG has not
	found any conflict between this document and IETF work; 2) The
	IESG thinks that this work is related to IETF work done in WG
	<X>, but this does not prevent publishing; 3) The IESG thinks
	that publication is harmful to work in WG <X> and recommends
	not publishing at this time; 4) The IESG thinks that this
	document violates the IETF procedures for <X> and should
	therefore not be published without IETF review and IESG
	approval; 5) The IESG thinks that this document extends an
	IETF protocol in a way that requires IETF review and should
	therefore not be published without IETF review and IESG
approval.
=20

                   =20
	Other matters may be recorded in comments to be passed on
	to the RFC Editor as community review of the document.


3.3.1 New Item
  o draft-iino-capwap-wicop-02.txt
    Wireless LAN Control Protocol (WiCoP) (Informational) - 1 of 2=20
    Note: This document is an independent submission via the RFC Editor.
In=20
    conformace with RFC 3932, Section 4, the IESG requests the
publication
of=20
    the following note: "This RFC documents the WiCoP protocol as it was
when=20
    submitted to the IETF as a basis for further work in the CAPWAP WG,
and=20
    therefore it may resemble a current IETF work in progress or a
published=20
    IETF work. This RFC itself is not a candidate for any level of
Internet.=20
    Standard. The IETF disclaims any knowledge of the fitness of this
RFC
for=20
    any purpose, and in particular notes that it has not had complete
IETF
=20
    review for such things as security, congestion control, or
inappropriate=20
    interaction with deployed protocols. The RFC Editor has chosen to
publish=20
    this document at its discretion."=20
    Token: Dan Romascanu
  o draft-ohara-capwap-lwapp-04.txt
    Light Weight Access Point Protocol (Informational) - 2 of 2=20
    Note: This document is an independent submission via the RFC Editor.
In=20
    conformace with RFC 3932, Section 4, the IESG requests the
publication
of=20
    the following note: "This RFC documents the LWAPP protocol as it was
when=20
    submitted to the IETF as a basis for further work in the CAPWAP WG,
and=20
    therefore it may resemble a current IETF work in progress or a
published=20
    IETF work. This RFC itself is not a candidate for any level of
Internet=20
    Standard. The IETF disclaims any knowledge of the fitness of this
RFC
for=20
    any purpose, and in particular notes that it has not had complete
IETF
=20
    review for such things as security, congestion control, or
inappropriate=20
    interaction with deployed protocols. The RFC Editor has chosen to
publish=20
    this document at its discretion."=20
    Token: Dan Romascanu

3.3.2 Returning Item
  o draft-narasimhan-ietf-slapp-01.txt
    SLAPP : Secure Light Access Point Protocol (Informational) - 1 of 1=20
    Note: This document is an independent submission via the RFC Editor.
In=20
    conformace with RFC 3932, Section 4, the IESG requests the
publication
of=20
    the following note: "This RFC documents the SLAPP protocol as it was
when=20
    submitted to the IETF as a basis for further work in the CAPWAP WG,
and=20
    therefore it may resemble a current IETF work in progress or a
published=20
    IETF work. This RFC itself is not a candidate for any level of
Internet=20
    Standard. The IETF disclaims any knowledge of the fitness of this
RFC
for=20
    any purpose, and in particular notes that it has not had complete
IETF
=20
    review for such things as security, congestion control, or
inappropriate=20
    interaction with deployed protocols. The RFC Editor has chosen to
publish=20
    this document at its discretion.".=20
    Token: Dan Romascanu



_______________________________________________
MIB-DOCTORS mailing list
MIB-DOCTORS@ietf.org
https://www1.ietf.org/mailman/listinfo/mib-doctors



