From jmh@joelhalpern.com Thu Jul 5 09:39:42 2012 Return-Path: X-Original-To: karp@ietfa.amsl.com Delivered-To: karp@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC96621F875C for ; Thu, 5 Jul 2012 09:39:42 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.387 X-Spam-Level: X-Spam-Status: No, score=-102.387 tagged_above=-999 required=5 tests=[AWL=-0.122, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZqGV36UqoO+Y for ; Thu, 5 Jul 2012 09:39:42 -0700 (PDT) Received: from morbo.mail.tigertech.net (morbo.mail.tigertech.net [67.131.251.54]) by ietfa.amsl.com (Postfix) with ESMTP id 1A23421F8602 for ; Thu, 5 Jul 2012 09:39:42 -0700 (PDT) Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) by morbo.tigertech.net (Postfix) with ESMTP id 9C301557F2C for ; Thu, 5 Jul 2012 09:39:55 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id DCBC81C9BE9 for ; Thu, 5 Jul 2012 09:39:54 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net Received: from [10.10.10.105] (pool-71-161-50-10.clppva.btas.verizon.net [71.161.50.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 5FD711C9BE5 for ; Thu, 5 Jul 2012 09:39:54 -0700 (PDT) Message-ID: <4FF5C351.3020204@joelhalpern.com> Date: Thu, 05 Jul 2012 12:39:45 -0400 From: Joel Halpern User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1 MIME-Version: 1.0 To: "karp@ietf.org" References: <4FEE33BE.7080609@joelhalpern.com> In-Reply-To: <4FEE33BE.7080609@joelhalpern.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [karp] WG LC: draft-ietf-karp-routing-tcp-analysis-02 to Informational X-BeenThere: karp@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Discussion list for key management for routing and transport protocols List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jul 2012 16:39:43 -0000 While the WG looks and this document, and the authors respond to the one comment we have received (which is helpful and appreciated), I need to take care of one bit of related procedure. Does anyone know of any unfiled IPR against this document? If so, please contact me, or file an appropriate IPR disclosure. To avoid problems, I also need each of the authors to explicitly confirm that all IPR on this document of which they are aware has been disclosed. The line from the shepherd writeup is: (7) Has each author confirmed that any and all appropriate IPR disclosures required for full conformance with the provisions of BCP 78 and BCP 79 have already been filed. Thank you, Joel M. Halpern, as KARP co-chair. On 6/29/2012 7:01 PM, Joel M. Halpern wrote: > This beings a two week WG last call to determine if folk support > submitting the draft: > http://datatracker.ietf.org/doc/draft-ietf-karp-routing-tcp-analysis/?include_text=1 > > to our AD for publication as an Informational RFC. > > Please send comments of support, or raising issues or concerns, to the > WG email list. (Comments with explanation are much more useful than > those without.) > > Given the weekend, the LC will run till 8pm PDT on 16-July-2012. > > Thank you, > Joel M. Halpern > and Brian Weis > co-chairs From vero.zheng@huawei.com Thu Jul 5 18:18:15 2012 Return-Path: X-Original-To: karp@ietfa.amsl.com Delivered-To: karp@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A2E7D11E810D for ; Thu, 5 Jul 2012 18:18:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 2.619 X-Spam-Level: ** X-Spam-Status: No, score=2.619 tagged_above=-999 required=5 tests=[AWL=-0.169, BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, CN_BODY_35=0.339, MIME_8BIT_HEADER=0.3, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-4, SARE_SUB_ENC_GB2312=1.345] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rhAKQYxuu4Jo for ; Thu, 5 Jul 2012 18:18:15 -0700 (PDT) Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id 0471611E8106 for ; Thu, 5 Jul 2012 18:18:14 -0700 (PDT) Received: from 172.18.9.243 (EHLO dfweml202-edg.china.huawei.com) ([172.18.9.243]) by dfwrg01-dlp.huawei.com (MOS 4.2.3-GA FastPath) with ESMTP id AHT19458; Thu, 05 Jul 2012 21:18:29 -0400 (EDT) Received: from DFWEML405-HUB.china.huawei.com (10.193.5.102) by dfweml202-edg.china.huawei.com (172.18.9.108) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 5 Jul 2012 18:18:05 -0700 Received: from SZXEML421-HUB.china.huawei.com (10.82.67.160) by dfweml405-hub.china.huawei.com (10.193.5.102) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 5 Jul 2012 18:18:03 -0700 Received: from SZXEML520-MBX.china.huawei.com ([169.254.1.66]) by szxeml421-hub.china.huawei.com ([10.82.67.160]) with mapi id 14.01.0323.003; Fri, 6 Jul 2012 09:17:58 +0800 From: Vero Zheng To: Joel Halpern , "karp@ietf.org" Thread-Topic: [karp] WG LC: draft-ietf-karp-routing-tcp-analysis-02 to Informational Thread-Index: AQHNWxUsz7nSrixGOUmKM86yM2xskg== Date: Fri, 6 Jul 2012 01:17:57 +0000 Message-ID: <2EEA459CD95CCB4988BFAFC0F2287B5C2C92025A@SZXEML520-MBX.china.huawei.com> References: <4FEE33BE.7080609@joelhalpern.com> <4FF5C351.3020204@joelhalpern.com> In-Reply-To: <4FF5C351.3020204@joelhalpern.com> Accept-Language: zh-CN, en-US Content-Language: zh-CN X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.111.99.57] Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: base64 MIME-Version: 1.0 X-CFilter-Loop: Reflected Subject: [karp] =?gb2312?b?tPC4tDogIFdHIExDOiBkcmFmdC1pZXRmLWthcnAtcm91?= =?gb2312?b?dGluZy10Y3AtYW5hbHlzaXMtMDIgdG8gSW5mb3JtYXRpb25hbA==?= X-BeenThere: karp@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Discussion list for key management for routing and transport protocols List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Jul 2012 01:18:15 -0000 Sm9lbCwNCg0KU3BlYWtpbmcgYXMgYSBjby1hdXRob3IsIEknbSBub3QgYXdhcmUgb2YgYW4gSVBS IGFwcGxpZXMgdG8gdGhpcyBkcmFmdC4NCg0KQlIsDQpWZXJvDQoNCi0tLS0t08q8/tStvP4tLS0t LQ0Kt6K8/sjLOiBrYXJwLWJvdW5jZXNAaWV0Zi5vcmcgW21haWx0bzprYXJwLWJvdW5jZXNAaWV0 Zi5vcmddILT6se0gSm9lbCBIYWxwZXJuDQq3osvNyrG85DogMjAxMsTqN9TCNsjVIDA6NDANCsrV vP7Iyzoga2FycEBpZXRmLm9yZw0K1vfM4jogUmU6IFtrYXJwXSBXRyBMQzogZHJhZnQtaWV0Zi1r YXJwLXJvdXRpbmctdGNwLWFuYWx5c2lzLTAyIHRvIEluZm9ybWF0aW9uYWwNCg0KV2hpbGUgdGhl IFdHIGxvb2tzIGFuZCB0aGlzIGRvY3VtZW50LCBhbmQgdGhlIGF1dGhvcnMgcmVzcG9uZCB0byB0 aGUgb25lIA0KY29tbWVudCB3ZSBoYXZlIHJlY2VpdmVkICh3aGljaCBpcyBoZWxwZnVsIGFuZCBh cHByZWNpYXRlZCksIEkgbmVlZCB0byANCnRha2UgY2FyZSBvZiBvbmUgYml0IG9mIHJlbGF0ZWQg cHJvY2VkdXJlLg0KDQpEb2VzIGFueW9uZSBrbm93IG9mIGFueSB1bmZpbGVkIElQUiBhZ2FpbnN0 IHRoaXMgZG9jdW1lbnQ/DQpJZiBzbywgcGxlYXNlIGNvbnRhY3QgbWUsIG9yIGZpbGUgYW4gYXBw cm9wcmlhdGUgSVBSIGRpc2Nsb3N1cmUuDQoNClRvIGF2b2lkIHByb2JsZW1zLCBJIGFsc28gbmVl ZCBlYWNoIG9mIHRoZSBhdXRob3JzIHRvIGV4cGxpY2l0bHkgY29uZmlybSANCnRoYXQgYWxsIElQ UiBvbiB0aGlzIGRvY3VtZW50IG9mIHdoaWNoIHRoZXkgYXJlIGF3YXJlIGhhcyBiZWVuIGRpc2Ns b3NlZC4NCg0KVGhlIGxpbmUgZnJvbSB0aGUgc2hlcGhlcmQgd3JpdGV1cCBpczoNCig3KSBIYXMg ZWFjaCBhdXRob3IgY29uZmlybWVkIHRoYXQgYW55IGFuZCBhbGwgYXBwcm9wcmlhdGUgSVBSDQpk aXNjbG9zdXJlcyByZXF1aXJlZCBmb3IgZnVsbCBjb25mb3JtYW5jZSB3aXRoIHRoZSBwcm92aXNp b25zIG9mIEJDUCA3OA0KYW5kIEJDUCA3OSBoYXZlIGFscmVhZHkgYmVlbiBmaWxlZC4NCg0KVGhh bmsgeW91LA0KSm9lbCBNLiBIYWxwZXJuLCBhcyBLQVJQIGNvLWNoYWlyLg0KDQoNCk9uIDYvMjkv MjAxMiA3OjAxIFBNLCBKb2VsIE0uIEhhbHBlcm4gd3JvdGU6DQo+IFRoaXMgYmVpbmdzIGEgdHdv IHdlZWsgV0cgbGFzdCBjYWxsIHRvIGRldGVybWluZSBpZiBmb2xrIHN1cHBvcnQNCj4gc3VibWl0 dGluZyB0aGUgZHJhZnQ6DQo+IGh0dHA6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQt aWV0Zi1rYXJwLXJvdXRpbmctdGNwLWFuYWx5c2lzLz9pbmNsdWRlX3RleHQ9MQ0KPg0KPiB0byBv dXIgQUQgZm9yIHB1YmxpY2F0aW9uIGFzIGFuIEluZm9ybWF0aW9uYWwgUkZDLg0KPg0KPiBQbGVh c2Ugc2VuZCBjb21tZW50cyBvZiBzdXBwb3J0LCBvciByYWlzaW5nIGlzc3VlcyBvciBjb25jZXJu cywgdG8gdGhlDQo+IFdHIGVtYWlsIGxpc3QuICAoQ29tbWVudHMgd2l0aCBleHBsYW5hdGlvbiBh cmUgbXVjaCBtb3JlIHVzZWZ1bCB0aGFuDQo+IHRob3NlIHdpdGhvdXQuKQ0KPg0KPiBHaXZlbiB0 aGUgd2Vla2VuZCwgdGhlIExDIHdpbGwgcnVuIHRpbGwgOHBtIFBEVCBvbiAxNi1KdWx5LTIwMTIu DQo+DQo+IFRoYW5rIHlvdSwNCj4gSm9lbCBNLiBIYWxwZXJuDQo+IGFuZCBCcmlhbiBXZWlzDQo+ IGNvLWNoYWlycw0KDQoNCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fDQprYXJwIG1haWxpbmcgbGlzdA0Ka2FycEBpZXRmLm9yZw0KaHR0cHM6Ly93d3cuaWV0 Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9rYXJwDQo= From touch@isi.edu Fri Jul 6 16:38:00 2012 Return-Path: X-Original-To: karp@ietfa.amsl.com Delivered-To: karp@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B6CE611E8089; Fri, 6 Jul 2012 16:38:00 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.511 X-Spam-Level: X-Spam-Status: No, score=-103.511 tagged_above=-999 required=5 tests=[AWL=-0.912, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eWoAVRtJnZfV; Fri, 6 Jul 2012 16:38:00 -0700 (PDT) Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by ietfa.amsl.com (Postfix) with ESMTP id 282A021F8636; Fri, 6 Jul 2012 16:38:00 -0700 (PDT) Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id q66Nbxdx013559 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 6 Jul 2012 16:37:59 -0700 (PDT) Message-ID: <4FF776D7.9040808@isi.edu> Date: Fri, 06 Jul 2012 16:37:59 -0700 From: Joe Touch User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1 MIME-Version: 1.0 To: internet-drafts@ietf.org References: <20120624002843.17335.73994.idtracker@ietfa.amsl.com> In-Reply-To: <20120624002843.17335.73994.idtracker@ietfa.amsl.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: touch@isi.edu Cc: karp@ietf.org, i-d-announce@ietf.org Subject: Re: [karp] I-D Action: draft-ietf-karp-routing-tcp-analysis-02.txt X-BeenThere: karp@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Discussion list for key management for routing and transport protocols List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Jul 2012 23:38:00 -0000 Hi, all, I note that this doc has numerous places where it refers to either TCP MD5 or TCP AO that need attention. A full pass would be useful. Some cursory observations follow to kickoff such a pass. Joe This doc continues to refer to TCP MD5, but fails to note that this protocol has been deprecated. It'd be useful to indicate that clearly, even noting that it remains in use if necessary. Sec 2.2 discusses problems changing keys with TCP MD5, but should also then note that this has been overcome in TCP AO, whether using manual keying or an out-of-band KMP. Sec 2.3.1.2 suggests use of a stronger hashing algorithm (implied within TCP MD5). It should not suggest an alternative that has not been proposed; it should note that SHA1 is one of the algorithms already supported by TCP AO. Sec 2.5's first paragraph should be revised to refer more directly to MSDP. Sec 4 discusses TCP AO, but claims "Even when keys are configured manually, a method for when to start using the new keys or stop using old keys has not been defined" In TCP AO's architecture, a method for starting/stopping keys would be part of a KMP. No such KMP is defined, but this is not a deficiency of TCP AO. it also states: "Also TCP-AO does not address the issue of connectionless reset, as it applies to routers that do not store MKT across reboots." See RFC 5925 Sec 7.27. The doc also states: As stated earlier TCP-AO [RFC5925] and its accompanying document Crypto Algorithms for TCP-AO [RFC5926] suggest that two MAC algorithms that MUST be supported are HMAC-SHA-1-96 as specified in HMAC [RFC2104] and AES-128-CMAC-96 as specified in NIST-SP800-38B [NIST-SP800-38B]. They don't suggest it; they require it. On 6/23/2012 5:28 PM, internet-drafts@ietf.org wrote: > > A New Internet-Draft is available from the on-line Internet-Drafts directories. > This draft is a work item of the Keying and Authentication for Routing Protocols Working Group of the IETF. > > Title : Analysis of BGP, LDP, PCEP and MSDP Issues According to KARP Design Guide > Author(s) : Mahesh Jethanandani > Keyur Patel > Lianshu Zheng > Filename : draft-ietf-karp-routing-tcp-analysis-02.txt > Pages : 17 > Date : 2012-06-23 > > Abstract: > This document analyzes BGP, LDP, PCEP and MSDP according to > guidelines set forth in section 4.2 of Keying and Authentication for > Routing Protocols Design Guidelines [RFC6518]. > > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-karp-routing-tcp-analysis > > There's also a htmlized version available at: > http://tools.ietf.org/html/draft-ietf-karp-routing-tcp-analysis-02 > > A diff from previous version is available at: > http://tools.ietf.org/rfcdiff?url2=draft-ietf-karp-routing-tcp-analysis-02 > > > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ > > _______________________________________________ > karp mailing list > karp@ietf.org > https://www.ietf.org/mailman/listinfo/karp > From jmh@joelhalpern.com Fri Jul 6 19:47:13 2012 Return-Path: X-Original-To: karp@ietfa.amsl.com Delivered-To: karp@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 35F7111E80BD; Fri, 6 Jul 2012 19:47:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.265 X-Spam-Level: X-Spam-Status: No, score=-102.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5HF7qAgWeGZE; Fri, 6 Jul 2012 19:47:12 -0700 (PDT) Received: from morbo.mail.tigertech.net (morbo.mail.tigertech.net [67.131.251.54]) by ietfa.amsl.com (Postfix) with ESMTP id 96CBE11E8072; Fri, 6 Jul 2012 19:47:12 -0700 (PDT) Received: from mailc2.tigertech.net (mailc2.tigertech.net [208.80.4.156]) by morbo.tigertech.net (Postfix) with ESMTP id 47AEA5581A0; Fri, 6 Jul 2012 19:47:30 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mailc2.tigertech.net (Postfix) with ESMTP id 223F31C16A2; Fri, 6 Jul 2012 19:47:29 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at c2.tigertech.net Received: from [192.168.6.243] (ip-64-134-170-143.public.wayport.net [64.134.170.143]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailc2.tigertech.net (Postfix) with ESMTPSA id 42E7B1C169F; Fri, 6 Jul 2012 19:47:26 -0700 (PDT) Message-ID: <4FF7A332.2000204@joelhalpern.com> Date: Fri, 06 Jul 2012 22:47:14 -0400 From: "Joel M. Halpern" User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1 MIME-Version: 1.0 To: "karp@ietf.org" , "lisp@ietf.org" References: <20120706211533.3449.10225.idtracker@ietfa.amsl.com> In-Reply-To: <20120706211533.3449.10225.idtracker@ietfa.amsl.com> X-Forwarded-Message-Id: <20120706211533.3449.10225.idtracker@ietfa.amsl.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: [karp] Fwd: NomCom 2012-13 Call for Volunteers X-BeenThere: karp@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Discussion list for key management for routing and transport protocols List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Jul 2012 02:47:13 -0000 The nomcom process is critical for the proper function of the IETF. Please volunteer if you are eligible. Thank you, Joel -------- Original Message -------- Subject: NomCom 2012-13 Call for Volunteers Date: Fri, 06 Jul 2012 14:15:33 -0700 From: NomCom Chair To: IETF Announcement List The IETF nominating committee process for 2012-13 has begun. The IETF nominating committee appoints folks to fill the open slots on the IAOC, the IAB, and the IESG. The 10 nominating committee members are selected randomly from a pool of volunteers. The more volunteers, the better chance we have of choosing a random yet representative cross section of the IETF population. The details of the operation of the nomcom can be found in RFC 3777. To be eligible, volunteers for the nomcom need to have attended 3 of the past 5 IETF meetings as of the time this announcement goes out. That is, 3 meetings from IETF 79 (Beijing) - IETF 83 (Paris). If you qualify, and if you will not be seeking appointment to any of the open positions that this nomcom will be filling, please consider volunteering. The list of people whose terms end with the March 2013 IETF meeting, and thus the positions for which the nominating committee is responsible for filling, are as follows: IAOC: -------- Dave Crocker IAB: -------- Alissa Cooper Joel Halpern David Kessens Danny McPherson Jon Peterson Dave Thaler IESG: -------- Russ Housley (General Area) Pete Resnick (Applications Area) Ralph Droms (Internet Area) Ronald Bonica (Operations and Management Area) Robert Sparks (Real-Time Applications and Infrastructure Area) Adrian Farrel (Routing Area) Stephen Farrell (Security Area) Wesley Eddy (Transport Area) The primary activity for this nomcom will begin in August 2012 and should be completed in January 2013. The nomcom will be collecting requirements from the community, as well as talking to candidates and obtaining feedback from community members about candidates. There will be regularly scheduled conference calls to ensure progress. Thus, being a nomcom member does require some time commitment. Please volunteer by sending an email before 11:59 pm EDT (UTC - 4 hours) August 5, 2012 as follows: To: mlepinski.ietf@gmail.com Subject: Nomcom 2012-13 Volunteer Please include the following information in the body: // As you enter in the IETF Registration Form, // First/Given name followed by Last/Family Name // typically what goes in the Company field // in the IETF Registration Form [] // // For confirmation if selected Please expect an email response from me within 3 business days stating whether or not you are qualified. If you don't receive a response, please re-send your email with the tag "RESEND:" added to the subject line. If you are not yet sure you would like to volunteer, please consider that nomcom members play a very important role in shaping the leadership of the IETF. Ensuring the leadership of the IETF is fair and balanced and comprised of those who can lead the IETF in the right direction is an important responsibility that rests on the IETF participants at large. Volunteering for the nomcom is a good way of contributing toward that goal. I will be publishing a more detailed timetable for nomcom activities, as well as details of the randomness seeds to be used for the RFC 3797 selection process, within the next couple weeks. Thank you, Matthew Lepinski mlepinski.ietf@gmail.com nomcom-chair@ietf.org From abdussalambaryun@gmail.com Sat Jul 7 05:02:40 2012 Return-Path: X-Original-To: karp@ietfa.amsl.com Delivered-To: karp@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 95DEF21F8629; Sat, 7 Jul 2012 05:02:40 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.657 X-Spam-Level: X-Spam-Status: No, score=-2.657 tagged_above=-999 required=5 tests=[AWL=-0.663, BAYES_00=-2.599, DEAR_SOMETHING=1.605, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id woSmBy6vL1gT; Sat, 7 Jul 2012 05:02:36 -0700 (PDT) Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id A411221F8596; Sat, 7 Jul 2012 05:02:35 -0700 (PDT) Received: by vbbez10 with SMTP id ez10so7180893vbb.31 for ; Sat, 07 Jul 2012 05:02:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=yuiP59dEvncHK3ydzVGqErSq7xVJFNxbF85ei0c9z0g=; b=fSY627+OXrtv5EqEg/IaKYJh+QGG+AV9L6Mq1X+ZcNKLhJKPTeTeBl3AhXRkLfKar+ OPlZgeBzfpiPq4Ez5yC1uTpaHiOZ20S61wwl38rhvHQF65LUILpjOjpBEo32xH+Krfbi JAq5A7DB3slzybXqsj84sMi5acVYW4QAfr92QetrJhlUowAcURHZJkKhZZ5f2KGY91zN WUEolxDjmAumITKdV2H3GJFL0sJrh+av++LEGADVTTOjmJtEtLhrPi6xIPnOuSMe70C/ q5yGn2N1xjyM+3gegAuxHK7ySUr6ACvWCA88WeDWmhmmoXmBeLSoUR+l3d42CyL4+x7c UYqA== MIME-Version: 1.0 Received: by 10.52.94.36 with SMTP id cz4mr13657353vdb.10.1341662574357; Sat, 07 Jul 2012 05:02:54 -0700 (PDT) Received: by 10.220.110.130 with HTTP; Sat, 7 Jul 2012 05:02:54 -0700 (PDT) Date: Sat, 7 Jul 2012 14:02:54 +0200 Message-ID: From: Abdussalam Baryun To: ietf Content-Type: text/plain; charset=ISO-8859-1 X-Mailman-Approved-At: Sat, 07 Jul 2012 08:32:51 -0700 Cc: kitten@ietf.org, websec@ietf.org, ipsec@ietf.org, opsec@ietf.org, "iesg@ietf.org" , sidr@ietf.org, stephen.farrell@cs.tcd.ie, hokey@ietf.org, karp@ietf.org Subject: [karp] IETF Technology Terminology and Protocol Implications X-BeenThere: karp@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Discussion list for key management for routing and transport protocols List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Jul 2012 12:02:41 -0000 Dear Sir or Madam, I suggest for terminology-documents in WGs to consider the security terms that are related to WG, and terms implication for security considerations. Security consideration section as required by RFC2223 (section-9), which can be used to define things. For example the approach was used in RFC2119 and in the I-D [AB]. Regarding RFCs that specify protocols, I suggest they mention in the security consideration section additionally to the protocol security implication also the related works of security WGs in IETF. This will build interaction between WGs and will help the readers and users. What do you think? please advise or comment, thanking you, References: [RFC2223] http://www.ietf.org/rfc/rfc2223.txt [RFC2119] http://www.ietf.org/rfc/rfc2119.txt [AB] http://tools.ietf.org/id/draft-baryun-manet-terminology-00.txt Yours Faithfully, Abdussalam Baryun University of Glamorgan, UK ***************************************************************************** This email and any attachments are confidential to the intended recipient and may also be privileged. If you are not the intended recipient please delete it from your system and notify the sender. The contents are comply to the IETF regulations, and WG procedures. You should not copy the email nor use it for any other purpose, nor disclose, nor distribute its contents to any other person. ***************************************************************************** From mjethanandani@gmail.com Sat Jul 7 16:18:11 2012 Return-Path: X-Original-To: karp@ietfa.amsl.com Delivered-To: karp@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC70B21F8522; Sat, 7 Jul 2012 16:18:11 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.598 X-Spam-Level: X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Xw0-F8jF+F14; Sat, 7 Jul 2012 16:18:10 -0700 (PDT) Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id 4C66621F850F; Sat, 7 Jul 2012 16:18:10 -0700 (PDT) Received: by pbcwy7 with SMTP id wy7so17275683pbc.31 for ; Sat, 07 Jul 2012 16:18:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :message-id:references:to:x-mailer; bh=rR/VaHyj97ntrnVIeKfuQIDycAr7DdD8RWYSzpp9TDA=; b=hrzOzmWhe+28IVI4YR03jbRlFb7V/7RnVTmKY2xYaVbaUYXMY6dXgVi5quLLprUWdr coaPYzU5hYZhjxpciZqfRchKZpbsLe241v2v7vlgRaGliHPCqHK53bOjtLqWGhfd7piG gA0LHNqhhQ0MS92Uc+Z2ho/fW2n5zobEP3twVjxRryo1K7/M1b1HsKfGb/7DxRmmgw1N sHeYuzbSGSWSYV1ldNpQOUvJ0FGtZYRW85VLokMSuKJ6grs+ytPsX0TxvHWn7C9o5zBu R2vAIVLhpaf086g3ZClE5IZ9SirOmhw/Y6VY0H1D/DVVMMqxaoSPSIBk5VqVsEXY+tYU yCRQ== Received: by 10.66.73.98 with SMTP id k2mr55075496pav.73.1341703110554; Sat, 07 Jul 2012 16:18:30 -0700 (PDT) Received: from [192.168.1.123] (c-24-6-173-225.hsd1.ca.comcast.net. [24.6.173.225]) by mx.google.com with ESMTPS id jz4sm24618631pbc.17.2012.07.07.16.18.27 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 07 Jul 2012 16:18:29 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: multipart/alternative; boundary=Apple-Mail-36-471169861 From: Mahesh Jethanandani In-Reply-To: <4FF776D7.9040808@isi.edu> Date: Sat, 7 Jul 2012 16:18:26 -0700 Message-Id: <43A00C82-7CC4-460C-989D-6234B80A206F@gmail.com> References: <20120624002843.17335.73994.idtracker@ietfa.amsl.com> <4FF776D7.9040808@isi.edu> To: Joe Touch X-Mailer: Apple Mail (2.1084) Cc: i-d-announce@ietf.org, internet-drafts@ietf.org, karp@ietf.org Subject: Re: [karp] I-D Action: draft-ietf-karp-routing-tcp-analysis-02.txt X-BeenThere: karp@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Discussion list for key management for routing and transport protocols List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Jul 2012 23:18:12 -0000 --Apple-Mail-36-471169861 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On Jul 6, 2012, at 4:37 PM, Joe Touch wrote: > This doc continues to refer to TCP MD5, but fails to note that this = protocol has been deprecated. It'd be useful to indicate that clearly, = even noting that it remains in use if necessary. The word deprecated has not been appended to TCP MD5. >=20 > Sec 2.2 discusses problems changing keys with TCP MD5, but should also = then note that this has been overcome in TCP AO, whether using manual = keying or an out-of-band KMP. >=20 > Sec 2.3.1.2 suggests use of a stronger hashing algorithm (implied = within TCP MD5). It should not suggest an alternative that has not been = proposed; it should note that SHA1 is one of the algorithms already = supported by TCP AO. Done. >=20 > Sec 2.5's first paragraph should be revised to refer more directly to = MSDP. Done. >=20 > Sec 4 discusses TCP AO, but claims "Even when keys are > configured manually, a method for when to start using the new keys = or > stop using old keys has not been defined" >=20 > In TCP AO's architecture, a method for starting/stopping keys would be = part of a KMP. No such KMP is defined, but this is not a deficiency of = TCP AO. This statement has been taken out. >=20 > it also states: "Also TCP-AO does not address the issue of = connectionless reset, as it > applies to routers that do not store MKT across reboots." >=20 > See RFC 5925 Sec 7.27. I think you meant Section 7.7. That section suggests that routers store = traffic keys in storage. The statement above is for cases where routers = cannot or do not want to store MKT across reboots. In that case, TCP-AO = does not address connectionless reset. >=20 > The doc also states: > As stated earlier TCP-AO [RFC5925] and its accompanying document > Crypto Algorithms for TCP-AO [RFC5926] suggest that two MAC > algorithms that MUST be supported are HMAC-SHA-1-96 as specified in > HMAC [RFC2104] and AES-128-CMAC-96 as specified in NIST-SP800-38B > [NIST-SP800-38B]. >=20 > They don't suggest it; they require it. The document has already been reworded around this section. >=20 >=20 >=20 >=20 > On 6/23/2012 5:28 PM, internet-drafts@ietf.org wrote: >>=20 >> A New Internet-Draft is available from the on-line Internet-Drafts = directories. >> This draft is a work item of the Keying and Authentication for = Routing Protocols Working Group of the IETF. >>=20 >> Title : Analysis of BGP, LDP, PCEP and MSDP Issues = According to KARP Design Guide >> Author(s) : Mahesh Jethanandani >> Keyur Patel >> Lianshu Zheng >> Filename : draft-ietf-karp-routing-tcp-analysis-02.txt >> Pages : 17 >> Date : 2012-06-23 >>=20 >> Abstract: >> This document analyzes BGP, LDP, PCEP and MSDP according to >> guidelines set forth in section 4.2 of Keying and Authentication = for >> Routing Protocols Design Guidelines [RFC6518]. >>=20 >> The IETF datatracker status page for this draft is: >> https://datatracker.ietf.org/doc/draft-ietf-karp-routing-tcp-analysis >>=20 >> There's also a htmlized version available at: >> http://tools.ietf.org/html/draft-ietf-karp-routing-tcp-analysis-02 >>=20 >> A diff from previous version is available at: >> = http://tools.ietf.org/rfcdiff?url2=3Ddraft-ietf-karp-routing-tcp-analysis-= 02 >>=20 >>=20 >> Internet-Drafts are also available by anonymous FTP at: >> ftp://ftp.ietf.org/internet-drafts/ >>=20 >> _______________________________________________ >> karp mailing list >> karp@ietf.org >> https://www.ietf.org/mailman/listinfo/karp >>=20 >=20 > _______________________________________________ > karp mailing list > karp@ietf.org > https://www.ietf.org/mailman/listinfo/karp Mahesh Jethanandani mjethanandani@gmail.com --Apple-Mail-36-471169861 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii
This doc continues to = refer to TCP MD5, but fails to note that this protocol has been = deprecated. It'd be useful to indicate that clearly, even noting that it = remains in use if necessary.

The = word deprecated has not been appended to TCP = MD5.


Sec 2.2 discusses = problems changing keys with TCP MD5, but should also then note that this = has been overcome in TCP AO, whether using manual keying or an = out-of-band KMP.

Sec 2.3.1.2 suggests use of a stronger hashing = algorithm (implied within TCP MD5). It should not suggest an alternative = that has not been proposed; it should note that SHA1 is one of the = algorithms already supported by TCP = AO.

Done.


Sec 2.5's first paragraph should be revised to = refer more directly to = MSDP.

Done.


Sec 4 discusses TCP AO, but claims "Even when = keys are
  configured manually, a method for when to start = using the new keys or
  stop using old keys has not been = defined"

In TCP = AO's architecture, a method for starting/stopping keys would be part of = a KMP. No such KMP is defined, but this is not a deficiency of TCP = AO.

This statement has been taken = out.


it also states: = "Also TCP-AO does not address the issue of connectionless reset, as = it
  applies to routers that do not store MKT across = reboots."

See RFC 5925 Sec = 7.27.

I think you meant Section = 7.7. That section suggests that routers store traffic keys in storage. = The statement above is for cases where routers cannot or do not want to = store MKT across reboots. In that case, TCP-AO does not address = connectionless reset.


The= doc also states:
  As stated earlier TCP-AO [RFC5925] and = its accompanying document
  Crypto Algorithms for TCP-AO = [RFC5926] suggest that two MAC
  algorithms that MUST be = supported are HMAC-SHA-1-96 as specified in
  HMAC = [RFC2104] and AES-128-CMAC-96 as specified in NIST-SP800-38B
=   [NIST-SP800-38B].

They don't suggest it; they require = it.

The document has already been = reworded around this section.





On 6/23/2012 5:28 PM, internet-drafts@ietf.org = wrote:

A New Internet-Draft is available from the on-line = Internet-Drafts directories.
=  This draft is a work item of the Keying and Authentication for = Routing Protocols Working Group of the IETF.

Title =           : Analysis = of BGP, LDP, PCEP and MSDP Issues According to KARP Design = Guide
Author(s) =       : Mahesh = Jethanandani
=             &n= bsp;           &nbs= p; Keyur Patel
=             &n= bsp;           &nbs= p; Lianshu Zheng
Filename =        : = draft-ietf-karp-routing-tcp-analysis-02.txt
= Pages =           : = 17
Date =            : = 2012-06-23

Abstract:
=    This document analyzes BGP, LDP, PCEP and MSDP = according to
=    guidelines set forth in section 4.2 of Keying and = Authentication for
=    Routing Protocols Design Guidelines = [RFC6518].

The IETF = datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-karp-routing-tcp-analysis=

There's also a = htmlized version available at:
http://tools.ietf.org/html/draft-ietf-karp-routing-tcp-analysis-02

A diff from previous version is available = at:
http://tools.ietf.org/rfcdiff?url2=3Ddraft-ietf-karp-routing-t= cp-analysis-02


Internet-Drafts = are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-d= rafts/

_______________________________________________
karp mailing = list
karp@ietf.org
https://www.ietf.org/m= ailman/listinfo/karp


_______________________________________= ________
karp mailing list
karp@ietf.org
https://www.ietf.org/ma= ilman/listinfo/karp

Mahesh = Jethanandani
<= div>


= --Apple-Mail-36-471169861-- From touch@isi.edu Sat Jul 7 17:38:41 2012 Return-Path: X-Original-To: karp@ietfa.amsl.com Delivered-To: karp@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C38D21F85B6; Sat, 7 Jul 2012 17:38:41 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.549 X-Spam-Level: X-Spam-Status: No, score=-102.549 tagged_above=-999 required=5 tests=[AWL=-1.347, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E1LalDoDvsbt; Sat, 7 Jul 2012 17:38:40 -0700 (PDT) Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id 519D121F855B; Sat, 7 Jul 2012 17:38:40 -0700 (PDT) Received: from [192.168.1.97] (pool-71-105-89-105.lsanca.dsl-w.verizon.net [71.105.89.105]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id q680caOE023842 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Sat, 7 Jul 2012 17:38:40 -0700 (PDT) References: <20120624002843.17335.73994.idtracker@ietfa.amsl.com> <4FF776D7.9040808@isi.edu> <43A00C82-7CC4-460C-989D-6234B80A206F@gmail.com> In-Reply-To: <43A00C82-7CC4-460C-989D-6234B80A206F@gmail.com> Mime-Version: 1.0 (1.0) Content-Type: multipart/alternative; boundary=Apple-Mail-36EEAE4B-2E1F-4960-9E9C-C4909ED3A8D8 Message-Id: <904BF161-AE5F-4449-9622-4C2126D70F47@isi.edu> Content-Transfer-Encoding: 7bit X-Mailer: iPhone Mail (9B206) From: Joe Touch Date: Sat, 7 Jul 2012 17:38:36 -0700 To: Mahesh Jethanandani X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: touch@isi.edu Cc: "i-d-announce@ietf.org" , "internet-drafts@ietf.org" , "karp@ietf.org" Subject: Re: [karp] I-D Action: draft-ietf-karp-routing-tcp-analysis-02.txt X-BeenThere: karp@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Discussion list for key management for routing and transport protocols List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Jul 2012 00:38:41 -0000 --Apple-Mail-36EEAE4B-2E1F-4960-9E9C-C4909ED3A8D8 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Notes below.=20 On Jul 7, 2012, at 4:18 PM, Mahesh Jethanandani wr= ote: >=20 > On Jul 6, 2012, at 4:37 PM, Joe Touch wrote: >=20 >> This doc continues to refer to TCP MD5, but fails to note that this proto= col has been deprecated. It'd be useful to indicate that clearly, even notin= g that it remains in use if necessary. >=20 > The word deprecated has not been appended to TCP MD5. It's not 'historic' but AO obsoletes it.=20 >> Sec 2.2 discusses problems changing keys with TCP MD5, but should also th= en note that this has been overcome in TCP AO, whether using manual keying o= r an out-of-band KMP. >>=20 >> Sec 2.3.1.2 suggests use of a stronger hashing algorithm (implied within T= CP MD5). It should not suggest an alternative that has not been proposed; it= should note that SHA1 is one of the algorithms already supported by TCP AO.= >=20 > Done. >=20 >>=20 >> Sec 2.5's first paragraph should be revised to refer more directly to MSD= P. >=20 > Done. >=20 >>=20 >> Sec 4 discusses TCP AO, but claims "Even when keys are >> configured manually, a method for when to start using the new keys or >> stop using old keys has not been defined" >>=20 >> In TCP AO's architecture, a method for starting/stopping keys would be pa= rt of a KMP. No such KMP is defined, but this is not a deficiency of TCP AO.= >=20 > This statement has been taken out. >=20 >>=20 >> it also states: "Also TCP-AO does not address the issue of connectionless= reset, as it >> applies to routers that do not store MKT across reboots." >>=20 >> See RFC 5925 Sec 7.27. >=20 > I think you meant Section 7.7 Yes. Autocorrect was too eager.=20 > That section suggests that routers store traffic keys in storage. The stat= ement above is for cases where routers cannot or do not want to store MKT ac= ross reboots. In that case, TCP-AO does not address connectionless reset. It does in detail - recommending use of TCP keepaives, BGP graceful restart,= and clearing out excess idle connection state. That's hardly considered not= addressing it.=20 >> The doc also states: >> As stated earlier TCP-AO [RFC5925] and its accompanying document >> Crypto Algorithms for TCP-AO [RFC5926] suggest that two MAC >> algorithms that MUST be supported are HMAC-SHA-1-96 as specified in >> HMAC [RFC2104] and AES-128-CMAC-96 as specified in NIST-SP800-38B >> [NIST-SP800-38B]. >>=20 >> They don't suggest it; they require it. >=20 > The document has already been reworded around this section. >=20 >>=20 >>=20 >>=20 >>=20 >> On 6/23/2012 5:28 PM, internet-drafts@ietf.org wrote: >>>=20 >>> A New Internet-Draft is available from the on-line Internet-Drafts direc= tories. >>> This draft is a work item of the Keying and Authentication for Routing P= rotocols Working Group of the IETF. >>>=20 >>> Title : Analysis of BGP, LDP, PCEP and MSDP Issues Accord= ing to KARP Design Guide >>> Author(s) : Mahesh Jethanandani >>> Keyur Patel >>> Lianshu Zheng >>> Filename : draft-ietf-karp-routing-tcp-analysis-02.txt >>> Pages : 17 >>> Date : 2012-06-23 >>>=20 >>> Abstract: >>> This document analyzes BGP, LDP, PCEP and MSDP according to >>> guidelines set forth in section 4.2 of Keying and Authentication for >>> Routing Protocols Design Guidelines [RFC6518]. >>>=20 >>> The IETF datatracker status page for this draft is: >>> https://datatracker.ietf.org/doc/draft-ietf-karp-routing-tcp-analysis >>>=20 >>> There's also a htmlized version available at: >>> http://tools.ietf.org/html/draft-ietf-karp-routing-tcp-analysis-02 >>>=20 >>> A diff from previous version is available at: >>> http://tools.ietf.org/rfcdiff?url2=3Ddraft-ietf-karp-routing-tcp-analysi= s-02 >>>=20 >>>=20 >>> Internet-Drafts are also available by anonymous FTP at: >>> ftp://ftp.ietf.org/internet-drafts/ >>>=20 >>> _______________________________________________ >>> karp mailing list >>> karp@ietf.org >>> https://www.ietf.org/mailman/listinfo/karp >>>=20 >>=20 >> _______________________________________________ >> karp mailing list >> karp@ietf.org >> https://www.ietf.org/mailman/listinfo/karp >=20 > Mahesh Jethanandani > mjethanandani@gmail.com >=20 >=20 >=20 --Apple-Mail-36EEAE4B-2E1F-4960-9E9C-C4909ED3A8D8 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8
Notes below. 

= On Jul 7, 2012, at 4:18 PM, Mahesh Jethanandani <mjethanandani@gmail.com> wrote:

=

On Jul 6, 2012, at 4:37 P= M, Joe Touch wrote:

This doc continu= es to refer to TCP MD5, but fails to note that this protocol has been deprec= ated. It'd be useful to indicate that clearly, even noting that it remains i= n use if necessary.

The word deprecated= has not been appended to TCP MD5.

It's not 'historic' but AO obsoletes it. 

Sec 2.2 discuss= es problems changing keys with TCP MD5, but should also then note that this h= as been overcome in TCP AO, whether using manual keying or an out-of-band KM= P.

Sec 2.3.1.2 suggests use of a stronger hashing algorithm (implied w= ithin TCP MD5). It should not suggest an alternative that has not been propo= sed; it should note that SHA1 is one of the algorithms already supported by T= CP AO.

Done.


Sec 2.5's first paragraph should be revised to refer m= ore directly to MSDP.

Done.
<= br>

Sec 4 discusses TCP AO, but claims "Ev= en when keys are
  configured manually, a method for when to s= tart using the new keys or
  stop using old keys has not been d= efined"

In TCP AO's arc= hitecture, a method for starting/stopping keys would be part of a KMP. No su= ch KMP is defined, but this is not a deficiency of TCP AO.

This statement has been taken out.


it also states: "Also TCP-AO does not address th= e issue of connectionless reset, as it
  applies to routers th= at do not store MKT across reboots."

See RFC 5925 Sec 7.27.
=

I think you meant Section 7.7

Yes. Autocorrect was too eager. 

That section suggests that routers store t= raffic keys in storage. The statement above is for cases where routers canno= t or do not want to store MKT across reboots. In that case, TCP-AO does not a= ddress connectionless reset.

It d= oes in detail - recommending use of TCP keepaives, BGP graceful restart, and= clearing out excess idle connection state. That's hardly considered not add= ressing it. 

The doc also states:
  As stated e= arlier TCP-AO [RFC5925] and its accompanying document
  Crypto= Algorithms for TCP-AO [RFC5926] suggest that two MAC
  algori= thms that MUST be supported are HMAC-SHA-1-96 as specified in
 &nbs= p;HMAC [RFC2104] and AES-128-CMAC-96 as specified in NIST-SP800-38B
&nbs= p; [NIST-SP800-38B].

They don't suggest it; they require it.
=

The document has already been reworded aro= und this section.




<= br>On 6/23/2012 5:28 PM, interne= t-drafts@ietf.org wrote:

<= blockquote type=3D"cite">A New Internet-Draft is available from the on-line I= nternet-Drafts directories.
 = ;This draft is a work item of the Keying and Authentication for Routing Prot= ocols Working Group of the IETF.
<= br>
Title       &n= bsp;   : Analysis of BGP, LDP, PCEP and MSDP Issues According= to KARP Design Guide
Author(s)  &nbs= p;    : Mahesh Jethanandani
          &n= bsp;            =    Keyur Patel
&nb= sp;            &= nbsp;            = ;Lianshu Zheng
Filename    &= nbsp;   : draft-ietf-karp-routing-tcp-analysis-02.txt
Pages       &n= bsp;   : 17
Date  &= nbsp;         : 2012-06-23
<= /blockquote>

Abstract:
   = This document analyzes BGP, LDP, PCEP and MSDP according to
=
   guidelines set forth in section= 4.2 of Keying and Authentication for
   Routing Protocols Design Guidelines [RFC6518].

The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-karp-= routing-tcp-analysis

There's also a htmlized version available a= t:
http://tools.ietf.org/html/d= raft-ietf-karp-routing-tcp-analysis-02

A diff from previous versi= on is available at:
h= ttp://tools.ietf.org/rfcdiff?url2=3Ddraft-ietf-karp-routing-tcp-analysis-02<= /a>


Internet-Drafts are a= lso available by anonymous FTP at:
ftp://ftp.ietf.org/internet= -drafts/

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


__________________________= _____________________
karp mailing list
karp@ietf.org
https://www.ietf.org/mailman/listinfo/karp

Mahesh Jethanandani



= --Apple-Mail-36EEAE4B-2E1F-4960-9E9C-C4909ED3A8D8-- From internet-drafts@ietf.org Sat Jul 7 23:40:44 2012 Return-Path: X-Original-To: karp@ietfa.amsl.com Delivered-To: karp@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF12821F8781; Sat, 7 Jul 2012 23:40:44 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.576 X-Spam-Level: X-Spam-Status: No, score=-102.576 tagged_above=-999 required=5 tests=[AWL=0.023, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ErH59OWwXGMe; Sat, 7 Jul 2012 23:40:42 -0700 (PDT) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2EE9D21F86F2; Sat, 7 Jul 2012 23:40:17 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 4.30p2 Message-ID: <20120708064017.18049.74776.idtracker@ietfa.amsl.com> Date: Sat, 07 Jul 2012 23:40:17 -0700 Cc: karp@ietf.org Subject: [karp] I-D Action: draft-ietf-karp-routing-tcp-analysis-03.txt X-BeenThere: karp@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Discussion list for key management for routing and transport protocols List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Jul 2012 06:40:45 -0000 A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the Keying and Authentication for Routing Pro= tocols Working Group of the IETF. Title : Analysis of BGP, LDP, PCEP and MSDP Issues According to = KARP Design Guide Author(s) : Mahesh Jethanandani Keyur Patel Lianshu Zheng Filename : draft-ietf-karp-routing-tcp-analysis-03.txt Pages : 18 Date : 2012-07-07 Abstract: This document analyzes BGP, LDP, PCEP and MSDP according to guidelines set forth in section 4.2 of Keying and Authentication for Routing Protocols Design Guidelines [RFC6518]. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-karp-routing-tcp-analysis There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-karp-routing-tcp-analysis-03 A diff from previous version is available at: http://tools.ietf.org/rfcdiff?url2=3Ddraft-ietf-karp-routing-tcp-analysis-03 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From internet-drafts@ietf.org Tue Jul 10 02:10:07 2012 Return-Path: X-Original-To: karp@ietfa.amsl.com Delivered-To: karp@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 67B8711E808E; Tue, 10 Jul 2012 02:10:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.551 X-Spam-Level: X-Spam-Status: No, score=-102.551 tagged_above=-999 required=5 tests=[AWL=0.048, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qwPdGtN92GwC; Tue, 10 Jul 2012 02:10:07 -0700 (PDT) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ED8DE11E80A0; Tue, 10 Jul 2012 02:10:06 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 4.30p3 Message-ID: <20120710091006.29249.20748.idtracker@ietfa.amsl.com> Date: Tue, 10 Jul 2012 02:10:06 -0700 Cc: karp@ietf.org Subject: [karp] I-D Action: draft-ietf-karp-ospf-analysis-05.txt X-BeenThere: karp@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Discussion list for key management for routing and transport protocols List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Jul 2012 09:10:07 -0000 A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the Keying and Authentication for Routing Pro= tocols Working Group of the IETF. Title : Analysis of OSPF Security According to KARP Design Guide Author(s) : Sam Hartman Dacheng Zhang Filename : draft-ietf-karp-ospf-analysis-05.txt Pages : 12 Date : 2012-07-10 Abstract: This document analyzes OSPFv2 and OSPFv3 according to the guidelines set forth in section 4.2 of RFC6518. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-karp-ospf-analysis There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-karp-ospf-analysis-05 A diff from previous version is available at: http://tools.ietf.org/rfcdiff?url2=3Ddraft-ietf-karp-ospf-analysis-05 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From internet-drafts@ietf.org Thu Jul 12 12:59:41 2012 Return-Path: X-Original-To: karp@ietfa.amsl.com Delivered-To: karp@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D49B021F86D4; Thu, 12 Jul 2012 12:59:41 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.537 X-Spam-Level: X-Spam-Status: No, score=-102.537 tagged_above=-999 required=5 tests=[AWL=0.062, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mEGsehXeHVKU; Thu, 12 Jul 2012 12:59:41 -0700 (PDT) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A66D21F86D1; Thu, 12 Jul 2012 12:59:41 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 4.30p3 Message-ID: <20120712195941.1480.64389.idtracker@ietfa.amsl.com> Date: Thu, 12 Jul 2012 12:59:41 -0700 Cc: karp@ietf.org Subject: [karp] I-D Action: draft-ietf-karp-ops-model-03.txt X-BeenThere: karp@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Discussion list for key management for routing and transport protocols List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jul 2012 19:59:42 -0000 A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the Keying and Authentication for Routing Pro= tocols Working Group of the IETF. Title : Operations Model for Router Keying Author(s) : Sam Hartman Dacheng Zhang Filename : draft-ietf-karp-ops-model-03.txt Pages : 21 Date : 2012-07-12 Abstract: Developing an operational and management model for routing protocol security that works across protocols will be critical to the success of routing protocol security efforts. This document discusses issues and begins to consider development of these models. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-karp-ops-model There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-karp-ops-model-03 A diff from previous version is available at: http://tools.ietf.org/rfcdiff?url2=3Ddraft-ietf-karp-ops-model-03 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From hartmans@mit.edu Thu Jul 12 13:04:18 2012 Return-Path: X-Original-To: karp@ietfa.amsl.com Delivered-To: karp@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1BC4B21F854B for ; Thu, 12 Jul 2012 13:04:18 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.153 X-Spam-Level: X-Spam-Status: No, score=-103.153 tagged_above=-999 required=5 tests=[AWL=-0.888, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A0QuOLPXLivT for ; Thu, 12 Jul 2012 13:04:17 -0700 (PDT) Received: from permutation-city.suchdamage.org (permutation-city.suchdamage.org [69.25.196.28]) by ietfa.amsl.com (Postfix) with ESMTP id 93E5421F853B for ; Thu, 12 Jul 2012 13:04:17 -0700 (PDT) Received: from carter-zimmerman.suchdamage.org (carter-zimmerman.suchdamage.org [69.25.196.178]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.suchdamage.org (Postfix) with ESMTPS id 4995C203BA for ; Thu, 12 Jul 2012 16:05:16 -0400 (EDT) Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 5D37941F0; Thu, 12 Jul 2012 16:04:37 -0400 (EDT) From: Sam Hartman To: karp@ietf.org Cc: References: <20120712195941.1480.64389.idtracker@ietfa.amsl.com> Date: Thu, 12 Jul 2012 16:04:37 -0400 In-Reply-To: <20120712195941.1480.64389.idtracker@ietfa.amsl.com> (internet-drafts@ietf.org's message of "Thu, 12 Jul 2012 12:59:41 -0700") Message-ID: User-Agent: Gnus/5.110009 (No Gnus v0.9) Emacs/22.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: [karp] I-D Action: draft-ietf-karp-ops-model-03.txt X-BeenThere: karp@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Discussion list for key management for routing and transport protocols List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jul 2012 20:04:18 -0000 This update serves two purposes; 1) We've improved the crypto table to deal with a lot of the issues brought up by the ops model. So the ops model talks about how things work in the crypto table rather than listing a bunch of things to think about. 2) we got some excellent feedback on fault handling and upgrades that we've tried to address. At this point I think we're now ready to track down suggestions for operators and vendors we received a couple of IETFs ago and get the feedback we need to make this useful to operators. From william.atwood@concordia.ca Mon Jul 16 19:13:24 2012 Return-Path: X-Original-To: karp@ietfa.amsl.com Delivered-To: karp@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B4AC21F85FB for ; Mon, 16 Jul 2012 19:13:24 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.597 X-Spam-Level: X-Spam-Status: No, score=-5.597 tagged_above=-999 required=5 tests=[AWL=1.002, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V+0v5goB0i+9 for ; Mon, 16 Jul 2012 19:13:23 -0700 (PDT) Received: from dillinger.concordia.ca (dillinger.Concordia.CA [132.205.122.20]) by ietfa.amsl.com (Postfix) with ESMTP id 2011821F85F9 for ; Mon, 16 Jul 2012 19:13:22 -0700 (PDT) Received: from mail.concordia.ca (ums-sgwhts1.Concordia.CA [132.205.123.42]) by dillinger.concordia.ca (8.14.3/8.14.3) with ESMTP id q6H2E4sf016337; Mon, 16 Jul 2012 22:14:05 -0400 Received: from UMS-SGWMBS1.concordia.ca ([fe80::a570:57d:a1a6:f054]) by ums-sgwhts1.concordia.ca ([fe80::284e:36fa:5415:1fa2%16]) with mapi id 14.01.0323.003; Mon, 16 Jul 2012 22:14:04 -0400 From: John William Atwood To: "karp@ietf.org" Thread-Topic: I-D Action: draft-atwood-karp-akam-rp-01.txt Thread-Index: AQHNY6xuUpTF0F/UfUKFZx1NpRsY65csu7Cg Date: Tue, 17 Jul 2012 02:14:03 +0000 Message-ID: <2211CC426882294BA4B228588413DAF95859C7@ums-sgwmbs1.concordia.ca> References: <20120716233936.1985.49824.idtracker@ietfa.amsl.com> In-Reply-To: <20120716233936.1985.49824.idtracker@ietfa.amsl.com> Accept-Language: en-CA, en-US Content-Language: en-CA X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [132.205.244.5] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.72 on 132.205.122.20 Cc: "revathi.bs@gmail.com" Subject: [karp] FW: I-D Action: draft-atwood-karp-akam-rp-01.txt X-BeenThere: karp@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Discussion list for key management for routing and transport protocols List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Jul 2012 02:13:24 -0000 We have posted draft-atwood-karp-akam-rp-01, which presents what we believe= is a general architecture and protocols for achieving key management and a= djacency management for Routing Protocol updates. This is a component of t= he solution for one of the goals of KARP:=0A= - Define one or more frameworks describing the common elements for modern= authentication in routing protocols.=0A= =0A= Some preliminary ideas were presented at IETF 83 in Paris. At that time, w= e had no corresponding Internet Draft. The draft that has been posted toda= y represents the completion of the first phase of work in our laboratory at= Concordia. It is a mix of justification and proposed solutions; it was pr= esented this way (literally copy-pasting from Revathi's thesis) to get the = information onto the screens of the Working Group members as quickly as pos= sible. We apologize for the fact that the figures are not in the draft; ve= rsion -03 will be presented as soon as the submission tool re-opens (Sunday= , July 29 at 17:00 Vancouver time), and will contain the missing ASCII art,= once we translate from the figures in the thesis.=0A= =0A= Our hope is to stimulate discussion on the suitability of the proposed appr= oach. We have asked for a presentation slot at IETF 84 in Vancouver. If w= e get positive feedback, then we will present future revisions to the draft= that will move it from a design document to a protocol specification. If = it is appropriate, we will produce two documents: one stating requirements = for Automatic Key Management (AKM), and the other specifying the message ex= changes among the components of the AKM framework.=0A= =0A= Any and all comments are welcome, before, during, or after IETF 84.=0A= =0A= Bill and Revathi=0A= =0A= Dr. J.W. Atwood, Eng. tel: +1 (514) 848-2424 x3046=0A= Distinguished Professor Emeritus fax: +1 (514) 848-2830=0A= Department of Computer Science=0A= and Software Engineering=0A= Concordia University EV 3.185 email:william.atwood@concordia.ca=0A= 1455 de Maisonneuve Blvd. West http://users.encs.concordia.ca/~bill=0A= Montreal, Quebec Canada H3G 1M8=0A= =0A= ________________________________________=0A= From: i-d-announce-bounces@ietf.org [i-d-announce-bounces@ietf.org] on beha= lf of internet-drafts@ietf.org [internet-drafts@ietf.org]=0A= Sent: July 16, 2012 7:39 PM=0A= To: i-d-announce@ietf.org=0A= Subject: I-D Action: draft-atwood-karp-akam-rp-01.txt=0A= =0A= A New Internet-Draft is available from the on-line Internet-Drafts director= ies.=0A= =0A= =0A= Title : Automatic Key and Adjacency Management for Routin= g Protocols=0A= Author(s) : William Atwood=0A= Revathi Bangalore Somanatha=0A= Filename : draft-atwood-karp-akam-rp-01.txt=0A= Pages : 34=0A= Date : 2012-07-16=0A= =0A= Abstract:=0A= When tightening the security of the core routing infrastructure, two=0A= steps are necessary. The first is to secure the routing protocols'=0A= packets on the wire. The second is to ensure that the keying=0A= material for the routing protocol exchanges is distributed only to=0A= the appropriate routers. This document specifies requirements on=0A= that distribution and proposes the use of a set of protocols to=0A= achieve those requirements.=0A= =0A= =0A= The IETF datatracker status page for this draft is:=0A= https://datatracker.ietf.org/doc/draft-atwood-karp-akam-rp=0A= =0A= There's also a htmlized version available at:=0A= http://tools.ietf.org/html/draft-atwood-karp-akam-rp-01=0A= =0A= A diff from previous version is available at:=0A= http://tools.ietf.org/rfcdiff?url2=3Ddraft-atwood-karp-akam-rp-01=0A= =0A= =0A= Internet-Drafts are also available by anonymous FTP at:=0A= ftp://ftp.ietf.org/internet-drafts/=0A= =0A= _______________________________________________=0A= I-D-Announce mailing list=0A= I-D-Announce@ietf.org=0A= https://www.ietf.org/mailman/listinfo/i-d-announce=0A= Internet-Draft directories: http://www.ietf.org/shadow.html=0A= or ftp://ftp.ietf.org/ietf/1shadow-sites.txt=0A= From jmh@joelhalpern.com Mon Jul 16 20:33:13 2012 Return-Path: X-Original-To: karp@ietfa.amsl.com Delivered-To: karp@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE66B11E8087 for ; Mon, 16 Jul 2012 20:33:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.374 X-Spam-Level: X-Spam-Status: No, score=-102.374 tagged_above=-999 required=5 tests=[AWL=-0.109, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kJmjq0Uw1bRE for ; Mon, 16 Jul 2012 20:33:13 -0700 (PDT) Received: from morbo.mail.tigertech.net (morbo.mail.tigertech.net [67.131.251.54]) by ietfa.amsl.com (Postfix) with ESMTP id 3C4FD11E8073 for ; Mon, 16 Jul 2012 20:33:13 -0700 (PDT) Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) by morbo.tigertech.net (Postfix) with ESMTP id 6E68BA381B for ; Mon, 16 Jul 2012 20:33:58 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id C7DC11C6EAC for ; Mon, 16 Jul 2012 20:33:57 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net Received: from [10.10.10.105] (pool-71-161-52-95.clppva.btas.verizon.net [71.161.52.95]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 5CEA61C073D for ; Mon, 16 Jul 2012 20:33:57 -0700 (PDT) Message-ID: <5004DD23.50805@joelhalpern.com> Date: Mon, 16 Jul 2012 23:33:55 -0400 From: "Joel M. Halpern" User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1 MIME-Version: 1.0 To: "karp@ietf.org" References: <4FEE33BE.7080609@joelhalpern.com> In-Reply-To: <4FEE33BE.7080609@joelhalpern.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [karp] WG LC: draft-ietf-karp-routing-tcp-analysis-02 to Informational X-BeenThere: karp@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Discussion list for key management for routing and transport protocols List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Jul 2012 03:33:13 -0000 There was not much comment on this draft during the last call. Can the authors please arrange to have a revision of the document which addresses the LC comments ready when I-D submission re-opens? Given that it has been discussed over time in the WG, I will treat silence as consent for sending this, with comments addressed, to the AD. Yours, Joel M. Halpern, KARP co-chair On 6/29/2012 7:01 PM, Joel M. Halpern wrote: > This beings a two week WG last call to determine if folk support > submitting the draft: > http://datatracker.ietf.org/doc/draft-ietf-karp-routing-tcp-analysis/?include_text=1 > > to our AD for publication as an Informational RFC. > > Please send comments of support, or raising issues or concerns, to the > WG email list. (Comments with explanation are much more useful than > those without.) > > Given the weekend, the LC will run till 8pm PDT on 16-July-2012. > > Thank you, > Joel M. Halpern > and Brian Weis > co-chairs > _______________________________________________ > karp mailing list > karp@ietf.org > https://www.ietf.org/mailman/listinfo/karp > From bew@cisco.com Fri Jul 20 16:13:18 2012 Return-Path: X-Original-To: karp@ietfa.amsl.com Delivered-To: karp@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2FD7121F8469 for ; Fri, 20 Jul 2012 16:13:18 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -110.599 X-Spam-Level: X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id si660p45CfED for ; Fri, 20 Jul 2012 16:13:17 -0700 (PDT) Received: from mtv-iport-4.cisco.com (mtv-iport-4.cisco.com [173.36.130.15]) by ietfa.amsl.com (Postfix) with ESMTP id 9799B21F8467 for ; Fri, 20 Jul 2012 16:13:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=bew@cisco.com; l=189; q=dns/txt; s=iport; t=1342826055; x=1344035655; h=from:content-transfer-encoding:subject:date:message-id: to:mime-version; bh=FmQnFw0VuaA2HzCFwJeJZD0G/K9s14t0FwNcEjxbIMU=; b=OOsbBYGhCrLhdvhIhHrdG7tbD8jlyH348UScZORxYBy3oYza0jqpH9Hz FoLGCg+37VsvxWw5r9Yx0oPvmHzCUTHvBTYKsZKsiGRDOMXea8cMhErz2 +raB40bJpEvoKJDdz99xJm96Obb+n3LwcMzqEFScb68todxa8Y4Idv4u9 4=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Al4HAA3lCVCrRDoI/2dsb2JhbABFjWKrdIEHgjkBJ4Iyh2oMnTeBKKARBI8FgjxgA4hNjHiOJIFmgn8 X-IronPort-AV: E=Sophos;i="4.77,626,1336348800"; d="scan'208";a="52471471" Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-4.cisco.com with ESMTP; 20 Jul 2012 23:14:14 +0000 Received: from stealth-10-32-244-210.cisco.com (stealth-10-32-244-210.cisco.com [10.32.244.210]) by mtv-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id q6KNEE71010919 for ; Fri, 20 Jul 2012 23:14:14 GMT From: Brian Weis Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Fri, 20 Jul 2012 16:14:13 -0700 Message-Id: <2D42528A-932A-406D-A195-11BFE5250E64@cisco.com> To: karp@ietf.org Mime-Version: 1.0 (Apple Message framework v1278) X-Mailer: Apple Mail (2.1278) Subject: [karp] IETF 84 KARP WG draft agenda posted X-BeenThere: karp@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Discussion list for key management for routing and transport protocols List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Jul 2012 23:13:18 -0000 Folks, There have been a few agenda requests for the KARP WG slot, and a draft = agenda has been published: = . Joel & Brian= From mjethanandani@gmail.com Fri Jul 20 21:36:11 2012 Return-Path: X-Original-To: karp@ietfa.amsl.com Delivered-To: karp@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 11F6811E8079 for ; Fri, 20 Jul 2012 21:36:11 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.599 X-Spam-Level: X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NvvK9O3c8v+g for ; Fri, 20 Jul 2012 21:36:10 -0700 (PDT) Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id F00D911E8086 for ; Fri, 20 Jul 2012 21:36:09 -0700 (PDT) Received: by vbbez10 with SMTP id ez10so3814479vbb.31 for ; Fri, 20 Jul 2012 21:37:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:from:in-reply-to:mime-version:date:message-id:subject:to :content-type; bh=7HeIl6kaf4TI0VwcNxvk/sYdz60sWftdj1x3jlhGJDg=; b=MN6Rbv5rNX89ZQG08LOCVjDFajZz7O0g9GA3wqjsWS0WoNrQs+c2ZHKzMyOQle+ZdF Ir5GH0C9XMETqC7oYsmFlnSw36e7dDFgjh3FE/1xvU6HgVur8cEtwkQkKSzYYi29V533 1IxpjaZGZDbLgaAz4q4WQ7NsUHPkfJb02BtTqtXrZqrRm96HpKCN2DZf91yOFulBTwXt b5hitVrY0bR1wMABgnFNpIY9N4AYVsUiYIu6Ni35GgTBM2xGyN1jNH/dfobtjmasSjwh ryTvplkKksA2x7uGo0/BbhI3f0yjpBRgRu2JzkyH1s365UI1/FwC2rTKKqe6S7j530n0 xe1Q== Received: by 10.220.221.131 with SMTP id ic3mr6425547vcb.46.1342845427336; Fri, 20 Jul 2012 21:37:07 -0700 (PDT) References: <2D42528A-932A-406D-A195-11BFE5250E64@cisco.com> From: Mahesh Jethanandani In-Reply-To: <2D42528A-932A-406D-A195-11BFE5250E64@cisco.com> Mime-Version: 1.0 (1.0) Date: Fri, 20 Jul 2012 21:37:03 -0700 Message-ID: <3095601404608869986@unknownmsgid> To: "karp@ietf.org" Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: [karp] IETF 84 KARP WG draft agenda posted X-BeenThere: karp@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Discussion list for key management for routing and transport protocols List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Jul 2012 04:36:11 -0000 Is there something written about this? Simplified Authentication Method for KARP KMP On Jul 20, 2012, at 4:14 PM, Brian Weis wrote: > Folks, > > There have been a few agenda requests for the KARP WG slot, and a draft agenda has been published: . > > Joel & Brian > _______________________________________________ > karp mailing list > karp@ietf.org > https://www.ietf.org/mailman/listinfo/karp From jmh@joelhalpern.com Tue Jul 24 14:39:04 2012 Return-Path: X-Original-To: karp@ietfa.amsl.com Delivered-To: karp@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F8F711E8072; Tue, 24 Jul 2012 14:39:04 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.265 X-Spam-Level: X-Spam-Status: No, score=-102.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MZLTP6Amh-wS; Tue, 24 Jul 2012 14:39:03 -0700 (PDT) Received: from morbo.mail.tigertech.net (morbo.mail.tigertech.net [67.131.251.54]) by ietfa.amsl.com (Postfix) with ESMTP id DF60E21F8565; Tue, 24 Jul 2012 14:39:03 -0700 (PDT) Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) by morbo.tigertech.net (Postfix) with ESMTP id 966F9A3952; Tue, 24 Jul 2012 14:39:03 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 8F22F1C9E22; Tue, 24 Jul 2012 14:39:02 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net Received: from [10.155.35.59] (unknown [129.192.185.163]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id D3B831C0863; Tue, 24 Jul 2012 14:39:01 -0700 (PDT) Message-ID: <500F15F2.1080606@joelhalpern.com> Date: Tue, 24 Jul 2012 17:38:58 -0400 From: "Joel M. Halpern" User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: "lisp@ietf.org" , "karp@ietf.org" References: <20120724200604.14449.1507.idtracker@ietfa.amsl.com> In-Reply-To: <20120724200604.14449.1507.idtracker@ietfa.amsl.com> X-Forwarded-Message-Id: <20120724200604.14449.1507.idtracker@ietfa.amsl.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: [karp] Fwd: NomCom 2012-2013: Second Call for Volunteers X-BeenThere: karp@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Discussion list for key management for routing and transport protocols List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jul 2012 21:39:04 -0000 If you are eligible, are not looking for appointment, and have not yet volunteered, please do so. The nomcom is important for the viability of the IETF. Thank you, Joel -------- Original Message -------- Subject: NomCom 2012-2013: Second Call for Volunteers Date: Tue, 24 Jul 2012 13:06:04 -0700 From: NomCom Chair To: IETF Announcement List The NomCom 2012-2013 Call for Volunteers has now passed its halfway point. Therefore, if you are considering volunteering to participate in the 2012-2013 NomCom, please do so soon. General information on this year's NomCom (including a list of positions to be filled) can be found at: https://www.ietf.org/nomcom/2012/ The success of the NomCom process depends on randomly selecting a committee that is a representative sample of the our community. We endeavor to have a NomCom reflecting the diversity of experience and viewpoints that is our community's greatest strength. However, to achieve this goal we must have the largest possible pool of volunteers that from throughout the IETF community. I am pleased to report that we have had a strong initial response to the First Call for Volunteers, with 74 qualified individuals agreeing to volunteer their time. I greatly appreciate the generosity and commitment to our community exhibited by all of these individuals. However, the pool of volunteers is not yet as diverse as it should be to reflect the breadth of our community with regards to nationality, gender and organizational affiliation. Therefore, I would especially encourage to volunteer those individuals whose participation would increase the diversity of our volunteer pool. If you have volunteered before 12:00 noon UTC on July 24, 2012 and you have not received a confirmation email from me, then an error has occurred and I would request that you resend your email. Details on how to volunteer can be found at the end of this message. To summarize, please volunteer by sending me an email containing your name, affiliation, and the email address you use to register for IETF meetings. The 74 qualified individuals who have so far volunteered are listed below. I apologize for any errors in this list, please notify me of any errors as soon as possible. Sam Aldrin, Huawei Ignas Bagdonas, Cisco Lou Berger, LabN Consulting Randy Bush, IIJ Dennis Cai, Cisco Daniele Ceccarelli, Ericsson Gang Chen, China Mobile Andras Csaszar, Ericsson Hui Deng, China Mobile Keith Drage, Alcatel-Lucent John Drake, Juniper Donald Eastlake, Huawei Charles Eckel, Cisco Mehmet Ersue, Nokia Siemens Networks Miguel Garcia, Ericsson Eric Gray, Ericsson Wassim Haddad, Ericsson Stephen Hanna, Juniper Sam Hartman, Painless Security Jia He, Huawei Giles Heron, Cisco Paul Hoffman, VPN Consortium Christer Holmberg, Ericsson Fangwei Hu, ZTE Andrew Hutton, Siemens Enterprise Communications Cullen Jennings, Cisco Yuanlong Jiang, Huawei Sheng Jiang, Huawei Lizhong Jin, ZTE Stephen Kent, BBN Ari Keranen, Ericsson Ning Kong, CNNIC Jouni Korhonen, Nokia Siemens Networks Mirja Kuehlewind, University of Stuttgart Eliot Lear, Cisco Hongyu Li, Huawei Guoman Liu, ZTE Wenhu Lu, Ericsson Yuxia Ma, ZTE Andrew Malis, Verizon Terry Manderson, ICANN Scott Mansfield, Ericsson Luca Martini, Cisco David Meyer, Cisco Monique Morrow, Cisco Thomas Nadeau, Juniper Karen O'Donoghue, Internet Society Borje Ohlman, Ericsson Keyur Patel, Cisco Teemu Savolainen, Nokia Benson Schliesser, Juniper John Scudder, Juniper Karen Seo, BBN Arturo Servin, LACNIC Shuo (Sean) Shen, CNNIC David Sini, Ericsson Haibin Song, Huawei Tom Taylor, PT Taylor Consulting Pascal Thubert, Cisco Mark Townsley, Cisco Tina Tsou, Huawei Bill VerSteeg, Cisco Thomas Walsh, Juniper Yinxing Wei, ZTE Stephan Wenger, Vidyo Magnus Westerlund, Ericsson Steven White, Alcatel-Lucent Qin (Bill) Wu, Huawei Leaf Yeh, Huawei Lixia Zhang, UCLA Zhaohui (Jeff) Zhang, Juniper Yi Zhao, Huawei Qian (Cathy) Zhou, Huawei Ning Zong, Huawei To be eligible, volunteers for the nomcom need to have attended 3 of the past 5 IETF meetings as of the time this announcement goes out. That is, 3 meetings from IETF 79 (Beijing) - IETF 83 (Paris). If you qualify, and if you will not be seeking appointment to any of the open positions that this nomcom will be filling, please consider volunteering. The primary activity for this nomcom will begin in August 2012 and should be completed in January 2013. The nomcom will be collecting requirements from the community, as well as talking to candidates and obtaining feedback from community members about candidates. There will be regularly scheduled conference calls to ensure progress. Thus, being a nomcom member does require some time commitment. Please volunteer by sending an email before 11:59 pm EDT (UTC - 4 hours) August 5, 2012 as follows: To: mlepinski.ietf@gmail.com Subject: Nomcom 2012-13 Volunteer Please include the following information in the body: // As you enter in the IETF Registration Form, // First/Given name followed by Last/Family Name // typically what goes in the Company field // in the IETF Registration Form [] // // For confirmation if selected Please expect an email response from me within 3 business days stating whether or not you are qualified. If you don't receive a response, please re-send your email with the tag "RESEND:" added to the subject line. If you are not yet sure you would like to volunteer, please consider that nomcom members play a very important role in shaping the leadership of the IETF. Ensuring the leadership of the IETF is fair and balanced and comprised of those who can lead the IETF in the right direction is an important responsibility that rests on the IETF participants at large. Volunteering for the nomcom is a good way of contributing toward that goal. I will be publishing a more detailed timetable for nomcom activities, as well as details of the randomness seeds to be used for the RFC 3797 selection process, within the next couple days. Thank you, Matthew Lepinski nomcom-chair@ietf.org (or mlepinski.ietf@gmail.com) From internet-drafts@ietf.org Mon Jul 30 09:21:12 2012 Return-Path: X-Original-To: karp@ietfa.amsl.com Delivered-To: karp@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 71E4A11E80A2; Mon, 30 Jul 2012 09:21:12 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.583 X-Spam-Level: X-Spam-Status: No, score=-102.583 tagged_above=-999 required=5 tests=[AWL=0.016, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QnLdPhu+gPlL; Mon, 30 Jul 2012 09:21:11 -0700 (PDT) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E09C11E8099; Mon, 30 Jul 2012 09:21:11 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 4.32 Message-ID: <20120730162111.10874.66597.idtracker@ietfa.amsl.com> Date: Mon, 30 Jul 2012 09:21:11 -0700 Cc: karp@ietf.org Subject: [karp] I-D Action: draft-ietf-karp-routing-tcp-analysis-04.txt X-BeenThere: karp@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Discussion list for key management for routing and transport protocols List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Jul 2012 16:21:12 -0000 A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the Keying and Authentication for Routing Pro= tocols Working Group of the IETF. Title : Analysis of BGP, LDP, PCEP and MSDP Issues According to = KARP Design Guide Author(s) : Mahesh Jethanandani Keyur Patel Lianshu Zheng Filename : draft-ietf-karp-routing-tcp-analysis-04.txt Pages : 18 Date : 2012-07-30 Abstract: This document analyzes BGP, LDP, PCEP and MSDP according to guidelines set forth in section 4.2 of Keying and Authentication for Routing Protocols Design Guidelines [RFC6518]. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-karp-routing-tcp-analysis There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-karp-routing-tcp-analysis-04 A diff from previous version is available at: http://tools.ietf.org/rfcdiff?url2=3Ddraft-ietf-karp-routing-tcp-analysis-04 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From mjethanandani@gmail.com Mon Jul 30 12:56:00 2012 Return-Path: X-Original-To: karp@ietfa.amsl.com Delivered-To: karp@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B4F311E81C5; Mon, 30 Jul 2012 12:56:00 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.599 X-Spam-Level: X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JhBUPme61uMp; Mon, 30 Jul 2012 12:55:59 -0700 (PDT) Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 9160611E815A; Mon, 30 Jul 2012 12:55:59 -0700 (PDT) Received: by vbbez10 with SMTP id ez10so5377867vbb.31 for ; Mon, 30 Jul 2012 12:55:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=DM1mxTe/6PI8ObTUxbdrXWKYxuEpVvhHxsWxnKl5bBM=; b=WKOzh7bRPIHCDGjCaFGnss4zUrSVjUEG2WWRLxLWd0jf+q2sgWBIxdx9FScZqw55Jb 8R8N0LuSJyIP+wp+0WdqpqfI+TZp8L8C7eIMjqsyuMVb8r7G016Wakzk9mpOGOgBSYUI VoKvIwLH8Lm3DWhnQOhiTdwaQnVksAyhOOYchbG1vRK0FW3kK6cdBvwY3pewIHEX9ifS KqasftxS0dnKzlZ2xTgCXPBZLzaTvRIahoYfr1dAWxu7iHBJjaDu+ZOoNRFqQD87xR6k 4Mpc8owo2Db/KVFDRVEYf1seXUXJCB9XVdHFBTPWTQoIZwQfKFg3O3M9jLBW9nkLc8ji ynRg== MIME-Version: 1.0 Received: by 10.59.1.193 with SMTP id bi1mr317307ved.57.1343678158914; Mon, 30 Jul 2012 12:55:58 -0700 (PDT) Received: by 10.58.75.202 with HTTP; Mon, 30 Jul 2012 12:55:58 -0700 (PDT) In-Reply-To: <20120730162111.10874.66597.idtracker@ietfa.amsl.com> References: <20120730162111.10874.66597.idtracker@ietfa.amsl.com> Date: Mon, 30 Jul 2012 12:55:58 -0700 Message-ID: From: Mahesh Jethanandani To: internet-drafts@ietf.org, "karp@ietf. org" Content-Type: multipart/alternative; boundary=047d7bdc9b6a5ac2f304c611738d Subject: Re: [karp] I-D Action: draft-ietf-karp-routing-tcp-analysis-04.txt X-BeenThere: karp@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Discussion list for key management for routing and transport protocols List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Jul 2012 19:56:00 -0000 --047d7bdc9b6a5ac2f304c611738d Content-Type: text/plain; charset=ISO-8859-1 This submission addresses the LC comments we received on the karp mailing list. Thanks. On Mon, Jul 30, 2012 at 9:21 AM, wrote: > > A New Internet-Draft is available from the on-line Internet-Drafts > directories. > This draft is a work item of the Keying and Authentication for Routing > Protocols Working Group of the IETF. > > Title : Analysis of BGP, LDP, PCEP and MSDP Issues > According to KARP Design Guide > Author(s) : Mahesh Jethanandani > Keyur Patel > Lianshu Zheng > Filename : draft-ietf-karp-routing-tcp-analysis-04.txt > Pages : 18 > Date : 2012-07-30 > > Abstract: > This document analyzes BGP, LDP, PCEP and MSDP according to > guidelines set forth in section 4.2 of Keying and Authentication for > Routing Protocols Design Guidelines [RFC6518]. > > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-karp-routing-tcp-analysis > > There's also a htmlized version available at: > http://tools.ietf.org/html/draft-ietf-karp-routing-tcp-analysis-04 > > A diff from previous version is available at: > http://tools.ietf.org/rfcdiff?url2=draft-ietf-karp-routing-tcp-analysis-04 > > > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ > > _______________________________________________ > karp mailing list > karp@ietf.org > https://www.ietf.org/mailman/listinfo/karp > --047d7bdc9b6a5ac2f304c611738d Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable This submission addresses the LC comments we received on the karp mailing l= ist.

Thanks.

On Mon, J= ul 30, 2012 at 9:21 AM, <internet-drafts@ietf.org> w= rote:

A New Internet-Draft is available from the on-line Internet-Drafts director= ies.
=A0This draft is a work item of the Keying and Authentication for Routing P= rotocols Working Group of the IETF.

=A0 =A0 =A0 =A0 Title =A0 =A0 =A0 =A0 =A0 : Analysis of BGP, LDP, PCEP and = MSDP Issues According to KARP Design Guide
=A0 =A0 =A0 =A0 Author(s) =A0 =A0 =A0 : Mahesh Jethanandani
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Keyur Patel
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Lianshu Zheng
=A0 =A0 =A0 =A0 Filename =A0 =A0 =A0 =A0: draft-ietf-karp-routing-tcp-analy= sis-04.txt
=A0 =A0 =A0 =A0 Pages =A0 =A0 =A0 =A0 =A0 : 18
=A0 =A0 =A0 =A0 Date =A0 =A0 =A0 =A0 =A0 =A0: 2012-07-30

Abstract:
=A0 =A0This document analyzes BGP, LDP, PCEP and MSDP according to
=A0 =A0guidelines set forth in section 4.2 of Keying and Authentication for=
=A0 =A0Routing Protocols Design Guidelines [RFC6518].

The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-karp-r= outing-tcp-analysis

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-karp-routing-tc= p-analysis-04

A diff from previous version is available at:
http://tools.ietf.org/rfcdiff?url2=3Ddraft-= ietf-karp-routing-tcp-analysis-04


Internet-Drafts are also available by anonymous FTP at:
ftp://ftp= .ietf.org/internet-drafts/

_______________________________________________
karp mailing list
karp@ietf.org
ht= tps://www.ietf.org/mailman/listinfo/karp

--047d7bdc9b6a5ac2f304c611738d-- From william.atwood@concordia.ca Mon Jul 30 14:45:06 2012 Return-Path: X-Original-To: karp@ietfa.amsl.com Delivered-To: karp@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 071F111E8101 for ; Mon, 30 Jul 2012 14:45:06 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.098 X-Spam-Level: X-Spam-Status: No, score=-6.098 tagged_above=-999 required=5 tests=[AWL=0.501, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z4-8xXVF6oKu for ; Mon, 30 Jul 2012 14:45:05 -0700 (PDT) Received: from oldperseverance.encs.concordia.ca (oldperseverance.encs.concordia.ca [132.205.96.94]) by ietfa.amsl.com (Postfix) with ESMTP id CB00D11E8197 for ; Mon, 30 Jul 2012 14:45:04 -0700 (PDT) Received: from [IPv6:::1] (bill@poise.encs.concordia.ca [132.205.2.209]) by oldperseverance.encs.concordia.ca (envelope-from william.atwood@concordia.ca) (8.13.7/8.13.7) with ESMTP id q6ULj1gA023740; Mon, 30 Jul 2012 17:45:01 -0400 Message-ID: <50170067.7060708@concordia.ca> Date: Mon, 30 Jul 2012 17:45:11 -0400 From: John William Atwood Organization: Concordia University, Montreal User-Agent: Mozilla/5.0 (Windows NT 6.0; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: KARP Working Group Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.58 on oldperseverance.encs.concordia.ca at 2012/07/30 17:45:01 EDT Cc: "Revathi B.S." Subject: [karp] draft-atwood-karp-akam-rp-02 X-BeenThere: karp@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Discussion list for key management for routing and transport protocols List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Jul 2012 21:45:06 -0000 We have posted version -02 of the above draft. It now includes the ACSII-art that was missing from version -01. Also, the internal cross-references are fixed, the external references are fixed, and there is a general tidying-up. We recognize that (as it is now) it is quite far from being a protocol specification. However, at this stage we wish to expose the design issues that we have explored, and get WG feedback on the desirability of moving it towards a precise specification. This draft will be presented tomorrow at the KARP WG session. Bill and Revathi -- Dr. J.W. Atwood, Eng. tel: +1 (514) 848-2424 x3046 Distinguished Professor Emeritus fax: +1 (514) 848-2830 Department of Computer Science and Software Engineering Concordia University EV 3.185 email:william.atwood@concordia.ca 1455 de Maisonneuve Blvd. West http://users.encs.concordia.ca/~bill Montreal, Quebec Canada H3G 1M8 From jmh@joelhalpern.com Mon Jul 30 22:19:01 2012 Return-Path: X-Original-To: karp@ietfa.amsl.com Delivered-To: karp@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB75C21F8645; Mon, 30 Jul 2012 22:19:01 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.265 X-Spam-Level: X-Spam-Status: No, score=-102.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U7ssncU0vuPm; Mon, 30 Jul 2012 22:19:01 -0700 (PDT) Received: from morbo.mail.tigertech.net (morbo.mail.tigertech.net [67.131.251.54]) by ietfa.amsl.com (Postfix) with ESMTP id 0605621F8644; Mon, 30 Jul 2012 22:19:01 -0700 (PDT) Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) by morbo.tigertech.net (Postfix) with ESMTP id B738AA6993; Mon, 30 Jul 2012 22:19:00 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 5D4131C0930; Mon, 30 Jul 2012 22:18:59 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net Received: from [130.129.70.15] (dhcp-460f.meeting.ietf.org [130.129.70.15]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id E7FFC1C08A5; Mon, 30 Jul 2012 22:18:58 -0700 (PDT) Message-ID: <50176ABF.4060009@joelhalpern.com> Date: Tue, 31 Jul 2012 01:18:55 -0400 From: "Joel M. Halpern" User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: "karp@ietf.org" , "lisp@ietf.org" References: <20120731044425.12307.52108.idtracker@ietfa.amsl.com> In-Reply-To: <20120731044425.12307.52108.idtracker@ietfa.amsl.com> X-Forwarded-Message-Id: <20120731044425.12307.52108.idtracker@ietfa.amsl.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: [karp] Fwd: NomCom 2012-2013: Third Call for Volunteers X-BeenThere: karp@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Discussion list for key management for routing and transport protocols List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Jul 2012 05:19:01 -0000 Sorry to belabour the obvious, but the community really needs folks to volunteer. Thanks, Joel -------- Original Message -------- Subject: NomCom 2012-2013: Third Call for Volunteers Date: Mon, 30 Jul 2012 21:44:25 -0700 From: NomCom Chair To: IETF Announcement List The NomCom 2012-2013 Call for Volunteers is nearing its conclusion. If you are considering volunteering to participate in the 2012-2013 NomCom, please volunteer soon. Individuals willing to serve on this year's NomCom must send email to nomcom-chair@ietf.org on or before Sunday, August 5. General information on this year's NomCom (including a list of positions to be filled) can be found at: https://www.ietf.org/nomcom/2012/ I am pleased to report at this time we have 98 qualified individuals who have generously volunteer their time to serve on this year's NomCom. However, last year the volunteer pool consisted of 120 members of our community and I would hope that we can have at least as many volunteers in the pool this year. Therefore, if you are eligible to serve on this year's NomCom (i.e., you have attended 3 of the last 5 IETF meetings), please consider volunteering! The success of the NomCom process depends on randomly selecting a committee that is a representative sample of the our community. We endeavor to have a NomCom reflecting the diversity of experience and viewpoints that is our community's greatest strength. However, to achieve this goal we must have the largest possible pool of volunteers that from throughout the IETF community. If you have volunteered before 15:00 UTC on July 30, 2012 and you have not received a confirmation email from me, then an error has occurred and I would request that you resend your email. The 98 qualified individuals who have thus far volunteered are listed below. I apologize for any errors in this list, please notify me of any errors as soon as possible. Sam Aldrin, Huawei Alia Atlas, Juniper Ignas Bagdonas, Cisco Marcelo Bagnulo, Universidad Carlos III de Madrid Lou Berger, LabN Consulting Deborah Brungard, AT&T John Brzozowski, Comcast Randy Bush, IIJ Dennis Cai, Cisco Daniele Ceccarelli, Ericsson Gang Chen, China Mobile Mach Chen, Huawei Andrew Chi, BBN Uma Chunduri, Ericsson Andras Csaszar, Ericsson Subir Das, ACS Hui Deng, China Mobile Keith Drage, Alcatel-Lucent John Drake, Juniper Donald Eastlake, Huawei Charles Eckel, Cisco Mehmet Ersue, Nokia Siemens Networks Miguel Garcia, Ericsson Wes George, Time Warner Cable Richard Graveman, RFG Security Eric Gray, Ericsson Jeff Haas, Juniper Wassim Haddad, Ericsson Stephen Hanna, Juniper Sam Hartman, Painless Security Jia He, Huawei Giles Heron, Cisco Paul Hoffman, VPN Consortium Christer Holmberg, Ericsson Lee Howard, Time Warner Cable Fangwei Hu, ZTE Jon Hudson, Brocade Andrew Hutton, Siemens Enterprise Communications Cullen Jennings, Cisco Yuanlong Jiang, Huawei Sheng Jiang, Huawei Lizhong Jin, ZTE Hadriel Kaplan, Acme Packet Stephen Kent, BBN Ari Keranen, Ericsson Ning Kong, CNNIC Jouni Korhonen, Nokia Siemens Networks Mirja Kuehlewind, University of Stuttgart Eliot Lear, Cisco Hongyu Li, Huawei Guoman Liu, ZTE Dapeng Liu, China Mobile Wenhu Lu, Ericsson Yuxia Ma, ZTE Andrew Malis, Verizon Terry Manderson, ICANN Scott Mansfield, Ericsson Luca Martini, Cisco Alexey Melnikov, Isode Limited David Meyer, Cisco Monique Morrow, Cisco Thomas Nadeau, Juniper Karen O'Donoghue, Internet Society Borje Ohlman, Ericsson Dimitri Papadimitriou , Alcatel-Lucent Keyur Patel, Cisco Radia Perlman, Intel Labs Teemu Savolainen, Nokia Benson Schliesser, Juniper John Scudder, Juniper Karen Seo, BBN Arturo Servin, LACNIC Shuo (Sean) Shen, CNNIC David Sinicrope , Ericsson Haibin Song, Huawei Tom Taylor, PT Taylor Consulting Pascal Thubert, Cisco Mark Townsley, Cisco Tina Tsou, Huawei Gunter Van de Velde, Cisco Bill VerSteeg, Cisco Thomas Walsh, Juniper Yinxing Wei, ZTE Stephan Wenger, Vidyo Magnus Westerlund, Ericsson Steven White, Alcatel-Lucent Ijsbrand (Ice) Wijnands, Cisco Qin (Bill) Wu, Huawei Jiankang Yao, CNNIC Leaf Yeh, Huawei Lucy Yong, Huawei Lixia Zhang, UCLA Zhaohui (Jeff) Zhang, Juniper Dacheng Zhang, Huawei Yi, Zhao Huawei Qian (Cathy) Zhou, Huawei Ning Zong, Huawei Glenn Zorn, Network Zen The primary activity for this nomcom will begin in August 2012 and should be completed in January 2013. The nomcom will be collecting requirements from the community, as well as talking to candidates and obtaining feedback from community members about candidates. There will be regularly scheduled conference calls to ensure progress. Thus, being a nomcom member does require some time commitment. Please volunteer by sending an email before 11:59 pm EDT (UTC - 4 hours) August 5, 2012 as follows: To: nomcom-chair@ietf.org Subject: Nomcom 2012-13 Volunteer Please include the following information in the body: // As you enter in the IETF Registration Form, // First/Given name followed by Last/Family Name // typically what goes in the Company field // in the IETF Registration Form [] // // For confirmation if selected Please expect an email response from me within 3 business days stating whether or not you are qualified. If you don't receive a response, please re-send your email with the tag "RESEND:" added to the subject line. If you are not yet sure you would like to volunteer, please consider that NomCom members play a very important role in shaping the leadership of the IETF. Ensuring the leadership of the IETF is fair and balanced and comprised of those who can lead the IETF in the right direction is an important responsibility that rests on the IETF participants at large. Volunteering for the nomcom is a good way of contributing toward that goal. Thank you, Matthew Lepinski nomcom-chair@ietf.org (or mlepinski.ietf@gmail.com)