Re: Status of <draft-ietf-6man-default-iids-16.txt> in AUTH48
Fernando Gont <fgont@si6networks.com> Sun, 12 February 2017 21:10 UTC
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0220F1293E3 for <ipv6@ietfa.amsl.com>; Sun, 12 Feb 2017 13:10:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 Jc1yOH6WqqcO for <ipv6@ietfa.amsl.com>; Sun, 12 Feb 2017 13:10:49 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6BC71128BA2 for <ipv6@ietf.org>; Sun, 12 Feb 2017 13:10:49 -0800 (PST)
Received: from [IPv6:2001:1291:200:42e::2] (cl-1071.udi-01.br.sixxs.net [IPv6:2001:1291:200:42e::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 04FB980556; Sun, 12 Feb 2017 22:10:44 +0100 (CET)
Subject: Re: Status of <draft-ietf-6man-default-iids-16.txt> in AUTH48
To: Fred Baker <fredbaker.ietf@gmail.com>, Bob Hinden <bob.hinden@gmail.com>
References: <C9FDAEB9-9F79-4186-9C48-5F44E5E07235@gmail.com> <CE675DB5-BE9D-448D-9B4A-A61474E4F166@gmail.com>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <9ddb1820-cfd6-6fdf-da28-70d85d7bb9dc@si6networks.com>
Date: Sun, 12 Feb 2017 17:33:11 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <CE675DB5-BE9D-448D-9B4A-A61474E4F166@gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/S5E5UYVszx6MeeqRMHQg6wEzUWo>
Cc: IPv6 List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 12 Feb 2017 21:10:52 -0000
On 02/11/2017 03:15 PM, Fred Baker wrote: > I take it these are family members of Fernando's? If so, this is common in books, but not in RFCs. These are Acknowledgements of an RFC you've written (RFC1812): ---- cut here ---- Acknowledgments O that we now had here But one ten thousand of those men in England That do no work to-day! What's he that wishes so? My cousin Westmoreland? No, my fair cousin: If we are mark'd to die, we are enow To do our country loss; and if to live, The fewer men, the greater share of honour. God's will! I pray thee, wish not one man more. By Jove, I am not covetous for gold, Nor care I who doth feed upon my cost; It yearns me not if men my garments wear; Such outward things dwell not in my desires: But if it be a sin to covet honour, I am the most offending soul alive. No, faith, my coz, wish not a man from England: God's peace! I would not lose so great an honour As one man more, methinks, would share from me For the best hope I have. O, do not wish one more! Rather proclaim it, Westmoreland, through my host, That he which hath no stomach to this fight, Let him depart; his passport shall be made And crowns for convoy put into his purse: We would not die in that man's company That fears his fellowship to die with us. This day is called the feast of Crispian: He that outlives this day, and comes safe home, Will stand a tip-toe when the day is named, And rouse him at the name of Crispian. He that shall live this day, and see old age, Will yearly on the vigil feast his neighbours, And say 'To-morrow is Saint Crispian:' Then will he strip his sleeve and show his scars. And say 'These wounds I had on Crispin's day.' Old men forget: yet all shall be forgot, But he'll remember with advantages What feats he did that day: then shall our names. Familiar in his mouth as household words Harry the king, Bedford and Exeter, Warwick and Talbot, Salisbury and Gloucester, Baker Standards Track [Page 173] RFC 1812 Requirements for IP Version 4 Routers June 1995 Be in their flowing cups freshly remember'd. This story shall the good man teach his son; And Crispin Crispian shall ne'er go by, From this day to the ending of the world, But we in it shall be remember'd; We few, we happy few, we band of brothers; For he to-day that sheds his blood with me Shall be my brother; be he ne'er so vile, This day shall gentle his condition: And gentlemen in England now a-bed Shall think themselves accursed they were not here, And hold their manhoods cheap whiles any speaks That fought with us upon Saint Crispin's day. -- William Shakespeare This memo is a product of the IETF's Router Requirements Working Group. A memo such as this one is of necessity the work of many more people than could be listed here. A wide variety of vendors, network managers, and other experts from the Internet community graciously contributed their time and wisdom to improve the quality of this memo. The editor wishes to extend sincere thanks to all of them. The current editor also wishes to single out and extend his heartfelt gratitude and appreciation to the original editor of this document; Philip Almquist. Without Philip's work, both as the original editor and as the Chair of the working group, this document would not have been produced. He also wishes to express deep and heartfelt gratitude to the previous editor, Frank Kastenholz. Frank changed the original document from a collection of information to a useful description of IP technology - in his words, a "snapshot" of the technology in 1991. One can only hope that this snapshot, of the technology in 1994, is as clear. Philip Almquist, Jeffrey Burgan, Frank Kastenholz, and Cathy Wittbrodt each wrote major chapters of this memo. Others who made major contributions to the document included Bill Barns, Steve Deering, Kent England, Jim Forster, Martin Gross, Jeff Honig, Steve Knowles, Yoni Malachi, Michael Reilly, and Walt Wimer. Additional text came from Andy Malis, Paul Traina, Art Berggreen, John Cavanaugh, Ross Callon, John Lekashman, Brian Lloyd, Gary Malkin, Milo Medin, John Moy, Craig Partridge, Stephanie Price, Yakov Rekhter, Steve Senum, Richard Smith, Frank Solensky, Rich Woundy, and others who have been inadvertently overlooked. Some of the text in this memo has been (shamelessly) plagiarized from earlier documents, most notably RFC-1122 by Bob Braden and the Host Baker Standards Track [Page 174] RFC 1812 Requirements for IP Version 4 Routers June 1995 Requirements Working Group, and RFC-1009 by Bob Braden and Jon Postel. The work of these earlier authors is gratefully acknowledged. Jim Forster was a co-chair of the Router Requirements Working Group during its early meetings, and was instrumental in getting the group off to a good start. Jon Postel, Bob Braden, and Walt Prue also contributed to the success by providing a wealth of good advice before the group's first meeting. Later on, Phill Gross, Vint Cerf, and Noel Chiappa all provided valuable advice and support. Mike St. Johns coordinated the Working Group's interactions with the security community, and Frank Kastenholz coordinated the Working Group's interactions with the network management area. Allison Mankin and K.K. Ramakrishnan provided expertise on the issues of congestion control and resource allocation. Many more people than could possibly be listed or credited here participated in the deliberations of the Router Requirements Working Group, either through electronic mail or by attending meetings. However, the efforts of Ross Callon and Vince Fuller in sorting out the difficult issues of route choice and route leaking are especially acknowledged. The editor thanks his employer, Cisco Systems, for allowing him to spend the time necessary to produce the 1994 snapshot. --- cut her ---- I guess I "crossed the line" with my two-line acks. P.S.: And no, I'm not "objecting" what *you* wrote in the Acks. Thanks, -- Fernando Gont SI6 Networks e-mail: fgont@si6networks.com PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
- Status of <draft-ietf-6man-default-iids-16.txt> i… Bob Hinden
- Re: Status of <draft-ietf-6man-default-iids-16.tx… Fred Baker
- Re: Status of <draft-ietf-6man-default-iids-16.tx… Fred Baker
- Re: Status of <draft-ietf-6man-default-iids-16.tx… Sander Steffann
- Re: Status of <draft-ietf-6man-default-iids-16.tx… Lorenzo Colitti
- Re: Status of <draft-ietf-6man-default-iids-16.tx… Enno Rey
- Re: Status of <draft-ietf-6man-default-iids-16.tx… t.petch
- Re: Status of <draft-ietf-6man-default-iids-16.tx… Brian E Carpenter
- Re: Status of <draft-ietf-6man-default-iids-16.tx… Joel M. Halpern
- Re: Status of <draft-ietf-6man-default-iids-16.tx… otroan
- Re: Status of <draft-ietf-6man-default-iids-16.tx… Fernando Gont
- Re: Status of <draft-ietf-6man-default-iids-16.tx… Fernando Gont
- Re: Status of <draft-ietf-6man-default-iids-16.tx… Fernando Gont
- Re: Status of <draft-ietf-6man-default-iids-16.tx… Sander Steffann
- Re: Status of <draft-ietf-6man-default-iids-16.tx… Fernando Gont
- Re: Status of <draft-ietf-6man-default-iids-16.tx… otroan
- Re: Status of <draft-ietf-6man-default-iids-16.tx… Fernando Gont
- Re: Status of <draft-ietf-6man-default-iids-16.tx… Brian E Carpenter
- Re: Status of <draft-ietf-6man-default-iids-16.tx… otroan
- Re: Status of <draft-ietf-6man-default-iids-16.tx… Brian E Carpenter
- Re: Status of <draft-ietf-6man-default-iids-16.tx… Fernando Gont
- Be professional and respectful (was Re: Status of… Suresh Krishnan
- Re: Status of <draft-ietf-6man-default-iids-16.tx… Alissa Cooper
- Re: Status of <draft-ietf-6man-default-iids-16.tx… Suresh Krishnan
- Re: Status of <draft-ietf-6man-default-iids-16.tx… Suresh Krishnan
- Re: Status of <draft-ietf-6man-default-iids-16.tx… Fernando Gont
- Re: Status of <draft-ietf-6man-default-iids-16.tx… Bless, Roland (TM)
- Re: Status of <draft-ietf-6man-default-iids-16.tx… Sander Steffann
- Re: Status of <draft-ietf-6man-default-iids-16.tx… Suresh Krishnan
- Re: Status of <draft-ietf-6man-default-iids-16.tx… Alexandre Petrescu
- Re: Status of <draft-ietf-6man-default-iids-16.tx… 神明達哉
- Re: Status of <draft-ietf-6man-default-iids-16.tx… Bob Hinden
- Re: Status of <draft-ietf-6man-default-iids-16.tx… Suresh Krishnan
- Re: Status of <draft-ietf-6man-default-iids-16.tx… Fernando Gont
- Re: Status of <draft-ietf-6man-default-iids-16.tx… Fred Baker
- Re: Status of <draft-ietf-6man-default-iids-16.tx… Fernando Gont
- Re: Status of <draft-ietf-6man-default-iids-16.tx… Iván Arce
- Re: Status of <draft-ietf-6man-default-iids-16.tx… sthaug
- Re: Status of <draft-ietf-6man-default-iids-16.tx… Alexandre Petrescu
- Re: Status of <draft-ietf-6man-default-iids-16.tx… Lorenzo Colitti
- Re: Status of <draft-ietf-6man-default-iids-16.tx… Suresh Krishnan
- Re: Status of <draft-ietf-6man-default-iids-16.tx… Iván Arce
- Re: Status of <draft-ietf-6man-default-iids-16.tx… Lorenzo Colitti