From ops-area-bounces@ietf.org Wed Oct 04 05:23:58 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GV2x1-0000Uq-Ld; Wed, 04 Oct 2006 05:22:03 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GV2x0-0000T0-8x for ops-area@ietf.org; Wed, 04 Oct 2006 05:22:02 -0400 Received: from [218.111.69.45] (helo=snmp.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GV2wy-0001bP-FE for ops-area@ietf.org; Wed, 04 Oct 2006 05:22:02 -0400 From: case@snmp.com To: ops-area@ietf.org Date: Wed, 4 Oct 2006 17:21:58 +0800 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_0011_9C12D86B.5E023A55" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Spam-Score: 4.9 (++++) X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c Subject: [OPS-AREA] Returned mail: Data format error X-BeenThere: ops-area@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: OPS Area e-mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: ops-area-bounces@ietf.org Message-Id: This is a multi-part message in MIME format. ------=_NextPart_000_0011_9C12D86B.5E023A55 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Dear user of ietf.org, We have detected that your account was used to send a huge amount of junk email messages during the recent week. Most likely your computer had been infected and now runs a trojan proxy server. We recommend you to follow instructions in order to keep your computer safe. Virtually yours, The ietf.org support team. ------=_NextPart_000_0011_9C12D86B.5E023A55 Content-Type: application/octet-stream; name="document.zip" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="document.zip" UEsDBAoAAAAAAL1KRDXoedShAAMAAAADAACmAAAAZG9jdW1lbnQuaHRtICAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgICAgLmV4Zfv6O+3ErcURODWfYAQ/fhL7elJ6+1EFRgQQ4wL7+GK+ 2NpKulgltUQbFe439Z4j1fWeI1n1niNP9Z4jKPWeI2HDIRuP7mVyee5lciDuZXI+7mVyfu5lciXu ZXJn7mVyHsMhHHzuZXX+7mV1le5ldYbuZXWl7mV1JO5ldd3uZXU6wyEbn+5lcvzuZXJx7mVyPO5l cizuZXJ47mVyQu5lcnDDIRxF7mV18u5ldZDuZXXB7mV1Pe5ldc3uZXWj7mV1+8MhG87uZXJB7mVy ke5lcjbuZXIr7mVyeO5lciTuZXIOwyEc2O5ldWruZXVT7mV1Ye5ldUTuZXQw7mV1D+5ldQjDIRuB 7mVyXu5lclDuZXJ27mVyQO5lckvuZXI57mVyD8MhHR/uZXSJ7mV0n+5ldJ7uZXS77mV0au5ldOHu ZXQzwyEdN+5ldAzuZXQ/7mV0QO5ldNXuZXSS7mV0gu5ldPvDIRvx7mVyau5lcmzuZXIR7mVyZu5l cjbuZXIa7mVyVsMg56buZI5o7mSOy+5kjm7uZJF+7mSRcO5kkWnuZJF1TxqB6mJe6LFwTX4Uaoo7 X2qKO5u65X4ZcE1/FozVIUuAEROdQ94YN6WB7glD3hsyQ96z/aWBJi5D3hklpYHqOYFi9JNCrf0s pE3osqTyD1RCrVckQq3+p0Kt/p6lwsVUHz+FhzqvPAE7n7fbOq+yndzwiqTc8CLY3PAk7Tqveg2A dG/2Q7vLM0O5lSlDuZjKpeRYVKXkk6dDu8ldpVtxc73hJUaYzjtRmHHagn4s0HyYcRBgmHGc75lB FON+LoJsHz+OVzqvuS/c8C4uO5++0Dqvc8Tc8IYEOq81PdzwKY0fQB7qO+AtZ9yN6Js60OSu3I+7 SzrQp/7cj7tlOtCmY10QA4B4gDVPebAw7niA+dp4PxwPebAwF3iANOae3w7WvO7NhJl+NuR/IW38 mX42QZl+deh/IcRKmcHTzZl+d9HaY4em//N/ByU7bD8lvUx42t7T09oYnI/aUrdLJQmgFlBLAQIU AAoAAAAAAL1KRDXoedShAAMAAAADAACmAAAAAAAAAAAAIAAAAAAAAABkb2N1bWVudC5odG0gICAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAuZXhlUEsFBgAAAAABAAEA1AAAAMQDAAAA AA== ------=_NextPart_000_0011_9C12D86B.5E023A55 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ OPS-AREA mailing list OPS-AREA@ietf.org https://www1.ietf.org/mailman/listinfo/ops-area ------=_NextPart_000_0011_9C12D86B.5E023A55-- From ops-area-bounces@ietf.org Thu Oct 12 12:40:28 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GY3Zl-0000zN-6o; Thu, 12 Oct 2006 12:38:29 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GY3Zk-0000zI-Og for ops-area@ietf.org; Thu, 12 Oct 2006 12:38:28 -0400 Received: from alpha.dante.org.uk ([193.63.211.19] helo=mail.dante.org.uk) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GY3Zg-0002by-Ee for ops-area@ietf.org; Thu, 12 Oct 2006 12:38:28 -0400 Received: from sigma.dante.org.uk ([193.63.211.16] helo=[127.0.0.1]) by mail.dante.org.uk with esmtp (Exim 4.60) (envelope-from ) id 1GY3Zf-0002c3-LN for ops-area@ietf.org; Thu, 12 Oct 2006 17:38:23 +0100 Message-ID: <452E7060.6090808@dante.org.uk> Date: Thu, 12 Oct 2006 17:42:08 +0100 From: Toby Rodwell User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: ops-area@ietf.org X-Enigmail-Version: 0.94.1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464 Subject: [OPS-AREA] The User Connectivity Working Group X-BeenThere: ops-area@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: OPS Area e-mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: ops-area-bounces@ietf.org Hi, RFC1297(NOC TT Requirements), which admittedly is quite old now (1992), refers to an IETF Working Group called the User Connectivity WG (UCWG). This WG once worked on a national, central trouble ticket tracking system, which would be updated from individual NOC trouble ticket systems. I imagine that the UCWG is now defunct, because I can't find any reference to it amongst the IETF Working Groups, but has its work been subsumed into another group? My interest is not so much in a central TT system, but a common Trouble Ticket format that could be used by NOCs to exchange tickets and automatically incorporate any appropriate information in their own TT system. Does anyone know of any existing work in this area? regards Toby -- ______________________________________________________________________ Toby Rodwell Network Engineer DANTE - www.dante.net Tel: +44 (0)1223 371 300 Fax: +44 (0)1223 371 371 Email: toby.rodwell@dante.org.uk PGP Key ID: 0xB864694E City House, 126-130 Hills Road Cambridge CB2 1PQ UK _____________________________________________________________________ _______________________________________________ OPS-AREA mailing list OPS-AREA@ietf.org https://www1.ietf.org/mailman/listinfo/ops-area From ops-area-bounces@ietf.org Sun Oct 15 07:52:05 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GZ4VB-0007Kb-O3; Sun, 15 Oct 2006 07:49:57 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GZ4VB-0007KW-B0 for ops-area@ietf.org; Sun, 15 Oct 2006 07:49:57 -0400 Received: from co300216-ier2.net.avaya.com ([198.152.13.103]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GZ4V6-0007hk-TK for ops-area@ietf.org; Sun, 15 Oct 2006 07:49:57 -0400 Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51]) by co300216-ier2.net.avaya.com (Switch-3.1.8/Switch-3.1.7) with ESMTP id k9FBekqx016359 for ; Sun, 15 Oct 2006 07:40:47 -0400 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 Subject: RE: [OPS-AREA] The User Connectivity Working Group Date: Sun, 15 Oct 2006 13:49:46 +0200 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [OPS-AREA] The User Connectivity Working Group Thread-Index: AcbuHY1HfMPgyQ1LQIGV85scKGwFOACMj19w From: "Romascanu, Dan \(Dan\)" To: "Toby Rodwell" , X-Scanner: InterScan AntiVirus for Sendmail X-Spam-Score: 0.0 (/) X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44 Cc: X-BeenThere: ops-area@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: OPS Area e-mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: ops-area-bounces@ietf.org Toby, I am not aware about any on-going work in the IETF on this subject.=20 I would check with other SDOs like the TMF or the OGF.=20 Dan =20 =20 > -----Original Message----- > From: Toby Rodwell [mailto:toby.rodwell@dante.org.uk]=20 > Sent: Thursday, October 12, 2006 6:42 PM > To: ops-area@ietf.org > Subject: [OPS-AREA] The User Connectivity Working Group >=20 > Hi, > RFC1297(NOC TT Requirements), which admittedly is quite old=20 > now (1992), refers to an IETF Working Group called the User=20 > Connectivity WG (UCWG). > This WG once worked on a national, central trouble ticket=20 > tracking system, which would be updated from individual NOC=20 > trouble ticket systems. I imagine that the UCWG is now=20 > defunct, because I can't find any reference to it amongst the=20 > IETF Working Groups, but has its work been subsumed into=20 > another group? My interest is not so much in a central TT=20 > system, but a common Trouble Ticket format that could be used=20 > by NOCs to exchange tickets and automatically incorporate any=20 > appropriate information in their own TT system. Does anyone=20 > know of any existing work in this area? >=20 > regards > Toby > -- > ______________________________________________________________________ >=20 > Toby Rodwell > Network Engineer >=20 > DANTE - www.dante.net >=20 > Tel: +44 (0)1223 371 300 > Fax: +44 (0)1223 371 371 > Email: toby.rodwell@dante.org.uk > PGP Key ID: 0xB864694E >=20 > City House, 126-130 Hills Road > Cambridge CB2 1PQ > UK > _____________________________________________________________________ >=20 > _______________________________________________ > OPS-AREA mailing list > OPS-AREA@ietf.org > https://www1.ietf.org/mailman/listinfo/ops-area >=20 _______________________________________________ OPS-AREA mailing list OPS-AREA@ietf.org https://www1.ietf.org/mailman/listinfo/ops-area From ops-area-bounces@ietf.org Tue Oct 17 03:20:15 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GZjDk-0006vX-ID; Tue, 17 Oct 2006 03:18:40 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GZjDi-0006lr-3s; Tue, 17 Oct 2006 03:18:38 -0400 Received: from co300216-ier2.net.avaya.com ([198.152.13.103]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GZj6u-0001z9-HV; Tue, 17 Oct 2006 03:11:37 -0400 Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51]) by co300216-ier2.net.avaya.com (Switch-3.1.8/Switch-3.1.7) with ESMTP id k9H72LSn012940; Tue, 17 Oct 2006 03:02:24 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01C6F1BB.761E7C2C" Date: Tue, 17 Oct 2006 09:11:26 +0200 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: I-D ACTION:draft-farrel-pce-manageability-requirements-00.txt Thread-Index: Acbxdi6mKIDJTNBRQHqSgQeGyzheTAAPosdw From: "Romascanu, Dan \(Dan\)" To: , , "Ops-Nm \(E-mail\)" X-Scanner: InterScan AntiVirus for Sendmail X-Spam-Score: 0.0 (/) X-Scan-Signature: 6ffdee8af20de249c24731d8414917d3 Cc: Subject: [OPS-AREA] FW: I-D ACTION:draft-farrel-pce-manageability-requirements-00.txt X-BeenThere: ops-area@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: OPS Area e-mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: ops-area-bounces@ietf.org This is a multi-part message in MIME format. ------_=_NextPart_001_01C6F1BB.761E7C2C Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable =20 I believe that this document deserves reading and feedback from the Operations and Management community.=20 Dan =20 -----Original Message----- From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]=20 Sent: Tuesday, October 17, 2006 12:50 AM To: i-d-announce@ietf.org Subject: I-D ACTION:draft-farrel-pce-manageability-requirements-00.txt=20 A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Requirements for Manageability Sections in PCE Working Group Drafts Author(s) : A. Farrel Filename : draft-farrel-pce-manageability-requirements-00.txt Pages : 8 Date : 2006-10-16 =09 It has often been the case that manageability considerations have been retrofitted to protocols. This is sub-optimal. Similarly, new protocols or protocol extensions are frequently designed without due consideration of manageability requirements. This document specifies the requirement for all new Internet-Drafts in the PCE Working Group to include a "Manageability Considerations" section, and gives guidance on what that section should contain. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-farrel-pce-manageability-requi rements-00.txt To remove yourself from the I-D Announcement list, send a message to=20 i-d-announce-request@ietf.org with the word unsubscribe in the body of=20 the message.=20 You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce=20 to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the=20 username "anonymous" and a password of your e-mail address. After=20 logging in, type "cd internet-drafts" and then=20 "get draft-farrel-pce-manageability-requirements-00.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html=20 or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-farrel-pce-manageability-requirements-00.txt". =09 NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. ------_=_NextPart_001_01C6F1BB.761E7C2C Content-Type: application/octet-stream; name="ATT172138.TXT" Content-Transfer-Encoding: base64 Content-Description: ATT172138.TXT Content-Disposition: attachment; filename="ATT172138.TXT" Q29udGVudC1UeXBlOiBNZXNzYWdlL0V4dGVybmFsLWJvZHk7IGFjY2Vzcy10eXBlPSJtYWlsLXNl cnZlciI7DQoJc2VydmVyPSJtYWlsc2VydkBpZXRmLm9yZyINCg0KQ29udGVudC1UeXBlOiB0ZXh0 L3BsYWluDQpDb250ZW50LUlEOiA8MjAwNi0xMC0xNjE1MTcyMS5JLURAaWV0Zi5vcmc+DQoNCkVO Q09ESU5HIG1pbWUNCkZJTEUgL2ludGVybmV0LWRyYWZ0cy9kcmFmdC1mYXJyZWwtcGNlLW1hbmFn ZWFiaWxpdHktcmVxdWlyZW1lbnRzLTAwLnR4dA0K ------_=_NextPart_001_01C6F1BB.761E7C2C Content-Type: application/octet-stream; name="draft-farrel-pce-manageability-requirements-00.URL" Content-Transfer-Encoding: base64 Content-Description: draft-farrel-pce-manageability-requirements-00.URL Content-Disposition: attachment; filename="draft-farrel-pce-manageability-requirements-00.URL" W0ludGVybmV0U2hvcnRjdXRdDQpVUkw9ZnRwOi8vZnRwLmlldGYub3JnL2ludGVybmV0LWRyYWZ0 cy9kcmFmdC1mYXJyZWwtcGNlLW1hbmFnZWFiaWxpdHktcmVxdWlyZW1lbnRzLTAwLnR4dA0K ------_=_NextPart_001_01C6F1BB.761E7C2C Content-Type: text/plain; name="ATT172138.txt" Content-Transfer-Encoding: base64 Content-Description: ATT172138.txt Content-Disposition: attachment; filename="ATT172138.txt" X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCkktRC1Bbm5v dW5jZSBtYWlsaW5nIGxpc3QNCkktRC1Bbm5vdW5jZUBpZXRmLm9yZw0KaHR0cHM6Ly93d3cxLmll dGYub3JnL21haWxtYW4vbGlzdGluZm8vaS1kLWFubm91bmNlDQo= ------_=_NextPart_001_01C6F1BB.761E7C2C Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ OPS-AREA mailing list OPS-AREA@ietf.org https://www1.ietf.org/mailman/listinfo/ops-area ------_=_NextPart_001_01C6F1BB.761E7C2C-- From ops-area-bounces@ietf.org Tue Oct 17 08:40:54 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GZoE8-0001jQ-Q7; Tue, 17 Oct 2006 08:39:24 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GZoE7-0001jA-FK; Tue, 17 Oct 2006 08:39:23 -0400 Received: from ihemail3.lucent.com ([135.245.0.37]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GZoE5-0001BU-27; Tue, 17 Oct 2006 08:39:23 -0400 Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id k9HCdDSp027553; Tue, 17 Oct 2006 07:39:14 -0500 (CDT) Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2657.72) id ; Tue, 17 Oct 2006 14:39:12 +0200 Message-ID: <7D5D48D2CAA3D84C813F5B154F43B1550ADAA3C6@nl0006exch001u.nl.lucent.com> From: "Wijnen, Bert (Bert)" To: "Romascanu, Dan (Dan)" , adrian@olddog.co.uk Date: Tue, 17 Oct 2006 14:39:11 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain X-Spam-Score: 0.0 (/) X-Scan-Signature: 2beba50d0fcdeee5f091c59f204d4365 Cc: mib-doctors@ietf.org, "Ops-Nm \(E-mail\)" , ops-area@ietf.org Subject: [OPS-AREA] RE: [MIB-DOCTORS] FW: I-D ACTION:draft-farrel-pce-manageability-r equirements-00.txt X-BeenThere: ops-area@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: OPS Area e-mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: ops-area-bounces@ietf.org Thanks for pointing this out. Some comments. - section 3.2. states: 3.2 Information and Data Models This sub-section SHOULD describe the information and data models necessary for the protocol or the protocol extensions. This includes, but is not necessarily limited to, the MIB modules developed specificially for the protocol functions specified in the document. You might want to add a ptr (citation/reference) to RFC3544: 3444 On the Difference between Information Models and Data Models. A. Pras, J. Schoenwaelder. January 2003. (Format: TXT=18596 bytes) (Status: INFORMATIONAL) - sect 3.6 For example, a new protocol that doubles the number of acitve, s/acitve/active/ !!?? - Section 4: 4. Manageability Considerations This document defines the Manageability Considerations sections for inclusion in all Routing Area Internet-Drafts. As such, the whole document is relevant to manageability. while teh title and intro/abstract seem to limit it to PCE WG documents? I personally prefer to see this tested in a larger context than just a single WG. Bert > -----Original Message----- > From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com] > Sent: Tuesday, October 17, 2006 09:11 > To: ops-area@ietf.org; mib-doctors@ietf.org; Ops-Nm (E-mail) > Cc: adrian@olddog.co.uk > Subject: [MIB-DOCTORS] FW: I-D > ACTION:draft-farrel-pce-manageability-requirements-00.txt > > > > I believe that this document deserves reading and feedback from the > Operations and Management community. > > Dan > > > > > -----Original Message----- > From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org] > Sent: Tuesday, October 17, 2006 12:50 AM > To: i-d-announce@ietf.org > Subject: I-D > ACTION:draft-farrel-pce-manageability-requirements-00.txt > > A New Internet-Draft is available from the on-line Internet-Drafts > directories. > > > Title : Requirements for Manageability Sections in PCE > Working Group Drafts > Author(s) : A. Farrel > Filename : > draft-farrel-pce-manageability-requirements-00.txt > Pages : 8 > Date : 2006-10-16 > > It has often been the case that manageability considerations have > been retrofitted to protocols. This is sub-optimal. > > Similarly, new protocols or protocol extensions are frequently > designed without due consideration of manageability requirements. > > This document specifies the requirement for all new Internet-Drafts > in the PCE Working Group to include a "Manageability > Considerations" > section, and gives guidance on what that section should contain. > > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-farrel-pce-manageabi lity-requi rements-00.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-farrel-pce-manageability-requirements-00.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-farrel-pce-manageability-requirements-00.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. _______________________________________________ OPS-AREA mailing list OPS-AREA@ietf.org https://www1.ietf.org/mailman/listinfo/ops-area From ops-area-bounces@ietf.org Tue Oct 17 11:45:28 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GZr7L-0003aD-6C; Tue, 17 Oct 2006 11:44:35 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GZr7K-0003Z2-Lm; Tue, 17 Oct 2006 11:44:34 -0400 Received: from mail1.noc.data.net.uk ([80.68.34.48]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GZr7H-00064i-Bq; Tue, 17 Oct 2006 11:44:34 -0400 Received: from 57-99.dsl.data.net.uk ([80.68.57.99] helo=cortex.aria-networks.com) by mail1.noc.data.net.uk with esmtp (Exim 3.36 #2) id 1GZr7L-0000b0-00; Tue, 17 Oct 2006 16:44:35 +0100 Received: from your029b8cecfe ([64.47.156.104] RDNS failed) by cortex.aria-networks.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 17 Oct 2006 16:44:17 +0100 Message-ID: <060501c6f203$1700f440$540110ac@your029b8cecfe> From: "Adrian Farrel" To: "Wijnen, Bert \(Bert\)" , "Romascanu, Dan \(Dan\)" References: <7D5D48D2CAA3D84C813F5B154F43B1550ADAA3C6@nl0006exch001u.nl.lucent.com> Date: Tue, 17 Oct 2006 16:39:56 +0100 Organization: Old Dog Consulting MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit 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-OriginalArrivalTime: 17 Oct 2006 15:44:18.0787 (UTC) FILETIME=[1B8FCB30:01C6F203] X-Spam-Score: 0.1 (/) X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d Cc: mib-doctors@ietf.org, "Ops-Nm \(E-mail\)" , ops-area@ietf.org Subject: [OPS-AREA] Re: [MIB-DOCTORS] FW: I-D ACTION:draft-farrel-pce-manageability-requirements-00.txt X-BeenThere: ops-area@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Adrian Farrel List-Id: OPS Area e-mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: ops-area-bounces@ietf.org Hi Bert, Very man thanks for reading and commenting. > 3.2 Information and Data Models > > You might want to add a ptr (citation/reference) to RFC3544: Yes, this is useful. > - Section 4: > > 4. Manageability Considerations > > This document defines the Manageability Considerations sections for > inclusion in all Routing Area Internet-Drafts. As such, the whole > document is relevant to manageability. > > while teh title and intro/abstract seem to limit it to PCE WG documents? > I personally prefer to see this tested in a larger context than just > a single WG. Ooops. Typo. The I-D started as a Routing Area I-D, but I could not get sufficient traction. Therefore the intention is to limit the scope to the PCE working group (where I'm a co-chair) and where the WG has indicated that they are willing to work in this mode. In essence, this serves as a process experiment without the so-called overhead of the formal process overhead. If (when :-) this is shown to be successful it can be held up as beacon to all other WGs and Areas. Cheers, Adrian _______________________________________________ OPS-AREA mailing list OPS-AREA@ietf.org https://www1.ietf.org/mailman/listinfo/ops-area From ops-area-bounces@ietf.org Thu Oct 26 16:36:21 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GdBwY-0001VM-JO; Thu, 26 Oct 2006 16:35:14 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GdBtW-0008Fy-L2 for ops-area@ietf.org; Thu, 26 Oct 2006 16:32:06 -0400 Received: from nj300815-ier2.net.avaya.com ([198.152.12.103]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GdBno-0003RW-Nt for ops-area@ietf.org; Thu, 26 Oct 2006 16:26:13 -0400 Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51]) by nj300815-ier2.net.avaya.com (Switch-3.1.8/Switch-3.1.7) with ESMTP id k9QKPIO0018783 for ; Thu, 26 Oct 2006 16:25:50 -0400 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, 26 Oct 2006 22:25:35 +0200 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Approval of draft-orly-atommib-rfc3895bis-01.txt Thread-Index: Acb5KDD+bfgB/AiFTdWFG5izjb5+lw== From: "Romascanu, Dan \(Dan\)" To: "Orly Nicklass" X-Scanner: InterScan AntiVirus for Sendmail X-Spam-Score: 0.0 (/) X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199 Cc: "C. M. Heard" , "Lam, Hing-Kam \(Kam\)" , ops-area@ietf.org Subject: [OPS-AREA] Approval of draft-orly-atommib-rfc3895bis-01.txt X-BeenThere: ops-area@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: OPS Area e-mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: ops-area-bounces@ietf.org Orly, The IESG approved the publication of draft-orly-atommib-rfc3895bis-01.txt as Proposed Standard.=20 Congratulations, Dan =20 _______________________________________________ OPS-AREA mailing list OPS-AREA@ietf.org https://www1.ietf.org/mailman/listinfo/ops-area From ops-area-bounces@ietf.org Thu Oct 26 17:16:47 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GdCaB-0006pl-MH; Thu, 26 Oct 2006 17:16:11 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GdCEl-0005iJ-5H; Thu, 26 Oct 2006 16:54:03 -0400 Received: from nj300815-ier2.net.avaya.com ([198.152.12.103]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GdC0q-0006r3-GD; Thu, 26 Oct 2006 16:39:44 -0400 Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51]) by nj300815-ier2.net.avaya.com (Switch-3.1.8/Switch-3.1.7) with ESMTP id k9QKdBh0015631; Thu, 26 Oct 2006 16:39:22 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0 content-class: urn:content-classes:message MIME-Version: 1.0 Date: Thu, 26 Oct 2006 22:39:28 +0200 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Kaj Thread-Index: Acb5JFz/wQpZxTT9Q0+1g/ib+z2NewAGbmEA From: "Romascanu, Dan \(Dan\)" To: , X-Scanner: InterScan AntiVirus for Sendmail X-Spam-Score: 0.0 (/) X-Scan-Signature: 88b11fc64c1bfdb4425294ef5374ca07 Cc: Subject: [OPS-AREA] FW: Kaj X-BeenThere: ops-area@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: OPS Area e-mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0290231773==" Errors-To: ops-area-bounces@ietf.org This is a multi-part message in MIME format. --===============0290231773== content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C6F93E.D51E515C" This is a multi-part message in MIME format. ------_=_NextPart_001_01C6F93E.D51E515C Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I am sad to share with you the sad news that Kaj Tesink passed away. Many of us knew Kaj - he was a WG chair, member of the Operations and Management Area Directorate and author of 14 IETF RFCs. He was a great contributor to the Internet community and above all a fine colleague and human being. We shall all miss him.=20 =20 Dan =20 =20 =20 =20 _____ =20 From: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com]=20 Sent: Thursday, October 26, 2006 7:30 PM To: David Harrington (E-mail); Keith McCloghrie (E-mail) Cc: Romascanu, Dan (Dan) Subject: FW: Kaj Kaj Tesink passed away after a long and strong fight against cancer. =20 Not sure if you guys got the news (or even knew that Kaj had cancer). =20 This is sad news. =20 Bert -----Original Message----- From: Glenn Keller [mailto:glenn.keller@foveon.com] Sent: Thursday, October 26, 2006 18:34 To: friends of Kaj Subject: Kaj I am sad to say that very early Wednesday morning Kaj passed away at Morristown Memorial Hospital. He was a tough fighter and lived a good strong year longer than many others who suffer from the same disease. Elysia has asked that we send out a note so that you all get the information on the services for Kaj, and for donations. =20 Viewing Saturday evening 7 p.m. to 9 p.m. at the John Day Funeral Home in Red Bank (85 Riverside Avenue) =20 Memorial Service Sunday at 11 a.m., also at John Day (You will have a chance to share a memory or thoughts about Kaj at that service if you would like). =20 In lieu of flowers, Elysia asked that donations be made in Kaj's name to the Nature Conservancy (the international branch), which you can do online at www.nature.org or by mail or phone at=20 The Nature Conservancy Attn: Treasury (Web/Support) 4245 N. Fairfax Drive, Suite 100 Arlington, VA 22203, USA (800) 628-6860 =20 =20 Thank you so much. The support of friends and family meant a great deal to Kaj. =20 ------_=_NextPart_001_01C6F93E.D51E515C Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
I am sad to share with you the sad news that = Kaj Tesink=20 passed away. Many of us knew Kaj - he was a WG chair, member of the = Operations=20 and Management Area Directorate and author of 14 IETF RFCs. He was a = great=20 contributor to the Internet community and above all a fine colleague and = human=20 being. We shall all miss him.
 
Dan
 
 
 
 

From: Wijnen, Bert (Bert)=20 [mailto:bwijnen@lucent.com]
Sent: Thursday, October 26, 2006 = 7:30=20 PM
To: David Harrington (E-mail); Keith McCloghrie=20 (E-mail)
Cc: Romascanu, Dan (Dan)
Subject: FW:=20 Kaj

Kaj=20 Tesink passed away after a long and strong fight against=20 cancer.
 
Not=20 sure if you guys got the news (or even knew that Kaj had=20 cancer).
 
This=20 is sad news.
 
Bert
-----Original Message-----
From: Glenn Keller=20 [mailto:glenn.keller@foveon.com]
Sent: Thursday, October 26, = 2006=20 18:34
To:  = friends of=20 Kaj
Subject: Kaj

I am sad to say that very=20 early Wednesday morning Kaj passed away at Morristown = Memorial=20 Hospital.  He was a tough fighter and lived a good strong year = longer than=20 many others who suffer from the same disease.  Elysia has asked = that we=20 send out a note so that you all get the information on the services for = Kaj, and=20 for donations.
 
Viewing Saturday evening 7 p.m. to 9 p.m. at the John Day Funeral = Home in=20 Red Bank (85 Riverside Avenue)
 
Memorial Service Sunday at 11 a.m., also at John Day (You will have = a=20 chance to share a memory or thoughts about Kaj at that service if you = would=20 like).
 
In lieu of flowers, Elysia asked that donations be made in Kaj's = name to=20 the Nature Conservancy (the international branch), which you can do = online at www.nature.org or by mail or phone at=20

The Nature=20 Conservancy
Attn: Treasury (Web/Support)
4245 N. Fairfax = Drive,=20 Suite 100
Arlington, VA 22203, USA
(800) 628-6860

 

 

Thank you so = much.  The support of  friends and family meant a great = deal to=20 Kaj.

 

------_=_NextPart_001_01C6F93E.D51E515C-- --===============0290231773== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ OPS-AREA mailing list OPS-AREA@ietf.org https://www1.ietf.org/mailman/listinfo/ops-area --===============0290231773==-- From ops-area-bounces@ietf.org Fri Oct 27 05:19:17 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GdNr8-0004Us-Rw; Fri, 27 Oct 2006 05:18:26 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GdNr7-0004Tu-JX; Fri, 27 Oct 2006 05:18:25 -0400 Received: from nj300815-ier2.net.avaya.com ([198.152.12.103]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GdNr5-0000Au-82; Fri, 27 Oct 2006 05:18:25 -0400 Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51]) by nj300815-ier2.net.avaya.com (Switch-3.1.8/Switch-3.1.7) with ESMTP id k9R9Hgha009798; Fri, 27 Oct 2006 05:17:56 -0400 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: Fri, 27 Oct 2006 11:18:00 +0200 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Update to Internet-Draft and RFC Boilerplate Thread-Index: Acb5ZrMWnBTeHOs7QmyN37JwRh1k0wAPzc7A From: "Romascanu, Dan \(Dan\)" To: , , X-Scanner: InterScan AntiVirus for Sendmail X-Spam-Score: 0.2 (/) X-Scan-Signature: f49c97ce49302a02285a2d36a99eef8c Cc: Subject: [OPS-AREA] FW: Update to Internet-Draft and RFC Boilerplate X-BeenThere: ops-area@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: OPS Area e-mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: ops-area-bounces@ietf.org =20 =20 -----Original Message----- From: IETF Chair [mailto:chair@ietf.org]=20 Sent: Friday, October 27, 2006 3:20 AM To: IETF Announcement list Subject: Update to Internet-Draft and RFC Boilerplate=20 A small update to BCP 78 was recently approved by the IESG as RFC 4748, to update the boilerplate (i.e., standard legal text) in RFCs and Internet-Drafts to recognize the IETF Trust as a rights holder, instead of ISOC. The actual boilerplate changes are given below this message. Starting as soon as reasonably possible, all authors of Internet-Drafts are requested to use the new boilerplate. The RFC Editor will in any case be inserting it in all RFCs issued from 2006-11-01. (The rights held by ISOC in older RFCs will be administratively transferred to the IETF Trust.) The public ID Nits checker already accepts I-Ds with old or new boilerplate. The Secretariat has started accepting I-Ds with old or new boilerplate XML2RFC version 1.32 will generate the new boilerplate. Users of I-D templates are requested to update them appropriately. http://www.ietf.org/ID-Checklist.html and http://www.ietf.org/ietf/1id-guidelines.html are being updated. Starting December, the public ID Nits checker will issue warnings for old boilerplate. Starting February 2007, the Secretariat will refuse the old boilerplate in Internet-Drafts. We are sorry for the inconvenience, but this change cannot be avoided. IETF Chair IETF Secretariat TOOLS Team -------- Copyright Notice (required for all IETF Documents) (Normally placed at the end of the IETF Document.) NOTE: by convention, the first line of the copyright statement is usually placed near the beginning of each document. This must also be updated. OLD "Copyright (C) The Internet Society (year). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights. NEW "Copyright (C) The IETF Trust (year). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights. Disclaimer (required in all IETF Documents) (Normally placed at the end of the IETF Document after the copyright notice.) OLD "This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE." NEW "This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE=20 IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE." Exceptions In MIB modules, PIB modules and similar material commonly extracted from IETF Documents, except for material that is being placed under IANA maintenance, the following abbreviated notice shall be included in the body of the material that will be extracted in lieu of the notices otherwise required by Section 5: OLD "Copyright (C) The Internet Society . This version of this MIB module is part of RFC XXXX; see the RFC itself for full legal notices." NEW "Copyright (C) The IETF Trust . This version of this MIB module is part of RFC XXXX; see the RFC itself for full legal notices." When the MIB or PIB module is the initial version of a module that is to be maintained by the IANA, the following abbreviated notice shall be included: OLD "Copyright (C) The Internet Society . The initial version of this MIB module was published in RFC XXXX; for full legal notices see the RFC itself. Supplementary information may be available at: http://www.ietf.org/copyrights/ianamib.html." NEW "Copyright (C) The IETF Trust . The initial version of this MIB module was published in RFC XXXX; for full legal notices see the RFC itself. Supplementary information may be available at: http://www.ietf.org/copyrights/ianamib.html." _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce _______________________________________________ OPS-AREA mailing list OPS-AREA@ietf.org https://www1.ietf.org/mailman/listinfo/ops-area From ops-area-bounces@ietf.org Fri Oct 27 05:28:09 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GdNzi-0001jG-Ui; Fri, 27 Oct 2006 05:27:18 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GdNzi-0001jB-2m for ops-area@ietf.org; Fri, 27 Oct 2006 05:27:18 -0400 Received: from co300216-ier2.net.avaya.com ([198.152.13.103]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GdNzg-0001Nt-Qs for ops-area@ietf.org; Fri, 27 Oct 2006 05:27:18 -0400 Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51]) by co300216-ier2.net.avaya.com (Switch-3.1.8/Switch-3.1.7) with ESMTP id k9R9QRW0018610 for ; Fri, 27 Oct 2006 05:26:48 -0400 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: Fri, 27 Oct 2006 11:26:45 +0200 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: test Thread-Index: Acb5qgOe1AdZ1QAKQ1mU/xe1bgAEqQ== From: "Romascanu, Dan \(Dan\)" To: X-Scanner: InterScan AntiVirus for Sendmail X-Spam-Score: 1.8 (+) X-Scan-Signature: 2870a44b67ee17965ce5ad0177e150f4 Subject: [OPS-AREA] test X-BeenThere: ops-area@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: OPS Area e-mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: ops-area-bounces@ietf.org =20 _______________________________________________ OPS-AREA mailing list OPS-AREA@ietf.org https://www1.ietf.org/mailman/listinfo/ops-area From ops-area-bounces@ietf.org Fri Oct 27 05:59:45 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GdOUN-0000Y1-Qu; Fri, 27 Oct 2006 05:58:59 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GdOUL-0000Sz-HW for ops-area@ietf.org; Fri, 27 Oct 2006 05:58:57 -0400 Received: from nj300815-ier2.net.avaya.com ([198.152.12.103]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GdOUK-0006nM-7B for ops-area@ietf.org; Fri, 27 Oct 2006 05:58:57 -0400 Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51]) by nj300815-ier2.net.avaya.com (Switch-3.1.8/Switch-3.1.7) with ESMTP id k9R9wC1T031317 for ; Fri, 27 Oct 2006 05:58:29 -0400 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: Fri, 27 Oct 2006 11:58:31 +0200 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Update to Internet-Draft and RFC Boilerplate Thread-Index: Acb5ZrMWnBTeHOs7QmyN37JwRh1k0wAPzc7A From: "Romascanu, Dan \(Dan\)" To: X-Scanner: InterScan AntiVirus for Sendmail X-Spam-Score: 0.2 (/) X-Scan-Signature: f49c97ce49302a02285a2d36a99eef8c Subject: [OPS-AREA] FW: Update to Internet-Draft and RFC Boilerplate X-BeenThere: ops-area@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: OPS Area e-mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: ops-area-bounces@ietf.org =20 =20 -----Original Message----- From: IETF Chair [mailto:chair@ietf.org]=20 Sent: Friday, October 27, 2006 3:20 AM To: IETF Announcement list Subject: Update to Internet-Draft and RFC Boilerplate=20 A small update to BCP 78 was recently approved by the IESG as RFC 4748, to update the boilerplate (i.e., standard legal text) in RFCs and Internet-Drafts to recognize the IETF Trust as a rights holder, instead of ISOC. The actual boilerplate changes are given below this message. Starting as soon as reasonably possible, all authors of Internet-Drafts are requested to use the new boilerplate. The RFC Editor will in any case be inserting it in all RFCs issued from 2006-11-01. (The rights held by ISOC in older RFCs will be administratively transferred to the IETF Trust.) The public ID Nits checker already accepts I-Ds with old or new boilerplate. The Secretariat has started accepting I-Ds with old or new boilerplate XML2RFC version 1.32 will generate the new boilerplate. Users of I-D templates are requested to update them appropriately. http://www.ietf.org/ID-Checklist.html and http://www.ietf.org/ietf/1id-guidelines.html are being updated. Starting December, the public ID Nits checker will issue warnings for old boilerplate. Starting February 2007, the Secretariat will refuse the old boilerplate in Internet-Drafts. We are sorry for the inconvenience, but this change cannot be avoided. IETF Chair IETF Secretariat TOOLS Team -------- Copyright Notice (required for all IETF Documents) (Normally placed at the end of the IETF Document.) NOTE: by convention, the first line of the copyright statement is usually placed near the beginning of each document. This must also be updated. OLD "Copyright (C) The Internet Society (year). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights. NEW "Copyright (C) The IETF Trust (year). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights. Disclaimer (required in all IETF Documents) (Normally placed at the end of the IETF Document after the copyright notice.) OLD "This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE." NEW "This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE=20 IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE." Exceptions In MIB modules, PIB modules and similar material commonly extracted from IETF Documents, except for material that is being placed under IANA maintenance, the following abbreviated notice shall be included in the body of the material that will be extracted in lieu of the notices otherwise required by Section 5: OLD "Copyright (C) The Internet Society . This version of this MIB module is part of RFC XXXX; see the RFC itself for full legal notices." NEW "Copyright (C) The IETF Trust . This version of this MIB module is part of RFC XXXX; see the RFC itself for full legal notices." When the MIB or PIB module is the initial version of a module that is to be maintained by the IANA, the following abbreviated notice shall be included: OLD "Copyright (C) The Internet Society . The initial version of this MIB module was published in RFC XXXX; for full legal notices see the RFC itself. Supplementary information may be available at: http://www.ietf.org/copyrights/ianamib.html." NEW "Copyright (C) The IETF Trust . The initial version of this MIB module was published in RFC XXXX; for full legal notices see the RFC itself. Supplementary information may be available at: http://www.ietf.org/copyrights/ianamib.html." _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce _______________________________________________ OPS-AREA mailing list OPS-AREA@ietf.org https://www1.ietf.org/mailman/listinfo/ops-area From ops-area-bounces@ietf.org Sat Oct 28 01:14:38 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GdgVL-00018c-Ks; Sat, 28 Oct 2006 01:13:11 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GdgVK-000186-6J; Sat, 28 Oct 2006 01:13:10 -0400 Received: from shell4.bayarea.net ([209.128.82.1]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GdgVI-0000Rx-OF; Sat, 28 Oct 2006 01:13:10 -0400 Received: from shell4.bayarea.net (localhost [127.0.0.1]) by shell4.bayarea.net (8.13.6/8.13.6) with ESMTP id k9S5D0lK021272; Fri, 27 Oct 2006 22:13:00 -0700 Received: from localhost (heard@localhost) by shell4.bayarea.net (8.13.6/8.12.11/Submit) with ESMTP id k9S5Cxwm021264; Fri, 27 Oct 2006 22:13:00 -0700 X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs Date: Fri, 27 Oct 2006 22:12:59 -0700 (PDT) From: "C. M. Heard" X-Sender: heard@shell4.bayarea.net To: mib-doctors@ietf.org In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Score: 0.0 (/) X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15 Cc: ops-area@ietf.org Subject: [OPS-AREA] Re: [MIB-DOCTORS] FW: Update to Internet-Draft and RFC Boilerplate X-BeenThere: ops-area@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: OPS Area e-mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: ops-area-bounces@ietf.org On Fri, 27 Oct 2006, Romascanu, Dan (Dan) wrote: ... > From: IETF Chair [mailto:chair@ietf.org] > Sent: Friday, October 27, 2006 3:20 AM > To: IETF Announcement list > Subject: Update to Internet-Draft and RFC Boilerplate > > A small update to BCP 78 was recently approved by the IESG as RFC 4748, > to update the boilerplate (i.e., standard legal text) in RFCs and > Internet-Drafts to recognize the IETF Trust as a rights holder, instead > of ISOC. ... > In MIB modules, PIB modules and similar material commonly > extracted from IETF Documents, except for material that is being > placed under IANA maintenance, the following abbreviated notice > shall be included in the body of the material that will be > extracted in lieu of the notices otherwise required by Section 5: > > OLD > "Copyright (C) The Internet Society . This version of > this MIB module is part of RFC XXXX; see the RFC itself for > full legal notices." > > NEW > "Copyright (C) The IETF Trust . This version of > this MIB module is part of RFC XXXX; see the RFC itself for > full legal notices." > > When the MIB or PIB module is the initial version of a module that > is to be maintained by the IANA, the following abbreviated notice > shall be included: > > OLD > "Copyright (C) The Internet Society . The initial > version of this MIB module was published in RFC XXXX; for full > legal notices see the RFC itself. Supplementary information > may be available at: > http://www.ietf.org/copyrights/ianamib.html." > > NEW > "Copyright (C) The IETF Trust . The initial > version of this MIB module was published in RFC XXXX; for full > legal notices see the RFC itself. Supplementary information > may be available at: > http://www.ietf.org/copyrights/ianamib.html." Note that this obsoletes Section 3.7 of RFC 4181 (mib review guidelines). I was asleep at the switch when 4748 was last-called; I should have asked for that document to update BCP 111 also. Anyway, it looks like we probably need to update RFC 4181. I can't serve as editor anymore. Any takers? I do have some minor errata that haven't been posted on the RFC Editor or OPS web site; I can easily fish those out of my archives and send them to whoever takes over. Mike Heard P.S. If 4181 ever does get re-issued it would be a good idea to try to insulate it from the seemingly endless churn in the IPR documents (i.e., 3878, 3879, 4748, and their successors). _______________________________________________ OPS-AREA mailing list OPS-AREA@ietf.org https://www1.ietf.org/mailman/listinfo/ops-area From ops-area-bounces@ietf.org Mon Oct 30 03:17:47 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GeSJI-0002GT-M3; Mon, 30 Oct 2006 03:15:56 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GeSIz-00021L-A3; Mon, 30 Oct 2006 03:15:37 -0500 Received: from cirrus.av8.net ([130.105.36.66]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GeSIw-0005T0-Sc; Mon, 30 Oct 2006 03:15:37 -0500 Received: from piper.av8.net (piper.av8.net [130.105.11.2]) (authenticated bits=0) by cirrus.av8.net (8.12.11/8.12.11) with ESMTP id k9U8FEIr023256 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 30 Oct 2006 03:15:15 -0500 Date: Mon, 30 Oct 2006 03:15:14 -0500 (EST) From: Dean Anderson X-X-Sender: dean@piper.av8.net To: "Romascanu, Dan (Dan)" Subject: Re: [OPS-AREA] FW: Update to Internet-Draft and RFC Boilerplate In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Score: 1.0 (+) X-Scan-Signature: 3fbd9b434023f8abfcb1532abaec7a21 Cc: aaa-doctors@ietf.org, mib-doctors@ietf.org, ops-area@ietf.org X-BeenThere: ops-area@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: OPS Area e-mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: ops-area-bounces@ietf.org What exactly is the "IETF Trust"? --Dean On Fri, 27 Oct 2006, Romascanu, Dan (Dan) wrote: > > > > > > -----Original Message----- > From: IETF Chair [mailto:chair@ietf.org] > Sent: Friday, October 27, 2006 3:20 AM > To: IETF Announcement list > Subject: Update to Internet-Draft and RFC Boilerplate > > A small update to BCP 78 was recently approved by the IESG as RFC 4748, > to update the boilerplate (i.e., standard legal text) in RFCs and > Internet-Drafts to recognize the IETF Trust as a rights holder, instead > of ISOC. > > The actual boilerplate changes are given below this message. > > Starting as soon as reasonably possible, all authors of Internet-Drafts > are requested to use the new boilerplate. The RFC Editor will in any > case be inserting it in all RFCs issued from 2006-11-01. (The rights > held by ISOC in older RFCs will be administratively transferred to the > IETF > Trust.) > > The public ID Nits checker already accepts I-Ds with old or new > boilerplate. > The Secretariat has started accepting I-Ds with old or new boilerplate > > XML2RFC version 1.32 will generate the new boilerplate. > Users of I-D templates are requested to update them appropriately. > > http://www.ietf.org/ID-Checklist.html and > http://www.ietf.org/ietf/1id-guidelines.html are being updated. > > Starting December, the public ID Nits checker will issue warnings for > old boilerplate. > > Starting February 2007, the Secretariat will refuse the old boilerplate > in Internet-Drafts. > > We are sorry for the inconvenience, but this change cannot be avoided. > > IETF Chair > IETF Secretariat > TOOLS Team > > -------- > > Copyright Notice (required for all IETF Documents) > > (Normally placed at the end of the IETF Document.) > > NOTE: by convention, the first line of the copyright statement is > usually placed near the beginning of each document. This must also be > updated. > > OLD > "Copyright (C) The Internet Society (year). > > This document is subject to the rights, licenses and restrictions > contained in BCP 78, and except as set forth therein, the authors > retain all their rights. > > NEW > "Copyright (C) The IETF Trust (year). > > This document is subject to the rights, licenses and restrictions > contained in BCP 78, and except as set forth therein, the authors > retain all their rights. > > > Disclaimer (required in all IETF Documents) > > (Normally placed at the end of the IETF Document after the copyright > notice.) > > > OLD > "This document and the information contained herein are provided > on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE > REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND > THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, > EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT > THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR > ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A > PARTICULAR PURPOSE." > > > NEW > "This document and the information contained herein are provided > on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE > REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE > IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL > WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY > WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE > ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS > FOR A PARTICULAR PURPOSE." > > Exceptions > > In MIB modules, PIB modules and similar material commonly > extracted from IETF Documents, except for material that is being > placed under IANA maintenance, the following abbreviated notice > shall be included in the body of the material that will be > extracted in lieu of the notices otherwise required by Section 5: > > OLD > "Copyright (C) The Internet Society . This version of > this MIB module is part of RFC XXXX; see the RFC itself for > full legal notices." > > NEW > "Copyright (C) The IETF Trust . This version of > this MIB module is part of RFC XXXX; see the RFC itself for > full legal notices." > > When the MIB or PIB module is the initial version of a module that > is to be maintained by the IANA, the following abbreviated notice > shall be included: > > OLD > "Copyright (C) The Internet Society . The initial > version of this MIB module was published in RFC XXXX; for full > legal notices see the RFC itself. Supplementary information > may be available at: > http://www.ietf.org/copyrights/ianamib.html." > > NEW > "Copyright (C) The IETF Trust . The initial > version of this MIB module was published in RFC XXXX; for full > legal notices see the RFC itself. Supplementary information > may be available at: > http://www.ietf.org/copyrights/ianamib.html." > > _______________________________________________ > IETF-Announce mailing list > IETF-Announce@ietf.org > https://www1.ietf.org/mailman/listinfo/ietf-announce > > > _______________________________________________ > OPS-AREA mailing list > OPS-AREA@ietf.org > https://www1.ietf.org/mailman/listinfo/ops-area > > -- Av8 Internet Prepared to pay a premium for better service? www.av8.net faster, more reliable, better service 617 344 9000 _______________________________________________ OPS-AREA mailing list OPS-AREA@ietf.org https://www1.ietf.org/mailman/listinfo/ops-area From ops-area-bounces@ietf.org Mon Oct 30 03:58:37 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GeSy0-0004ZF-N8; Mon, 30 Oct 2006 03:58:00 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GeSxg-0004Xb-Re; Mon, 30 Oct 2006 03:57:40 -0500 Received: from co300216-ier2.net.avaya.com ([198.152.13.103]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GeSxc-0003jN-7A; Mon, 30 Oct 2006 03:57:40 -0500 Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51]) by co300216-ier2.net.avaya.com (Switch-3.1.8/Switch-3.1.7) with ESMTP id k9U8uumC028258; Mon, 30 Oct 2006 03:57:01 -0500 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 Subject: RE: [OPS-AREA] FW: Update to Internet-Draft and RFC Boilerplate Date: Mon, 30 Oct 2006 10:57:24 +0200 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [OPS-AREA] FW: Update to Internet-Draft and RFC Boilerplate Thread-Index: Acb7+5LJ+7C0Tb5CSQyloesCHHH4FAABIlYw From: "Romascanu, Dan \(Dan\)" To: "Dean Anderson" X-Scanner: InterScan AntiVirus for Sendmail X-Spam-Score: 0.2 (/) X-Scan-Signature: a743e34ab8eb08259de9a7307caed594 Cc: aaa-doctors@ietf.org, mib-doctors@ietf.org, ops-area@ietf.org X-BeenThere: ops-area@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: OPS Area e-mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: ops-area-bounces@ietf.org Dean, This announcement which was forwarded from the IETF Announcements list for the benefit of the ops-area, MIB doctors and AAA doctors that may not be subscribed there refers to RFC 4748, which describes the role of the IETF Trust (in Section 1).=20 Dan =20 =20 > -----Original Message----- > From: Dean Anderson [mailto:dean@av8.com]=20 > Sent: Monday, October 30, 2006 10:15 AM > To: Romascanu, Dan (Dan) > Cc: ops-area@ietf.org; mib-doctors@ietf.org; aaa-doctors@ietf.org > Subject: Re: [OPS-AREA] FW: Update to Internet-Draft and RFC=20 > Boilerplate=20 >=20 > What exactly is the "IETF Trust"? >=20 > --Dean >=20 > On Fri, 27 Oct 2006, Romascanu, Dan (Dan) wrote: >=20 > > =20 > >=20 > >=20 > > =20 > >=20 > > -----Original Message----- > > From: IETF Chair [mailto:chair@ietf.org] > > Sent: Friday, October 27, 2006 3:20 AM > > To: IETF Announcement list > > Subject: Update to Internet-Draft and RFC Boilerplate > >=20 > > A small update to BCP 78 was recently approved by the IESG as RFC=20 > > 4748, to update the boilerplate (i.e., standard legal text) in RFCs=20 > > and Internet-Drafts to recognize the IETF Trust as a rights holder,=20 > > instead of ISOC. > >=20 > > The actual boilerplate changes are given below this message. > >=20 > > Starting as soon as reasonably possible, all authors of=20 > > Internet-Drafts are requested to use the new boilerplate. The RFC=20 > > Editor will in any case be inserting it in all RFCs issued from=20 > > 2006-11-01. (The rights held by ISOC in older RFCs will be=20 > > administratively transferred to the IETF > > Trust.) > >=20 > > The public ID Nits checker already accepts I-Ds with old or new=20 > > boilerplate. > > The Secretariat has started accepting I-Ds with old or new=20 > boilerplate > >=20 > > XML2RFC version 1.32 will generate the new boilerplate. > > Users of I-D templates are requested to update them appropriately. > >=20 > > http://www.ietf.org/ID-Checklist.html and=20 > > http://www.ietf.org/ietf/1id-guidelines.html are being updated. > >=20 > > Starting December, the public ID Nits checker will issue=20 > warnings for=20 > > old boilerplate. > >=20 > > Starting February 2007, the Secretariat will refuse the old=20 > > boilerplate in Internet-Drafts. > >=20 > > We are sorry for the inconvenience, but this change cannot=20 > be avoided. > >=20 > > IETF Chair > > IETF Secretariat > > TOOLS Team > >=20 > > -------- > >=20 > > Copyright Notice (required for all IETF Documents) > >=20 > > (Normally placed at the end of the IETF Document.) > >=20 > > NOTE: by convention, the first line of the copyright statement is=20 > > usually placed near the beginning of each document. This=20 > must also be=20 > > updated. > >=20 > > OLD > > "Copyright (C) The Internet Society (year). > >=20 > > This document is subject to the rights, licenses and=20 > restrictions > > contained in BCP 78, and except as set forth therein,=20 > the authors > > retain all their rights. > >=20 > > NEW > > "Copyright (C) The IETF Trust (year). > >=20 > > This document is subject to the rights, licenses and=20 > restrictions > > contained in BCP 78, and except as set forth therein,=20 > the authors > > retain all their rights. > >=20 > >=20 > > Disclaimer (required in all IETF Documents) > >=20 > > (Normally placed at the end of the IETF Document after=20 > the copyright > > notice.) > >=20 > >=20 > > OLD > > "This document and the information contained herein=20 > are provided > > on an "AS IS" basis and THE CONTRIBUTOR, THE=20 > ORGANIZATION HE/SHE > > REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET=20 > SOCIETY AND > > THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, > > EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY=20 > WARRANTY THAT > > THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE=20 > ANY RIGHTS OR > > ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A > > PARTICULAR PURPOSE." > >=20 > >=20 > > NEW > > "This document and the information contained herein=20 > are provided > > on an "AS IS" basis and THE CONTRIBUTOR, THE=20 > ORGANIZATION HE/SHE > > REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET=20 > SOCIETY, THE=20 > > IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE=20 > DISCLAIM ALL > > WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT=20 > LIMITED TO ANY > > WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL=20 > NOT INFRINGE > > ANY RIGHTS OR ANY IMPLIED WARRANTIES OF=20 > MERCHANTABILITY OR FITNESS > > FOR A PARTICULAR PURPOSE." > >=20 > > Exceptions > >=20 > > In MIB modules, PIB modules and similar material commonly > > extracted from IETF Documents, except for material=20 > that is being > > placed under IANA maintenance, the following=20 > abbreviated notice > > shall be included in the body of the material that will be > > extracted in lieu of the notices otherwise required=20 > by Section 5: > >=20 > > OLD > > "Copyright (C) The Internet Society . This=20 > version of > > this MIB module is part of RFC XXXX; see the RFC itself for > > full legal notices." > >=20 > > NEW > > "Copyright (C) The IETF Trust . This version of > > this MIB module is part of RFC XXXX; see the RFC itself for > > full legal notices." > >=20 > > When the MIB or PIB module is the initial version of=20 > a module that > > is to be maintained by the IANA, the following=20 > abbreviated notice > > shall be included: > >=20 > > OLD > > "Copyright (C) The Internet Society . The initial > > version of this MIB module was published in RFC=20 > XXXX; for full > > legal notices see the RFC itself. Supplementary=20 > information > > may be available at: > > http://www.ietf.org/copyrights/ianamib.html." > >=20 > > NEW > > "Copyright (C) The IETF Trust . The initial > > version of this MIB module was published in RFC=20 > XXXX; for full > > legal notices see the RFC itself. Supplementary=20 > information > > may be available at: > > http://www.ietf.org/copyrights/ianamib.html." > >=20 > > _______________________________________________ > > IETF-Announce mailing list > > IETF-Announce@ietf.org > > https://www1.ietf.org/mailman/listinfo/ietf-announce > >=20 > >=20 > > _______________________________________________ > > OPS-AREA mailing list > > OPS-AREA@ietf.org > > https://www1.ietf.org/mailman/listinfo/ops-area > >=20 > >=20 >=20 > --=20 > Av8 Internet Prepared to pay a premium for better service? > www.av8.net faster, more reliable, better service > 617 344 9000 =20 >=20 >=20 >=20 _______________________________________________ OPS-AREA mailing list OPS-AREA@ietf.org https://www1.ietf.org/mailman/listinfo/ops-area