From adrian@olddog.co.uk Sat Feb 2 09:07:54 2013 Return-Path: X-Original-To: routing-discussion@ietfa.amsl.com Delivered-To: routing-discussion@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0BEA021F8574 for ; Sat, 2 Feb 2013 09:07:54 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.511 X-Spam-Level: X-Spam-Status: No, score=-2.511 tagged_above=-999 required=5 tests=[AWL=0.087, BAYES_00=-2.599, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gdTDfcQx4rvW for ; Sat, 2 Feb 2013 09:07:53 -0800 (PST) Received: from asmtp5.iomartmail.com (asmtp5.iomartmail.com [62.128.201.176]) by ietfa.amsl.com (Postfix) with ESMTP id 52C6921F857A for ; Sat, 2 Feb 2013 09:07:52 -0800 (PST) Received: from asmtp5.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id r12H7owP004764 for ; Sat, 2 Feb 2013 17:07:51 GMT Received: from 950129200 (089144192189.atnat0001.highway.a1.net [89.144.192.189]) (authenticated bits=0) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id r12H7ib3004710 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Sat, 2 Feb 2013 17:07:50 GMT From: "Adrian Farrel" To: References: In-Reply-To: Subject: FW: Call for Comment: "RFC Format Requirements and Future Development" Date: Sat, 2 Feb 2013 17:07:43 -0000 Message-ID: <01cc01ce0167$d4835880$7d8a0980$@olddog.co.uk> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_01CD_01CE0167.D4883A80" X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQGqF0I8z/011A2wdjolYmtak5x0CZiummog Content-Language: en-gb X-BeenThere: routing-discussion@ietf.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: adrian@olddog.co.uk List-Id: Routing Area General mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Feb 2013 17:07:54 -0000 This is a multipart message in MIME format. ------=_NextPart_000_01CD_01CE0167.D4883A80 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Heads up. It will affect you all. Adrian. =20 From: ietf-announce-bounces@ietf.org = [mailto:ietf-announce-bounces@ietf.org] On Behalf Of IAB Chair Sent: 01 February 2013 19:53 To: ietf-announce@ietf.org Cc: rfc-interest@rfc-editor.org Subject: Call for Comment: "RFC Format Requirements and Future = Development" =20 This is an announcement of an IETF-wide Call for Comment on "RFC Format = Requirements and Future Development". The document is being considered for publication as an Informational RFC = within the IAB stream, and is available for inspection here:=20 http://tools.ietf.org/html/draft-iab-rfcformatreq =20 The Call for Comment will last until February 29, 2013. Please send = comments to iab at iab.org or submit them via TRAC (see below). Please = also cc: rfc-interest@rfc-editor.org (for membership info, see: = https://www.rfc-editor.org/mailman/listinfo/rfc-interest). =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=20 Submitting Comments via TRAC=20 1. To submit an issue in TRAC, you first need to login to the IAB site = on the tools server:=20 http://tools.ietf.org/wg/iab/trac/login=20 =20 2. If you don't already have a login ID, you can obtain one by = navigating to this site:=20 http://trac.tools.ietf.org/newlogin=20 =20 3. Once you have obtained an account, and have logged in, you can file = an issue by navigating to the ticket entry form:=20 http://trac.tools.ietf.org/wg/iab/trac/newticket=20 =20 4. When opening an issue:=20 a. The Type: field should be set to "defect" for an issue with the = current document text, or "enhancement" for a proposed addition of = functionality (such as an additional requirement).=20 b. The Priority: field is set based on the severity of the Issue. For = example, editorial issues are typically "minor" or "trivial".=20 c. The Milestone: field should be set to milestone1 (useless, I know).=20 d. The Component: field should be set to the document you are filing the = issue on.=20 e. The Version: field should be set to "1.0".=20 f. The Severity: field should be set to based on the status of the = document (e.g. "In WG Last Call" for a document in IAB last call)=20 g. The Keywords: and CC: fields can be left blank unless inspiration = seizes you.=20 h. The Assign To: field is generally filled in with the email address of = the editor.=20 =20 5. Typically it won't be necessary to enclose a file with the ticket, = but if you need to, select "I have files to attach to this ticket".=20 =20 6. If you want to preview your Issue, click on the "Preview" button. = When you're ready to submit the issue, click on the "Create Ticket" = button.=20 =20 7. If you want to update an issue, go to the "View Tickets" page:=20 http://trac.tools.ietf.org/wg/iab/trac/report/1=20 =20 Click on the ticket # you want to update, and then modify the ticket = fields as required.=20 =20 ------=_NextPart_000_01CD_01CE0167.D4883A80 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable

Heads up. It will affect you = all.

Adrian.

 

From: = ietf-announce-bounces@ietf.org [mailto:ietf-announce-bounces@ietf.org] = On Behalf Of IAB Chair
Sent: 01 February 2013 = 19:53
To: ietf-announce@ietf.org
Cc: = rfc-interest@rfc-editor.org
Subject: Call for Comment: = "RFC Format Requirements and Future = Development"

 

This is an = announcement of an IETF-wide Call for Comment on "RFC Format Requirements and Future = Development".


The document is being considered for publication as an = Informational RFC within the IAB stream, and is available for inspection = here: 
http://tools.i= etf.org/html/draft-iab-rfcformatreq
 
The Call for = Comment will last until February 29, 2013. Please send comments to iab = at iab.org or submit them via TRAC (see = below). Please also cc: rfc-interest@rfc-editor.org (for membership info, see: https:/= /www.rfc-editor.org/mailman/listinfo/rfc-interest).
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D 
Submitting = Comments via TRAC 
1. To submit an issue in TRAC, you first need = to login to the IAB site on the tools server: 
http://tools.ietf.org/wg= /iab/trac/login 
 
2. If you don't already have a = login ID, you can obtain one by navigating to this site: 
http://trac.tools.ietf.org/n= ewlogin 
 
3. Once you have obtained an account, and = have logged in, you can file an issue by navigating to the ticket entry = form: 
http://trac.too= ls.ietf.org/wg/iab/trac/newticket 
 
4. When opening = an issue: 
a. The Type: field should be set to = "defect" for an issue with the current document text, or = "enhancement" for a proposed addition of functionality (such = as an additional requirement). 
b. The Priority: field is = set based on the severity of the Issue. For example, editorial issues = are typically "minor" or "trivial". 
c. The = Milestone: field should be set to milestone1 (useless, I = know). 
d. The Component: field should be set to the document = you are filing the issue on. 
e. The Version: field should be = set to "1.0". 
f. The Severity: field should be set to = based on the status of the document (e.g. "In WG Last Call" = for a document in IAB last call) 
g. The Keywords: and CC: = fields can be left blank unless inspiration seizes you. 
h. The = Assign To: field is generally filled in with the email address of the = editor. 
 
5. Typically it won't be necessary to enclose = a file with the ticket, but if you need to, select "I have files to = attach to this ticket". 
 
6. If you want to = preview your Issue, click on the "Preview" button. When you're = ready to submit the issue, click on the "Create Ticket" = button. 
 
7. If you want to update an issue, go to the = "View Tickets" page: 
http://trac.tool= s.ietf.org/wg/iab/trac/report/1 
 
Click on the = ticket # you want to update, and then modify the ticket fields as = required. 
 

<= /html> ------=_NextPart_000_01CD_01CE0167.D4883A80-- From abdussalambaryun@gmail.com Wed Feb 6 04:01:47 2013 Return-Path: X-Original-To: routing-discussion@ietfa.amsl.com Delivered-To: routing-discussion@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D51A21F8A0D for ; Wed, 6 Feb 2013 04:01:39 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.979 X-Spam-Level: X-Spam-Status: No, score=-2.979 tagged_above=-999 required=5 tests=[AWL=0.620, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MULO1OOUbxFC for ; Wed, 6 Feb 2013 04:01:35 -0800 (PST) Received: from mail-wg0-f53.google.com (mail-wg0-f53.google.com [74.125.82.53]) by ietfa.amsl.com (Postfix) with ESMTP id 07E9421F8A1E for ; Wed, 6 Feb 2013 04:01:23 -0800 (PST) Received: by mail-wg0-f53.google.com with SMTP id fn15so1008666wgb.8 for ; Wed, 06 Feb 2013 04:01:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=XqLLDKndWF+SGwzPFptVgj8D5oGG/khA/cSMtUCAlJE=; b=w7ZBTWKOKR8AApsTcIBB1OdjsJoDsc8hfuyc/liPuqrBLYgBaU+oqy2LzEq/2xguyq RrAGH9ajV3Ij6rOwJP6Zzl/P1XCxTlQW+Jh6dCSNTMUs82wHTqKXx7yttlsInIZIVCjt eqWu22faYZlqZP/ABoVj4amvFI6AZgcI0VFT4bSqRmPvRMREfPLPIMWJzEf0B9uVe9GA 4x/UhTQAvmraxfa90KrN+bsMrjMzqhkI2fSMLUtNWIAKhK/rtYYfEZpisphS0QpyMWFm YTrmU1MLVVaypgxe/rRiiXyx/vN+X95bRZvTcagxp5xlC+bJr5aNj2mr1fKcbBBwFClj bFvQ== MIME-Version: 1.0 X-Received: by 10.194.20.231 with SMTP id q7mr49239806wje.44.1360152081939; Wed, 06 Feb 2013 04:01:21 -0800 (PST) Received: by 10.180.101.70 with HTTP; Wed, 6 Feb 2013 04:01:21 -0800 (PST) In-Reply-To: <01cc01ce0167$d4835880$7d8a0980$@olddog.co.uk> References: <01cc01ce0167$d4835880$7d8a0980$@olddog.co.uk> Date: Wed, 6 Feb 2013 13:01:21 +0100 Message-ID: Subject: Re: FW: Call for Comment: "RFC Format Requirements and Future Development" From: Abdussalam Baryun To: routing-discussion@ietf.org Content-Type: text/plain; charset=ISO-8859-1 X-BeenThere: routing-discussion@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Routing Area General mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Feb 2013 12:01:48 -0000 it should been for a longer period to give more chances for comments, at least until the end date of ietf meeting AB On 2/2/13, Adrian Farrel wrote: > Heads up. It will affect you all. > Adrian. > > From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-bounces@ietf.org] > On Behalf Of IAB Chair > Sent: 01 February 2013 19:53 > To: ietf-announce@ietf.org > Cc: rfc-interest@rfc-editor.org > Subject: Call for Comment: "RFC Format Requirements and Future Development" > > This is an announcement of an IETF-wide Call for Comment on "RFC Format > Requirements and Future Development". > > The document is being considered for publication as an Informational RFC > within the IAB stream, and is available for inspection here: > http://tools.ietf.org/html/draft-iab-rfcformatreq > > The Call for Comment will last until February 29, 2013. Please send comments > to iab at iab.org or submit them via TRAC (see below). Please also cc: > rfc-interest@rfc-editor.org (for membership info, see: > https://www.rfc-editor.org/mailman/listinfo/rfc-interest). > =============================================================== > Submitting Comments via TRAC > 1. To submit an issue in TRAC, you first need to login to the IAB site on > the tools server: > http://tools.ietf.org/wg/iab/trac/login > > 2. If you don't already have a login ID, you can obtain one by navigating to > this site: > http://trac.tools.ietf.org/newlogin > > 3. Once you have obtained an account, and have logged in, you can file an > issue by navigating to the ticket entry form: > http://trac.tools.ietf.org/wg/iab/trac/newticket > > 4. When opening an issue: > a. The Type: field should be set to "defect" for an issue with the current > document text, or "enhancement" for a proposed addition of functionality > (such as an additional requirement). > b. The Priority: field is set based on the severity of the Issue. For > example, editorial issues are typically "minor" or "trivial". > c. The Milestone: field should be set to milestone1 (useless, I know). > d. The Component: field should be set to the document you are filing the > issue on. > e. The Version: field should be set to "1.0". > f. The Severity: field should be set to based on the status of the document > (e.g. "In WG Last Call" for a document in IAB last call) > g. The Keywords: and CC: fields can be left blank unless inspiration seizes > you. > h. The Assign To: field is generally filled in with the email address of the > editor. > > 5. Typically it won't be necessary to enclose a file with the ticket, but if > you need to, select "I have files to attach to this ticket". > > 6. If you want to preview your Issue, click on the "Preview" button. When > you're ready to submit the issue, click on the "Create Ticket" button. > > 7. If you want to update an issue, go to the "View Tickets" page: > http://trac.tools.ietf.org/wg/iab/trac/report/1 > > Click on the ticket # you want to update, and then modify the ticket fields > as required. > > From adrian@olddog.co.uk Wed Feb 6 04:24:35 2013 Return-Path: X-Original-To: routing-discussion@ietfa.amsl.com Delivered-To: routing-discussion@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 64B0D21F87ED for ; Wed, 6 Feb 2013 04:24:35 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.521 X-Spam-Level: X-Spam-Status: No, score=-2.521 tagged_above=-999 required=5 tests=[AWL=0.079, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vjZ1bBJiavv8 for ; Wed, 6 Feb 2013 04:24:34 -0800 (PST) Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) by ietfa.amsl.com (Postfix) with ESMTP id 6A9A121F855F for ; Wed, 6 Feb 2013 04:24:34 -0800 (PST) Received: from asmtp1.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id r16CORtF014862; Wed, 6 Feb 2013 12:24:27 GMT Received: from 950129200 (89-26-111-90.bruck.stat.salzburg-online.at [89.26.111.90]) (authenticated bits=0) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id r16COP5e014848 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 6 Feb 2013 12:24:26 GMT From: "Adrian Farrel" To: "'Abdussalam Baryun'" , References: <01cc01ce0167$d4835880$7d8a0980$@olddog.co.uk> In-Reply-To: Subject: RE: FW: Call for Comment: "RFC Format Requirements and Future Development" Date: Wed, 6 Feb 2013 12:24:25 -0000 Message-ID: <043501ce0464$e75c7540$b6155fc0$@olddog.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQGqF0I8z/011A2wdjolYmtak5x0CQKMMPW6Ah8DPh6Yj0CZcA== Content-Language: en-gb X-BeenThere: routing-discussion@ietf.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: adrian@olddog.co.uk List-Id: Routing Area General mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Feb 2013 12:24:35 -0000 AB, I can't control the IAB. I might wish I could, but there we go :-) I am sure that if there is not enough time for you to get your comments in, and yet you have a definite date by which you plan to make comments, you could tell the IAB and ask permission to submit comments late. Adrian > -----Original Message----- > From: routing-discussion-bounces@ietf.org [mailto:routing-discussion- > bounces@ietf.org] On Behalf Of Abdussalam Baryun > Sent: 06 February 2013 12:01 > To: routing-discussion@ietf.org > Subject: Re: FW: Call for Comment: "RFC Format Requirements and Future > Development" > > it should been for a longer period to give more chances for comments, > at least until the end date of ietf meeting > > AB > > On 2/2/13, Adrian Farrel wrote: > > Heads up. It will affect you all. > > Adrian. > > > > From: ietf-announce-bounces@ietf.org [mailto:ietf-announce- > bounces@ietf.org] > > On Behalf Of IAB Chair > > Sent: 01 February 2013 19:53 > > To: ietf-announce@ietf.org > > Cc: rfc-interest@rfc-editor.org > > Subject: Call for Comment: "RFC Format Requirements and Future > Development" > > > > This is an announcement of an IETF-wide Call for Comment on "RFC Format > > Requirements and Future Development". > > > > The document is being considered for publication as an Informational RFC > > within the IAB stream, and is available for inspection here: > > http://tools.ietf.org/html/draft-iab-rfcformatreq > > > > The Call for Comment will last until February 29, 2013. Please send comments > > to iab at iab.org or submit them via TRAC (see below). Please also cc: > > rfc-interest@rfc-editor.org (for membership info, see: > > https://www.rfc-editor.org/mailman/listinfo/rfc-interest). > > > ============================================================== > = > > Submitting Comments via TRAC > > 1. To submit an issue in TRAC, you first need to login to the IAB site on > > the tools server: > > http://tools.ietf.org/wg/iab/trac/login > > > > 2. If you don't already have a login ID, you can obtain one by navigating to > > this site: > > http://trac.tools.ietf.org/newlogin > > > > 3. Once you have obtained an account, and have logged in, you can file an > > issue by navigating to the ticket entry form: > > http://trac.tools.ietf.org/wg/iab/trac/newticket > > > > 4. When opening an issue: > > a. The Type: field should be set to "defect" for an issue with the current > > document text, or "enhancement" for a proposed addition of functionality > > (such as an additional requirement). > > b. The Priority: field is set based on the severity of the Issue. For > > example, editorial issues are typically "minor" or "trivial". > > c. The Milestone: field should be set to milestone1 (useless, I know). > > d. The Component: field should be set to the document you are filing the > > issue on. > > e. The Version: field should be set to "1.0". > > f. The Severity: field should be set to based on the status of the document > > (e.g. "In WG Last Call" for a document in IAB last call) > > g. The Keywords: and CC: fields can be left blank unless inspiration seizes > > you. > > h. The Assign To: field is generally filled in with the email address of the > > editor. > > > > 5. Typically it won't be necessary to enclose a file with the ticket, but if > > you need to, select "I have files to attach to this ticket". > > > > 6. If you want to preview your Issue, click on the "Preview" button. When > > you're ready to submit the issue, click on the "Create Ticket" button. > > > > 7. If you want to update an issue, go to the "View Tickets" page: > > http://trac.tools.ietf.org/wg/iab/trac/report/1 > > > > Click on the ticket # you want to update, and then modify the ticket fields > > as required. > > > > > _______________________________________________ > routing-discussion mailing list > routing-discussion@ietf.org > https://www.ietf.org/mailman/listinfo/routing-discussion From adrian@olddog.co.uk Wed Feb 6 09:06:33 2013 Return-Path: X-Original-To: routing-discussion@ietfa.amsl.com Delivered-To: routing-discussion@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 578A321F85E2 for ; Wed, 6 Feb 2013 09:06:33 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZO9f6xSgvuqW for ; Wed, 6 Feb 2013 09:06:32 -0800 (PST) Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249]) by ietfa.amsl.com (Postfix) with ESMTP id 8B6A421F85CC for ; Wed, 6 Feb 2013 09:06:32 -0800 (PST) Received: from asmtp2.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id r16H6UN8001374 for ; Wed, 6 Feb 2013 17:06:30 GMT Received: from 950129200 (ixe-nat1.juniper.net [193.110.54.36]) (authenticated bits=0) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id r16H6RwU001359 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Wed, 6 Feb 2013 17:06:30 GMT From: "Adrian Farrel" To: References: <20130206152017.17915.96646.idtracker@ietfa.amsl.com> In-Reply-To: <20130206152017.17915.96646.idtracker@ietfa.amsl.com> Subject: FW: Nomcom 2012: Feedback on TSV Nominees Date: Wed, 6 Feb 2013 17:06:26 -0000 Message-ID: <050201ce048c$4ebb3fb0$ec31bf10$@olddog.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQLMDs5jQcUYuECfzXi7f+LcUfXu35Zw+oqQ Content-Language: en-gb X-BeenThere: routing-discussion@ietf.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: adrian@olddog.co.uk List-Id: Routing Area General mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Feb 2013 17:06:33 -0000 The Nominations Committee is seeking further feedback on potential = candidates for the TSV Area Director position. Please be sure to give them any opinions you have on the matter. The timeline is short. Thanks, Adrian > -----Original Message----- > From: ietf-announce-bounces@ietf.org [mailto:ietf-announce- > bounces@ietf.org] On Behalf Of NomCom Chair > Sent: 06 February 2013 15:20 > To: IETF Announcement List > Subject: Nomcom 2012: Feedback on TSV Nominees >=20 > Thanks to everyone who helped the IETF Nominating Committee > (Nomcom) by responding to our call for Transport (TSV) Area Director > nominations. >=20 > Three individuals accepted nominations for the TSV area director = position. > The Nomcom is therefore seeking input from the community about > whether these nominees are a good fit for the TSV Area Director = position. >=20 > The Nomcom is therefore seeking community feedback about the > following individuals: > -- Spencer Dawkins > -- Mark Townsley > -- Margaret Wasserman > -- Ken Carlberg > -- Linda Dunbar > -- Tom Haynes >=20 > The Nomcom is happy to accept input from the community either via = email > to nomcom12@ietf.org or via our web tool: > https://www.ietf.org/group/nomcom/2012/input/ >=20 > Note that our webtool requires an ietf.org login, anyone can easily = get an > ietf.org account at: https://datatracker.ietf.org/accounts >=20 > Note that the Nomcom is following the guidelines in RFC 5680 in making > public the list of individuals who have agreed to be considered for = the > position of TSV Area Director. >=20 > The Nomcom is operating on a very tight time schedule, and would > appreciate input as soon as possible. To ensure your input is received = in > time to be useful to the Nomcom please send input on or before = Monday, > February 11. >=20 > Thanks again for your help, > - Matt Lepinski > nomcom-chair@ietf.org From adrian@olddog.co.uk Wed Feb 20 06:20:03 2013 Return-Path: X-Original-To: routing-discussion@ietfa.amsl.com Delivered-To: routing-discussion@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 08ACF21F8780; Wed, 20 Feb 2013 06:20:03 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IzMQCa+wMQ8Z; Wed, 20 Feb 2013 06:20:02 -0800 (PST) Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249]) by ietfa.amsl.com (Postfix) with ESMTP id 374B421F877A; Wed, 20 Feb 2013 06:20:02 -0800 (PST) Received: from asmtp2.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id r1KEJsX9023001; Wed, 20 Feb 2013 14:19:54 GMT Received: from 950129200 ([37.61.186.220]) (authenticated bits=0) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id r1KEJqeD022958 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 20 Feb 2013 14:19:53 GMT From: "Adrian Farrel" To: , , Subject: Routing ADs Office Hours in Orlando Date: Wed, 20 Feb 2013 14:19:53 -0000 Message-ID: <026701ce0f75$5ad6f430$1084dc90$@olddog.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 14.0 Thread-Index: Ac4PdPb9ZxWLvqWbSVuMKXOs3YAF0Q== Content-Language: en-gb Cc: stbryant@cisco.com X-BeenThere: routing-discussion@ietf.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: adrian@olddog.co.uk List-Id: Routing Area General mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Feb 2013 14:20:03 -0000 Hi, Stewart and I will hold office hours on Tuesday from 11.30(ish) to 13.00. Not sure how lunch will be working, but we will try to grab something that we can eat while you talk to us. (Moved from the usual Sunday afternoon to avoid a conflict with the IAOC's tutorial and open-house). Meeting room will be the IESG Office. Thanks, Adrian and Stewart From adrian@olddog.co.uk Thu Feb 21 12:09:54 2013 Return-Path: X-Original-To: routing-discussion@ietfa.amsl.com Delivered-To: routing-discussion@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E8CF921F8F5D for ; Thu, 21 Feb 2013 12:09:54 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.632 X-Spam-Level: X-Spam-Status: No, score=-2.632 tagged_above=-999 required=5 tests=[AWL=-0.033, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZChSjFP+RrXp for ; Thu, 21 Feb 2013 12:09:54 -0800 (PST) Received: from asmtp3.iomartmail.com (asmtp3.iomartmail.com [62.128.201.159]) by ietfa.amsl.com (Postfix) with ESMTP id 1D8F021F8F61 for ; Thu, 21 Feb 2013 12:09:53 -0800 (PST) Received: from asmtp3.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id r1LK9qJG007617 for ; Thu, 21 Feb 2013 20:09:52 GMT Received: from 950129200 ([37.61.186.220]) (authenticated bits=0) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id r1LK9p9J007608 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Thu, 21 Feb 2013 20:09:52 GMT From: "Adrian Farrel" To: Subject: Please consider standing for the ISOC Board of Trustees Date: Thu, 21 Feb 2013 20:09:51 -0000 Message-ID: <019a01ce106f$68f5b330$3ae11990$@olddog.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 14.0 Thread-Index: Ac4Qb2hEnUc0SjO1Rjqpe/NaJ0Jnyw== Content-Language: en-gb X-BeenThere: routing-discussion@ietf.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: adrian@olddog.co.uk List-Id: Routing Area General mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Feb 2013 20:09:55 -0000 Hi, The IAB are taking nominations for their appointment to the ISOC Board of Trustees. See their announcement at: https://www.ietf.org/ibin/c5i?mid=6&rid=49&gid=0&k1=934&k2=11676&tid=1361477230 Is this a job you could do? Do you know someone who could do this job? Thanks, Adrian From adrian@olddog.co.uk Thu Feb 28 05:58:52 2013 Return-Path: X-Original-To: routing-discussion@ietfa.amsl.com Delivered-To: routing-discussion@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3FF4421F88A2; Thu, 28 Feb 2013 05:58:52 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.592 X-Spam-Level: X-Spam-Status: No, score=-2.592 tagged_above=-999 required=5 tests=[AWL=0.007, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QSHeb7nAN4C5; Thu, 28 Feb 2013 05:58:51 -0800 (PST) Received: from asmtp3.iomartmail.com (asmtp3.iomartmail.com [62.128.201.159]) by ietfa.amsl.com (Postfix) with ESMTP id 495AA21F8881; Thu, 28 Feb 2013 05:58:51 -0800 (PST) Received: from asmtp3.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id r1SDwm0b020089; Thu, 28 Feb 2013 13:58:48 GMT Received: from 950129200 (089144192031.atnat0001.highway.a1.net [89.144.192.31]) (authenticated bits=0) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id r1SDwUbn019733 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 28 Feb 2013 13:58:47 GMT From: "Adrian Farrel" To: Subject: Discussion topic for Routing Area Open Meeting in Orlando Date: Thu, 28 Feb 2013 13:58:32 -0000 Message-ID: <008701ce15bb$bc87ff20$3597fd60$@olddog.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 14.0 Thread-Index: Ac4VqBA9zxE3XKqsRzanD8+wl8QPvg== Content-Language: en-gb Cc: draft-mrw-abfab-trust-router@tools.ietf.org, rtg-dir@ietf.org, rtgwg-chairs@tools.ietf.org X-BeenThere: routing-discussion@ietf.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: adrian@olddog.co.uk List-Id: Routing Area General mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Feb 2013 13:58:52 -0000 Hi, In the Routing Area meeting in Orlando we will continue our occasional series of discussions of "routing in other areas". In this case we will spend some time on "Trust Routers". Although this topic is not about routing packets, the tree construction and "shortest" path computations have some resemblance to BGP and other routing protocols, and there are also similarities to the SIP routing issues that we heard about a while back. The authors say it would interesting to get some routing folks involved to make sure we avoid the well-understood pitfalls with those sorts of algorithms. It looks to me to me that there are many commonalities of functional concept even if the environment (i.e. application space) is free of many of the constraints we see on routers. As background reading, you might like to look at: http://datatracker.ietf.org/doc/ You can also look at two older (i.e., expired) drafts: http://tools.ietf.org/html/draft-howlett-abfab-trust-router-ps-02 http://tools.ietf.org/html/draft-mrw-abfab-multihop-fed-02 Thanks, Adrian From mrw@lilacglade.org Thu Feb 28 07:07:30 2013 Return-Path: X-Original-To: routing-discussion@ietfa.amsl.com Delivered-To: routing-discussion@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 85EAC21F8C04; Thu, 28 Feb 2013 07:07:30 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.932 X-Spam-Level: X-Spam-Status: No, score=-102.932 tagged_above=-999 required=5 tests=[AWL=-0.333, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Rv-WbAQfkM92; Thu, 28 Feb 2013 07:07:16 -0800 (PST) Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id 430A921F8BEA; Thu, 28 Feb 2013 07:07:16 -0800 (PST) Received: from new-host-4.home (pool-71-184-79-25.bstnma.fios.verizon.net [71.184.79.25]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mail.painless-security.com (Postfix) with ESMTPSA id 9AC6620144; Thu, 28 Feb 2013 10:02:18 -0500 (EST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) Subject: Re: Discussion topic for Routing Area Open Meeting in Orlando From: Margaret Wasserman In-Reply-To: <008701ce15bb$bc87ff20$3597fd60$@olddog.co.uk> Date: Thu, 28 Feb 2013 10:07:14 -0500 Content-Transfer-Encoding: quoted-printable Message-Id: <27839D85-247E-4BA3-8E4D-0250E40FBCEF@lilacglade.org> References: <008701ce15bb$bc87ff20$3597fd60$@olddog.co.uk> To: X-Mailer: Apple Mail (2.1499) X-Mailman-Approved-At: Thu, 28 Feb 2013 07:11:48 -0800 Cc: draft-mrw-abfab-trust-router@tools.ietf.org, rtg-dir@ietf.org, rtgwg-chairs@tools.ietf.org, routing-discussion@ietf.org X-BeenThere: routing-discussion@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Routing Area General mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Feb 2013 15:07:30 -0000 On Feb 28, 2013, at 8:58 AM, "Adrian Farrel" = wrote: >=20 > As background reading, you might like to look at: > http://datatracker.ietf.org/doc/=09 This should be: http://datatracker.ietf.org/doc/draft-mrw-abfab-trust-router/ For those of you who are unfamiliar with Application Bridging Beyond the = Web (abfab), you might also wish to look at the abfab architecture = document to understand the environment in which the Trust Router is = intended to work. It can be found here: http://datatracker.ietf.org/doc/draft-ietf-abfab-arch/ Margaret From abdussalambaryun@gmail.com Thu Feb 28 14:10:57 2013 Return-Path: X-Original-To: routing-discussion@ietfa.amsl.com Delivered-To: routing-discussion@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C71DD21F871D for ; Thu, 28 Feb 2013 14:10:57 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.545 X-Spam-Level: X-Spam-Status: No, score=-3.545 tagged_above=-999 required=5 tests=[AWL=0.054, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GshCbPM83bxq for ; Thu, 28 Feb 2013 14:10:57 -0800 (PST) Received: from mail-pb0-f41.google.com (mail-pb0-f41.google.com [209.85.160.41]) by ietfa.amsl.com (Postfix) with ESMTP id A76C021F86F4 for ; Thu, 28 Feb 2013 14:10:55 -0800 (PST) Received: by mail-pb0-f41.google.com with SMTP id um15so1334887pbc.28 for ; Thu, 28 Feb 2013 14:10:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=yPG1fwPtUeCEPHRSZ0O+AfFw9uJ8E7LEp/ZB8tq4jVs=; b=zzqPt9j2Vk9tNOgBjHExY2Z+o/gTJfp8ffr6UTTY74XTFXVLDN3pTvLvuEiF9rcPSS HSXoRHx6wfmu5NQK1Wjkn5GWeLit1TseILtsTXxSKU3uueSedkQXBYNr49h6Y9reinyI Aj63WLqQOJM0LrWLG0Jie1q+8ODuT28EiaMK5+iQD54LY4LeqhVsy+ErCVELQOenDq7D rohyzka8jsBZqY8fV6d10ClgtjlB2v+ff+ClIFAiJnJKhctj11Xvgl5EFpYExWwOP9zJ rspFfoJkRbMbTYPy7zqYHmujasHu+q3+/4SHMiVN4YAP/SlbMf8mWHUMvrtwlPCfiszW 6+QA== MIME-Version: 1.0 X-Received: by 10.68.138.170 with SMTP id qr10mr11238274pbb.190.1362089455421; Thu, 28 Feb 2013 14:10:55 -0800 (PST) Received: by 10.68.33.132 with HTTP; Thu, 28 Feb 2013 14:10:55 -0800 (PST) Date: Thu, 28 Feb 2013 23:10:55 +0100 Message-ID: Subject: A question regarding how to track decisions in this area From: Abdussalam Baryun To: routing-discussion@ietf.org Content-Type: text/plain; charset=ISO-8859-1 X-BeenThere: routing-discussion@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Routing Area General mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Feb 2013 22:10:57 -0000 Hi Folks, I have a question regarding the WG under the Routing Area, There was one protocol DFF sent to IESG and mentioned that there was no WG that relates to it, which I think it was 6Lowpan. I got a respond that this WG may not accept new drafts. Please advise why? and When/where was the decision made, or how to track such decision in the Routing Area? AB From ietf@thomasclausen.org Thu Feb 28 14:20:17 2013 Return-Path: X-Original-To: routing-discussion@ietfa.amsl.com Delivered-To: routing-discussion@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8295521F84A7 for ; Thu, 28 Feb 2013 14:20:17 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.829 X-Spam-Level: X-Spam-Status: No, score=-0.829 tagged_above=-999 required=5 tests=[AWL=0.374, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 80yz+r2twzRh for ; Thu, 28 Feb 2013 14:20:13 -0800 (PST) Received: from mailc2.tigertech.net (mailc2.tigertech.net [208.80.4.156]) by ietfa.amsl.com (Postfix) with ESMTP id C688521F84A6 for ; Thu, 28 Feb 2013 14:20:13 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by mailc2.tigertech.net (Postfix) with ESMTP id 2713F1C01652; Thu, 28 Feb 2013 14:20:10 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at c2.tigertech.net Received: from [192.168.147.191] (mtg91-1-82-227-24-173.fbx.proxad.net [82.227.24.173]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mailc2.tigertech.net (Postfix) with ESMTPSA id AAFB41C01650; Thu, 28 Feb 2013 14:20:09 -0800 (PST) References: Mime-Version: 1.0 (1.0) In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Message-Id: <54CEF97A-E5AD-4756-B620-8E4F37E1623E@thomasclausen.org> X-Mailer: iPhone Mail (10B143) From: Thomas Heide Clausen Subject: Re: A question regarding how to track decisions in this area Date: Thu, 28 Feb 2013 23:20:04 +0100 To: Abdussalam Baryun Cc: "routing-discussion@ietf.org" X-BeenThere: routing-discussion@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Routing Area General mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Feb 2013 22:20:17 -0000 AFAIK, 6LoWPAN is not a routing area WG, so I guess you will have more luck a= sking elsewhere (say, the AD overseeing 6LoWPAN).=20 Thomas --=20 Thomas Heide Clausen http://www.thomasclausen.org "Today's scientists have substituted mathematics for=20 experiments, and they wander off through equation=20 after equation, and eventually build a structure=20 which has no relation to reality." - Nikola Tesla,=20 Modern Mechanics and Inventions, July, 1934 On 28 f=C3=A9vr. 2013, at 23:10, Abdussalam Baryun wrote: > Hi Folks, >=20 > I have a question regarding the WG under the Routing Area, >=20 > There was one protocol DFF sent to IESG and mentioned that there was > no WG that relates to it, which I think it was 6Lowpan. I got a > respond that this WG may not accept new drafts. Please advise why? and > When/where was the decision made, or how to track such decision in the > Routing Area? >=20 > AB > _______________________________________________ > routing-discussion mailing list > routing-discussion@ietf.org > https://www.ietf.org/mailman/listinfo/routing-discussion