Re: [Idr] draft-ietf-idr-ls-distribution-12.txt - Need IPR Statements from Stefano and Adrian Farell
"Adrian Farrel" <adrian@olddog.co.uk> Thu, 08 October 2015 17:40 UTC
Return-Path: <adrian@olddog.co.uk>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 69F341B2C8F for <idr@ietfa.amsl.com>; Thu, 8 Oct 2015 10:40:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id da2SBRUzc6J5 for <idr@ietfa.amsl.com>; Thu, 8 Oct 2015 10:40:05 -0700 (PDT)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 008BC1B2C6A for <idr@ietf.org>; Thu, 8 Oct 2015 10:40:03 -0700 (PDT)
Received: from asmtp1.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id t98HdwUF010227; Thu, 8 Oct 2015 18:39:58 +0100
Received: from 950129200 ([195.235.52.107]) (authenticated bits=0) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id t98HduTj010214 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Thu, 8 Oct 2015 18:39:57 +0100
From: Adrian Farrel <adrian@olddog.co.uk>
To: 'Susan Hares' <shares@ndzh.com>, idr@ietf.org
References: <026601d101ea$9d06d220$d7147660$@ndzh.com>
In-Reply-To: <026601d101ea$9d06d220$d7147660$@ndzh.com>
Date: Thu, 08 Oct 2015 18:39:55 +0100
Message-ID: <026b01d101f0$58d8b130$0a8a1390$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----=_NextPart_000_0270_01D101F8.BAB709D0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQH278KreJAKH0WIdvWHfK53ffa7j54V//3A
Content-Language: en-gb
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-7.1.0.1679-8.0.0.1202-21868.001
X-TM-AS-Result: No--30.939-10.0-31-10
X-imss-scan-details: No--30.939-10.0-31-10
X-TMASE-MatchedRID: UP6whsI5SHI7iuZ/mdYYtjWTue91XZHDBzeUreHAzYgo2+Ok231z9WHz kjQ054ZHfdrAxCWNGK4D2WXLXdz+AT5ZauPuz7Kf5DJ1FS+XdBMC8rQ71d/YfmslT14R4xhzXFf PPGX02lRfxjHOlzzBh1rXg0lwq1E0pjnmJgKhwtG0ljd+XDHvv6HqtQEoMNNyNW6MKrEwJQSpsn 4veQ+UcJFN+B8oJZ5a71Wx2uUbPLdDr8MVm6DK3TA4N9SXuYkp/hkBSy3LYQ17CjyP3UZ5MbpGA Q2wD/3Qyx6w4CJ+2uX2Ii0VSfdeQzuvYa1v2IFhTx0U/40+rr7a6BBkIrnTcudLZPVW5sDNedxy f/baQ0eb2ohNz0F+pNT+TcIhUUCBZJAk04EAz2WSs1st/hpgblzOKVR59i8DP5mpBtPr/e7et/a EQRVJHkNKRRr2LbXrWCjDJRYeAZ0BL/XzNFFmHxS11FlOYRohXalr5okxvJoO7TPqCvpgyqwvTQ psPBALizFhECDuofD4pTO56aJ0/JAX3UzEQF1Gte8MfJIL55SVIEi8fvjB8mtqvVA5MKaPOXn4h ABxhWTyUQNiagGSs9sfxZpQv2qMHYJM0iEvYc+YI2SdJezB/xKQZ2ZC35dZZeWOGcHSVtrab8Bo o9+oYI+axNKleguEnVTWWiNp+v8tlZY1WAfRjbLLTvamG8BJxoPTvryEwdE7hqeHvZGqTq26Pw0 p8J2yav6y9O33wRuZroPNdqiG8/riLmWBrDIEDO+DX+rUwfaEO4fjYvg2E6fv1BvYvhnLFwNwQX pdRk5EpXseTYQiwxLuW4a3q2WG6Pzo2DwBrIqbKItl61J/yZUdXE/WGn0FfeZdJ1XsorgfnX1OO O1e19o+XQHhuyp8OIMWCsd8LVZwP6ZWAcVaZqB2cfLRaJG2ftwZ3X11IV0=
Archived-At: <http://mailarchive.ietf.org/arch/msg/idr/YBRkdNC_exsgQjTS1hHd0E3_5LA>
Subject: Re: [Idr] draft-ietf-idr-ls-distribution-12.txt - Need IPR Statements from Stefano and Adrian Farell
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Oct 2015 17:40:11 -0000
Hi Sue, Attached. And then, of course, I just posted the latest revision as can be seen by the datatracker, and that version includes... This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. But, to avoid a discussion: No, I am not aware of any IPR related to this document that has not already been disclosed. Thanks, Adrian From: Susan Hares [mailto:shares@ndzh.com] Sent: 08 October 2015 17:59 To: idr@ietf.org; 'Adrian Farrel'; sprevidi@cisco.com' Cc: 'Alvaro Retana (aretana)' Subject: draft-ietf-idr-ls-distribution-12.txt - Need IPR Statements from Stefano and Adrian Farell Stefano and Adrian: We cannot finishing processing of draft-ietf-idr-ls-distribution until you answers the WG LC IPR Statement Do you know if any IPR other than the disclosure WG IPR at: https://datatracker.ietf.org/ipr/1864/ Sue Hares For Shepherd Jie Dong
--- Begin Message ---Hi Sue, I am personally unaware of any IPR that has not already been disclosed that might impact upon this draft. Thanks, Adrian From: Susan Hares [mailto:shares@ndzh.com] Sent: 05 March 2014 04:57 To: draft-ietf-idr-ls-distribution@tools.ietf.org; Bruno Rijsman; Hannes Gredler Cc: 'Adrian Farrel'; Alia Atlas; John G. Scudder Subject: Mail regarding draft-ietf-idr-ls-distribution Bruno, Adrian, Hannes, Jan, Stefano, and Saikat Welcome to the phase of the RFC process that can be painful. I am your document shepherd as well as WG co-chair. This message is one of a stream of emails you will need to respond quickly to in order to push this to RFC quickly. First of all, please confirm for the RFC process that you have disclosed all IPR. Please respond to this message. It is a gating factor on the early allocation that Alia Atlas (our new AD) will perform. Unfortunately, you will also be asked to confirm this on-list during the WG LC call. Here's my current plan for the approval process of this document in March-April. 3/5/14 - Update shepherd's write-up gets forwarded to Alia Atlas (new AD) can approve the early allocation a) AFI/SAFI b) BGP Path Attribute 3/6-3/11: Editorial comments (see below) will be sent to you from me (and perhaps Alia) on this document and the implementation report. The first set of these editorial comments is the fixing of the nits below. The second set will be sent on Thursday based on my re-reading the document and the IETF 89 discussion. Please spin this document with the fixes. 3/12-3/26: I will do a WG LC I will do a WG LC, and send this draft to GEN-ART, OPS-DIR, ISIS chairs, I2RS WG chairs, routing directorate, and Routing AD for early review. The early review process allows these groups to provide early review prior to the IESG process. The benefit to these reviews is that we may spin a copy of the draft prior to entering the IESG approval process. As Adrian will tell you, a document which goes in pre-approved by these groups tends to go through quicker. Please plan to select members of the team to respond to these editorials. 3/26: Final check before IESG Evaluation If you have responded to the GEN-ART, OPS-IDR, ISIS Chairs, and Routing AD, We'll do a last email exchange and then I will send it to Alia Atlas and Adrian for IESG Review. 3/27-4/30(?) Adrian and Alia have the following steps to go through: a) IETF LC b) Directorate formal reviews (GEN-ART, OPS-DIR, Routing Directorate (if they wish)) c) Final IESG review Again, please elect someone to respond quickly to these action. Thank you, Susan Hares =============== Editorial comments on: On draft-ietf-idr-ls-distribution: 1) Please provide XML, TXT, and pdf as input 2) Please fix the following nits Checking nits according to http://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- == There are 1 instance of lines with private range IPv4 addresses in the document. If these are generic example addresses, they should be changed to use any of the ranges defined in RFC 5735 (or successor): 192.0.2.x, 198.51.100.x or 203.0.113.x. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document seems to lack the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords -- however, there's a paragraph with a matching beginning. Boilerplate error? (The document does seem to have the reference to RFC 2119 which the ID-Checklist requires). -- The document date (July 15, 2012) is 597 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Obsolete normative reference: RFC 4893 (Obsoleted by RFC 6793) == Outdated reference: A later version (-26) exists of draft-ietf-alto-protocol-11 == Outdated reference: draft-ietf-isis-mi has been published as RFC 6822 Summary: 1 error (**), 0 flaws (~~), 5 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. ========= Editorial comments on the implementation report 1) If you have a third implementation - please add it by 3/10 2) Make sure to provide txt, xml, and pdf - in good forms.--- End Message ---
- [Idr] draft-ietf-idr-ls-distribution-12.txt - Nee… Susan Hares
- Re: [Idr] draft-ietf-idr-ls-distribution-12.txt -… Susan Hares
- Re: [Idr] draft-ietf-idr-ls-distribution-12.txt -… Stefano Previdi (sprevidi)
- Re: [Idr] draft-ietf-idr-ls-distribution-12.txt -… Adrian Farrel
- Re: [Idr] draft-ietf-idr-ls-distribution-12.txt -… Susan Hares