Re: RFC 5378 representation

Fred Baker <fred@cisco.com> Fri, 19 December 2008 17:38 UTC

Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietf-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 32B5F28C147; Fri, 19 Dec 2008 09:38:14 -0800 (PST)
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 12FE03A6958 for <ietf@core3.amsl.com>; Thu, 18 Dec 2008 15:10:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.01
X-Spam-Level:
X-Spam-Status: No, score=-106.01 tagged_above=-999 required=5 tests=[AWL=-0.296, BAYES_00=-2.599, HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H9fU+MwISRcr for <ietf@core3.amsl.com>; Thu, 18 Dec 2008 15:10:33 -0800 (PST)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by core3.amsl.com (Postfix) with ESMTP id D93363A63EB for <ietf@ietf.org>; Thu, 18 Dec 2008 15:10:33 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.36,245,1228089600"; d="scan'208,217";a="124768920"
Received: from sj-dkim-1.cisco.com ([171.71.179.21]) by sj-iport-3.cisco.com with ESMTP; 18 Dec 2008 23:10:26 +0000
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254]) by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id mBINAQt0019011 for <ietf@ietf.org>; Thu, 18 Dec 2008 15:10:26 -0800
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id mBINAIeo016061 for <ietf@ietf.org>; Thu, 18 Dec 2008 23:10:26 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 18 Dec 2008 15:10:15 -0800
Received: from stealth-10-32-244-219.cisco.com ([10.32.244.219]) by xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 18 Dec 2008 15:10:14 -0800
Message-Id: <9C69123B-AC66-4435-8880-351CAA12EF8C@cisco.com>
From: Fred Baker <fred@cisco.com>
To: IETF discussion list <ietf@ietf.org>
In-Reply-To: <5F20691E-AC69-4A06-8F3F-1DEB0E3578AE@cisco.com>
Mime-Version: 1.0 (Apple Message framework v930.3)
Subject: Re: RFC 5378 representation
Date: Thu, 18 Dec 2008 15:10:13 -0800
References: <9DFF8BF6-6125-4126-9896-EC0D4E59CE8E@cisco.com> <5F20691E-AC69-4A06-8F3F-1DEB0E3578AE@cisco.com>
X-Mailer: Apple Mail (2.930.3)
X-OriginalArrivalTime: 18 Dec 2008 23:10:14.0553 (UTC) FILETIME=[C8D17090:01C96165]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=29647; t=1229641826; x=1230505826; c=relaxed/simple; s=sjdkim1004; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=fred@cisco.com; z=From:=20Fred=20Baker=20<fred@cisco.com> |Subject:=20Re=3A=20RFC=205378=20representation |Sender:=20; bh=DByHd0tpqOG0mvFoARidcgIFNkRQUD5fgwWhDs3dX+0=; b=f93VUKIm5mz8fWfzh3axBJSPAe+cTO2H+re5Z9iDo6YE1Xwf0t1kC7OyZw +plHdn+NT567DAaBPvrZMN57QlEHCSpOZsxU/ar3EAp6cuX2Jm5qZI80Asmq gJYjV9qq2nFQPagYddUSs+vtokqb8zBhrMV/yrZz9PUyAk2ZBALzI=;
Authentication-Results: sj-dkim-1; header.From=fred@cisco.com; dkim=pass ( sig from cisco.com/sjdkim1004 verified; );
X-Mailman-Approved-At: Fri, 19 Dec 2008 09:38:12 -0800
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0066735065=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

So, having just cleared this note with the Trustees, sending it in,  
and forwarding the note to the IETF list, I observe http://trustee.ietf.org/docs/Contributor_Non-Exclusive_License_RFC5378.pdf 
.

By all means, folks, use the form.

<!@#$%^>

On Dec 18, 2008, at 2:58 PM, Fred Baker wrote:

> For the record, I have sent the following email to the IAD, signed  
> using my PGP key. I would encourage others to send similar notes.
>
>
>
>> From: Fred Baker <fred@cisco.com>
>> Date: December 18, 2008 2:56:20 PM PST
>> To: iad@ietf.org
>> Cc: Trustees <trustees@ietf.org>
>> Subject: RFC 5378 representation
>>
>> I, Fred Baker, am one of the authors or editors of a variety of  
>> RFCs whose publication pre-dates RFC 5378, noted at the end of this  
>> email. I speak for myself, but not for my co-authors or co-editors  
>> or any current or previous employer.
>>
>> I have always understood that work that I did in the community and  
>> contributions that I made to it belonged to the community. In one  
>> case, the community asked me to describe an algorithm that my  
>> employer described in a web page in an internet draft; On that, I  
>> did not seek my employer's release, and so did not authorize  
>> derivative works from that internet draft (http://tools.ietf.org/html/draft-baker-sava-cisco-ip-source-guard 
>> ). In all other cases, I authorize the IETF to produce works  
>> derivative from my past efforts, and disclaim any rights that would  
>> prevent it from doing so.
>> RFC 1220
>> Point-to-Point Protocol extensions for bridging. F. Baker. April 1  
>> 1991. (Format: TXT=38165 bytes) (Obsoleted by RFC 1638) (Status:  
>> PROPOSED STANDARD)
>> RFC 1232
>> Definitions of managed objects for the DS1 Interface type. F.  
>> Baker, C.P. Kolb. May 1991. (Format: TXT=60757 bytes) (Obsoleted by  
>> RFC 1406) (Updated by RFC 1239) (Status: PROPOSED STANDARD)
>> RFC 1248
>> OSPF Version 2 Management Information Base. F. Baker, R. Coltun.  
>> July 1991. (Format: TXT=74347 bytes) (Obsoleted by RFC 1252)  
>> (Updated by RFC 1349) (Status: PROPOSED STANDARD)
>> RFC 1252
>> OSPF Version 2 Management Information Base. F. Baker, R. Coltun.  
>> August 1991. (Format: TXT=74471 bytes) (Obsoletes RFC 1248)  
>> (Obsoleted by RFC 1253) (Also RFC 1247, RFC 1245) (Status: PROPOSED  
>> STANDARD)
>> RFC 1253
>> OSPF Version 2 Management Information Base. F. Baker, R. Coltun.  
>> August 1991. (Format: TXT=74453 bytes) (Obsoletes RFC 1252)  
>> (Obsoleted by RFC 1850) (Also RFC 1247, RFC 1245, RFC 1246)  
>> (Status: PROPOSED STANDARD)
>> RFC 1315
>> Management Information Base for Frame Relay DTEs. C. Brown, F.  
>> Baker, C. Carvalho. April 1992. (Format: TXT=33825 bytes)  
>> (Obsoleted by RFC 2115) (Status: PROPOSED STANDARD)
>> RFC 1354
>> IP Forwarding Table MIB. F. Baker. July 1992. (Format: TXT=24905  
>> bytes) (Obsoleted by RFC 2096) (Status: PROPOSED STANDARD)
>> RFC 1381
>> SNMP MIB Extension for X.25 LAPB. D. Throop, F. Baker. November  
>> 1992. (Format: TXT=71253 bytes) (Status: PROPOSED STANDARD)
>> RFC 1389
>> RIP Version 2 MIB Extensions. G. Malkin, F. Baker. January 1993.  
>> (Format: TXT=23569 bytes) (Obsoleted by RFC 1724) (Status: PROPOSED  
>> STANDARD)
>> RFC 1406
>> Definitions of Managed Objects for the DS1 and E1 Interface Types.  
>> F. Baker, J. Watt, Eds.. January 1993. (Format: TXT=97559 bytes)  
>> (Obsoletes RFC 1232) (Obsoleted by RFC 2495) (Status: PROPOSED  
>> STANDARD)
>> RFC 1638
>> PPP Bridging Control Protocol (BCP). F. Baker, R. Bowen. June 1994.  
>> (Format: TXT=58477 bytes) (Obsoletes RFC 1220) (Obsoleted by RFC  
>> 2878) (Status: PROPOSED STANDARD)
>> RFC 1724
>> RIP Version 2 MIB Extension. G. Malkin, F. Baker. November 1994.  
>> (Format: TXT=29645 bytes) (Obsoletes RFC 1389) (Status: DRAFT  
>> STANDARD)
>> RFC 1749
>> IEEE 802.5 Station Source Routing MIB using SMIv2. K. McCloghrie,  
>> F. Baker, E. Decker. December 1994. (Format: TXT=17563 bytes)  
>> (Updates RFC 1748) (Status: HISTORIC)
>> RFC 1812
>> Requirements for IP Version 4 Routers. F. Baker, Ed.. June 1995.  
>> (Format: TXT=415740 bytes) (Obsoletes RFC 1716, RFC 1009) (Updated  
>> by RFC 2644) (Status: PROPOSED STANDARD)
>> RFC 1850
>> OSPF Version 2 Management Information Base. F. Baker, R. Coltun.  
>> November 1995. (Format: TXT=140255 bytes) (Obsoletes RFC 1253)  
>> (Obsoleted by RFC 4750) (Status: DRAFT STANDARD)
>> RFC 2082
>> RIP-2 MD5 Authentication. F. Baker, R. Atkinson. January 1997.  
>> (Format: TXT=25436 bytes) (Obsoleted by RFC 4822) (Status: PROPOSED  
>> STANDARD)
>> RFC 2096
>> IP Forwarding Table MIB. F. Baker. January 1997. (Format: TXT=35930  
>> bytes) (Obsoletes RFC 1354) (Obsoleted by RFC 4292) (Status:  
>> PROPOSED STANDARD)
>> RFC 2115
>> Management Information Base for Frame Relay DTEs Using SMIv2. C.  
>> Brown, F. Baker. September 1997. (Format: TXT=59950 bytes)  
>> (Obsoletes RFC 1315) (Status: DRAFT STANDARD)
>> RFC 2206
>> RSVP Management Information Base using SMIv2. F. Baker, J.  
>> Krawczyk, A. Sastry. September 1997. (Format: TXT=112937 bytes)  
>> (Status: PROPOSED STANDARD)
>> RFC 2208
>> Resource ReSerVation Protocol (RSVP) -- Version 1 Applicability  
>> Statement Some Guidelines on Deployment. A. Mankin, Ed., F. Baker,  
>> B. Braden, S. Bradner, M. O`Dell, A. Romanow, A. Weinrib, L. Zhang.  
>> September 1997. (Format: TXT=14289 bytes) (Status: INFORMATIONAL)
>> RFC 2213
>> Integrated Services Management Information Base using SMIv2. F.  
>> Baker, J. Krawczyk, A. Sastry. September 1997. (Format: TXT=36147  
>> bytes) (Status: PROPOSED STANDARD)
>> RFC 2214
>> Integrated Services Management Information Base Guaranteed Service  
>> Extensions using SMIv2. F. Baker, J. Krawczyk, A. Sastry. September  
>> 1997. (Format: TXT=15971 bytes) (Status: PROPOSED STANDARD)
>> RFC 2382
>> A Framework for Integrated Services and RSVP over ATM. E. Crawley,  
>> Ed., L. Berger, S. Berson, F. Baker, M. Borden, J. Krawczyk. August  
>> 1998. (Format: TXT=73865 bytes) (Status: INFORMATIONAL)
>> RFC 2474
>> Definition of the Differentiated Services Field (DS Field) in the  
>> IPv4 and IPv6 Headers. K. Nichols, S. Blake, F. Baker, D. Black.  
>> December 1998. (Format: TXT=50576 bytes) (Obsoletes RFC 1455, RFC  
>> 1349) (Updated by RFC 3168, RFC 3260) (Status: PROPOSED STANDARD)
>> RFC 2597
>> Assured Forwarding PHB Group. J. Heinanen, F. Baker, W. Weiss, J.  
>> Wroclawski. June 1999. (Format: TXT=24068 bytes) (Updated by RFC  
>> 3260) (Status: PROPOSED STANDARD)
>> RFC 2747
>> RSVP Cryptographic Authentication. F. Baker, B. Lindell, M. Talwar.  
>> January 2000. (Format: TXT=49477 bytes) (Updated by RFC 3097)  
>> (Status: PROPOSED STANDARD)
>> RFC 2804
>> IETF Policy on Wiretapping. IAB, IESG. May 2000. (Format: TXT=18934  
>> bytes) (Status: INFORMATIONAL)
>> RFC 2814
>> SBM (Subnet Bandwidth Manager): A Protocol for RSVP-based Admission  
>> Control over IEEE 802-style networks. R. Yavatkar, D. Hoffman, Y.  
>> Bernet, F. Baker, M. Speer. May 2000. (Format: TXT=141886 bytes)  
>> (Status: PROPOSED STANDARD)
>> RFC 2860
>> Memorandum of Understanding Concerning the Technical Work of the  
>> Internet Assigned Numbers Authority. B. Carpenter, F. Baker, M.  
>> Roberts. June 2000. (Format: TXT=12361 bytes) (Status: INFORMATIONAL)
>> RFC 2998
>> A Framework for Integrated Services Operation over Diffserv  
>> Networks. Y. Bernet, P. Ford, R. Yavatkar, F. Baker, L. Zhang, M.  
>> Speer, R. Braden, B. Davie, J. Wroclawski, E. Felstaine. November  
>> 2000. (Format: TXT=76378 bytes) (Status: INFORMATIONAL)
>> RFC 3175
>> Aggregation of RSVP for IPv4 and IPv6 Reservations. F. Baker, C.  
>> Iturralde, F. Le Faucheur, B. Davie. September 2001. (Format:  
>> TXT=88681 bytes) (Status: PROPOSED STANDARD)
>> RFC 3289
>> Management Information Base for the Differentiated Services  
>> Architecture. F. Baker, K. Chan, A. Smith. May 2002. (Format:  
>> TXT=239041 bytes) (Status: PROPOSED STANDARD)
>> RFC 3518
>> Point-to-Point Protocol (PPP) Bridging Control Protocol (BCP). M.  
>> Higashiyama, F. Baker, T. Liao. April 2003. (Format: TXT=82102  
>> bytes) (Obsoletes RFC 2878) (Status: PROPOSED STANDARD)
>> RFC 3704
>> Ingress Filtering for Multihomed Networks. F. Baker, P. Savola.  
>> March 2004. (Format: TXT=35942 bytes) (Updates RFC 2827) (Also  
>> BCP0084) (Status: BEST CURRENT PRACTICE)
>> RFC 3716
>> The IETF in the Large: Administration and Execution. IAB Advisory  
>> Committee. March 2004. (Format: TXT=91326 bytes) (Status:  
>> INFORMATIONAL)
>> RFC 3924
>> Cisco Architecture for Lawful Intercept in IP Networks. F. Baker,  
>> B. Foster, C. Sharp. October 2004. (Format: TXT=40826 bytes)  
>> (Status: INFORMATIONAL)
>> RFC 4053
>> Procedures for Handling Liaison Statements to and from the IETF. S.  
>> Trowbridge, S. Bradner, F. Baker. April 2005. (Format: TXT=38816  
>> bytes) (Also BCP0103) (Status: BEST CURRENT PRACTICE)
>> RFC 4192
>> Procedures for Renumbering an IPv6 Network without a Flag Day. F.  
>> Baker, E. Lear, R. Droms. September 2005. (Format: TXT=52110 bytes)  
>> (Updates RFC 2072) (Status: INFORMATIONAL)
>> RFC 4542
>> Implementing an Emergency Telecommunications Service (ETS) for Real- 
>> Time Services in the Internet Protocol Suite. F. Baker, J. Polk.  
>> May 2006. (Format: TXT=99770 bytes) (Status: INFORMATIONAL)
>> RFC 4594
>> Configuration Guidelines for DiffServ Service Classes. J. Babiarz,  
>> K. Chan, F. Baker. August 2006. (Format: TXT=144044 bytes) (Status:  
>> INFORMATIONAL)
>> RFC 4750
>> OSPF Version 2 Management Information Base. D. Joyal, Ed., P.  
>> Galecki, Ed., S. Giacalone, Ed., R. Coltun, F. Baker. December  
>> 2006. (Format: TXT=222459 bytes) (Obsoletes RFC 1850) (Status:  
>> PROPOSED STANDARD)
>> RFC 4923
>> Quality of Service (QoS) Signaling in a Nested Virtual Private  
>> Network. F. Baker, P. Bose. August 2007. (Format: TXT=92632 bytes)  
>> (Status: INFORMATIONAL)
>> RFC 5127
>> Aggregation of DiffServ Service Classes. K. Chan, J. Babiarz, F.  
>> Baker. February 2008. (Format: TXT=43751 bytes) (Status:  
>> INFORMATIONAL)
>


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