From nobody Thu Apr 3 02:46:26 2014 Return-Path: X-Original-To: mib-doctors@ietfa.amsl.com Delivered-To: mib-doctors@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 05A961A0156 for ; Thu, 3 Apr 2014 02:46:24 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -9.51 X-Spam-Level: X-Spam-Status: No, score=-9.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZW055TiE4m3Z for ; Thu, 3 Apr 2014 02:46:19 -0700 (PDT) Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) by ietfa.amsl.com (Postfix) with ESMTP id 7F0221A014B for ; Thu, 3 Apr 2014 02:46:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=21518; q=dns/txt; s=iport; t=1396518372; x=1397727972; h=message-id:date:from:mime-version:to:subject:references: in-reply-to; bh=YkoUbmksVt4DF6Azw7pvGAXT089fM9wAMpsdJl5rdB0=; b=jstwunZKIFrDiDY/CtVjqnG/9JMjPb4Pl6UQN+g8KgO1bHOu6/da/7lT vDRO3bDru0UiOrrlR13QT12qaE8h79prkQSXkcaOS2KXN0GTk55ZfSVA0 ZCFgoVKBZjcx08vDB07AQpAYRZA0tsFzANgUNALKfIjQss6q5tWRqdfkl 0=; X-IronPort-AV: E=Sophos; i="4.97,786,1389744000"; d="scan'208,217"; a="12982839" Received: from aer-core-2.cisco.com ([173.38.203.7]) by aer-iport-2.cisco.com with ESMTP; 03 Apr 2014 09:46:11 +0000 Received: from [10.60.67.85] (ams-bclaise-8914.cisco.com [10.60.67.85]) by aer-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s339k7Vr021629; Thu, 3 Apr 2014 09:46:08 GMT Message-ID: <533D2DDF.6070408@cisco.com> Date: Thu, 03 Apr 2014 11:46:07 +0200 From: Benoit Claise User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: Dave Thaler , "Romascanu, Dan (Dan)" , "MIB Doctors (E-mail)" , "Alissa Cooper (alcoop)" , Martin Bjorklund References: <53353BB2.7000706@cisco.com> <53353BFB.7050906@cisco.com> <9904FB1B0159DA42B0B887B7FA8119CA2E46AB5B@AZ-FFEXMB04.global.avaya.com> <9fcaf2a8cc004642a5c9ba27474a10af@BY2PR03MB412.namprd03.prod.outlook.com> In-Reply-To: <9fcaf2a8cc004642a5c9ba27474a10af@BY2PR03MB412.namprd03.prod.outlook.com> Content-Type: multipart/alternative; boundary="------------050101080006060502080309" Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/k8RhEF8dpaU6sVPbMjB_RDb6tJw Subject: Re: [MIB-DOCTORS] Errata? : Re: Alissa Cooper's Discuss on draft-ietf-netmod-ip-cfg-13: (with DISCUSS) X-BeenThere: mib-doctors@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: MIB Doctors list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2014 09:46:24 -0000 This is a multi-part message in MIME format. --------------050101080006060502080309 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Thanks Dan and Dave. That makes sense to me. Regards, Benoit > > In this case it's not even an error. > > The reference is in an "e.g." so it's just mentioned by way of example. > > The fact that it was obsoleted by a later RFC does not make the > example incorrect or invalid. > > So I do not believe an errata is warranted. > > -Dave > > *From:*MIB-DOCTORS [mailto:mib-doctors-bounces@ietf.org] *On Behalf Of > *Romascanu, Dan (Dan) > *Sent:* Sunday, March 30, 2014 10:35 AM > *To:* Benoit Claise; MIB Doctors (E-mail) > *Subject:* Re: [MIB-DOCTORS] Errata? : Re: Alissa Cooper's Discuss on > draft-ietf-netmod-ip-cfg-13: (with DISCUSS) > > Hi, > > This raises a question that may be worth being discussed first. It is > not only a MIB doctors issue. RFC 4941 was published after RFC 4293. > So this erratum would not correct a technical or editorial error. Is > this the right thing to so -- 'this' meaning to issue an errata that > points to a reference that did not exist at the time the RFC was > published? > > Regards, > > Dan > > *From:*MIB-DOCTORS [mailto:mib-doctors-bounces@ietf.org] *On Behalf Of > *Benoit Claise > *Sent:* Friday, March 28, 2014 12:08 PM > *To:* MIB Doctors (E-mail) > *Subject:* [MIB-DOCTORS] Errata? : Re: Alissa Cooper's Discuss on > draft-ietf-netmod-ip-cfg-13: (with DISCUSS) > > MIB doctors, > > Anyone interested in filing an errata on RFC 4293? > > Regards, Benoit > > > > -------- Original Message -------- > > *Subject: * > > > > Re: Alissa Cooper's Discuss on draft-ietf-netmod-ip-cfg-13: (with DISCUSS) > > *Date: * > > > > Fri, 28 Mar 2014 10:06:58 +0100 > > *From: * > > > > Benoit Claise > > *To: * > > > > Alissa Cooper , Martin > Bjorklund > > *CC: * > > > > netmod-chairs@tools.ietf.org , > iesg@ietf.org , > draft-ietf-netmod-ip-cfg@tools.ietf.org > > > On 28/03/2014 00:59, Alissa Cooper wrote: > > I cleared my DISCUSS, thanks for agreeing to this change. One comment > > below, probably more for Benoit ... > > > > On 3/26/14 3:47 PM, "Martin Bjorklund" wrote: > > > >> Hi, > >> > >> "Alissa Cooper" wrote: > >>> ---------------------------------------------------------------------- > >>> DISCUSS: > >>> ---------------------------------------------------------------------- > >>> > >>> These type definition descriptions for ip-address-origin in Section 4 > >>> don't seem quite right: > >>> > >>> enum link-layer { > >>> description > >>> "Indicates an address created by IPv6 stateless > >>> auto-configuration."; > >>> } > >>> enum random { > >>> description > >>> "Indicates an address chosen by the system at > >>> random, e.g., an IPv4 address within 169.254/16, or an > >>> RFC 4941 privacy address."; > >>> } > >>> > >>> Randomized IIDs, whether static or generated according to RFC 4941, are > >>> used in statelessly auto-configured addresses (that is, those addresses > >>> are a subset of what is enumerated as "link-layer" above). > >> Ok. The text above is copied from^H^H aligned with the > >> IpAddressOriginTC from IP-MIB (RFC 4293). > > Might it be worth updating that document as well? RFC 4293 even still > > references RFC 3041 as the citation for temporary addresses, which has > > been obsoleted by RFC 4941. Would this be small enough to do in an errata? > I don't believe that updating a MIB textual convention as an errata > level type of update. > On the other hand, an editorial change waiting for an RFC update (if it > ever comes) doesn't do any harm. > Let me forward to the MIB doctors. > > Regards, Benoit > --------------050101080006060502080309 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
Thanks Dan and Dave.
That makes sense to me.

Regards, Benoit

In this case it’s not even an error.

 

The reference is in an “e.g.” so it’s just mentioned by way of example.

The fact that it was obsoleted by a later RFC does not make the example incorrect or invalid.

 

So I do not believe an errata is warranted.

 

-Dave

 

From: MIB-DOCTORS [mailto:mib-doctors-bounces@ietf.org] On Behalf Of Romascanu, Dan (Dan)
Sent: Sunday, March 30, 2014 10:35 AM
To: Benoit Claise; MIB Doctors (E-mail)
Subject: Re: [MIB-DOCTORS] Errata? : Re: Alissa Cooper's Discuss on draft-ietf-netmod-ip-cfg-13: (with DISCUSS)

 

Hi,

 

This raises a question that may be worth being discussed first. It is not only a MIB doctors issue. RFC 4941 was published after RFC 4293. So this erratum would not correct a technical or editorial error. Is this the right thing to so – ‘this’ meaning to issue an errata that points to a reference that did not exist at the time the RFC was published?

 

Regards,

 

Dan

 

 

From: MIB-DOCTORS [mailto:mib-doctors-bounces@ietf.org] On Behalf Of Benoit Claise
Sent: Friday, March 28, 2014 12:08 PM
To: MIB Doctors (E-mail)
Subject: [MIB-DOCTORS] Errata? : Re: Alissa Cooper's Discuss on draft-ietf-netmod-ip-cfg-13: (with DISCUSS)

 

MIB doctors,

Anyone interested in filing an errata on RFC 4293?

Regards, Benoit



-------- Original Message --------

Subject:

Re: Alissa Cooper's Discuss on draft-ietf-netmod-ip-cfg-13: (with DISCUSS)

Date:

Fri, 28 Mar 2014 10:06:58 +0100

From:

Benoit Claise <bclaise@cisco.com>

To:

Alissa Cooper <alissa@cooperw.in>, Martin Bjorklund <mbj@tail-f.com>

CC:

netmod-chairs@tools.ietf.org, iesg@ietf.org, draft-ietf-netmod-ip-cfg@tools.ietf.org

 

On 28/03/2014 00:59, Alissa Cooper wrote:
> I cleared my DISCUSS, thanks for agreeing to this change. One comment
> below, probably more for Benoit ...
> 
> On 3/26/14 3:47 PM, "Martin Bjorklund" <mbj@tail-f.com> wrote:
> 
>> Hi,
>> 
>> "Alissa Cooper" <alissa@cooperw.in> wrote:
>>> ----------------------------------------------------------------------
>>> DISCUSS:
>>> ----------------------------------------------------------------------
>>> 
>>> These type definition descriptions for ip-address-origin in Section 4
>>> don't seem quite right:
>>> 
>>>          enum link-layer {
>>>            description
>>>              "Indicates an address created by IPv6 stateless
>>>               auto-configuration.";
>>>          }
>>>          enum random {
>>>            description
>>>              "Indicates an address chosen by the system at
>>>               random, e.g., an IPv4 address within 169.254/16, or an
>>>               RFC 4941 privacy address.";
>>>          }
>>> 
>>> Randomized IIDs, whether static or generated according to RFC 4941, are
>>> used in statelessly auto-configured addresses (that is, those addresses
>>> are a subset of what is enumerated as "link-layer" above).
>> Ok.  The text above is copied from^H^H aligned with the
>> IpAddressOriginTC from IP-MIB (RFC 4293).
> Might it be worth updating that document as well? RFC 4293 even still
> references RFC 3041 as the citation for temporary addresses, which has
> been obsoleted by RFC 4941. Would this be small enough to do in an errata?
I don't believe that updating a MIB textual convention as an errata 
level type of update.
On the other hand, an editorial change waiting for an RFC update (if it 
ever comes) doesn't do any harm.
Let me forward to the MIB doctors.
 
Regards, Benoit

 

 


--------------050101080006060502080309-- From nobody Thu Apr 3 07:26:24 2014 Return-Path: X-Original-To: mib-doctors@ietfa.amsl.com Delivered-To: mib-doctors@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 59A661A01CE for ; Thu, 3 Apr 2014 07:21:20 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.911 X-Spam-Level: X-Spam-Status: No, score=-8.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_CHICKENPOX_61=0.6, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2SibCq5B9PLD for ; Thu, 3 Apr 2014 07:21:16 -0700 (PDT) Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) by ietfa.amsl.com (Postfix) with ESMTP id 787711A01D5 for ; Thu, 3 Apr 2014 07:21:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4947; q=dns/txt; s=iport; t=1396534872; x=1397744472; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=AdFKCsx2GJw9eID+FJwCfECAUzSD6n/YbPyO8FlYmiA=; b=K9OtJPKYHskNLMWzpM55n+VN5TN9cLMfa7BpEABC8khXDzGstOzX7G7r q7mVig0bnOoa3N5eu1Qauz6KdCH9aEHuRLSC0586RQcE6tMVNpaJwRfjv EUHI24Fg2oAfwzdxK+adrNZvqgsLQPHFrfk4kIDrdlis3F5of9pvFBjbB 4=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Am4UANNtPVOtJV2Z/2dsb2JhbABYgwaBErxGhzCBHxZ0giUBAQEEJ14EAgEIEQMBAQEkBAcyFAkIAgQBEod4Ac8eF44+OgaEMgEDmFuSPoFxgT+BaSQe X-IronPort-AV: E=Sophos;i="4.97,787,1389744000"; d="scan'208";a="32604019" Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by alln-iport-7.cisco.com with ESMTP; 03 Apr 2014 14:21:10 +0000 Received: from xhc-aln-x13.cisco.com (xhc-aln-x13.cisco.com [173.36.12.87]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s33ELABn016826 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 3 Apr 2014 14:21:10 GMT Received: from xmb-rcd-x09.cisco.com ([169.254.9.247]) by xhc-aln-x13.cisco.com ([173.36.12.87]) with mapi id 14.03.0123.003; Thu, 3 Apr 2014 09:21:09 -0500 From: "Alissa Cooper (alcoop)" To: "Benoit Claise (bclaise)" , Dave Thaler , "Romascanu, Dan (Dan)" , "MIB Doctors (E-mail)" , Martin Bjorklund Thread-Topic: [MIB-DOCTORS] Errata? : Re: Alissa Cooper's Discuss on draft-ietf-netmod-ip-cfg-13: (with DISCUSS) Thread-Index: AQHPTyGOOxEUDfYRekuYk18GNq0jJZr/0B+A Date: Thu, 3 Apr 2014 14:21:08 +0000 Message-ID: References: <53353BB2.7000706@cisco.com> <53353BFB.7050906@cisco.com> <9904FB1B0159DA42B0B887B7FA8119CA2E46AB5B@AZ-FFEXMB04.global.avaya.com> <9fcaf2a8cc004642a5c9ba27474a10af@BY2PR03MB412.namprd03.prod.outlook.com> <533D2DDF.6070408@cisco.com> In-Reply-To: <533D2DDF.6070408@cisco.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [171.68.18.132] Content-Type: text/plain; charset="Windows-1252" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/b7XtHKsbCtU8O6rYibrDhBkmJ-Q X-Mailman-Approved-At: Thu, 03 Apr 2014 07:26:20 -0700 Subject: Re: [MIB-DOCTORS] Errata? : Re: Alissa Cooper's Discuss on draft-ietf-netmod-ip-cfg-13: (with DISCUSS) X-BeenThere: mib-doctors@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: MIB Doctors list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2014 14:21:20 -0000 Putting aside the reference issue, do you all think the characterization of the address classes is correct? IpAddressOriginTC ::=3D TEXTUAL-CONVENTION STATUS current DESCRIPTION "The origin of the address. manual(2) indicates that the address was manually configured to a specified address, e.g., by user configuration. dhcp(4) indicates an address that was assigned to this system by a DHCP server. linklayer(5) indicates an address created by IPv6 stateless auto-configuration. random(6) indicates an address chosen by the system at random, e.g., an IPv4 address within 169.254/16, or an RFC 3041 privacy address." Why is "linklayer" the right label for any address generated by SLAAC? Why are RFC 3041 addresses not considered SLAAC addresses? Thanks, Alissa On 4/3/14 2:46 AM, "Benoit Claise (bclaise)" wrote: >Thanks Dan and Dave. >That makes sense to me. > >Regards, Benoit > > >In this case it=B9s not even an error. >=20 >The reference is in an =B3e.g.=B2 so it=B9s just mentioned by way of examp= le. >The fact that it was obsoleted by a later RFC does not make the example >incorrect or invalid. >=20 >So I do not believe an errata is warranted. >=20 >-Dave >=20 >From: MIB-DOCTORS [mailto:mib-doctors-bounces@ietf.org] >On Behalf Of Romascanu, Dan (Dan) >Sent: Sunday, March 30, 2014 10:35 AM >To: Benoit Claise; MIB Doctors (E-mail) >Subject: Re: [MIB-DOCTORS] Errata? : Re: Alissa Cooper's Discuss on >draft-ietf-netmod-ip-cfg-13: (with DISCUSS) > > >=20 >Hi, >=20 >This raises a question that may be worth being discussed first. It is not >only a MIB doctors issue. RFC 4941 was published after RFC 4293. So this >erratum would > not correct a technical or editorial error. Is this the right thing to >so =AD =8Cthis=B9 meaning to issue an errata that points to a reference th= at >did not exist at the time the RFC was published? > >=20 >Regards, >=20 >Dan >=20 >=20 >From: MIB-DOCTORS [mailto:mib-doctors-bounces@ietf.org] >On Behalf Of Benoit Claise >Sent: Friday, March 28, 2014 12:08 PM >To: MIB Doctors (E-mail) >Subject: [MIB-DOCTORS] Errata? : Re: Alissa Cooper's Discuss on >draft-ietf-netmod-ip-cfg-13: (with DISCUSS) > > >=20 >MIB doctors, > >Anyone interested in filing an errata on RFC 4293? > >Regards, Benoit > > >-------- Original Message -------- >Subject:=20 >Re: Alissa Cooper's Discuss on draft-ietf-netmod-ip-cfg-13: (with DISCUSS) >Date:=20 >Fri, 28 Mar 2014 10:06:58 +0100 >From:=20 >Benoit Claise=20 > >To:=20 >Alissa Cooper=20 > , Martin Bjorklund > >CC:=20 >netmod-chairs@tools.ietf.org, >iesg@ietf.org,=20 >draft-ietf-netmod-ip-cfg@tools.ietf.org > >=20 >On 28/03/2014 00:59, Alissa Cooper wrote:> I cleared my DISCUSS, thanks >for agreeing to this change. One comment> below, probably more for Benoit >...> > On 3/26/14 3:47 PM, "Martin Bjorklund" > wrote:> >> Hi,>> >> "Alissa Cooper" > wrote:>>> >---------------------------------------------------------------------->>> >DISCUSS:>>>=20 >---------------------------------------------------------------------->>> >>>> These type definition descriptions for ip-address-origin in Section >>>>4>>> don't seem quite right:>>> >>> enum link-layer {>>> >>>> description>>> "Indicates an address created by >>>>IPv6 stateless>>> auto-configuration.";>>> }>>> >>>> enum random {>>> description>>> >>>>"Indicates an address chosen by the system at>>> random, >>>>e.g., an IPv4 address within 169.254/16, or an>>> RFC >>>>4941 privacy address.";>>> }>>> >>> Randomized IIDs, whether >>>>static or generated according to RFC 4941, are>>> used in statelessly >>>>auto-configured addresses (that is, those addresses>>> are a subset of >>>>what is enumerated as "link-layer" above).>> Ok. The text above is >>>>copied from^H^H aligned with the>> IpAddressOriginTC from IP-MIB (RFC >>>>4293).> Might it be worth updating that document as well? RFC 4293 >>>>even still> references RFC 3041 as the citation for temporary >>>>addresses, which has> been obsoleted by RFC 4941. Would this be small >>>>enough to do in an errata?I don't believe that updating a MIB textual >>>>convention as an errata level type of update.On the other hand, an >>>>editorial change waiting for an RFC update (if it ever comes) doesn't >>>>do any harm.Let me forward to the MIB doctors. Regards, Benoit > >=20 > > > > > From nobody Fri Apr 4 15:43:49 2014 Return-Path: X-Original-To: mib-doctors@ietfa.amsl.com Delivered-To: mib-doctors@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A5E6D1A01F0 for ; Fri, 4 Apr 2014 15:43:45 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.978 X-Spam-Level: X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=unavailable Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UQIkF65IQWuc for ; Fri, 4 Apr 2014 15:43:40 -0700 (PDT) Received: from mail-qa0-f48.google.com (mail-qa0-f48.google.com [209.85.216.48]) by ietfa.amsl.com (Postfix) with ESMTP id B45D71A01C8 for ; Fri, 4 Apr 2014 15:43:40 -0700 (PDT) Received: by mail-qa0-f48.google.com with SMTP id m5so3701360qaj.21 for ; Fri, 04 Apr 2014 15:43:35 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=DrarkwHYBUjurfEIkHwihpKseNWoiMHW+7h3w3YikIM=; b=ATdC5lW7gqi/0gFC8Zbqrqenc7n2/BDFgqBdsJBphIk1ryIuy6Vq68GiamYuG6HNcD S6z0s57VylxH7PsH87aq40G3PlEbJ0tHLdY/8GFtW4o2Kqynac6Vkvta2Sl0E8mi9eHj 9vrL+Sv2q/6IPPj/uTxjKzGsXpgqRog206kijhBDwyEJFYSCNv82lTTfG34/41EngKep E23u5m+FNImS2CZsHxjxlJNRknDWdxccSDR6n8621gEYgI4HrTQCrQ19Lgx/beDM2sHL x1dFmCrDTHpWIjqghG3n+LWhOtR2/jkRCYzaGqs0WDKsJmjwcX1EU3qCRyeZzBUbnodg uDZA== X-Gm-Message-State: ALoCoQmB9B5ia3qXhizhLsAM4aA0vFufBjqpRDtcAr4aSqwZXGitLC7Qek8TRrIjqSUeJiM629Ka MIME-Version: 1.0 X-Received: by 10.140.104.103 with SMTP id z94mr11997234qge.91.1396651415813; Fri, 04 Apr 2014 15:43:35 -0700 (PDT) Received: by 10.140.41.134 with HTTP; Fri, 4 Apr 2014 15:43:35 -0700 (PDT) Date: Fri, 4 Apr 2014 15:43:35 -0700 Message-ID: From: Andy Bierman To: YANG Doctors , "MIB Doctors (E-mail)" Content-Type: multipart/alternative; boundary=001a1134f2be83d1d704f63f3fb3 Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/df9ARB6sGuK0ksAC2s_rpb34xWs Subject: [MIB-DOCTORS] YANG life-cycle issues - lessons from SNMP? X-BeenThere: mib-doctors@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: MIB Doctors list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Apr 2014 22:43:45 -0000 --001a1134f2be83d1d704f63f3fb3 Content-Type: text/plain; charset=ISO-8859-1 Hi, I am trying to think about NETCONF update procedures. IMO SNMP mechanisms seem to have worked well over the years. The module update rules have not been a heavy burden like they are becoming for NETCONF/YANG. Is that just because of configuration vs. monitoring? A client can easily ignore all new monitoring data but it cannot easily ignore new input parameters. Does SMIv2 allow a mandatory column to be added to a table in a module update? It appears yes. It would just be a change to the RowStatus description clause, e.g., "column A, B, and E must be present in order for this row to be in the active state". But SNMP Set is not really deployed so maybe that is why addition of mandatory columns is not visible as a problem. Andy --001a1134f2be83d1d704f63f3fb3 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi,

I am trying to think about NETCONF = update procedures.
IMO SNMP mechanisms seem to have worked well
over the years. =A0The module update rules have not
been= a heavy burden like they are becoming for NETCONF/YANG.

Is that just because of configuration vs. monitoring?
A client can easily ignore all new monitoring data but
i= t cannot easily ignore new input parameters.

Does = SMIv2 allow a mandatory column to be added
to a table in a module update? It appears yes.
It would just= be a change to the RowStatus description
clause, e.g., "col= umn A, B, and E must be present in order
for this row to be in th= e active state".

But SNMP Set is not really deployed so maybe that is wh= y
addition of mandatory columns is not visible as a problem.


Andy

--001a1134f2be83d1d704f63f3fb3-- From nobody Fri Apr 4 16:09:22 2014 Return-Path: X-Original-To: mib-doctors@ietfa.amsl.com Delivered-To: mib-doctors@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8EB1E1A029B; Fri, 4 Apr 2014 16:09:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.6 X-Spam-Level: X-Spam-Status: No, score=-0.6 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MCdWXt2_xMa6; Fri, 4 Apr 2014 16:09:09 -0700 (PDT) Received: from elasmtp-masked.atl.sa.earthlink.net (elasmtp-masked.atl.sa.earthlink.net [209.86.89.68]) by ietfa.amsl.com (Postfix) with ESMTP id 9D12A1A02EA; Fri, 4 Apr 2014 16:09:05 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=VXjA1qIRI2IorCsVPRjyYEOmOf/hmE5Vk3zt6GyKa6RsXYSHpNdVoZu3TOo/xJ5N; h=Message-ID:Date:From:Reply-To:To:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding:X-Mailer:X-ELNK-Trace:X-Originating-IP; Received: from [209.86.224.50] (helo=mswamui-swiss.atl.sa.earthlink.net) by elasmtp-masked.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from ) id 1WWDEI-0007bk-M4; Fri, 04 Apr 2014 19:08:58 -0400 Received: from 99.23.163.18 by webmail.earthlink.net with HTTP; Fri, 4 Apr 2014 19:08:58 -0400 Message-ID: <24653790.1396652938704.JavaMail.root@mswamui-swiss.atl.sa.earthlink.net> Date: Fri, 4 Apr 2014 16:08:58 -0700 (GMT-07:00) From: Randy Presuhn To: YANG Doctors , "MIB Doctors (E-mail)" Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Mailer: EarthLink Zoo Mail 1.0 X-ELNK-Trace: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d88891b749bef7332bbca3946af56bf69f523ac7963751da33aa350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 209.86.224.50 Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/hEZ7oat2E3ed8Ek8mDI4WhVu68E Subject: Re: [MIB-DOCTORS] YANG life-cycle issues - lessons from SNMP? X-BeenThere: mib-doctors@ietf.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: Randy Presuhn List-Id: MIB Doctors list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Apr 2014 23:09:16 -0000 Hi - >From: Andy Bierman >Sent: Apr 4, 2014 3:43 PM >To: YANG Doctors , "MIB Doctors (E-mail)" >Subject: [MIB-DOCTORS] YANG life-cycle issues - lessons from SNMP? ... >Is that just because of configuration vs. monitoring? I don't think that's it. I think it has more to do with the (lack of an) underlying metamodel, rules for type extensibility and a not completely-thought- through approach to defining the limits of how inter- version compatibility is supposed to work. ... >Does SMIv2 allow a mandatory column to be added >to a table in a module update? It appears yes. >It would just be a change to the RowStatus description >clause, e.g., "column A, B, and E must be present in order >for this row to be in the active state". Disagree. Such a change to the semantics of a Rowstatus object would violate the SMI revision rule that "Otherwise, if the semantics of any previously defined object are changed (i.e., if a non-editorial change is made to any clause other than those specifically allowed above), then the OBJECT IDENTIFIER value associated with that object must also be changed." Randy From nobody Fri Apr 4 16:27:03 2014 Return-Path: X-Original-To: mib-doctors@ietfa.amsl.com Delivered-To: mib-doctors@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 495021A0280 for ; Fri, 4 Apr 2014 16:27:00 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.978 X-Spam-Level: X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=unavailable Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wbHbn5KXYwcM for ; Fri, 4 Apr 2014 16:26:56 -0700 (PDT) Received: from mail-qa0-f43.google.com (mail-qa0-f43.google.com [209.85.216.43]) by ietfa.amsl.com (Postfix) with ESMTP id CB0961A025A for ; Fri, 4 Apr 2014 16:26:55 -0700 (PDT) Received: by mail-qa0-f43.google.com with SMTP id j15so3836617qaq.30 for ; Fri, 04 Apr 2014 16:26:51 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=y748nIPZt502jsh5X2sOFikDFuPKATxHNAER26mW2Ro=; b=CYrcPxOEJ4DL7taACKd6uwjCsWwYhrOCcOpjtfKQZYAhRpP72xtiAqLLr6quExsFwk NTNUOC1rJhEuWTY+/NtQaXabmRX3bAeoyHFgHg9hO6q2yCp+dQuUfU6YPCogq2VVuTnY yTjujwObpdfcT8p58mhCd14xKLPTovvT5aXWSG5qv+DblJRRj7jKhYEGfKVemT8k7Mv0 jgxzmHC9oUfiCeKJyOp+DLS8rsSbXm7HP13tNPDkbOQbUAWluOKyBW0N3U87EihoZpOs TTmUhzTzV0sr3Ch8D7sHUMPOphQZNREHm/Z9jTBP0hF3eNa7VraZ1z0w4YZ9j6MHcLNL PPuw== X-Gm-Message-State: ALoCoQn5e3xIf0D80a6pyivsPDMd6198rv6STqDBiLW2yWV1koitTsUjkecWFaeoq7Xa0p1HP+8T MIME-Version: 1.0 X-Received: by 10.224.69.193 with SMTP id a1mr5642138qaj.95.1396654010875; Fri, 04 Apr 2014 16:26:50 -0700 (PDT) Received: by 10.140.41.134 with HTTP; Fri, 4 Apr 2014 16:26:50 -0700 (PDT) In-Reply-To: <24653790.1396652938704.JavaMail.root@mswamui-swiss.atl.sa.earthlink.net> References: <24653790.1396652938704.JavaMail.root@mswamui-swiss.atl.sa.earthlink.net> Date: Fri, 4 Apr 2014 16:26:50 -0700 Message-ID: From: Andy Bierman To: Randy Presuhn Content-Type: multipart/alternative; boundary=001a11c2b26431530204f63fda1c Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/-bvsvUYbo05O6jifb9YLkVBAtM4 Cc: YANG Doctors , "MIB Doctors \(E-mail\)" Subject: Re: [MIB-DOCTORS] YANG life-cycle issues - lessons from SNMP? X-BeenThere: mib-doctors@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: MIB Doctors list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Apr 2014 23:27:00 -0000 --001a11c2b26431530204f63fda1c Content-Type: text/plain; charset=ISO-8859-1 On Fri, Apr 4, 2014 at 4:08 PM, Randy Presuhn wrote: > Hi - > > >From: Andy Bierman > >Sent: Apr 4, 2014 3:43 PM > >To: YANG Doctors , "MIB Doctors (E-mail)" < > mib-doctors@ietf.org> > >Subject: [MIB-DOCTORS] YANG life-cycle issues - lessons from SNMP? > ... > >Is that just because of configuration vs. monitoring? > > I don't think that's it. I think it has more to do > with the (lack of an) underlying metamodel, rules > for type extensibility and a not completely-thought- > through approach to defining the limits of how inter- > version compatibility is supposed to work. > > How many mandatory objects are there in SNMP? none? How hard is it for a client to receive some monitoring info it doesn't know or care about? Monitoring is really easy compared to configuration. I agree NETCONF's framework is still evolving (to be kind). We have never had any meaningful standard CM data models, let alone updates to them 3 - 5 years later. > ... > >Does SMIv2 allow a mandatory column to be added > >to a table in a module update? It appears yes. > >It would just be a change to the RowStatus description > >clause, e.g., "column A, B, and E must be present in order > >for this row to be in the active state". > > Disagree. Such a change to the semantics of a Rowstatus > object would violate the SMI revision rule that "Otherwise, > if the semantics of any previously defined object are > changed (i.e., if a non-editorial change is made to any > clause other than those specifically allowed above), then > the OBJECT IDENTIFIER value associated with that object > must also be changed." > > OK -- just checking. I implemented a lot of MIB modules, some (RMON suite) with Set support. There was never any update to a read-create table that I can remember. I am not convinced that the strict rules for YANG are so smart. Looks to be trading 1 set of problems for a different set (e.g., obsolete and start over is intrusive and expensive) > Randy > > Andy --001a11c2b26431530204f63fda1c Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable



On Fri, Apr 4, 2014 at 4:08 PM, Randy Presuhn <= ;randy_pr= esuhn@mindspring.com> wrote:
Hi -

>From: Andy Bierman <andy@yumaw= orks.com>
>Sent: Apr 4, 2014 3:43 PM
>To: YANG Doctors <yang-doct= ors@ietf.org>, "MIB Doctors (E-mail)" <mib-doctors@ietf.org>
>Subject: [MIB-DOCTORS] YANG life-cycle issues - lessons from SNMP?
...
>Is that just because of configuration vs. monitoring?

I don't think that's it. =A0I think it has more to do
with the (lack of an) underlying metamodel, rules
for type extensibility and a not completely-thought-
through approach to defining the limits of how inter-
version compatibility is supposed to work.



How many mandatory obje= cts are there in SNMP? none?
How hard is it for a client to recei= ve some monitoring info
it doesn't know or care about? =A0Mon= itoring is really easy
compared to configuration.

I agree NETCONF= 9;s framework is still evolving (to be kind).
We have never had a= ny meaningful standard CM data models,
let alone updates to them = 3 - 5 years later.

=A0
...
>Does SMIv2 allow a mandatory column to be added
>to a table in a module update? It appears yes.
>It would just be a change to the RowStatus description
>clause, e.g., "column A, B, and E must be present in order
>for this row to be in the active state".

Disagree. =A0Such a change to the semantics of a Rowstatus
object would violate the SMI revision rule that "Otherwise,
if the semantics of any previously defined object are
changed (i.e., if a non-editorial change is made to any
clause other than those specifically allowed above), then
the OBJECT IDENTIFIER value associated with that object
must also be changed."


OK -- just checking. =A0I implemented = a lot of MIB modules,
some (RMON suite) with Set support. =A0Ther= e was never
any update to a read-create table that I can remember= .

I am not convinced that the strict rules for YANG are s= o smart.
Looks to be trading 1 set of problems for a different se= t
(e.g., obsolete and start over is intrusive and expensive)

=A0
Randy


Andy

<= /div> --001a11c2b26431530204f63fda1c-- From nobody Fri Apr 4 23:00:39 2014 Return-Path: X-Original-To: mib-doctors@ietfa.amsl.com Delivered-To: mib-doctors@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E5AFC1A02FB; Fri, 4 Apr 2014 23:00:37 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2 X-Spam-Level: X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TZaVZKe16z-i; Fri, 4 Apr 2014 23:00:33 -0700 (PDT) Received: from elasmtp-mealy.atl.sa.earthlink.net (elasmtp-mealy.atl.sa.earthlink.net [209.86.89.69]) by ietfa.amsl.com (Postfix) with ESMTP id AF6F11A00B0; Fri, 4 Apr 2014 23:00:33 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=PrT3uPrvoxB/kMTM3XvPQHx5Mpsl2nPw0rCgUbRYSYXz3BBJxWotCRfmFP/HHmG9; h=Message-ID:Date:From:Reply-To:To:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding:X-Mailer:X-ELNK-Trace:X-Originating-IP; Received: from [209.86.224.24] (helo=mswamui-andean.atl.sa.earthlink.net) by elasmtp-mealy.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from ) id 1WWJeV-0000kw-TW; Sat, 05 Apr 2014 02:00:27 -0400 Received: from 99.187.239.249 by webmail.earthlink.net with HTTP; Sat, 5 Apr 2014 02:00:27 -0400 Message-ID: <15834853.1396677627902.JavaMail.root@mswamui-andean.atl.sa.earthlink.net> Date: Fri, 4 Apr 2014 23:00:27 -0700 (GMT-07:00) From: Randy Presuhn To: YANG Doctors , "MIB Doctors (E-mail)" Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Mailer: EarthLink Zoo Mail 1.0 X-ELNK-Trace: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d88891b749bef7332bbcc8adff836fdbf308bec89e4b6ab0d27e350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 209.86.224.24 Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/zRfO-FhTScJnMP-VRsNu31Z6Y48 Subject: Re: [MIB-DOCTORS] YANG life-cycle issues - lessons from SNMP? X-BeenThere: mib-doctors@ietf.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: Randy Presuhn List-Id: MIB Doctors list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Apr 2014 06:00:38 -0000 Hi - >From: Andy Bierman >Sent: Apr 4, 2014 4:26 PM >To: Randy Presuhn >Cc: YANG Doctors , "MIB Doctors (E-mail)" >Subject: Re: [MIB-DOCTORS] YANG life-cycle issues - lessons from SNMP? ... >How many mandatory objects are there in SNMP? none? Look at the RowStatus for a table, and it will tell you exactly what the mandatory objects are. >How hard is it for a client to receive some monitoring info >it doesn't know or care about? Monitoring is really easy >compared to configuration. I think there's a pitfall to relying overmuch on this kind of analogy. Yes, a monitor will will skip over information it doesn't understand, but any semi-intelligent monitor won't bother asking for stuff it knows it won't understand. The fact that monitors have to spend so much energy coping with extraneous stuff is just an artifact of SNMP's bizarre GetNext and GetBulk operators. So what do I think one should do with unintelligible configuration information? One can live dangerously and ignore it, or behave more prudently and complain. I'd argue that an attempt to configure a system with unsupported configuration data is prima facie evidence that the configuration is in error, and only potentially makes sense when provisioning components whose software has not yet been delivered. Randy From nobody Sat Apr 5 08:17:11 2014 Return-Path: X-Original-To: mib-doctors@ietfa.amsl.com Delivered-To: mib-doctors@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 519731A01C4 for ; Sat, 5 Apr 2014 08:17:09 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.278 X-Spam-Level: X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EQALcXoMZeVk for ; Sat, 5 Apr 2014 08:17:05 -0700 (PDT) Received: from mail-qg0-f43.google.com (mail-qg0-f43.google.com [209.85.192.43]) by ietfa.amsl.com (Postfix) with ESMTP id 601431A01BC for ; Sat, 5 Apr 2014 08:17:05 -0700 (PDT) Received: by mail-qg0-f43.google.com with SMTP id f51so4536715qge.2 for ; Sat, 05 Apr 2014 08:17:00 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=svnaRJkdTadGWGYLhS+J7PnS+GQWZhBLDmJhHD+yG/Y=; b=kJNN5EFg1hE5mdS2f1ePXlJfOy79clP+eMv7wopcXeduLwyoHh7TKlb+CI0wZniuHr Kg2kAKfPtrKOnXta/b1oPOvEuPXbpf0ngAHnVKtS4Bn3TAbQRP/M7/NWOwcMUkZFl6HZ pCp2W2TRESrMqCpF+FvWz/svdKfJAyL4ZHUSZms9A2w7Z61UbKpM6rThKEe6E7vWjQw7 mZafbXac8qxC4B2H/EH56kAtRBddTXVtnliswqtwzejEFrHU/PSuEx97xHac3AwX8Ysq hgKo+vO2r/e67hD4EOM4D5R0fhkXEU9C3aclgEzWd4hO8T0u+I8r6d/4NLnKoedbB1W/ RSvw== X-Gm-Message-State: ALoCoQnjYedyRXK0mQcv9YjNViK/P766ZTG6p2iKfG0DkzvUno6vULKrKpjzihuv9fkPksQl8xBL MIME-Version: 1.0 X-Received: by 10.140.27.193 with SMTP id 59mr20521050qgx.18.1396711020216; Sat, 05 Apr 2014 08:17:00 -0700 (PDT) Received: by 10.140.41.134 with HTTP; Sat, 5 Apr 2014 08:17:00 -0700 (PDT) In-Reply-To: <15834853.1396677627902.JavaMail.root@mswamui-andean.atl.sa.earthlink.net> References: <15834853.1396677627902.JavaMail.root@mswamui-andean.atl.sa.earthlink.net> Date: Sat, 5 Apr 2014 08:17:00 -0700 Message-ID: From: Andy Bierman To: Randy Presuhn Content-Type: multipart/alternative; boundary=001a11c1233a36d66904f64d208d Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/qnPpuULNjinshyYmCMs-i5NImcI Cc: YANG Doctors , "MIB Doctors \(E-mail\)" Subject: Re: [MIB-DOCTORS] YANG life-cycle issues - lessons from SNMP? X-BeenThere: mib-doctors@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: MIB Doctors list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Apr 2014 15:17:09 -0000 --001a11c1233a36d66904f64d208d Content-Type: text/plain; charset=ISO-8859-1 On Fri, Apr 4, 2014 at 11:00 PM, Randy Presuhn wrote: > Hi - > > >From: Andy Bierman > >Sent: Apr 4, 2014 4:26 PM > >To: Randy Presuhn > >Cc: YANG Doctors , "MIB Doctors (E-mail)" < > mib-doctors@ietf.org> > >Subject: Re: [MIB-DOCTORS] YANG life-cycle issues - lessons from SNMP? > ... > >How many mandatory objects are there in SNMP? none? > > Look at the RowStatus for a table, and it will tell you exactly > what the mandatory objects are. > > >How hard is it for a client to receive some monitoring info > >it doesn't know or care about? Monitoring is really easy > >compared to configuration. > > I think there's a pitfall to relying overmuch on this > kind of analogy. Yes, a monitor will will skip over > information it doesn't understand, but any semi-intelligent > monitor won't bother asking for stuff it knows it won't > understand. The fact that monitors have to spend so > much energy coping with extraneous stuff is just an > artifact of SNMP's bizarre GetNext and GetBulk operators. > > So what do I think one should do with unintelligible > configuration information? One can live dangerously > and ignore it, or behave more prudently and complain. > > I'd argue that an attempt to configure a system with > unsupported configuration data is prima facie evidence > that the configuration is in error, and only potentially > makes sense when provisioning components whose software > has not yet been delivered. > > In theory old managers can keep doing their 'old' work and new managers support the new functionality. Since configuration has been done via ad-hoc CLI for so many years, it is hard to say how closely these rules have been followed, or how much they matter. Randy > > Andy --001a11c1233a36d66904f64d208d Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable



On Fri, Apr 4, 2014 at 11:00 PM, Randy Presuhn &l= t;randy_p= resuhn@mindspring.com> wrote:
Hi -

>From: Andy Bierman <andy@yumaw= orks.com>
>Sent: Apr 4, 2014 4:26 PM
>To: Randy Presuhn <r= andy_presuhn@mindspring.com>
>Cc: YANG Doctors <yang-doct= ors@ietf.org>, "MIB Doctors (E-mail)" <mib-doctors@ietf.org>
>Subject: Re: [MIB-DOCTORS] YANG life-cycle issues - lessons from SNMP?<= br> ...
>How many mandatory objects are there in SNMP? none?

Look at the RowStatus for a table, and it will tell you exactly
what the mandatory objects are.

>How hard is it for a client to receive some monitoring info
>it doesn't know or care about? =A0Monitoring is really easy
>compared to configuration.

I think there's a pitfall to relying overmuch on this
kind of analogy. =A0Yes, a monitor will will skip over
information it doesn't understand, but any semi-intelligent
monitor won't bother asking for stuff it knows it won't
understand. =A0The fact that monitors have to spend so
much energy coping with extraneous stuff is just an
artifact of SNMP's bizarre GetNext and GetBulk operators.

So what do I think one should do with unintelligible
configuration information? =A0One can live dangerously
and ignore it, or behave more prudently and complain.

I'd argue that an attempt to configure a system with
unsupported configuration data is prima facie evidence
that the configuration is in error, and only potentially
makes sense when provisioning components whose software
has not yet been delivered.



In theory old managers = can keep doing their 'old' work
and new managers support = the new functionality.
Since configuration has been done via ad-h= oc CLI for
so many years, it is hard to say how closely these rules
hav= e been followed, or how much they matter.


Randy


Andy

<= /div> --001a11c1233a36d66904f64d208d-- From nobody Fri Apr 18 02:42:02 2014 Return-Path: X-Original-To: mib-doctors@ietfa.amsl.com Delivered-To: mib-doctors@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 542231A02F9 for ; Fri, 18 Apr 2014 02:42:01 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -9.773 X-Spam-Level: X-Spam-Status: No, score=-9.773 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xOlY1J3HmtC7 for ; Fri, 18 Apr 2014 02:41:57 -0700 (PDT) Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) by ietfa.amsl.com (Postfix) with ESMTP id EC93F1A02E8 for ; Fri, 18 Apr 2014 02:41:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=435; q=dns/txt; s=iport; t=1397814113; x=1399023713; h=message-id:date:from:mime-version:to:cc:subject: content-transfer-encoding; bh=Pi4uqMWuJKIBa6L96/cFivzojjQr/FcWDfNNgPlLRro=; b=eDADHqDqh6zMPe2OsKJSERJaGqmEXI7M5OpD2lIjDJTse2JTcHm3KJx3 AWBfkt+7mnH4UB9u0u0WJM2SNq9TduyxKPWPDmXqBq/YUd2PDXJmDKNvv CpDDSdOq7o/cIcXrNg4Tyz2mJAKYPpVbTxkw6W9exmFyOfEysd2dufLU0 w=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: As8HAEzyUFOtJssW/2dsb2JhbABag0GOAa8ShycKgTV0gmRBKRM0AkwNAQcBAQWHcw3MOxeOEQEBT4Q/AQOYboE3hSGLd4MzO4E1 X-IronPort-AV: E=Sophos;i="4.97,883,1389744000"; d="scan'208";a="14894341" Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP; 18 Apr 2014 09:41:52 +0000 Received: from [10.60.67.86] (ams-bclaise-8915.cisco.com [10.60.67.86]) by aer-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s3I9fqBd011721; Fri, 18 Apr 2014 09:41:52 GMT Message-ID: <5350F360.30800@cisco.com> Date: Fri, 18 Apr 2014 11:41:52 +0200 From: Benoit Claise User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: Chris Elliott Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/O69oCFsdOebPrBTAx87RGQeqjsg Cc: "MIB Doctors \(E-mail\)" , "Black, David" Subject: [MIB-DOCTORS] MIB doctor review: draft-ietf-bfd-tc-mib-05 and draft-ietf-bfd-mib-17 X-BeenThere: mib-doctors@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: MIB Doctors list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Apr 2014 09:42:01 -0000 Hi Chris, Trying to round-robin MIB reviews (http://trac.tools.ietf.org/area/ops/trac/wiki/mib-doctors-review-history), would you be available to review draft-ietf-bfd-tc-mib-05 and draft-ietf-bfd-mib-17? Note that David Black already provided some useful feedback part of his GEN-ART review, and that generated some good discussion. See http://www.ietf.org/mail-archive/web/ietf/current/msg87489.html Regards, Benoit From nobody Fri Apr 18 06:48:17 2014 Return-Path: X-Original-To: mib-doctors@ietfa.amsl.com Delivered-To: mib-doctors@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A1AB01A01F6; Fri, 18 Apr 2014 06:48:10 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -9.773 X-Spam-Level: X-Spam-Status: No, score=-9.773 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VUbIFzc22WxQ; Fri, 18 Apr 2014 06:48:09 -0700 (PDT) Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) by ietfa.amsl.com (Postfix) with ESMTP id 301B51A0146; Fri, 18 Apr 2014 06:48:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3332; q=dns/txt; s=iport; t=1397828885; x=1399038485; h=message-id:date:from:mime-version:to:subject:references: in-reply-to:content-transfer-encoding; bh=e9/F92GwIVl4TsHjPJbcIAEtLqZr2rASk5B9fjupvoU=; b=YpfOLFGuim5mcLjIo8hD0pCqZXJ1sinxoZLZzE2gKvNT8I+vDMGcGjNM tuojHkKfM8/apjdpAXWg2wZwSGi6y1xbSo9/qWbrI8Fw72DhSBrnWHrXI 2daD7zCTBO0fKwWpBVULvScT4FnNnLNTnQQ8U1HuMJVDKqt+1KORh6F61 g=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AqAEAPcrUVOtJssW/2dsb2JhbABag1XER4ExdIIlAQEBBDhADQQsFg8JAwIBAgFFBgEMCAEBiD0NzGITBI5phDgBA5huhliLd4MzOw X-IronPort-AV: E=Sophos;i="4.97,884,1389744000"; d="scan'208";a="14982844" Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP; 18 Apr 2014 13:48:03 +0000 Received: from [10.60.67.86] (ams-bclaise-8915.cisco.com [10.60.67.86]) by aer-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s3IDm3e2002505; Fri, 18 Apr 2014 13:48:03 GMT Message-ID: <53512D13.9080504@cisco.com> Date: Fri, 18 Apr 2014 15:48:03 +0200 From: Benoit Claise User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: "aaa-doctors@ietf.org" , "MIB Doctors (E-mail)" , YANG Doctors , "ops-dir@ietf.org" , "pm-dir@ietf.org" , IETF DNS Directorate References: <20140417220347.30384.65100.idtracker@ietfa.amsl.com> In-Reply-To: <20140417220347.30384.65100.idtracker@ietfa.amsl.com> X-Forwarded-Message-Id: <20140417220347.30384.65100.idtracker@ietfa.amsl.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/z57dEGPpbG3Vqt28R_3LTSj0cck Subject: [MIB-DOCTORS] Summarized Agenda for the 2014-04-24 IESG Teleconference X-BeenThere: mib-doctors@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: MIB Doctors list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Apr 2014 13:48:10 -0000 Dear all, Please find below the agenda of the April 24th IESG telechat. Please send your questions, comments, and concerns before April 23rd COB. Thanks and Regards, Benoit. -------- Original Message -------- INTERNET ENGINEERING STEERING GROUP (IESG) Summarized Agenda for the 2014-04-24 IESG Teleconference This agenda was generated at 2014-04-17 15:01:42 PDT Up-to-date web version of this agenda can be found at: https://datatracker.ietf.org/iesg/agenda/ 2. Protocol Actions 2.1 WG Submissions 2.1.1 New Items o draft-ietf-precis-framework-15 - IETF stream PRECIS Framework: Preparation and Comparison of Internationalized Strings in Application Protocols (Proposed Standard) Token: Pete Resnick IANA Review: IANA - Review Needed Consensus: Yes Last call expires: 2014-04-23 o draft-ietf-mpls-ldp-applicability-label-adv-03 - IETF stream Label Advertisement Discipline for LDP FECs (Proposed Standard) Token: Adrian Farrel IANA Review: IANA OK - Actions Needed Consensus: Yes o draft-ietf-idr-aigp-17 - IETF stream The Accumulated IGP Metric Attribute for BGP (Proposed Standard) Token: Alia Atlas IANA Review: IANA OK - Actions Needed Consensus: Yes 2.1.2 Returning Items NONE 2.2 Individual Submissions 2.2.1 New Items NONE 2.2.2 Returning Items NONE 2.3 Status Changes 2.3.1 New Items NONE 2.3.2 Returning Items NONE 3. Document Actions 3.1 WG Submissions 3.1.1 New Items NONE 3.1.2 Returning Items o draft-ietf-opsec-vpn-leakages-04 - IETF stream Virtual Private Network (VPN) traffic leakages in dual-stack hosts/ networks (Informational) Token: Joel Jaeggli IANA Review: Version Changed - Review Needed Consensus: Yes 3.2 Individual Submissions Via AD 3.2.1 New Items NONE 3.2.2 Returning Items o draft-housley-pkix-oids-02 - IETF stream Object Identifier Registry for the PKIX Working Group (Informational) Token: Stephen Farrell IANA Review: IANA OK - Actions Needed Consensus: Yes 3.3 Status Changes 3.3.1 New Items o status-change-ipv4-address-mapping-classes-to-historic-01 - IETF stream RFC 796 (Address Mappings) to Historic (None) Token: Ted Lemon 3.3.2 Returning Items NONE 3.4 IRTF and Independent Submission Stream Documents 3.4.1 New Items o conflict-review-dunbar-armd-arp-nd-scaling-practices-01 IETF conflict review for draft-dunbar-armd-arp-nd-scaling-practices draft-dunbar-armd-arp-nd-scaling-practices-07 Practices for scaling ARP and ND for large data centers (ISE: Informational) Token: Brian Haberman 3.4.2 Returning Items o conflict-review-andrews-dnsext-expire-00 IETF conflict review for draft-andrews-dnsext-expire draft-andrews-dnsext-expire-04 EDNS EXPIRE OPTION (ISE: Experimental) Token: Ted Lemon 4. Working Group Actions 4.1 WG Creation 4.1.1 Proposed for IETF Review NONE 4.1.2 Proposed for Approval NONE 4.2 WG Rechartering 4.2.1 Under Evaluation for IETF Review NONE 4.2.2 Proposed for Approval o JavaScript Object Notation (json) From nobody Tue Apr 22 07:36:09 2014 Return-Path: X-Original-To: mib-doctors@ietfa.amsl.com Delivered-To: mib-doctors@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D1B901A0499 for ; Tue, 22 Apr 2014 07:36:06 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -9.773 X-Spam-Level: X-Spam-Status: No, score=-9.773 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CjTJR6WFzHKs for ; Tue, 22 Apr 2014 07:36:01 -0700 (PDT) Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) by ietfa.amsl.com (Postfix) with ESMTP id 6CE071A0494 for ; Tue, 22 Apr 2014 07:36:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=514; q=dns/txt; s=iport; t=1398177356; x=1399386956; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=mDycssoHo/iXFAEaoqcAcSn7wmxo4iVMypvvaiCH8/Y=; b=i7Y2Ddldrc/383z8EzY2sl45dm0VU7iFT3viThGe08N26zGF9aug+4E/ v52XY3H8gBrrQ/AWQN9gXSoubUNQg1yhlAJul/jMZyfBfsgFQ3EKRcz1Q BeG2L2Py77qhnT2ocQY09BZsRAqUgbJmKxe1HwHBzvjv8VQuTU6MW5d5U c=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AnsIADV9VlOQ/khN/2dsb2JhbABZgwZPvTuHKgqBFRZ0giYBAQQ4QAEQCw4TFg8JAwIBAgFFBg0BBwEBBYg4DcxQF44FAQFPB4Q4AQOYcIE3hSKLeYMzO4E1 X-IronPort-AV: E=Sophos;i="4.97,904,1389744000"; d="scan'208";a="23995074" Received: from ams-core-4.cisco.com ([144.254.72.77]) by aer-iport-1.cisco.com with ESMTP; 22 Apr 2014 14:35:55 +0000 Received: from [10.60.67.86] (ams-bclaise-8915.cisco.com [10.60.67.86]) by ams-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id s3MEZt1Z008923; Tue, 22 Apr 2014 14:35:55 GMT Message-ID: <53567E4A.4020004@cisco.com> Date: Tue, 22 Apr 2014 16:35:54 +0200 From: Benoit Claise User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: Chris Elliott References: <5350F360.30800@cisco.com> In-Reply-To: <5350F360.30800@cisco.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/iuWDZs6G3QuJDYoOV9GdxRTslgI Cc: "MIB Doctors \(E-mail\)" , "Black, David" Subject: Re: [MIB-DOCTORS] MIB doctor review: draft-ietf-bfd-tc-mib-05 and draft-ietf-bfd-mib-17 X-BeenThere: mib-doctors@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: MIB Doctors list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Apr 2014 14:36:07 -0000 Hi Chris, Please let us know. Regards, Benoit > Hi Chris, > > Trying to round-robin MIB reviews > (http://trac.tools.ietf.org/area/ops/trac/wiki/mib-doctors-review-history), > would you be available to review draft-ietf-bfd-tc-mib-05 and > draft-ietf-bfd-mib-17? > Note that David Black already provided some useful feedback part of > his GEN-ART review, and that generated some good discussion. > See http://www.ietf.org/mail-archive/web/ietf/current/msg87489.html > > Regards, Benoit > > From nobody Tue Apr 22 07:42:52 2014 Return-Path: X-Original-To: mib-doctors@ietfa.amsl.com Delivered-To: mib-doctors@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D44451A0502 for ; Tue, 22 Apr 2014 07:42:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -9.772 X-Spam-Level: X-Spam-Status: No, score=-9.772 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3gA28nRuTG6R for ; Tue, 22 Apr 2014 07:42:46 -0700 (PDT) Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) by ietfa.amsl.com (Postfix) with ESMTP id 3EE181A04F8 for ; Tue, 22 Apr 2014 07:42:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1883; q=dns/txt; s=iport; t=1398177734; x=1399387334; h=message-id:date:from:mime-version:to:cc:subject; bh=QAR/1mRqICZuK08k/6++rJ7QMeNpukD4uLa2b/aX0/4=; b=LvIgMwy2Bbjv2taFXEcpf4RBNFrTZqbFW9102VmDsF52Qx+dBIw7KZi1 DgtHT4xGuA3NhCdtw628IUhPg3KSzqb99+xiU6Dh2BvNytuiNoS955sl4 ePqEVE+eqmHDJtAmz3DnrUxNdJpF45d8dIc1ZL8mrxhoNOLsuoszGHc2v Q=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ArMIAF1+VlOQ/khR/2dsb2JhbABZgwZPiUOzeIc0gRUWdIMkAR8BHBYYAwIBAgFLDQEHAQEFiDgNzFsXjlaEPwSYcIE3hSKLeYMzOw X-IronPort-AV: E=Sophos; i="4.97,904,1389744000"; d="scan'208,217"; a="24000154" Received: from ams-core-1.cisco.com ([144.254.72.81]) by aer-iport-1.cisco.com with ESMTP; 22 Apr 2014 14:42:13 +0000 Received: from [10.60.67.86] (ams-bclaise-8915.cisco.com [10.60.67.86]) by ams-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s3MEgDwx021950; Tue, 22 Apr 2014 14:42:13 GMT Message-ID: <53567FC5.9080802@cisco.com> Date: Tue, 22 Apr 2014 16:42:13 +0200 From: Benoit Claise User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: "MIB Doctors (E-mail)" Content-Type: multipart/alternative; boundary="------------030302090702000100090905" Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/wkPHg0p4zEf2GzJQPXCvf6-UrRU Cc: Spencer Dawkins Subject: [MIB-DOCTORS] MIB doctor review: draft-ietf-behave-nat-mib-11 X-BeenThere: mib-doctors@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: MIB Doctors list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Apr 2014 14:42:51 -0000 This is a multi-part message in MIME format. --------------030302090702000100090905 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Dear all, Who would be available for this draft-ietf-behave-nat-mib-11 MIB review? This document will be AD-sponsored by Spencer Comparing http://trac.tools.ietf.org/area/ops/trac/wiki/mib-doctors-review-history and http://www.ietf.org/iesg/directorate/mib-doctors.html, maybe: Bill Fenner Andy Bierman Glenn Waters John Flick Please let me know. Regards, Benoit --------------030302090702000100090905 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Dear all,

Who would be available for this draft-ietf-behave-nat-mib-11 MIB review?
This document will be AD-sponsored by Spencer
Comparing http://trac.tools.ietf.org/area/ops/trac/wiki/mib-doctors-review-history and http://www.ietf.org/iesg/directorate/mib-doctors.html, maybe:
    Bill Fenner
    Andy Bierman
    Glenn Waters
    John Flick
   
Please let me know.

Regards, Benoit
--------------030302090702000100090905-- From nobody Tue Apr 29 01:00:27 2014 Return-Path: X-Original-To: mib-doctors@ietfa.amsl.com Delivered-To: mib-doctors@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C52121A076F for ; Tue, 29 Apr 2014 01:00:24 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -10.151 X-Spam-Level: X-Spam-Status: No, score=-10.151 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tSL4599OLyjN for ; Tue, 29 Apr 2014 01:00:23 -0700 (PDT) Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) by ietfa.amsl.com (Postfix) with ESMTP id EE6161A0764 for ; Tue, 29 Apr 2014 01:00:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3137; q=dns/txt; s=iport; t=1398758422; x=1399968022; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=Nnd4CGcaEMpqbb/Cn+vGc3nObzCR2/XCNCzktqv5Nuo=; b=OQhmNQqmfAjHqkwbpRXX4jOl/HKuUh/GY2dtrE2/QMJDka9AZdg7m3JE 96am80LpSaULpkX6QQj3c23plmEJHnUdPO+wXecCgz6Bl4qqj05XyyI5i PKCBuNsH9aeMeNsMLDP8lvoa6WkOu3g0/cvj+hkLmDwLIQqcQbrUIxTth 4=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AvoHAE9bX1OtJssW/2dsb2JhbABZg1W+FAEHhzGBM3SCJgEBBAEBAWsKARALBB0WDwkDAgECARUwBg0BBQIBAQWIOA3IeheOTweEOQEDmQ2BPIUjjAKDMzs X-IronPort-AV: E=Sophos; i="4.97,949,1389744000"; d="scan'208,217"; a="26724237" Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP; 29 Apr 2014 08:00:21 +0000 Received: from [10.60.67.86] (ams-bclaise-8915.cisco.com [10.60.67.86]) by aer-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id s3T80LJp011673; Tue, 29 Apr 2014 08:00:21 GMT Message-ID: <535F5C15.3040908@cisco.com> Date: Tue, 29 Apr 2014 10:00:21 +0200 From: Benoit Claise User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: "MIB Doctors (E-mail)" References: <53567FC5.9080802@cisco.com> In-Reply-To: <53567FC5.9080802@cisco.com> Content-Type: multipart/alternative; boundary="------------020501090507020608010301" Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/BNGcNJz6u2wS4KTjr0CTq_LVQxQ Cc: Spencer Dawkins Subject: Re: [MIB-DOCTORS] MIB doctor review: draft-ietf-behave-nat-mib-11 X-BeenThere: mib-doctors@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: MIB Doctors list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Apr 2014 08:00:25 -0000 This is a multi-part message in MIME format. --------------020501090507020608010301 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Dear all, David Harrington has accepted to review this MIB module. Thank you very much David. Regards, Benoit > Dear all, > > Who would be available for this draft-ietf-behave-nat-mib-11 > MIB review? > This document will be AD-sponsored by Spencer > Comparing > http://trac.tools.ietf.org/area/ops/trac/wiki/mib-doctors-review-history > and http://www.ietf.org/iesg/directorate/mib-doctors.html, maybe: > Bill Fenner > Andy Bierman > Glenn Waters > John Flick > > Please let me know. > > Regards, Benoit > > > _______________________________________________ > MIB-DOCTORS mailing list > MIB-DOCTORS@ietf.org > https://www.ietf.org/mailman/listinfo/mib-doctors --------------020501090507020608010301 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
Dear all,

David Harrington has accepted to review this MIB module.
Thank you very much David.

Regards, Benoit
Dear all,

Who would be available for this draft-ietf-behave-nat-mib-11 MIB review?
This document will be AD-sponsored by Spencer
Comparing http://trac.tools.ietf.org/area/ops/trac/wiki/mib-doctors-review-history and http://www.ietf.org/iesg/directorate/mib-doctors.html, maybe:
    Bill Fenner
    Andy Bierman
    Glenn Waters
    John Flick
   
Please let me know.

Regards, Benoit


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

--------------020501090507020608010301-- From nobody Tue Apr 29 01:08:58 2014 Return-Path: X-Original-To: mib-doctors@ietfa.amsl.com Delivered-To: mib-doctors@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D3341A08BB for ; Tue, 29 Apr 2014 01:08:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -10.152 X-Spam-Level: X-Spam-Status: No, score=-10.152 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KV49GLcD-Lui for ; Tue, 29 Apr 2014 01:08:48 -0700 (PDT) Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) by ietfa.amsl.com (Postfix) with ESMTP id 420031A08BA for ; Tue, 29 Apr 2014 01:08:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=17; q=dns/txt; s=iport; t=1398758927; x=1399968527; h=message-id:date:from:mime-version:to:subject: content-transfer-encoding; bh=/arwFErP0t6d5869rZT3o0Px8DsJ6PsqfbDRb8UlZTk=; b=Nk6Us24dvx4m56mR/CApgr95yCNDb06hGg7qUi9tpLHpBGEsmn+BqP6z wrCI8PXnJl3uxSZX4epXRWXai4fXTSd4tbdOtOL/+jX87UhqNREnNO3u4 kE9uAFmuulnHohzvHdAF/jx1EvisoKY6qFBly6vZdqpCg24yV48npXeaP k=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AvYHAP9cX1OtJssW/2dsb2JhbABZwXGHJwEBgTt0gkUfQD0WGAMCAQIBSw0IAQGIPZYismMXkw8BA40bi3KGX32LBYMzOw X-IronPort-AV: E=Sophos;i="4.97,949,1389744000"; d="scan'208";a="26747776" Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP; 29 Apr 2014 08:08:46 +0000 Received: from [10.60.67.86] (ams-bclaise-8915.cisco.com [10.60.67.86]) by aer-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id s3T88kXf024279 for ; Tue, 29 Apr 2014 08:08:46 GMT Message-ID: <535F5E0E.1070808@cisco.com> Date: Tue, 29 Apr 2014 10:08:46 +0200 From: Benoit Claise User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: "MIB Doctors (E-mail)" Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/lxnsocZ9JiMWfXZkXHshQtDgtYE Subject: [MIB-DOCTORS] Chris Elliott has been removed from the MIB doctors list X-BeenThere: mib-doctors@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: MIB Doctors list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Apr 2014 08:08:50 -0000 Regards, Benoit