From rtgwg-bounces@ietf.org Fri Jan 16 13:57:01 2009 Return-Path: X-Original-To: rtgwg-archive@optimus.ietf.org Delivered-To: ietfarch-rtgwg-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 222063A6AFA; Fri, 16 Jan 2009 13:57:01 -0800 (PST) X-Original-To: rtgwg@core3.amsl.com Delivered-To: rtgwg@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E6C023A67DF for ; Fri, 16 Jan 2009 13:56:59 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.52 X-Spam-Level: X-Spam-Status: No, score=-6.52 tagged_above=-999 required=5 tests=[AWL=0.079, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Uk55OjaBSRPy for ; Fri, 16 Jan 2009 13:56:59 -0800 (PST) Received: from exprod7og108.obsmtp.com (exprod7og108.obsmtp.com [64.18.2.169]) by core3.amsl.com (Postfix) with ESMTP id 1677D3A6AF6 for ; Fri, 16 Jan 2009 13:56:59 -0800 (PST) Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob108.postini.com ([64.18.6.12]) with SMTP ID DSNKSXECmpKKvklySRzfyR4IkOe6LHUABGLN@postini.com; Fri, 16 Jan 2009 13:56:44 PST Received: from p-emfe01-sac.jnpr.net (66.129.254.72) by P-EMHUB01-HQ.jnpr.net (172.24.192.35) with Microsoft SMTP Server id 8.1.336.0; Fri, 16 Jan 2009 13:54:16 -0800 Received: from p-emlb01-sac.jnpr.net ([66.129.254.46]) by p-emfe01-sac.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Fri, 16 Jan 2009 13:54:16 -0800 Received: from emailsmtp56.jnpr.net ([172.24.60.77]) by p-emlb01-sac.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Fri, 16 Jan 2009 13:54:16 -0800 Received: from magenta.juniper.net ([172.17.27.123]) by emailsmtp56.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Fri, 16 Jan 2009 13:54:16 -0800 Received: from [172.16.13.200] ([172.16.13.200]) by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id n0GLsFM60019 for ; Fri, 16 Jan 2009 13:54:15 -0800 (PST) (envelope-from jgs@juniper.net) Message-ID: From: "John G. Scudder" To: rtgwg@ietf.org MIME-Version: 1.0 (Apple Message framework v930.3) Subject: Fwd: RFC 5378 and Draft Submissions Date: Fri, 16 Jan 2009 16:54:14 -0500 References: X-Mailer: Apple Mail (2.930.3) X-OriginalArrivalTime: 16 Jan 2009 21:54:16.0613 (UTC) FILETIME=[FA0DBD50:01C97824] X-BeenThere: rtgwg@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes" Sender: rtgwg-bounces@ietf.org Errors-To: rtgwg-bounces@ietf.org Folks submitting Internet Drafts which incorporate material from earlier IETF content should be aware of the below. You may also want to take a look at http://www.ietf.org/mail-archive/web/ietf/current/msg54839.html . I would be interested in knowing if any rtgwg draft authors believe they will be affected by this issue. Any discussion of this issue not specifically related to rtgwg drafts should be taken to the main IETF discussion list where you will find a lively discussion underway. --John Begin forwarded message: > From: "Eric Rescorla" > Date: January 15, 2009 12:03:42 AM GMT-05:00 > To: "Working Group Chairs" > Subject: Fwd: RFC 5378 and Draft Submissions > > FYI > > > ---------- Forwarded message ---------- > From: Eric Rescorla > Date: Wed, Jan 14, 2009 at 9:03 PM > Subject: RFC 5378 and Draft Submissions > To: tls@ietf.org > > > IETF Chair Russ Housley has asked WG chairs to apprise their WGs of > the following information. > > If you've been following the IETF mailing list, you may be aware of > the ongoing discussion about the impact of RFC 5378 on revised draft > submissions. Briefly, RFC 5378 requires Contributors to grant a more > expansive set of rights than were granted by RFC 3978, and 4748. If > you are submitting a document which contains text contributed by > others prior to the publication of RFC 5378 you may need to obtain > additional rights from the > copyright holders of that text in order to contribute under the 5378 > terms. > > The IESG and the IETF Trustees are working to resolve those issues > (see > http://trustee.ietf.org/docs/Background-to-Draft-Update-to-IETF-Trust-Legal-Provisions.txt) > . > However, > at present I would advise care prior to submitting any draft > which contains material derived from an RFC, draft, or mailing > list message published prior to November 10, 2008. > Speaking personally, I have chosen not to submit new versions > of most of my drafts until matters are resolved. > > Please take any general discussion of RFC 5378 to ietf@ietf.org > > -Ekr > [As WG Chair] _______________________________________________ rtgwg mailing list rtgwg@ietf.org https://www.ietf.org/mailman/listinfo/rtgwg From rtgwg-bounces@ietf.org Fri Jan 16 16:26:44 2009 Return-Path: X-Original-To: rtgwg-archive@optimus.ietf.org Delivered-To: ietfarch-rtgwg-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8EC8F3A6A41; Fri, 16 Jan 2009 16:26:44 -0800 (PST) X-Original-To: rtgwg@core3.amsl.com Delivered-To: rtgwg@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EC7E33A6A41 for ; Fri, 16 Jan 2009 16:26:43 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.599 X-Spam-Level: X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YUB3CstAetZG for ; Fri, 16 Jan 2009 16:26:43 -0800 (PST) Received: from exprod7og101.obsmtp.com (exprod7og101.obsmtp.com [64.18.2.155]) by core3.amsl.com (Postfix) with ESMTP id ED7B43A68C8 for ; Fri, 16 Jan 2009 16:26:42 -0800 (PST) Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob101.postini.com ([64.18.6.12]) with SMTP ID DSNKSXElqHLwoNdojxWwYkqzv1mRwaHFKRTI@postini.com; Fri, 16 Jan 2009 16:26:28 PST Received: from p-emfe01-sac.jnpr.net (66.129.254.72) by P-EMHUB01-HQ.jnpr.net (172.24.192.35) with Microsoft SMTP Server id 8.1.336.0; Fri, 16 Jan 2009 16:23:53 -0800 Received: from p-emlb01-sac.jnpr.net ([66.129.254.46]) by p-emfe01-sac.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Fri, 16 Jan 2009 16:23:53 -0800 Received: from emailsmtp55.jnpr.net ([172.24.18.132]) by p-emlb01-sac.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Fri, 16 Jan 2009 16:23:52 -0800 Received: from magenta.juniper.net ([172.17.27.123]) by emailsmtp55.jnpr.net with Microsoft SMTPSVC(6.0.3790.1830); Fri, 16 Jan 2009 16:23:52 -0800 Received: from [172.26.250.98] ([172.26.250.98]) by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id n0H0NpM28300; Fri, 16 Jan 2009 16:23:51 -0800 (PST) (envelope-from raszuk@juniper.net) Message-ID: <49712516.8000904@juniper.net> Date: Fri, 16 Jan 2009 16:23:50 -0800 From: Robert Raszuk User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: "John G. Scudder" Subject: Re: Fwd: RFC 5378 and Draft Submissions References: In-Reply-To: X-OriginalArrivalTime: 17 Jan 2009 00:23:52.0573 (UTC) FILETIME=[E0248AD0:01C97839] Cc: rtgwg@ietf.org X-BeenThere: rtgwg@ietf.org X-Mailman-Version: 2.1.9 Precedence: list Reply-To: raszuk@juniper.net List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: rtgwg-bounces@ietf.org Errors-To: rtgwg-bounces@ietf.org Hi John, Not for rtgwg but for idr wg I have been struggling with this for the last 10 days and it's just hopeless. Can we ask Bill to post real xml2rfc translation 1.34 which does the job right and we all are done ? The beta 1.34r2 currently available still fails the new IDNITS check. Thx, R. > Folks submitting Internet Drafts which incorporate material from earlier > IETF content should be aware of the below. You may also want to take a > look at http://www.ietf.org/mail-archive/web/ietf/current/msg54839.html . > > I would be interested in knowing if any rtgwg draft authors believe they > will be affected by this issue. Any discussion of this issue not > specifically related to rtgwg drafts should be taken to the main IETF > discussion list where you will find a lively discussion underway. > > --John > > Begin forwarded message: > >> From: "Eric Rescorla" >> Date: January 15, 2009 12:03:42 AM GMT-05:00 >> To: "Working Group Chairs" >> Subject: Fwd: RFC 5378 and Draft Submissions >> >> FYI >> >> >> ---------- Forwarded message ---------- >> From: Eric Rescorla >> Date: Wed, Jan 14, 2009 at 9:03 PM >> Subject: RFC 5378 and Draft Submissions >> To: tls@ietf.org >> >> >> IETF Chair Russ Housley has asked WG chairs to apprise their WGs of >> the following information. >> >> If you've been following the IETF mailing list, you may be aware of >> the ongoing discussion about the impact of RFC 5378 on revised draft >> submissions. Briefly, RFC 5378 requires Contributors to grant a more >> expansive set of rights than were granted by RFC 3978, and 4748. If >> you are submitting a document which contains text contributed by >> others prior to the publication of RFC 5378 you may need to obtain >> additional rights from the >> copyright holders of that text in order to contribute under the 5378 >> terms. >> >> The IESG and the IETF Trustees are working to resolve those issues >> (see >> http://trustee.ietf.org/docs/Background-to-Draft-Update-to-IETF-Trust-Legal-Provisions.txt). >> >> However, >> at present I would advise care prior to submitting any draft >> which contains material derived from an RFC, draft, or mailing >> list message published prior to November 10, 2008. >> Speaking personally, I have chosen not to submit new versions >> of most of my drafts until matters are resolved. >> >> Please take any general discussion of RFC 5378 to ietf@ietf.org >> >> -Ekr >> [As WG Chair] > > _______________________________________________ > rtgwg mailing list > rtgwg@ietf.org > https://www.ietf.org/mailman/listinfo/rtgwg > _______________________________________________ rtgwg mailing list rtgwg@ietf.org https://www.ietf.org/mailman/listinfo/rtgwg From rtgwg-bounces@ietf.org Sat Jan 17 16:22:12 2009 Return-Path: X-Original-To: rtgwg-archive@optimus.ietf.org Delivered-To: ietfarch-rtgwg-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F3BA83A69CC; Sat, 17 Jan 2009 16:22:11 -0800 (PST) X-Original-To: rtgwg@core3.amsl.com Delivered-To: rtgwg@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 031983A69CC for ; Sat, 17 Jan 2009 16:22:11 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.523 X-Spam-Level: X-Spam-Status: No, score=-6.523 tagged_above=-999 required=5 tests=[AWL=0.076, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6RXf3B08JJ8T for ; Sat, 17 Jan 2009 16:22:10 -0800 (PST) Received: from exprod7og102.obsmtp.com (exprod7og102.obsmtp.com [64.18.2.157]) by core3.amsl.com (Postfix) with ESMTP id EF6B43A694D for ; Sat, 17 Jan 2009 16:22:09 -0800 (PST) Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob102.postini.com ([64.18.6.12]) with SMTP ID DSNKSXJ2Hpz9uY4C5EUidJg4PizHxgzuRxVX@postini.com; Sat, 17 Jan 2009 16:21:55 PST Received: from p-emfe01-sac.jnpr.net (66.129.254.72) by P-EMHUB01-HQ.jnpr.net (172.24.192.35) with Microsoft SMTP Server id 8.1.336.0; Sat, 17 Jan 2009 16:19:15 -0800 Received: from p-emlb01-sac.jnpr.net ([66.129.254.46]) by p-emfe01-sac.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Sat, 17 Jan 2009 16:19:14 -0800 Received: from emailsmtp56.jnpr.net ([172.24.60.77]) by p-emlb01-sac.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Sat, 17 Jan 2009 16:19:14 -0800 Received: from magenta.juniper.net ([172.17.27.123]) by emailsmtp56.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Sat, 17 Jan 2009 16:19:14 -0800 Received: from [172.16.13.200] ([172.16.13.200]) by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id n0I0JBM26629; Sat, 17 Jan 2009 16:19:11 -0800 (PST) (envelope-from jgs@juniper.net) Message-ID: <91A0C4B5-9A4D-42CA-8F96-E75624A2D571@juniper.net> From: "John G. Scudder" To: rtgwg@ietf.org In-Reply-To: <49712516.8000904@juniper.net> MIME-Version: 1.0 (Apple Message framework v930.3) Subject: Re: RFC 5378 and Draft Submissions Date: Sat, 17 Jan 2009 19:19:10 -0500 References: <49712516.8000904@juniper.net> X-Mailer: Apple Mail (2.930.3) X-OriginalArrivalTime: 18 Jan 2009 00:19:14.0734 (UTC) FILETIME=[64F36CE0:01C97902] X-BeenThere: rtgwg@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes" Sender: rtgwg-bounces@ietf.org Errors-To: rtgwg-bounces@ietf.org For the benefit of others: The problem Robert was having turned out to be that to pass the new idnits, assuming you're using the XML template you have to not only use the beta xml2rfc but also put in 'ipr="trust200811"' in the element. Note that having done so, your I-D will contain new IPR language. Whether that IPR language is acceptable to you is another matter and is what the initial message was about. --John On Jan 16, 2009, at 7:23 PM, Robert Raszuk wrote: > Hi John, > > Not for rtgwg but for idr wg I have been struggling with this for > the last 10 days and it's just hopeless. > > Can we ask Bill to post real xml2rfc translation 1.34 which does the > job right and we all are done ? > > The beta 1.34r2 currently available still fails the new IDNITS check. > > Thx, > R. > >> Folks submitting Internet Drafts which incorporate material from >> earlier IETF content should be aware of the below. You may also >> want to take a look at http://www.ietf.org/mail-archive/web/ietf/current/msg54839.html >> . >> I would be interested in knowing if any rtgwg draft authors believe >> they will be affected by this issue. Any discussion of this issue >> not specifically related to rtgwg drafts should be taken to the >> main IETF discussion list where you will find a lively discussion >> underway. >> --John >> Begin forwarded message: >>> From: "Eric Rescorla" >>> Date: January 15, 2009 12:03:42 AM GMT-05:00 >>> To: "Working Group Chairs" >>> Subject: Fwd: RFC 5378 and Draft Submissions >>> >>> FYI >>> >>> >>> ---------- Forwarded message ---------- >>> From: Eric Rescorla >>> Date: Wed, Jan 14, 2009 at 9:03 PM >>> Subject: RFC 5378 and Draft Submissions >>> To: tls@ietf.org >>> >>> >>> IETF Chair Russ Housley has asked WG chairs to apprise their WGs of >>> the following information. >>> >>> If you've been following the IETF mailing list, you may be aware of >>> the ongoing discussion about the impact of RFC 5378 on revised draft >>> submissions. Briefly, RFC 5378 requires Contributors to grant a more >>> expansive set of rights than were granted by RFC 3978, and 4748. If >>> you are submitting a document which contains text contributed by >>> others prior to the publication of RFC 5378 you may need to obtain >>> additional rights from the >>> copyright holders of that text in order to contribute under the 5378 >>> terms. >>> >>> The IESG and the IETF Trustees are working to resolve those issues >>> (see >>> http://trustee.ietf.org/docs/Background-to-Draft-Update-to-IETF-Trust-Legal-Provisions.txt) >>> . >>> However, >>> at present I would advise care prior to submitting any draft >>> which contains material derived from an RFC, draft, or mailing >>> list message published prior to November 10, 2008. >>> Speaking personally, I have chosen not to submit new versions >>> of most of my drafts until matters are resolved. >>> >>> Please take any general discussion of RFC 5378 to ietf@ietf.org >>> >>> -Ekr >>> [As WG Chair] >> _______________________________________________ >> rtgwg mailing list >> rtgwg@ietf.org >> https://www.ietf.org/mailman/listinfo/rtgwg > > _______________________________________________ > rtgwg mailing list > rtgwg@ietf.org > https://www.ietf.org/mailman/listinfo/rtgwg _______________________________________________ rtgwg mailing list rtgwg@ietf.org https://www.ietf.org/mailman/listinfo/rtgwg Return-Path: X-Original-To: rtgwg@ietf.org Delivered-To: rtgwg@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 0) id 1590E3A67D0; Fri, 27 Feb 2009 06:30:02 -0800 (PST) From: Internet-Drafts@ietf.org To: i-d-announce@ietf.org Subject: I-D Action:draft-ietf-rtgwg-ipfrr-framework-10.txt Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 Message-Id: <20090227143002.1590E3A67D0@core3.amsl.com> Date: Fri, 27 Feb 2009 06:30:02 -0800 (PST) Cc: rtgwg@ietf.org X-BeenThere: rtgwg@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Feb 2009 14:30:02 -0000 --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Routing Area Working Group Working Group of the IETF. Title : IP Fast Reroute Framework Author(s) : M. Shand, S. Bryant Filename : draft-ietf-rtgwg-ipfrr-framework-10.txt Pages : 15 Date : 2009-02-27 This document provides a framework for the development of IP fast- reroute mechanisms which provide protection against link or router failure by invoking locally determined repair paths. Unlike MPLS fast-reroute, the mechanisms are applicable to a network employing conventional IP routing and forwarding. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-rtgwg-ipfrr-framework-10.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Message/External-body; name="draft-ietf-rtgwg-ipfrr-framework-10.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2009-02-27062958.I-D@ietf.org> --NextPart--