
From daedulus@btconnect.com  Thu Nov  1 02:31:20 2012
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE34921F854F for <ietf@ietfa.amsl.com>; Thu,  1 Nov 2012 02:31:20 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ix0hn0BWpBWR for <ietf@ietfa.amsl.com>; Thu,  1 Nov 2012 02:31:20 -0700 (PDT)
Received: from va3outboundpool.messaging.microsoft.com (va3ehsobe003.messaging.microsoft.com [216.32.180.13]) by ietfa.amsl.com (Postfix) with ESMTP id C5FF621F854A for <ietf@ietf.org>; Thu,  1 Nov 2012 02:31:19 -0700 (PDT)
Received: from mail244-va3-R.bigfish.com (10.7.14.250) by VA3EHSOBE011.bigfish.com (10.7.40.61) with Microsoft SMTP Server id 14.1.225.23; Thu, 1 Nov 2012 09:31:18 +0000
Received: from mail244-va3 (localhost [127.0.0.1])	by mail244-va3-R.bigfish.com (Postfix) with ESMTP id 9D58A6C02EC	for <ietf@ietf.org>; Thu,  1 Nov 2012 09:31:18 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.253.85; KIP:(null); UIP:(null); IPV:NLI; H:DB3PRD0710HT004.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -24
X-BigFish: PS-24(zz9371I119bI542M1432Izz1202h1d1ah1d2ahzz8275ch1033IL17326ah8275bh8275dhz2dh2a8h5a9h668h839hd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h304l1155h)
Received: from mail244-va3 (localhost.localdomain [127.0.0.1]) by mail244-va3 (MessageSwitch) id 135176227641222_19939; Thu,  1 Nov 2012 09:31:16 +0000 (UTC)
Received: from VA3EHSMHS013.bigfish.com (unknown [10.7.14.250])	by mail244-va3.bigfish.com (Postfix) with ESMTP id EF29D700047	for <ietf@ietf.org>; Thu,  1 Nov 2012 09:31:15 +0000 (UTC)
Received: from DB3PRD0710HT004.eurprd07.prod.outlook.com (157.56.253.85) by VA3EHSMHS013.bigfish.com (10.7.99.23) with Microsoft SMTP Server (TLS) id 14.1.225.23; Thu, 1 Nov 2012 09:31:15 +0000
Received: from DB3PRD0510HT002.eurprd05.prod.outlook.com (157.56.252.37) by pod51017.outlook.com (10.255.75.39) with Microsoft SMTP Server (TLS) id 14.16.233.2; Thu, 1 Nov 2012 09:31:07 +0000
Message-ID: <005801cdb813$894c97c0$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: <ietf@ietf.org>
References: <20121030154625.13482.31090.idtracker@ietfa.amsl.com>
Subject: Re: WG Action: Rechartered Bidirectional Forwarding Detection (bfd)
Date: Thu, 1 Nov 2012 09:28:19 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [157.56.252.37]
X-OriginatorOrg: btconnect.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Nov 2012 09:31:20 -0000

I realise that the timekeeping of the IETF is not on a par with its
engineering, but it seems a shame to promulgate a new charter for which
every milestone is already several months in arrears.

Tom Petch


----- Original Message -----
From: "The IESG" <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
Cc: "bfd WG" <rtg-bfd@ietf.org>
Sent: Tuesday, October 30, 2012 3:46 PM

> The Bidirectional Forwarding Detection (bfd) working group in the
Routing
> Area of the IETF has been rechartered. For additional information
please
> contact the Area Directors or the WG Chairs.
>
> Bidirectional Forwarding Detection (bfd)
> ------------------------------------------------
> Current Status: Active Working Group
>
> Chairs:
>   David Ward <dward@cisco.com>
>   Jeffrey Haas <jhaas@pfrc.org>
>
> Technical advisors:
>   Dave Katz <dkatz@juniper.net>
>
> Assigned Area Director:
>   Adrian Farrel <adrian@olddog.co.uk>
>
> Mailing list
>   Address: rtg-bfd@ietf.org
>   To Subscribe: rtg-bfd-request@ietf.org
>   Archive: http://www.ietf.org/mail-archive/web/rtg-bfd/
>
> Charter of Working Group:
>
> The BFD Working Group is chartered to standardize and support the
> bidirectional forwarding detection protocol (BFD) and its extensions.
A
> core goal of the working group is to standardize BFD in the context of
IP
> routing, or protocols such as MPLS that are based on IP routing, in a
way
> that will encourage multiple, inter-operable vendor implementations.
The
> Working Group will also provide advice and guidance on BFD to other
> working groups or standards bodies as requested.
>
> BFD is a protocol intended to detect faults in the bidirectional path
> between two forwarding engines, including physical interfaces,
> subinterfaces, data link(s), and to the extent possible the forwarding
> engines themselves, with potentially very low latency. It operates
> independently of media, data protocols, and routing protocols. An
> additional goal is to provide a single mechanism that can be used for
> liveness detection over any media, at any protocol layer, with
> a wide range of detection times and overhead, to avoid a proliferation
> of different methods.
>
> Important characteristics of BFD include:
>
> - Simple, fixed-field encoding to facilitate implementations in
hardware.
>
> - Independence of the data protocol being forwarded between two
systems.
>   BFD packets are carried as the payload of whatever encapsulating
>   protocol is appropriate for the medium and network.
>
> - Path independence: BFD can provide failure detection on any kind of
>   path between systems, including direct physical links, virtual
circuits,
>   tunnels, MPLS LSPs, multihop routed paths, and unidirectional links
(so
>   long as there is some return path, of course).
>
> - Ability to be bootstrapped by any other protocol that automatically
>   forms peer, neighbor or adjacency relationships to seed BFD endpoint
>   discovery.
>
> The working group is chartered to complete the following work items:
>
> 1. Develop the MIB module for BFD and submit it to the IESG for
> publication as a Proposed Standard.
>
> 2a. Provide a generic keying-based cryptographic authentication
mechanism
> for the BFD protocol in discussion with the KARP working group.  This
> mechanism will support authentication through a key identifier for the
BFD
> session's Security Association rather than specifying new
authentication
> extensions.
>
> 2b. Provide extensions to the BFD MIB in support of the generic
> keying-based cryptographic authentication mechanism.
>
> 2c. Specify cryptographic authentication procedures for the BFD
protocol
> using HMAC-SHA-256 (possibly truncated to a smaller integrity check
> value) using the generic keying-based cryptographic authentication
mechanism.
>
> 3. Provide an extension to the BFD core protocol in support of
point-to-
> multipoint links and networks.
>
> 4. Assist the MPLS working group in the standardization of the BFD
> protocol for MPLS-TP.  The preferred solution will be interoperable
with the
> current BFD specification.
>
> 5. Provide one or more mechanisms to run BFD over Link Aggregation
Group
> Interfaces.
>
> The working group will maintain a relationship with the KARP and MPLS
> working groups, and will communicate with the IEEE with respect to BFD
> over LAGs.
>
> Milestones:
>   Done     - Submit the base protocol specification to the IESG to be
> considered as a Proposed Standard
>   Done     - Submit BFD encapsulation and usage profile for single-hop
> IPv4 and IPv6 adjacencies to the IESG to be considered as a Proposed
> Standard
>   Done     - Submit BFD encapsulation and usage profile for MPLS LSPs
to
> the IESG to be considered as a Proposed Standard
>   Done     - Submit BFD encapsulation and usage profile for multi-hop
> IPv4 and IPv6 adjacencies to the IESG to be considered as a Proposed
> Standard
>   Sep 2011 - Submit the BFD MIB to the IESG to be considered as a
> Proposed Standard
>   Dec 2011 - Submit the generic keying based cryptographic
authentication
> mechanism to the IESG to be considered as a Proposed Standard
>   Dec 2011 - Submit a BFD MIB extension in support of the generic
keying
> document to the IESG to be considered as a Proposed Standard
>   Dec 2011 - Submit the cryptographic authentication procedures for
BFD
> to the IESG to be considered as a Proposed Standard
>   Mar 2012 - Submit the the document on BFD point-to-multipoint
support
> to the IESG to be considered as a Proposed Standard
>   Jun 2012 - Submit the bootstrapping mechanism for BFD using DHCP to
the
> IESG to be considered as a Proposed Standard
>



From turchanyi.geza@gmail.com  Thu Nov  1 03:25:41 2012
Return-Path: <turchanyi.geza@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 01A3221F84D2 for <ietf@ietfa.amsl.com>; Thu,  1 Nov 2012 03:25:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.842
X-Spam-Level: 
X-Spam-Status: No, score=-2.842 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_42=0.6, RCVD_IN_DNSWL_LOW=-1, SUBJECT_FUZZY_TION=0.156]
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 wPlciagILi5Z for <ietf@ietfa.amsl.com>; Thu,  1 Nov 2012 03:25:40 -0700 (PDT)
Received: from mail-da0-f44.google.com (mail-da0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id 87D3521F84CC for <ietf@ietf.org>; Thu,  1 Nov 2012 03:25:40 -0700 (PDT)
Received: by mail-da0-f44.google.com with SMTP id h15so1104219dan.31 for <ietf@ietf.org>; Thu, 01 Nov 2012 03:25:40 -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 :cc:content-type; bh=nDf1+t+g//s21RuARungMu7r95v7nmca/YEtWLr8m0g=; b=Rvg89PLxna225xPb9jpc+/CKs7eNMwBiTbSHaPwkeoU6yvISAZ1cMAgDJ492Z1+utX 3R5Lxp6D+1W30a0YEYLxccN9MgXftY1iPVRTeHDNkl/RjrdrWXMF0AgYyMhbVqcxET/z DAx53luMHT6VVRAjSr+K17ig3UDgIgaxe/jMFZWY+RWVAjWSnMWQYvXSK/OAJs0HdZ7x 11mmrT4cMfeIURl0VPve6QtLjyrpj30Sh4coEomCjmbPycEJvcaQ/tQzBeGFyIQe0Awm O/VIMa4dvFL03L07PZnmsqpIJwPK9sZkdQc5zrLuV2jKCDJXBlLhUINXwGDhpSEXQC9w XMzA==
MIME-Version: 1.0
Received: by 10.68.190.71 with SMTP id go7mr121919465pbc.66.1351765539989; Thu, 01 Nov 2012 03:25:39 -0700 (PDT)
Received: by 10.66.19.135 with HTTP; Thu, 1 Nov 2012 03:25:39 -0700 (PDT)
In-Reply-To: <1158F458-8810-4CD2-B874-3DE1A1B8B0B5@kumari.net>
References: <50919671.6000605@ogud.com> <5091CD21.3010504@gmail.com> <1158F458-8810-4CD2-B874-3DE1A1B8B0B5@kumari.net>
Date: Thu, 1 Nov 2012 11:25:39 +0100
Message-ID: <CAJfR-+PDvsswi3yU-H5TsK_W8RNeSwNMD2Gcdc2SksKEG1xDYQ@mail.gmail.com>
Subject: Re: [IETF] Re: Recall petition for Mr. Marshall Eubanks
From: Turchanyi Geza <turchanyi.geza@gmail.com>
To: Warren Kumari <warren@kumari.net>
Content-Type: multipart/alternative; boundary=e89a8ff1cb36d4a99c04cd6c7065
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Nov 2012 10:25:41 -0000

--e89a8ff1cb36d4a99c04cd6c7065
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hello,

I am glad to see that apparently there are no more supporters of this
proposal.

Please be more tolerant to Marshall Eubank.

Best,

G=E9za


On Thu, Nov 1, 2012 at 2:22 AM, Warren Kumari <warren@kumari.net> wrote:

>
>
> Warren Kumari
> ------
> Please excuse typing, etc -- This was sent from a device with a tiny
> keyboard.
>
> On Oct 31, 2012, at 9:15 PM, Melinda Shore <melinda.shore@gmail.com>
> wrote:
>
> > On 10/31/12 1:21 PM, Olafur Gudmundsson wrote:
> >> Fellow IETF'rs
> >> below is a recall petition that I plan on submitting soon if there is
> >> enough support.
> >
> > I regret having to do it this way,
>
> +1
>
> > but since it seems to be necessary
> > and there is no agreed-upon alternative, I support this.
> >
>
> As do I.
>
> :-(
>
> W
>
> > Melinda
> >
> >
>

--e89a8ff1cb36d4a99c04cd6c7065
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hello,<br><br>I am glad to see that apparently there are no more supporters=
 of this proposal.<br><br>Please be more tolerant to Marshall Eubank.<br><b=
r>Best,<br><br>G=E9za<br><br><br><div class=3D"gmail_quote">On Thu, Nov 1, =
2012 at 2:22 AM, Warren Kumari <span dir=3D"ltr">&lt;<a href=3D"mailto:warr=
en@kumari.net" target=3D"_blank">warren@kumari.net</a>&gt;</span> wrote:<br=
>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><br>
<br>
Warren Kumari<br>
------<br>
Please excuse typing, etc -- This was sent from a device with a tiny keyboa=
rd.<br>
<div class=3D"im"><br>
On Oct 31, 2012, at 9:15 PM, Melinda Shore &lt;<a href=3D"mailto:melinda.sh=
ore@gmail.com">melinda.shore@gmail.com</a>&gt; wrote:<br>
<br>
&gt; On 10/31/12 1:21 PM, Olafur Gudmundsson wrote:<br>
&gt;&gt; Fellow IETF&#39;rs<br>
&gt;&gt; below is a recall petition that I plan on submitting soon if there=
 is<br>
&gt;&gt; enough support.<br>
&gt;<br>
&gt; I regret having to do it this way,<br>
<br>
</div>+1<br>
<div class=3D"im"><br>
&gt; but since it seems to be necessary<br>
&gt; and there is no agreed-upon alternative, I support this.<br>
&gt;<br>
<br>
</div>As do I.<br>
<br>
:-(<br>
<br>
W<br>
<br>
&gt; Melinda<br>
&gt;<br>
&gt;<br>
</blockquote></div><br>

--e89a8ff1cb36d4a99c04cd6c7065--

From nomcom-chair@ietf.org  Thu Nov  1 05:30:32 2012
Return-Path: <nomcom-chair@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7680621F8A3C for <ietf@ietfa.amsl.com>; Thu,  1 Nov 2012 05:30:32 -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=-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 MCSZovILOWeO for <ietf@ietfa.amsl.com>; Thu,  1 Nov 2012 05:30:32 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 507AE21F8A30 for <ietf@ietf.org>; Thu,  1 Nov 2012 05:30:32 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: NomCom Chair <nomcom-chair@ietf.org>
To: ietf@ietf.org
Subject: NomCom 2012: Feedback and Office Hours
X-Test-IDTracker: no
X-IETF-IDTracker: 4.35
Message-ID: <20121101123032.14074.55631.idtracker@ietfa.amsl.com>
Date: Thu, 01 Nov 2012 05:30:32 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Nov 2012 12:30:32 -0000

The IETF Nominations Committee (NomCom) continues to seek input from
the IETF Community.

The final list of candidates (as per RFC 5680) that the NomCom is
considering for open positions can be found at:
https://www.ietf.org/group/nomcom/2012/input/

The NomCom will be holding office hours during IETF 85, Monday-
Thursday from 1:00pm to 3:00pm in Room 305. The NomCom welcomes
comments on specific individuals, as well as general feedback related to
any of the positions that NomCom is considering.

Note: A list of leadership positions that the NomCom is considering can be
found at: https://www.ietf.org/group/nomcom/2012/

If the NomCom office hours are inconvenient for you or if you cannot
attend IETF 85, the NomCom is happy to take community input via email
to nomcom12@ietf.org. Additionally, the NomCom is happy to arrange a
meeting outside of office hours, just send us email and we can set
something up.

Comments on specific candidates can also be provided to the NomCom
via the web feedback tool:
https://www.ietf.org/group/nomcom/2012/input/

In order to ensure that your input is received in time to be useful, please
provide your input on or before Sunday, November 11.

Thank you for your help,
- Matt Lepinski
  nomcom-chair@ietf.org

From olaf@NLnetLabs.nl  Thu Nov  1 07:10:24 2012
Return-Path: <olaf@NLnetLabs.nl>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF61221F8CCC for <ietf@ietfa.amsl.com>; Thu,  1 Nov 2012 07:10:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.599
X-Spam-Level: 
X-Spam-Status: No, score=-104.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_I_LETTER=-2, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, 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 zn-DbdvipRmo for <ietf@ietfa.amsl.com>; Thu,  1 Nov 2012 07:10:24 -0700 (PDT)
Received: from open.nlnetlabs.nl (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8366421F8CCB for <ietf@ietf.org>; Thu,  1 Nov 2012 07:10:23 -0700 (PDT)
Received: from [IPv6:2001:7b8:206:1:ba8d:12ff:fe04:cd14] ([IPv6:2001:7b8:206:1:ba8d:12ff:fe04:cd14]) (authenticated bits=0) by open.nlnetlabs.nl (8.14.5/8.14.4) with ESMTP id qA1EAFed011316 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 1 Nov 2012 15:10:16 +0100 (CET) (envelope-from olaf@NLnetLabs.nl)
X-DKIM: OpenDKIM Filter v2.6.7 open.nlnetlabs.nl qA1EAFed011316
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nlnetlabs.nl; s=default; t=1351779017; bh=GNivbjsyi+pM3z5wIRtG+VrgoY4Gi7OCe8MoXozXqGU=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=YktdHpieYh2vIw5Hjt5zFeWIwG8rjaZrvaOhN3Kmtm4AIJmzethTwke1Za0ulmlsf 2j15ROeqtxm5lI1/9MKXOXK8U0nHcXvkVjgRrYz9aEeWltHVV2NLo/t7NKIoET0Q96 zLa3f0TbFr8GfCHe8P92CYYeEopEg4dM88cET/oQ=
Content-Type: multipart/alternative; boundary="Apple-Mail=_59C743A6-0D3C-4C13-AE73-6EC25EFF7E98"
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: IAOC Request for community feedback
From: Olaf Kolkman <olaf@NLnetLabs.nl>
In-Reply-To: <20121022234941.28301.7687.idtracker@ietfa.amsl.com>
Date: Thu, 1 Nov 2012 15:10:19 +0100
Message-Id: <7E81548C-33E5-46D0-B8F6-1F3602E2C34B@NLnetLabs.nl>
References: <20121022234941.28301.7687.idtracker@ietfa.amsl.com>
To: "ietf@ietf.org list" <ietf@ietf.org>
X-Mailer: Apple Mail (2.1499)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::1]); Thu, 01 Nov 2012 15:10:16 +0100 (CET)
Cc: Olafur Gudmundsson <ogud+shinkuro@ogud.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Nov 2012 14:10:25 -0000

--Apple-Mail=_59C743A6-0D3C-4C13-AE73-6EC25EFF7E98
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On Oct 23, 2012, at 1:49 AM, The IAOC <bob.hinden@gmail.com> wrote:

> The IAOC is requesting feedback from the community concerning a
> vacancy that the IAOC feels is not adequately covered by existing IETF
> rules.
>=20
> Marshall Eubanks has been a active IETF participant for many years and
> a member of the IAOC since 2009. However, he recently stopped
> participating in the IAOC and Trust.


First: I cannot help to think there is a personal tragedy behind all =
this. I hope Marshall makes it back to this community because I will =
miss him.

[ deep breath ]

That said, I believe Bob made a case: Regardless of definition there =
seems to be a problem.

Reading this thread I am sensitive to the arguments that we have a =
process that prevents people being removed without due diligence and I =
understand that if one does not follow the procedure one may be creating =
dangerous and exploitable precedents.=20

However, I also feel we should -as an organization- be more pragmatic at =
times.=20

It seems that the IAOC is trying to be diligent in solving a delicate =
situation most transparently and try to have buy in from the community.

This is the type of pragmatism that is IMHO lives not to the letter but =
to the spirit of our documents. Therefore, without wanting to set =
precedent, I support this cause of action.

I also offer my signature under the recall procedure, in case pragmatism =
doesn't prevail.

--Olaf





NLnet
Labs
Olaf M. Kolkman

www.NLnetLabs.nl
olaf@NLnetLabs.nl

Science Park 400, 1098 XH Amsterdam, The Netherlands




--Apple-Mail=_59C743A6-0D3C-4C13-AE73-6EC25EFF7E98
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><div><div>On Oct 23, 2012, at 1:49 AM, The IAOC &lt;<a =
href=3D"mailto:bob.hinden@gmail.com">bob.hinden@gmail.com</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><span style=3D"font-family: Monaco; font-size: medium; =
font-style: normal; font-variant: normal; font-weight: normal; =
letter-spacing: normal; line-height: normal; orphans: 2; text-align: =
-webkit-auto; text-indent: 0px; text-transform: none; white-space: =
normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px; display: inline !important; float: none; =
">The IAOC is requesting feedback from the community concerning =
a</span><br style=3D"font-family: Monaco; font-size: medium; font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; orphans: 2; text-align: -webkit-auto; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px; "><span style=3D"font-family: Monaco; =
font-size: medium; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: =
none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; display: =
inline !important; float: none; ">vacancy that the IAOC feels is not =
adequately covered by existing IETF</span><br style=3D"font-family: =
Monaco; font-size: medium; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: =
none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><span =
style=3D"font-family: Monaco; font-size: medium; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: =
0px; text-transform: none; white-space: normal; widows: 2; word-spacing: =
0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; =
display: inline !important; float: none; ">rules.</span><br =
style=3D"font-family: Monaco; font-size: medium; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: =
0px; text-transform: none; white-space: normal; widows: 2; word-spacing: =
0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; =
"><br style=3D"font-family: Monaco; font-size: medium; font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; orphans: 2; text-align: -webkit-auto; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px; "><span style=3D"font-family: Monaco; =
font-size: medium; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: =
none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; display: =
inline !important; float: none; ">Marshall Eubanks has been a active =
IETF participant for many years and</span><br style=3D"font-family: =
Monaco; font-size: medium; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: =
none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><span =
style=3D"font-family: Monaco; font-size: medium; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: =
0px; text-transform: none; white-space: normal; widows: 2; word-spacing: =
0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; =
display: inline !important; float: none; ">a member of the IAOC since =
2009. However, he recently stopped</span><br style=3D"font-family: =
Monaco; font-size: medium; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: =
none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><span =
style=3D"font-family: Monaco; font-size: medium; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: =
0px; text-transform: none; white-space: normal; widows: 2; word-spacing: =
0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; =
display: inline !important; float: none; ">participating in the IAOC and =
Trust.</span></blockquote></div><br><div><br =
class=3D"webkit-block-placeholder"></div><div>First: I cannot help to =
think there is a personal tragedy behind all this. I hope Marshall makes =
it back to this community because I will miss =
him.</div><div><br></div><div>[ deep breath =
]</div><div><br></div><div>That said, I believe Bob made a case: =
Regardless of definition there seems to be a =
problem.</div><div><br></div><div>Reading this thread&nbsp;I am =
sensitive to the arguments that we have a process that prevents people =
being removed without due diligence and I understand that if one does =
not follow the procedure one may be creating dangerous and exploitable =
precedents.&nbsp;</div><div><br></div><div>However, I also feel we =
should -as an organization- be more pragmatic at =
times.&nbsp;</div><div><br></div><div>It seems that the IAOC is trying =
to be diligent in solving a delicate situation most transparently and =
try to have buy in from the community.</div><div><br></div><div>This is =
the type of pragmatism that is IMHO lives not to the letter but to the =
spirit of our documents. Therefore, without wanting to set precedent, I =
support this cause of action.</div><div><br></div><div>I also offer my =
signature under the recall procedure, in case pragmatism doesn't =
prevail.</div><div><br></div><div>--Olaf</div><div><br></div><div><br></di=
v><div><br></div><div><br class=3D"webkit-block-placeholder"></div><div>
<span class=3D"Apple-style-span" style=3D"border-collapse: separate; =
border-spacing: 0px; "><span class=3D"Apple-style-span" =
style=3D"font-family: Helvetica; font-size: 12px; "><br =
class=3D"Apple-interchange-newline"><table cellspacing=3D"0" =
cellpadding=3D"0" style=3D"background-color: rgb(255, 255, 255); =
border-collapse: collapse; "><tbody><tr><td rowspan=3D"2" valign=3D"top" =
style=3D"width: 97.8px; height: 56.3px; border-top-style: solid; =
border-right-style: solid; border-bottom-style: solid; =
border-left-style: solid; border-top-width: 1px; border-right-width: =
0px; border-bottom-width: 0px; border-left-width: 0px; border-top-color: =
rgb(180, 180, 180); border-right-color: transparent; =
border-bottom-color: transparent; border-left-color: transparent; =
padding-top: 5px; padding-right: 5px; padding-bottom: 5px; padding-left: =
5px; "><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px; text-align: right; font: normal normal normal =
19px/normal 'Gill Sans'; "><font class=3D"Apple-style-span" =
color=3D"#777777"><span style=3D"letter-spacing: 0px; =
"><b>NLnet<br></b></span><span style=3D"font: normal normal normal =
24px/normal 'Gill Sans'; letter-spacing: 0px; =
">Labs</span></font></div></td><td valign=3D"top" style=3D"width: =
114.5px; height: 18.1px; border-top-style: solid; border-right-style: =
solid; border-bottom-style: solid; border-left-style: solid; =
border-top-width: 1px; border-right-width: 0px; border-bottom-width: =
1px; border-left-width: 0px; border-top-color: rgb(180, 180, 180); =
border-right-color: transparent; border-bottom-color: rgb(202, 202, =
202); border-left-color: transparent; padding-top: 5px; padding-right: =
5px; padding-bottom: 5px; padding-left: 5px; "><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: =
normal normal normal 12px/normal Helvetica; "><span =
style=3D"letter-spacing: 0px; "><font class=3D"Apple-style-span" =
color=3D"#777777">Olaf M. Kolkman</font></span></div></td><td =
valign=3D"top" style=3D"width: 2.3px; height: 18.1px; border-top-style: =
solid; border-right-style: solid; border-bottom-style: solid; =
border-left-style: solid; border-top-width: 1px; border-right-width: =
0px; border-bottom-width: 1px; border-left-width: 0px; border-top-color: =
rgb(180, 180, 180); border-right-color: transparent; =
border-bottom-color: rgb(202, 202, 202); border-left-color: transparent; =
padding-top: 5px; padding-right: 5px; padding-bottom: 5px; padding-left: =
5px; "><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px; font: normal normal normal 12px/normal Helvetica; =
min-height: 14px; "><font class=3D"Apple-style-span" =
color=3D"#777777"><br></font></div></td></tr><tr><td valign=3D"top" =
style=3D"width: 114.5px; height: 27.2px; border-top-style: solid; =
border-right-style: solid; border-bottom-style: solid; =
border-left-style: solid; border-top-width: 1px; border-right-width: =
0px; border-bottom-width: 0px; border-left-width: 0px; border-top-color: =
rgb(202, 202, 202); border-right-color: transparent; =
border-bottom-color: transparent; border-left-color: transparent; =
padding-top: 5px; padding-right: 5px; padding-bottom: 5px; padding-left: =
5px; "><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px; font: normal normal normal 9px/normal Helvetica; =
"><span style=3D"text-decoration: underline; letter-spacing: 0px; "><a =
href=3D"http://www.NLnetLabs.nl"><font class=3D"Apple-style-span" =
color=3D"#777777">www.NLnetLabs.nl</font></a></span></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; font: normal normal normal 9px/normal Helvetica; =
"><span style=3D"text-decoration: underline; letter-spacing: 0px; "><a =
href=3D"mailto:olaf@NLnetLabs.nl"><font class=3D"Apple-style-span" =
color=3D"#777777">olaf@NLnetLabs.nl</font></a></span></div></td><td =
valign=3D"top" style=3D"width: 2.3px; height: 27.2px; border-top-style: =
solid; border-right-style: solid; border-bottom-style: solid; =
border-left-style: solid; border-top-width: 1px; border-right-width: =
0px; border-bottom-width: 0px; border-left-width: 0px; border-top-color: =
rgb(202, 202, 202); border-right-color: transparent; =
border-bottom-color: transparent; border-left-color: transparent; =
padding-top: 5px; padding-right: 5px; padding-bottom: 5px; padding-left: =
5px; "><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px; font: normal normal normal 12px/normal Helvetica; =
min-height: 14px; "><font class=3D"Apple-style-span" =
color=3D"#777777"><br></font></div></td></tr><tr><td colspan=3D"3" =
valign=3D"top" style=3D"width: 234.6px; height: 13.2px; padding-top: =
5px; padding-right: 5px; padding-bottom: 5px; padding-left: 5px; "><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; font: normal normal normal 9px/normal Helvetica; =
"><span style=3D"letter-spacing: 0px; "><font class=3D"Apple-style-span" =
color=3D"#777777">Science Park 400, 1098 XH Amsterdam, The =
Netherlands</font></span></div></td></tr></tbody></table><div =
style=3D"color: rgb(158, 158, 158); margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; font: normal normal normal =
12px/normal Helvetica; min-height: 14px; "><br></div></span></span><br =
class=3D"Apple-interchange-newline">
</div>

<br></body></html>=

--Apple-Mail=_59C743A6-0D3C-4C13-AE73-6EC25EFF7E98--

From tglassey@earthlink.net  Thu Nov  1 07:36:44 2012
Return-Path: <tglassey@earthlink.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6AA4621F8C8E; Thu,  1 Nov 2012 07:36:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.299
X-Spam-Level: 
X-Spam-Status: No, score=-1.299 tagged_above=-999 required=5 tests=[AWL=1.299,  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 olauWwoY1bak; Thu,  1 Nov 2012 07:36:44 -0700 (PDT)
Received: from elasmtp-spurfowl.atl.sa.earthlink.net (elasmtp-spurfowl.atl.sa.earthlink.net [209.86.89.66]) by ietfa.amsl.com (Postfix) with ESMTP id E9A2D21F86CE; Thu,  1 Nov 2012 07:36:31 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=OFyKxw+O5zR0NBPLzBwAKymZba2MyGfsVBzENjKA5GH2qSTDDSRoenaiI2U05fIq; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:X-ELNK-Trace:X-Originating-IP;
Received: from [67.180.133.21] (helo=[192.168.15.2]) by elasmtp-spurfowl.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <tglassey@earthlink.net>) id 1TTvsk-0000eo-Qv; Thu, 01 Nov 2012 10:36:31 -0400
Message-ID: <509288F0.3090004@earthlink.net>
Date: Thu, 01 Nov 2012 07:36:32 -0700
From: tglassey <tglassey@earthlink.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: Bert <bert@secret-wg.org>
Subject: Re: Doesn't the legal standard for maintaining documents also control this? - Re: IESG Statement on Removal of an Internet-Draft from the IETF Web Site -
References: <20121025184720.8144.21627.idtracker@ietfa.amsl.com> <50899BF5.3050703@earthlink.net> <F4D50611-4401-4A94-A7D5-FEC355D8143D@secret-wg.org>
In-Reply-To: <F4D50611-4401-4A94-A7D5-FEC355D8143D@secret-wg.org>
Content-Type: multipart/alternative; boundary="------------030506020204040505090602"
X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec7941f064a79c96ba6cdce0001c15b893d8350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 67.180.133.21
Cc: IETF Chair <chair@ietf.org>, ietf@ietf.org, Jorge Contreras <contreraslegal@att.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Nov 2012 14:36:44 -0000

This is a multi-part message in MIME format.
--------------030506020204040505090602
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 11/1/2012 7:23 AM, Bert wrote:
>
> tglassey wrote:
>
>> //Confidential Mailing - Please destroy this if you are not the 
>> intended recipient.
>
>
> Oh.. better safe than sorry then ****poof****
>
Bert - My apologies let me explain - notice the phrase "...If you are 
not the intended recipient" and since you were a list member you were 
the intended recipient.

Does this answer this question ???

"poof"

Todd

-- 
Regards TSG
"Ex-Cruce-Leo"

//Confidential Mailing - Please destroy this if you are not the intended recipient.


--------------030506020204040505090602
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">On 11/1/2012 7:23 AM, Bert wrote:<br>
    </div>
    <blockquote
      cite="mid:F4D50611-4401-4A94-A7D5-FEC355D8143D@secret-wg.org"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      <div>
        <div><br>
        </div>
        <div>tglassey wrote:</div>
        <br>
        <blockquote type="cite"><span style="font-family: Monaco;
            font-size: medium; font-style: normal; font-variant: normal;
            font-weight: normal; letter-spacing: normal; line-height:
            normal; orphans: 2; text-align: -webkit-auto; text-indent:
            0px; text-transform: none; white-space: normal; widows: 2;
            word-spacing: 0px; -webkit-text-size-adjust: auto;
            -webkit-text-stroke-width: 0px; display: inline !important;
            float: none; ">//Confidential Mailing - Please destroy this
            if you are not the intended recipient.</span></blockquote>
      </div>
      <br>
      <div apple-content-edited="true"><span class="Apple-style-span"
          style="border-collapse: separate; color: rgb(0, 0, 0);
          font-family: Monaco; font-style: normal; font-variant: normal;
          font-weight: normal; letter-spacing: normal; line-height:
          normal; orphans: 2; text-align: -webkit-auto; text-indent:
          0px; text-transform: none; white-space: normal; widows: 2;
          word-spacing: 0px; -webkit-border-horizontal-spacing: 0px;
          -webkit-border-vertical-spacing: 0px;
          -webkit-text-decorations-in-effect: none;
          -webkit-text-size-adjust: auto; -webkit-text-stroke-width:
          0px; font-size: medium; "><span class="Apple-style-span"
            style="font-family: Helvetica; font-size: 12px; ">
            <div style="color: rgb(158, 158, 158); margin-top: 0px;
              margin-right: 0px; margin-bottom: 0px; margin-left: 0px;
              font: normal normal normal 12px/normal Helvetica;
              min-height: 14px; "><br>
            </div>
          </span></span>Oh.. better safe than sorry then&nbsp;****poof****</div>
      <br>
    </blockquote>
    Bert - My apologies let me explain - notice the phrase "...If you
    are not the intended recipient" and since you were a list member you
    were the intended recipient. <br>
    <br>
    Does this answer this question ???<br>
    <br>
    "poof"<br>
    <br>
    Todd<br>
    <br>
    <pre class="moz-signature" cols="72">-- 
Regards TSG
"Ex-Cruce-Leo"

//Confidential Mailing - Please destroy this if you are not the intended recipient. 
</pre>
  </body>
</html>

--------------030506020204040505090602--

From margaretw42@gmail.com  Wed Oct 31 14:30:34 2012
Return-Path: <margaretw42@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A5C321F8621 for <ietf@ietfa.amsl.com>; Wed, 31 Oct 2012 14:30:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[AWL=0.622,  BAYES_00=-2.599, GB_I_LETTER=-2, J_CHICKENPOX_42=0.6, RCVD_IN_DNSWL_LOW=-1, SUBJECT_FUZZY_TION=0.156]
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 420f6KBFQS+7 for <ietf@ietfa.amsl.com>; Wed, 31 Oct 2012 14:30:33 -0700 (PDT)
Received: from mail-qc0-f172.google.com (mail-qc0-f172.google.com [209.85.216.172]) by ietfa.amsl.com (Postfix) with ESMTP id 9F2FA21F861F for <ietf@ietf.org>; Wed, 31 Oct 2012 14:30:33 -0700 (PDT)
Received: by mail-qc0-f172.google.com with SMTP id b25so1439436qca.31 for <ietf@ietf.org>; Wed, 31 Oct 2012 14:30:32 -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 :content-transfer-encoding:message-id:references:to:x-mailer; bh=CzGYapSY15d+06U5KPuT00StRdyXimje1ShUaEJ00ak=; b=xaArXfiNEEayOlZD1RAgOsm/xEgcI8POpeZR7aHTtPtfJS8whVhV/YjdoQ74IfLMOP v53Z+vfVMhowTp61jvzgAP7Ft6ZrS6rnPlTgtScEXM8vlfaXwJCWTyMAd+BGSqLLzC/E EplX5Ioi6J7io0zwJd5CyMTxnoHOBqP0o2vTNQPFpdFg2OM3ceoLtu2Zd1zRJZGU7TgY ka50F5UxFe5MU2x6mCI4hjF2+37F840M8NM76DzTfHv/7gfO83lSYhgqVATFsaLuVV3X immSzniZx0YUm30BsHjv5JqeO1gfMtLvk/+Z65kK4vQBVJBv4a0DJhsaKrwTQDRsD6Le aRXQ==
Received: by 10.224.95.196 with SMTP id e4mr20455794qan.88.1351719032888; Wed, 31 Oct 2012 14:30:32 -0700 (PDT)
Received: from lilac-too.home (pool-71-184-79-25.bstnma.fios.verizon.net. [71.184.79.25]) by mx.google.com with ESMTPS id gu9sm2328232qab.4.2012.10.31.14.30.30 (version=SSLv3 cipher=OTHER); Wed, 31 Oct 2012 14:30:32 -0700 (PDT)
Subject: Re: Recall petition for Mr. Marshall Eubanks
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Margaret Wasserman <margaretw42@gmail.com>
In-Reply-To: <50919671.6000605@ogud.com>
Date: Wed, 31 Oct 2012 17:30:27 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <305F66E3-B414-4344-B497-D7F6FC7D6620@lilacglade.org>
References: <50919671.6000605@ogud.com>
To: Olafur Gudmundsson <ogud@ogud.com>
X-Mailer: Apple Mail (2.1084)
X-Mailman-Approved-At: Thu, 01 Nov 2012 08:09:22 -0700
Cc: 'IETF-Discussion list' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Oct 2012 21:30:34 -0000

I am more concerned than disappointed about Marshall's disappearance =
from the IETF.  However, I agree that complete absence from an I* =
position for three months without explanation should be grounds for =
recall.  So, please consider me to be one of the "signers" of this =
petition.

Marshall, if you are out there, please just let us know you are okay! =20=


Margaret


On Oct 31, 2012, at 5:21 PM, Olafur Gudmundsson wrote:

> Fellow IETF'rs
> below is a recall petition that I plan on submitting soon if there is =
enough support.
>=20
> If you agree with this petition please either comment on this posting, =
or send me email of support noting if you are NomCom eligible (I'm =
arbitrarily limiting the submitted signers of the petition to people =
that have demonstrated recent IETF attendance and participation)
>=20
> The reason I'm starting this recall petition is that I think no other =
way will vacate the positions that Marchall holds before the end of the =
year, I have purposely held of starting this process in the hope that =
Marshall on his own resigned but that has not happened even after he has =
been publicly exposed for over a week.
>=20
> I'm disappointed that a person that took on a responsibility that he =
his not able/willing to fulfill anymore, has not had the courtesy to =
take a few minutes to draft and send a letter of resignation or an =
explanation.
>=20
> Olafur
>=20
> -------- Recall Petition ------------
>=20
> Lynn St. Amour ISOC president,
>=20
>  In accordance with the rules in RFC 3777 Section 7, I request that =
you start recall proceedings  against Mr. Marshall Eubanks as member of =
the IAOC as well as IETF Trustee, due to his total disappearance from =
the IAOC and IETF Trust for over 3 months, and either inability or =
refusal to resign.
>=20
> Evidence to this effect was presented by Bob Hinden [1], as well as =
further evidence that the IETF Trust ousted Mr. Eubanks as  chair of the =
IETF Trust[2] , due to his prolonged absence in that body as well .
>=20
>  I as an IETF member in good standing (having attended over 50 =
meetings since 1987, including 9 of the last 10 meetings), regrettably =
request that you start the recall procedure. Below are listed statements =
of support for this recall petition from  more than 20 other NomCom =
eligible IETF participants.
>=20
>=20
> Thanks
>=20
>      Olafur Gudmundsson
>=20
> [1] =
https://www.ietf.org/ibin/c5i?mid=3D6&rid=3D49&gid=3D0&k1=3D934&k2=3D11277=
&tid=3D1351092666
> [2] =
https://www.ietf.org/ibin/c5i?mid=3D6&rid=3D49&gid=3D0&k1=3D933&k2=3D65510=
&tid=3D1351272565
>=20


From bert@secret-wg.org  Thu Nov  1 07:23:58 2012
Return-Path: <bert@secret-wg.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 687AA21F8B14; Thu,  1 Nov 2012 07:23:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[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 vL0Vc2JlJKzI; Thu,  1 Nov 2012 07:23:55 -0700 (PDT)
Received: from mx.secret-wg.org (bert.secret-wg.org [IPv6:2001:7b8:206:1:0:1234:be21:e31e]) by ietfa.amsl.com (Postfix) with ESMTP id 973F721F8B12; Thu,  1 Nov 2012 07:23:52 -0700 (PDT)
Received: from dhcp-100.nlnetlabs.nl (dhcp-100.nlnetlabs.nl [213.154.224.100]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx.secret-wg.org (Postfix) with ESMTPSA id E3FFC50F5F; Thu,  1 Nov 2012 15:23:50 +0100 (CET)
X-DKIM: OpenDKIM Filter v2.5.2 mx.secret-wg.org E3FFC50F5F
Content-Type: multipart/alternative; boundary="Apple-Mail=_FF2D210B-BEDB-4665-A182-D783DFC07626"
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: Doesn't the legal standard for maintaining documents also control this? - Re: IESG Statement on Removal of an Internet-Draft from the IETF Web Site -
From: Bert <bert@secret-wg.org>
In-Reply-To: <50899BF5.3050703@earthlink.net>
Date: Thu, 1 Nov 2012 15:23:49 +0100
Message-Id: <F4D50611-4401-4A94-A7D5-FEC355D8143D@secret-wg.org>
References: <20121025184720.8144.21627.idtracker@ietfa.amsl.com> <50899BF5.3050703@earthlink.net>
To: tglassey <tglassey@earthlink.net>
X-Mailer: Apple Mail (2.1499)
X-Virus-Scanned: clamav-milter 0.97.6 at bert.secret-wg.org
X-Virus-Status: Clean
X-Mailman-Approved-At: Thu, 01 Nov 2012 08:09:22 -0700
Cc: IETF Chair <chair@ietf.org>, ietf@ietf.org, Jorge Contreras <contreraslegal@att.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Nov 2012 14:23:59 -0000

--Apple-Mail=_FF2D210B-BEDB-4665-A182-D783DFC07626
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


tglassey wrote:

> //Confidential Mailing - Please destroy this if you are not the =
intended recipient.


Oh.. better safe than sorry then ****poof****


--Apple-Mail=_FF2D210B-BEDB-4665-A182-D783DFC07626
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><div><br></div><div>tglassey wrote:</div><br><blockquote =
type=3D"cite"><span style=3D"font-family: Monaco; font-size: medium; =
font-style: normal; font-variant: normal; font-weight: normal; =
letter-spacing: normal; line-height: normal; orphans: 2; text-align: =
-webkit-auto; text-indent: 0px; text-transform: none; white-space: =
normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px; display: inline !important; float: none; =
">//Confidential Mailing - Please destroy this if you are not the =
intended recipient.</span></blockquote></div><br><div =
apple-content-edited=3D"true"><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
Monaco; font-style: normal; font-variant: normal; font-weight: normal; =
letter-spacing: normal; line-height: normal; orphans: 2; text-align: =
-webkit-auto; text-indent: 0px; text-transform: none; white-space: =
normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: =
0px; -webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span =
class=3D"Apple-style-span" style=3D"font-family: Helvetica; font-size: =
12px; "><div style=3D"color: rgb(158, 158, 158); margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal =
normal normal 12px/normal Helvetica; min-height: 14px; =
"><br></div></span></span>Oh.. better safe than sorry =
then&nbsp;****poof****</div>

<br></body></html>=

--Apple-Mail=_FF2D210B-BEDB-4665-A182-D783DFC07626--

From tglassey@earthlink.net  Thu Nov  1 09:08:49 2012
Return-Path: <tglassey@earthlink.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 668A921F8D96 for <ietf@ietfa.amsl.com>; Thu,  1 Nov 2012 09:08:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.571
X-Spam-Level: 
X-Spam-Status: No, score=-2.571 tagged_above=-999 required=5 tests=[AWL=1.272,  BAYES_00=-2.599, GB_I_LETTER=-2, J_CHICKENPOX_42=0.6, SUBJECT_FUZZY_TION=0.156]
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 i7dUoXy9299V for <ietf@ietfa.amsl.com>; Thu,  1 Nov 2012 09:08:48 -0700 (PDT)
Received: from elasmtp-masked.atl.sa.earthlink.net (elasmtp-masked.atl.sa.earthlink.net [209.86.89.68]) by ietfa.amsl.com (Postfix) with ESMTP id B1FCA21F8D8E for <ietf@ietf.org>; Thu,  1 Nov 2012 09:08:48 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=q751ya7eJzoNX95ZnzU50NNxE4rpLjbQ5LdWwgwmpPliswtwdFr4WoPgtPXNy47P; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [67.180.133.21] (helo=[192.168.15.2]) by elasmtp-masked.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <tglassey@earthlink.net>) id 1TTxK4-0003Yb-1c for ietf@ietf.org; Thu, 01 Nov 2012 12:08:48 -0400
Message-ID: <50929E91.3090509@earthlink.net>
Date: Thu, 01 Nov 2012 09:08:49 -0700
From: tglassey <tglassey@earthlink.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Recall petition for Mr. Marshall Eubanks
References: <50919671.6000605@ogud.com> <305F66E3-B414-4344-B497-D7F6FC7D6620@lilacglade.org>
In-Reply-To: <305F66E3-B414-4344-B497-D7F6FC7D6620@lilacglade.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec79b62796eeb244b08c2d37f610802adca5350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 67.180.133.21
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Nov 2012 16:08:49 -0000

On 10/31/2012 2:30 PM, Margaret Wasserman wrote:
> I am more concerned than disappointed about Marshall's disappearance from the IETF.  However, I agree that complete absence from an I* position for three months without explanation should be grounds for recall.  So, please consider me to be one of the "signers" of this petition.
>
> Marshall, if you are out there, please just let us know you are okay!
Wouldnt it make sense to add this as a policy and then use the new 
policy to make this change rather than a special vote with no underlying 
framework or in-place policy to support this type of termination.

Todd
>
> Margaret
>
>
> On Oct 31, 2012, at 5:21 PM, Olafur Gudmundsson wrote:
>
>> Fellow IETF'rs
>> below is a recall petition that I plan on submitting soon if there is enough support.
>>
>> If you agree with this petition please either comment on this posting, or send me email of support noting if you are NomCom eligible (I'm arbitrarily limiting the submitted signers of the petition to people that have demonstrated recent IETF attendance and participation)
>>
>> The reason I'm starting this recall petition is that I think no other way will vacate the positions that Marchall holds before the end of the year, I have purposely held of starting this process in the hope that Marshall on his own resigned but that has not happened even after he has been publicly exposed for over a week.
>>
>> I'm disappointed that a person that took on a responsibility that he his not able/willing to fulfill anymore, has not had the courtesy to take a few minutes to draft and send a letter of resignation or an explanation.
>>
>> Olafur
>>
>> -------- Recall Petition ------------
>>
>> Lynn St. Amour ISOC president,
>>
>>   In accordance with the rules in RFC 3777 Section 7, I request that you start recall proceedings  against Mr. Marshall Eubanks as member of the IAOC as well as IETF Trustee, due to his total disappearance from the IAOC and IETF Trust for over 3 months, and either inability or refusal to resign.
>>
>> Evidence to this effect was presented by Bob Hinden [1], as well as further evidence that the IETF Trust ousted Mr. Eubanks as  chair of the IETF Trust[2] , due to his prolonged absence in that body as well .
>>
>>   I as an IETF member in good standing (having attended over 50 meetings since 1987, including 9 of the last 10 meetings), regrettably request that you start the recall procedure. Below are listed statements of support for this recall petition from  more than 20 other NomCom eligible IETF participants.
>>
>>
>> Thanks
>>
>>       Olafur Gudmundsson
>>
>> [1] https://www.ietf.org/ibin/c5i?mid=6&rid=49&gid=0&k1=934&k2=11277&tid=1351092666
>> [2] https://www.ietf.org/ibin/c5i?mid=6&rid=49&gid=0&k1=933&k2=65510&tid=1351272565
>>
>


-- 
Regards TSG
"Ex-Cruce-Leo"

//Confidential Mailing - Please destroy this if you are not the intended recipient.


From olaf@NLnetLabs.nl  Thu Nov  1 09:32:29 2012
Return-Path: <olaf@NLnetLabs.nl>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 956E321F9015 for <ietf@ietfa.amsl.com>; Thu,  1 Nov 2012 09:32:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.554
X-Spam-Level: 
X-Spam-Status: No, score=-103.554 tagged_above=-999 required=5 tests=[AWL=0.289, BAYES_00=-2.599, GB_I_LETTER=-2, HTML_MESSAGE=0.001,  J_CHICKENPOX_42=0.6, NO_RELAYS=-0.001, SUBJECT_FUZZY_TION=0.156, 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 OTeqWQwiwOkP for <ietf@ietfa.amsl.com>; Thu,  1 Nov 2012 09:32:28 -0700 (PDT)
Received: from open.nlnetlabs.nl (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 82BBB21F900C for <ietf@ietf.org>; Thu,  1 Nov 2012 09:32:27 -0700 (PDT)
Received: from [IPv6:2001:7b8:206:1:ba8d:12ff:fe04:cd14] ([IPv6:2001:7b8:206:1:ba8d:12ff:fe04:cd14]) (authenticated bits=0) by open.nlnetlabs.nl (8.14.5/8.14.4) with ESMTP id qA1GWJS1067014 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 1 Nov 2012 17:32:20 +0100 (CET) (envelope-from olaf@NLnetLabs.nl)
X-DKIM: OpenDKIM Filter v2.6.7 open.nlnetlabs.nl qA1GWJS1067014
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nlnetlabs.nl; s=default; t=1351787542; bh=0RmguTcN+K8BODAP2CaUwuO/LW6r133LPoM9FPccHSY=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=y0KZUytaWtP93u2pm23rUCtIgsO+FgnSzTPOBf+0ekcikrlXILsoe011yI9KrpMGU v2lRQvBqbkTWU9Qxui+dvo8vNbEh7kewVw0rgXIkjSg8VAtpHYXYmDhAFzpJcfZyXA Y/+yXFgKorFBS6Y5zdoGT3b5vHVq53NhRWxKAKEw=
Content-Type: multipart/alternative; boundary="Apple-Mail=_3F0D1633-C78A-4C67-8149-89C568F30D05"
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: Recall petition for Mr. Marshall Eubanks
From: Olaf Kolkman <olaf@NLnetLabs.nl>
In-Reply-To: <50919671.6000605@ogud.com>
Date: Thu, 1 Nov 2012 17:32:23 +0100
Message-Id: <7F4FE714-DEDC-4D64-ADD8-AA6ECF53EABB@NLnetLabs.nl>
References: <50919671.6000605@ogud.com>
To: Olafur Gudmundsson <ogud@ogud.com>
X-Mailer: Apple Mail (2.1499)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::1]); Thu, 01 Nov 2012 17:32:21 +0100 (CET)
Cc: 'IETF-Discussion list' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Nov 2012 16:32:30 -0000

--Apple-Mail=_3F0D1633-C78A-4C67-8149-89C568F30D05
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1


On Oct 31, 2012, at 10:21 PM, Olafur Gudmundsson <ogud@ogud.com> wrote:

> Fellow IETF'rs
> below is a recall petition that I plan on submitting soon if there is =
enough support.
>=20
> If you agree with this petition please either comment on this posting, =
or send me email of support noting if you are NomCom eligible (I'm =
arbitrarily limiting the submitted signers of the petition to people =
that have demonstrated recent IETF attendance and participation)
>=20
> The reason I'm starting this recall petition is that I think no other =
way will vacate the positions that Marchall holds before the end of the =
year, I have purposely held of starting this process in the hope that =
Marshall on his own resigned but that has not happened even after he has =
been publicly exposed for over a week.
>=20
> I'm disappointed that a person that took on a responsibility that he =
his not able/willing to fulfill anymore, has not had the courtesy to =
take a few minutes to draft and send a letter of resignation or an =
explanation.
>=20
> Olafur
>=20
> -------- Recall Petition ------------
>=20
> Lynn St. Amour ISOC president,
>=20
>  In accordance with the rules in RFC 3777 Section 7, I request that =
you start recall proceedings  against Mr. Marshall Eubanks as member of =
the IAOC as well as IETF Trustee, due to his total disappearance from =
the IAOC and IETF Trust for over 3 months, and either inability or =
refusal to resign.
>=20
> Evidence to this effect was presented by Bob Hinden [1], as well as =
further evidence that the IETF Trust ousted Mr. Eubanks as  chair of the =
IETF Trust[2] , due to his prolonged absence in that body as well .
>=20
>  I as an IETF member in good standing (having attended over 50 =
meetings since 1987, including 9 of the last 10 meetings), regrettably =
request that you start the recall procedure. Below are listed statements =
of support for this recall petition from  more than 20 other NomCom =
eligible IETF participants.
>=20
>=20
> Thanks
>=20
>      Olafur Gudmundsson
>=20
> [1] =
https://www.ietf.org/ibin/c5i?mid=3D6&rid=3D49&gid=3D0&k1=3D934&k2=3D11277=
&tid=3D1351092666
> [2] =
https://www.ietf.org/ibin/c5i?mid=3D6&rid=3D49&gid=3D0&k1=3D933&k2=3D65510=
&tid=3D1351272565



I also offer my signature under the recall procedure, in case pragmatism =
doesn't prevail (see my other note).

My offer of signature should in no way be interpreted as reflecting an =
opinion about Marshall's character.


--Olaf




NLnet
Labs
Olaf M. Kolkman

www.NLnetLabs.nl
olaf@NLnetLabs.nl

Science Park 400, 1098 XH Amsterdam, The Netherlands




--Apple-Mail=_3F0D1633-C78A-4C67-8149-89C568F30D05
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=iso-8859-1

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Diso-8859-1"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><div><div>On Oct 31, 2012, at 10:21 PM, Olafur Gudmundsson &lt;<a =
href=3D"mailto:ogud@ogud.com">ogud@ogud.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite">Fellow =
IETF'rs<br>below is a recall petition that I plan on submitting soon if =
there is enough support.<br><br>If you agree with this petition please =
either comment on this posting, or send me email of support noting if =
you are NomCom eligible (I'm arbitrarily limiting the submitted signers =
of the petition to people that have demonstrated recent IETF attendance =
and participation)<br><br>The reason I'm starting this recall petition =
is that I think no other way will vacate the positions that Marchall =
holds before the end of the year, I have purposely held of starting this =
process in the hope that Marshall on his own resigned but that has not =
happened even after he has been publicly exposed for over a =
week.<br><br>I'm disappointed that a person that took on a =
responsibility that he his not able/willing to fulfill anymore, has not =
had the courtesy to take a few minutes to draft and send a letter of =
resignation or an explanation.<br><br>Olafur<br><br>-------- Recall =
Petition ------------<br><br>Lynn St. Amour ISOC president,<br><br> =
&nbsp;In accordance with the rules in RFC 3777 Section 7, I request that =
you start recall proceedings &nbsp;against Mr. Marshall Eubanks as =
member of the IAOC as well as IETF Trustee, due to his total =
disappearance from the IAOC and IETF Trust for over 3 months, and either =
inability or refusal to resign.<br><br>Evidence to this effect was =
presented by Bob Hinden [1], as well as further evidence that the IETF =
Trust ousted Mr. Eubanks as &nbsp;chair of the IETF Trust[2] , due to =
his prolonged absence in that body as well .<br><br> &nbsp;I as an IETF =
member in good standing (having attended over 50 meetings since 1987, =
including 9 of the last 10 meetings), regrettably request that you start =
the recall procedure. Below are listed statements of support for this =
recall petition from &nbsp;more than 20 other NomCom eligible IETF =
participants.<br><br><br>Thanks<br><br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Olafur Gudmundsson<br><br>[1] <a =
href=3D"https://www.ietf.org/ibin/c5i?mid=3D6&amp;rid=3D49&amp;gid=3D0&amp=
;k1=3D934&amp;k2=3D11277&amp;tid=3D1351092666">https://www.ietf.org/ibin/c=
5i?mid=3D6&amp;rid=3D49&amp;gid=3D0&amp;k1=3D934&amp;k2=3D11277&amp;tid=3D=
1351092666</a><br>[2] <a =
href=3D"https://www.ietf.org/ibin/c5i?mid=3D6&amp;rid=3D49&amp;gid=3D0&amp=
;k1=3D933&amp;k2=3D65510&amp;tid=3D1351272565">https://www.ietf.org/ibin/c=
5i?mid=3D6&amp;rid=3D49&amp;gid=3D0&amp;k1=3D933&amp;k2=3D65510&amp;tid=3D=
1351272565</a><br></blockquote></div><br><div><br =
class=3D"webkit-block-placeholder"></div><div><br =
class=3D"webkit-block-placeholder"></div><div><div>I also offer my =
signature under the recall procedure, in case pragmatism doesn't prevail =
(see my other note).</div></div><div><br></div><div>My offer of =
signature should in no way be interpreted as reflecting an opinion about =
Marshall's =
character.</div><div><br></div><div><br></div><div>--Olaf</div><div><br></=
div><div><br class=3D"webkit-block-placeholder"></div><div><br =
class=3D"webkit-block-placeholder"></div><div>
<span class=3D"Apple-style-span" style=3D"border-collapse: separate; =
border-spacing: 0px; "><span class=3D"Apple-style-span" =
style=3D"font-family: Helvetica; font-size: 12px; "><br =
class=3D"Apple-interchange-newline"><table cellspacing=3D"0" =
cellpadding=3D"0" style=3D"background-color: rgb(255, 255, 255); =
border-collapse: collapse; "><tbody><tr><td rowspan=3D"2" valign=3D"top" =
style=3D"width: 97.8px; height: 56.3px; border-top-style: solid; =
border-right-style: solid; border-bottom-style: solid; =
border-left-style: solid; border-top-width: 1px; border-right-width: =
0px; border-bottom-width: 0px; border-left-width: 0px; border-top-color: =
rgb(180, 180, 180); border-right-color: transparent; =
border-bottom-color: transparent; border-left-color: transparent; =
padding-top: 5px; padding-right: 5px; padding-bottom: 5px; padding-left: =
5px; "><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px; text-align: right; font: normal normal normal =
19px/normal 'Gill Sans'; "><font class=3D"Apple-style-span" =
color=3D"#777777"><span style=3D"letter-spacing: 0px; =
"><b>NLnet<br></b></span><span style=3D"font: normal normal normal =
24px/normal 'Gill Sans'; letter-spacing: 0px; =
">Labs</span></font></div></td><td valign=3D"top" style=3D"width: =
114.5px; height: 18.1px; border-top-style: solid; border-right-style: =
solid; border-bottom-style: solid; border-left-style: solid; =
border-top-width: 1px; border-right-width: 0px; border-bottom-width: =
1px; border-left-width: 0px; border-top-color: rgb(180, 180, 180); =
border-right-color: transparent; border-bottom-color: rgb(202, 202, =
202); border-left-color: transparent; padding-top: 5px; padding-right: =
5px; padding-bottom: 5px; padding-left: 5px; "><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: =
normal normal normal 12px/normal Helvetica; "><span =
style=3D"letter-spacing: 0px; "><font class=3D"Apple-style-span" =
color=3D"#777777">Olaf M. Kolkman</font></span></div></td><td =
valign=3D"top" style=3D"width: 2.3px; height: 18.1px; border-top-style: =
solid; border-right-style: solid; border-bottom-style: solid; =
border-left-style: solid; border-top-width: 1px; border-right-width: =
0px; border-bottom-width: 1px; border-left-width: 0px; border-top-color: =
rgb(180, 180, 180); border-right-color: transparent; =
border-bottom-color: rgb(202, 202, 202); border-left-color: transparent; =
padding-top: 5px; padding-right: 5px; padding-bottom: 5px; padding-left: =
5px; "><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px; font: normal normal normal 12px/normal Helvetica; =
min-height: 14px; "><font class=3D"Apple-style-span" =
color=3D"#777777"><br></font></div></td></tr><tr><td valign=3D"top" =
style=3D"width: 114.5px; height: 27.2px; border-top-style: solid; =
border-right-style: solid; border-bottom-style: solid; =
border-left-style: solid; border-top-width: 1px; border-right-width: =
0px; border-bottom-width: 0px; border-left-width: 0px; border-top-color: =
rgb(202, 202, 202); border-right-color: transparent; =
border-bottom-color: transparent; border-left-color: transparent; =
padding-top: 5px; padding-right: 5px; padding-bottom: 5px; padding-left: =
5px; "><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px; font: normal normal normal 9px/normal Helvetica; =
"><span style=3D"text-decoration: underline; letter-spacing: 0px; "><a =
href=3D"http://www.NLnetLabs.nl"><font class=3D"Apple-style-span" =
color=3D"#777777">www.NLnetLabs.nl</font></a></span></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; font: normal normal normal 9px/normal Helvetica; =
"><span style=3D"text-decoration: underline; letter-spacing: 0px; "><a =
href=3D"mailto:olaf@NLnetLabs.nl"><font class=3D"Apple-style-span" =
color=3D"#777777">olaf@NLnetLabs.nl</font></a></span></div></td><td =
valign=3D"top" style=3D"width: 2.3px; height: 27.2px; border-top-style: =
solid; border-right-style: solid; border-bottom-style: solid; =
border-left-style: solid; border-top-width: 1px; border-right-width: =
0px; border-bottom-width: 0px; border-left-width: 0px; border-top-color: =
rgb(202, 202, 202); border-right-color: transparent; =
border-bottom-color: transparent; border-left-color: transparent; =
padding-top: 5px; padding-right: 5px; padding-bottom: 5px; padding-left: =
5px; "><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px; font: normal normal normal 12px/normal Helvetica; =
min-height: 14px; "><font class=3D"Apple-style-span" =
color=3D"#777777"><br></font></div></td></tr><tr><td colspan=3D"3" =
valign=3D"top" style=3D"width: 234.6px; height: 13.2px; padding-top: =
5px; padding-right: 5px; padding-bottom: 5px; padding-left: 5px; "><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; font: normal normal normal 9px/normal Helvetica; =
"><span style=3D"letter-spacing: 0px; "><font class=3D"Apple-style-span" =
color=3D"#777777">Science Park 400, 1098 XH Amsterdam, The =
Netherlands</font></span></div></td></tr></tbody></table><div =
style=3D"color: rgb(158, 158, 158); margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; font: normal normal normal =
12px/normal Helvetica; min-height: 14px; "><br></div></span></span><br =
class=3D"Apple-interchange-newline">
</div>

<br></body></html>=

--Apple-Mail=_3F0D1633-C78A-4C67-8149-89C568F30D05--

From dave@cridland.net  Thu Nov  1 09:38:21 2012
Return-Path: <dave@cridland.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 81E8A21F8D5F for <ietf@ietfa.amsl.com>; Thu,  1 Nov 2012 09:38:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.22
X-Spam-Level: 
X-Spam-Status: No, score=-2.22 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, J_CHICKENPOX_42=0.6, RCVD_IN_DNSWL_LOW=-1, SUBJECT_FUZZY_TION=0.156]
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 SHe0kWahYdPa for <ietf@ietfa.amsl.com>; Thu,  1 Nov 2012 09:38:19 -0700 (PDT)
Received: from mail-wi0-f172.google.com (mail-wi0-f172.google.com [209.85.212.172]) by ietfa.amsl.com (Postfix) with ESMTP id 4C2CF21F8CB3 for <ietf@ietf.org>; Thu,  1 Nov 2012 09:38:17 -0700 (PDT)
Received: by mail-wi0-f172.google.com with SMTP id hq12so438411wib.13 for <ietf@ietf.org>; Thu, 01 Nov 2012 09:38:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=6me5GKViIlJMWk3B3kHv236DDehnanGp85DFVBHcjXk=; b=TwZ7ukVd2Skgqm15qChqBX7II/u6N8OUKrxqetxhGbcAkg0l02Y8/k2IYApNclfAAG 5ZnW6pr6vftZ5J0uGjnpS9maGn1TfDDyj9qhaJPr1Tn4BNqLQC9EuC6Qzkv73bQjmooU AXHg2w2smk6Lm+P0wGlv8im3dCoxRrD2HWErg=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=6me5GKViIlJMWk3B3kHv236DDehnanGp85DFVBHcjXk=; b=ZspiNiRZQarwM1+htUwBuHdDYTv4RKjK53gln/cCBB1UsHLguzXYXIDQazILCRSJgi pRVRlaxoNsic/oY39un8nT0MN1tofLyiZIZA0//tUyHZHMa5FY7/U+3VKnqrOM1pYHUS VrURoaXmFXaVGt7C6sXvR+0BLIigr7wcTljFPcIbpsJWSlWVdMz8+mk/vta2r97xBDxk C5gJXxWqbDEyFkhhCIHOMz0nmsKD1ZlXr1CWYa/vtUPw+D0sEUqMppDjZSERD9XszETr v23qjK+goKqU+EulcAUIHSbqqEO89bQjTSu91Q6sNaIX8ttd5/t5rzI0vynKZqm6AjFe jOIw==
MIME-Version: 1.0
Received: by 10.216.93.80 with SMTP id k58mr18593649wef.98.1351787896374; Thu, 01 Nov 2012 09:38:16 -0700 (PDT)
Received: by 10.194.135.47 with HTTP; Thu, 1 Nov 2012 09:38:16 -0700 (PDT)
Received: by 10.194.135.47 with HTTP; Thu, 1 Nov 2012 09:38:16 -0700 (PDT)
In-Reply-To: <CAJfR-+PDvsswi3yU-H5TsK_W8RNeSwNMD2Gcdc2SksKEG1xDYQ@mail.gmail.com>
References: <50919671.6000605@ogud.com> <5091CD21.3010504@gmail.com> <1158F458-8810-4CD2-B874-3DE1A1B8B0B5@kumari.net> <CAJfR-+PDvsswi3yU-H5TsK_W8RNeSwNMD2Gcdc2SksKEG1xDYQ@mail.gmail.com>
Date: Thu, 1 Nov 2012 16:38:16 +0000
Message-ID: <CAKHUCzzeaFf3iS8Un9nXyAEYaBncraCgfWBg4vrNkHGmPKAMfA@mail.gmail.com>
Subject: Re: [IETF] Re: Recall petition for Mr. Marshall Eubanks
From: Dave Cridland <dave@cridland.net>
To: Turchanyi Geza <turchanyi.geza@gmail.com>
Content-Type: multipart/alternative; boundary=0016e6d7e04f6006ea04cd71a5f6
X-Gm-Message-State: ALoCoQkpSotNEhfhuVnXFQWT/bj3By1ZINqXHK5JGoPYv0dtNiwsdM6mY0UuYJ+5xM2SOFRihamC
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Nov 2012 16:38:21 -0000

--0016e6d7e04f6006ea04cd71a5f6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

I am not NomCom qualified, but I do support the recall. I also suspect
that, given the total disappearance of Marshall Eubanks from all online
activity in early August, he is either ill, deceased, or otherwise unable
to fulfill his obligations. Whichever, the IAOC needs a functional member,
and so recall is our best current option. I just hope the explanation turns
out to involve Marshall being okay.

Dave.
On Nov 1, 2012 10:25 AM, "Turchanyi Geza" <turchanyi.geza@gmail.com> wrote:

> Hello,
>
> I am glad to see that apparently there are no more supporters of this
> proposal.
>
> Please be more tolerant to Marshall Eubank.
>
> Best,
>
> G=E9za
>
>
> On Thu, Nov 1, 2012 at 2:22 AM, Warren Kumari <warren@kumari.net> wrote:
>
>>
>>
>> Warren Kumari
>> ------
>> Please excuse typing, etc -- This was sent from a device with a tiny
>> keyboard.
>>
>> On Oct 31, 2012, at 9:15 PM, Melinda Shore <melinda.shore@gmail.com>
>> wrote:
>>
>> > On 10/31/12 1:21 PM, Olafur Gudmundsson wrote:
>> >> Fellow IETF'rs
>> >> below is a recall petition that I plan on submitting soon if there is
>> >> enough support.
>> >
>> > I regret having to do it this way,
>>
>> +1
>>
>> > but since it seems to be necessary
>> > and there is no agreed-upon alternative, I support this.
>> >
>>
>> As do I.
>>
>> :-(
>>
>> W
>>
>> > Melinda
>> >
>> >
>>
>
>

--0016e6d7e04f6006ea04cd71a5f6
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<p>I am not NomCom qualified, but I do support the recall. I also suspect t=
hat, given the total disappearance of Marshall Eubanks from all online acti=
vity in early August, he is either ill, deceased, or otherwise unable to fu=
lfill his obligations. Whichever, the IAOC needs a functional member, and s=
o recall is our best current option. I just hope the explanation turns out =
to involve Marshall being okay.</p>

<p>Dave.</p>
<div class=3D"gmail_quote">On Nov 1, 2012 10:25 AM, &quot;Turchanyi Geza&qu=
ot; &lt;<a href=3D"mailto:turchanyi.geza@gmail.com">turchanyi.geza@gmail.co=
m</a>&gt; wrote:<br type=3D"attribution"><blockquote class=3D"gmail_quote" =
style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hello,<br><br>I am glad to see that apparently there are no more supporters=
 of this proposal.<br><br>Please be more tolerant to Marshall Eubank.<br><b=
r>Best,<br><br>G=E9za<br><br><br><div class=3D"gmail_quote">On Thu, Nov 1, =
2012 at 2:22 AM, Warren Kumari <span dir=3D"ltr">&lt;<a href=3D"mailto:warr=
en@kumari.net" target=3D"_blank">warren@kumari.net</a>&gt;</span> wrote:<br=
>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><br>
<br>
Warren Kumari<br>
------<br>
Please excuse typing, etc -- This was sent from a device with a tiny keyboa=
rd.<br>
<div><br>
On Oct 31, 2012, at 9:15 PM, Melinda Shore &lt;<a href=3D"mailto:melinda.sh=
ore@gmail.com" target=3D"_blank">melinda.shore@gmail.com</a>&gt; wrote:<br>
<br>
&gt; On 10/31/12 1:21 PM, Olafur Gudmundsson wrote:<br>
&gt;&gt; Fellow IETF&#39;rs<br>
&gt;&gt; below is a recall petition that I plan on submitting soon if there=
 is<br>
&gt;&gt; enough support.<br>
&gt;<br>
&gt; I regret having to do it this way,<br>
<br>
</div>+1<br>
<div><br>
&gt; but since it seems to be necessary<br>
&gt; and there is no agreed-upon alternative, I support this.<br>
&gt;<br>
<br>
</div>As do I.<br>
<br>
:-(<br>
<br>
W<br>
<br>
&gt; Melinda<br>
&gt;<br>
&gt;<br>
</blockquote></div><br>
</blockquote></div>

--0016e6d7e04f6006ea04cd71a5f6--

From worley@shell01.TheWorld.com  Thu Nov  1 09:38:22 2012
Return-Path: <worley@shell01.TheWorld.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 46DA121F8D6D for <ietf@ietfa.amsl.com>; Thu,  1 Nov 2012 09:38:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.566
X-Spam-Level: 
X-Spam-Status: No, score=-0.566 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, RCVD_IN_DNSWL_LOW=-1, RCVD_IN_SORBS_WEB=0.619]
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 kMpsmM22xP7q for <ietf@ietfa.amsl.com>; Thu,  1 Nov 2012 09:38:21 -0700 (PDT)
Received: from TheWorld.com (pcls2.std.com [192.74.137.142]) by ietfa.amsl.com (Postfix) with ESMTP id 9A42721F8D69 for <ietf@ietf.org>; Thu,  1 Nov 2012 09:38:20 -0700 (PDT)
Received: from shell.TheWorld.com (root@shell01.theworld.com [192.74.137.71]) by TheWorld.com (8.14.5/8.14.5) with ESMTP id qA1GcEFd005592 for <ietf@ietf.org>; Thu, 1 Nov 2012 12:38:16 -0400
Received: from shell01.TheWorld.com (localhost.theworld.com [127.0.0.1]) by shell.TheWorld.com (8.13.6/8.12.8) with ESMTP id qA1GcEnl152373 for <ietf@ietf.org>; Thu, 1 Nov 2012 11:38:14 -0500 (EST)
Received: (from worley@localhost) by shell01.TheWorld.com (8.13.6/8.13.6/Submit) id qA1GcEXI155593; Thu, 1 Nov 2012 12:38:14 -0400 (EDT)
Date: Thu, 1 Nov 2012 12:38:14 -0400 (EDT)
Message-Id: <201211011638.qA1GcEXI155593@shell01.TheWorld.com>
From: worley@ariadne.com (Dale R. Worley)
Sender: worley@ariadne.com (Dale R. Worley)
To: ietf@ietf.org
In-reply-to: <7E81548C-33E5-46D0-B8F6-1F3602E2C34B@NLnetLabs.nl> (olaf@NLnetLabs.nl)
Subject: Re: IAOC Request for community feedback
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Nov 2012 16:38:22 -0000

There seems to me to be a "constitutional" issue that has not been
addressed, and may well bedevil us in the future:  In any collective
body, there is a concept of a quorum, which is set high enough to
ensure that the actions of any meeting represent the opinions of the
body as a whole, and which is set low enough that the expected level
of absences will not prevent business from being done.

The current crisis is (apparently) due to the chronic absence of *one*
member causing *chronic* failures of the IAOC to achieve a quorum.
This suggests to me that the quorum of the IAOC is too high to allow
it to reliably conduct business -- after all, any of a thousand
accidents can cause one member to be absent for a long period of time.

What are the quorum rules of the IAOC?  Should they be revised?

Dale

From mstjohns@comcast.net  Thu Nov  1 10:52:50 2012
Return-Path: <mstjohns@comcast.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 81C7E21F89A2 for <ietf@ietfa.amsl.com>; Thu,  1 Nov 2012 10:52:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.68
X-Spam-Level: 
X-Spam-Status: No, score=-99.68 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611,  HTML_MESSAGE=0.001, J_CHICKENPOX_42=0.6, RDNS_NONE=0.1, SUBJECT_FUZZY_TION=0.156, 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 hJPY7cr2f6bv for <ietf@ietfa.amsl.com>; Thu,  1 Nov 2012 10:52:50 -0700 (PDT)
Received: from qmta05.westchester.pa.mail.comcast.net (qmta05.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:48]) by ietfa.amsl.com (Postfix) with ESMTP id D92C521F89A0 for <ietf@ietf.org>; Thu,  1 Nov 2012 10:52:49 -0700 (PDT)
Received: from omta17.westchester.pa.mail.comcast.net ([76.96.62.89]) by qmta05.westchester.pa.mail.comcast.net with comcast id JAi91k0041vXlb855HsuGp; Thu, 01 Nov 2012 17:52:54 +0000
Received: from Mike-T530.comcast.net ([68.83.212.126]) by omta17.westchester.pa.mail.comcast.net with comcast id JHsw1k00f2kB7pQ3dHsx3M; Thu, 01 Nov 2012 17:52:57 +0000
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Thu, 01 Nov 2012 13:52:57 -0400
To: Turchanyi Geza <turchanyi.geza@gmail.com>, Warren Kumari <warren@kumari.net>
From: Michael StJohns <mstjohns@comcast.net>
Subject: Re: [IETF] Re: Recall petition for Mr. Marshall Eubanks
In-Reply-To: <CAJfR-+PDvsswi3yU-H5TsK_W8RNeSwNMD2Gcdc2SksKEG1xDYQ@mail.g mail.com>
References: <50919671.6000605@ogud.com> <5091CD21.3010504@gmail.com> <1158F458-8810-4CD2-B874-3DE1A1B8B0B5@kumari.net> <CAJfR-+PDvsswi3yU-H5TsK_W8RNeSwNMD2Gcdc2SksKEG1xDYQ@mail.gmail.com>
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=====================_787260184==.ALT"
Message-Id: <20121101175249.D92C521F89A0@ietfa.amsl.com>
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Nov 2012 17:52:50 -0000

--=====================_787260184==.ALT
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Per Olafur's email, I submitted my signature directly to him, along with my=
 Nomcom eligibility status.  I'm sure other's did as well, so you shouldn't=
 take the absence of emails on this list as lack of support for the=
 proposal.

Mike


At 06:25 AM 11/1/2012, Turchanyi Geza wrote:
>Hello,
>
>I am glad to see that apparently there are no more supporters of this=
 proposal.
>
>Please be more tolerant to Marshall Eubank.
>
>Best,
>
>G=E9za
>
>
>On Thu, Nov 1, 2012 at 2:22 AM, Warren Kumari=
 <<mailto:warren@kumari.net>warren@kumari.net> wrote:
>
>
>Warren Kumari
>------
>Please excuse typing, etc -- This was sent from a device with a tiny=
 keyboard.
>
>On Oct 31, 2012, at 9:15 PM, Melinda Shore=
 <<mailto:melinda.shore@gmail.com>melinda.shore@gmail.com> wrote:
>
>> On 10/31/12 1:21 PM, Olafur Gudmundsson wrote:
>>> Fellow IETF'rs
>>> below is a recall petition that I plan on submitting soon if there is
>>> enough support.
>>
>> I regret having to do it this way,
>
>+1
>
>> but since it seems to be necessary
>> and there is no agreed-upon alternative, I support this.
>>
>
>As do I.
>
>:-(
>
>W
>
>> Melinda
>>
>>
>


--=====================_787260184==.ALT
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<body>
Per Olafur's email, I submitted my signature directly to him, along with
my Nomcom eligibility status.&nbsp; I'm sure other's did as well, so you
shouldn't take the absence of emails on this list as lack of support for
the proposal.<br><br>
Mike<br><br>
<br>
At 06:25 AM 11/1/2012, Turchanyi Geza wrote:<br>
<blockquote type=3Dcite class=3Dcite cite=3D"">Hello,<br><br>
I am glad to see that apparently there are no more supporters of this
proposal.<br><br>
Please be more tolerant to Marshall Eubank.<br><br>
Best,<br><br>
G=E9za<br><br>
<br>
On Thu, Nov 1, 2012 at 2:22 AM, Warren Kumari
&lt;<a href=3D"mailto:warren@kumari.net">warren@kumari.net</a>&gt;
wrote:<br>

<dl><br><br>

<dd>Warren Kumari<br>

<dd>------<br>

<dd>Please excuse typing, etc -- This was sent from a device with a tiny
keyboard.<br><br>

<dd>On Oct 31, 2012, at 9:15 PM, Melinda Shore
&lt;<a href=3D"mailto:melinda.shore@gmail.com">melinda.shore@gmail.com</a>
&gt; wrote:<br><br>

<dd>&gt; On 10/31/12 1:21 PM, Olafur Gudmundsson wrote:<br>

<dd>&gt;&gt; Fellow IETF'rs<br>

<dd>&gt;&gt; below is a recall petition that I plan on submitting soon if
there is<br>

<dd>&gt;&gt; enough support.<br>

<dd>&gt;<br>

<dd>&gt; I regret having to do it this way,<br><br>

<dd>+1<br><br>

<dd>&gt; but since it seems to be necessary<br>

<dd>&gt; and there is no agreed-upon alternative, I support this.<br>

<dd>&gt;<br><br>

<dd>As do I.<br><br>

<dd>:-(<br><br>

<dd>W<br><br>

<dd>&gt; Melinda<br>

<dd>&gt;<br>

<dd>&gt;<br><br>

</dl></blockquote></body>
<br>
</html>

--=====================_787260184==.ALT--


From turchanyi.geza@gmail.com  Thu Nov  1 10:58:37 2012
Return-Path: <turchanyi.geza@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 671E521F8F8A for <ietf@ietfa.amsl.com>; Thu,  1 Nov 2012 10:58:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.22
X-Spam-Level: 
X-Spam-Status: No, score=-3.22 tagged_above=-999 required=5 tests=[AWL=0.378,  BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 aEfqyrVVq6YN for <ietf@ietfa.amsl.com>; Thu,  1 Nov 2012 10:58:37 -0700 (PDT)
Received: from mail-pa0-f44.google.com (mail-pa0-f44.google.com [209.85.220.44]) by ietfa.amsl.com (Postfix) with ESMTP id AC49B21F8E33 for <ietf@ietf.org>; Thu,  1 Nov 2012 10:58:36 -0700 (PDT)
Received: by mail-pa0-f44.google.com with SMTP id fb11so1897259pad.31 for <ietf@ietf.org>; Thu, 01 Nov 2012 10:58:36 -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 :cc:content-type; bh=WRAETdFnDtioAmzRPls56lYAqVmzwKOx1Kn4MDl8/dk=; b=zNUNrZD4kBT00wq/efdKpT+PipnuQHJlw+ehBAgbR9SlMLG8MRtTUQxHGH2GdpbFKt 6zcsXyDro/8riKNEXZ60STGuwAmxhaJ+2ry5L5qKtckteA6mqC9enJg2rrOwnyZ0CwKj hnQVLtOtQsCtNhHiJJYsBiWF0Z4QF2z8b5k0ZCJMO2IgN0Jw3Ezb79S4eqAY183rkrBs tfuA8qiI2v9IEVsDEXofV/EOy6BMenpf4oLH01wa5p7fY2BaKHRouop9LAUPwHL/Z609 xc1xPIQWP8yOJcU8kFo0cYi4FMb9JF75O9pCS6jYdwxYHjboCIOPERo0PRHXFwNcvxjB YkPg==
MIME-Version: 1.0
Received: by 10.68.132.165 with SMTP id ov5mr122880874pbb.105.1351792716247; Thu, 01 Nov 2012 10:58:36 -0700 (PDT)
Received: by 10.66.19.135 with HTTP; Thu, 1 Nov 2012 10:58:36 -0700 (PDT)
In-Reply-To: <7E81548C-33E5-46D0-B8F6-1F3602E2C34B@NLnetLabs.nl>
References: <20121022234941.28301.7687.idtracker@ietfa.amsl.com> <7E81548C-33E5-46D0-B8F6-1F3602E2C34B@NLnetLabs.nl>
Date: Thu, 1 Nov 2012 18:58:36 +0100
Message-ID: <CAJfR-+Pfo_fZGdetwq34OAuzZ=Jf4fcZ2cqaSn5doGtT2CthmQ@mail.gmail.com>
Subject: Re: IAOC Request for community feedback
From: Turchanyi Geza <turchanyi.geza@gmail.com>
To: Olaf Kolkman <olaf@nlnetlabs.nl>
Content-Type: multipart/alternative; boundary=047d7b15a917a9712f04cd72c4bc
Cc: Olafur Gudmundsson <ogud+shinkuro@ogud.com>, "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Nov 2012 17:58:37 -0000

--047d7b15a917a9712f04cd72c4bc
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Olaf and all,


> First: I cannot help to think there is a personal tragedy behind all this=
.
> I hope Marshall makes it back to this community because I will miss him.
>
> [ deep breath ]
>
>
> Exactly. This is why I hope that some of his best freinds will try to
contact him personally, or at least figure out when it would be possible to
contact him personally.

Should not we help Marshall to come back? Unfortunately, I can not,
however, there are no others?

Best,

G=E9za

--047d7b15a917a9712f04cd72c4bc
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Olaf and all,<br><br><div class=3D"gmail_quote"><blockquote class=3D"gmail_=
quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1=
ex"><div style=3D"word-wrap:break-word"><div class=3D"im"><div><br></div></=
div><div>
First: I cannot help to think there is a personal tragedy behind all this. =
I hope Marshall makes it back to this community because I will miss him.</d=
iv><div><br></div><div>[ deep breath ]</div><div><br></div><br></div></bloc=
kquote>
</div>Exactly. This is why I hope that some of his best freinds will try to=
 contact him personally, or at least figure out when it would be possible t=
o contact him personally.<br><br>Should not we help Marshall to come back? =
Unfortunately, I can not, however, there are no others?<br>
<br>Best,<br><br>G=E9za<br><br><br>

--047d7b15a917a9712f04cd72c4bc--

From dhc@dcrocker.net  Thu Nov  1 11:09:01 2012
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 330F421F8E7B for <ietf@ietfa.amsl.com>; Thu,  1 Nov 2012 11:09:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.8
X-Spam-Level: 
X-Spam-Status: No, score=-4.8 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, RCVD_IN_NJABL_PROXY=1.643, SUBJECT_FUZZY_TION=0.156]
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 DUuwM6HqbMsp for <ietf@ietfa.amsl.com>; Thu,  1 Nov 2012 11:09:00 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 361CC21F8FAE for <ietf@ietf.org>; Thu,  1 Nov 2012 11:09:00 -0700 (PDT)
Received: from [192.168.1.6] (adsl-67-127-56-94.dsl.pltn13.pacbell.net [67.127.56.94]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id qA1I8SNR015823 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 1 Nov 2012 11:08:29 -0700
Message-ID: <5092BA96.9020909@dcrocker.net>
Date: Thu, 01 Nov 2012 11:08:22 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: Michael StJohns <mstjohns@comcast.net>
Subject: Re: [IETF] Re: Recall petition for Mr. Marshall Eubanks
References: <50919671.6000605@ogud.com> <5091CD21.3010504@gmail.com> <1158F458-8810-4CD2-B874-3DE1A1B8B0B5@kumari.net> <CAJfR-+PDvsswi3yU-H5TsK_W8RNeSwNMD2Gcdc2SksKEG1xDYQ@mail.gmail.com> <20121101175249.D92C521F89A0@ietfa.amsl.com>
In-Reply-To: <20121101175249.D92C521F89A0@ietfa.amsl.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Thu, 01 Nov 2012 11:08:29 -0700 (PDT)
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Nov 2012 18:09:01 -0000

On 11/1/2012 10:52 AM, Michael StJohns wrote:
> Per Olafur's email, I submitted my signature directly to him, along with
> my Nomcom eligibility status.  I'm sure other's did as well, so you
> shouldn't take the absence of emails on this list as lack of support for
> the proposal.


(wearing no hat)


As a small point of procedures, no one is sending an actual signature.

It therefore would provide a modicum of better assurance for signatories 
to send the email that declares their signature directly to the ISOC 
President rather than to the person initiating the recall.


d/

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From tglassey@earthlink.net  Thu Nov  1 11:22:04 2012
Return-Path: <tglassey@earthlink.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 55C0A21F920B for <ietf@ietfa.amsl.com>; Thu,  1 Nov 2012 11:22:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.295
X-Spam-Level: 
X-Spam-Status: No, score=-2.295 tagged_above=-999 required=5 tests=[AWL=0.148,  BAYES_00=-2.599, SUBJECT_FUZZY_TION=0.156]
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 VqdNJfOXlu0T for <ietf@ietfa.amsl.com>; Thu,  1 Nov 2012 11:22:04 -0700 (PDT)
Received: from elasmtp-banded.atl.sa.earthlink.net (elasmtp-banded.atl.sa.earthlink.net [209.86.89.70]) by ietfa.amsl.com (Postfix) with ESMTP id E34B121F8FF6 for <ietf@ietf.org>; Thu,  1 Nov 2012 11:22:03 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=KME0rPWXWaaVSb91tQ6k31JUZoplwuxgRCMa2qEWCNGe0IbVlPCtLxLYKEyUUjeP; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [67.180.133.21] (helo=[192.168.15.2]) by elasmtp-banded.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <tglassey@earthlink.net>) id 1TTzP0-00022j-MP for ietf@ietf.org; Thu, 01 Nov 2012 14:22:03 -0400
Message-ID: <5092BDCB.8080701@earthlink.net>
Date: Thu, 01 Nov 2012 11:22:03 -0700
From: tglassey <tglassey@earthlink.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: [IETF] Re: Recall petition for Mr. Marshall Eubanks
References: <50919671.6000605@ogud.com> <5091CD21.3010504@gmail.com> <1158F458-8810-4CD2-B874-3DE1A1B8B0B5@kumari.net> <CAJfR-+PDvsswi3yU-H5TsK_W8RNeSwNMD2Gcdc2SksKEG1xDYQ@mail.gmail.com> <20121101175249.D92C521F89A0@ietfa.amsl.com> <5092BA96.9020909@dcrocker.net>
In-Reply-To: <5092BA96.9020909@dcrocker.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec79b22d984bfd2c1a5760ac46c1f9980eb6350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 67.180.133.21
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Nov 2012 18:22:04 -0000

On 11/1/2012 11:08 AM, Dave Crocker wrote:
>
>
> On 11/1/2012 10:52 AM, Michael StJohns wrote:
>> Per Olafur's email, I submitted my signature directly to him, along with
>> my Nomcom eligibility status.  I'm sure other's did as well, so you
>> shouldn't take the absence of emails on this list as lack of support for
>> the proposal.
>
>
> (wearing no hat)
>
>
> As a small point of procedures, no one is sending an actual signature.
But eSign works if we agree it does.
>
> It therefore would provide a modicum of better assurance for 
> signatories to send the email that declares their signature directly 
> to the ISOC President rather than to the person initiating the recall.
At which point the framework has a bump - would you send all notices or 
votes for a finding of consensus to the IESG? It is after all the same 
model right?  If so then no one votes on the consensus within the WG 
anymore it would seem and this also would need to be done before the 
IESG in some form as well...

todd
>
>
> d/
>


-- 
Regards TSG
"Ex-Cruce-Leo"

//Confidential Mailing - Please destroy this if you are not the intended recipient.


From ogud@ogud.com  Thu Nov  1 11:39:05 2012
Return-Path: <ogud@ogud.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B5B1521F9320 for <ietf@ietfa.amsl.com>; Thu,  1 Nov 2012 11:39:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.143
X-Spam-Level: 
X-Spam-Status: No, score=-104.143 tagged_above=-999 required=5 tests=[AWL=-0.700, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, SUBJECT_FUZZY_TION=0.156, 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 YPw7j915kLOR for <ietf@ietfa.amsl.com>; Thu,  1 Nov 2012 11:39:05 -0700 (PDT)
Received: from smtp187.iad.emailsrvr.com (smtp187.iad.emailsrvr.com [207.97.245.187]) by ietfa.amsl.com (Postfix) with ESMTP id 3F91A21F9325 for <ietf@ietf.org>; Thu,  1 Nov 2012 11:39:05 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp48.relay.iad1a.emailsrvr.com (SMTP Server) with ESMTP id 7997D16A44E; Thu,  1 Nov 2012 14:39:04 -0400 (EDT)
X-Virus-Scanned: OK
Received: by smtp48.relay.iad1a.emailsrvr.com (Authenticated sender: ogud-AT-ogud.com) with ESMTPSA id 4E70A16A2A5;  Thu,  1 Nov 2012 14:39:04 -0400 (EDT)
Message-ID: <5092C1C5.4090006@ogud.com>
Date: Thu, 01 Nov 2012 14:39:01 -0400
From: Olafur Gudmundsson <ogud@ogud.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: [IETF] Re: Recall petition for Mr. Marshall Eubanks
References: <50919671.6000605@ogud.com> <5091CD21.3010504@gmail.com> <1158F458-8810-4CD2-B874-3DE1A1B8B0B5@kumari.net> <CAJfR-+PDvsswi3yU-H5TsK_W8RNeSwNMD2Gcdc2SksKEG1xDYQ@mail.gmail.com> <20121101175249.D92C521F89A0@ietfa.amsl.com> <5092BA96.9020909@dcrocker.net>
In-Reply-To: <5092BA96.9020909@dcrocker.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ogud@ogud.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Nov 2012 18:39:05 -0000

On 01/11/2012 14:08, Dave Crocker wrote:
>
>
> On 11/1/2012 10:52 AM, Michael StJohns wrote:
>> Per Olafur's email, I submitted my signature directly to him, along with
>> my Nomcom eligibility status.  I'm sure other's did as well, so you
>> shouldn't take the absence of emails on this list as lack of support for
>> the proposal.
>
>
> (wearing no hat)
>
>
> As a small point of procedures, no one is sending an actual signature.
>
> It therefore would provide a modicum of better assurance for 
> signatories to send the email that declares their signature directly 
> to the ISOC President rather than to the person initiating the recall.
>
>
> d/
>

Dave,

As this never been attempted before, by collecting the "signatures" 
myself, checking the NomCom eligibility and diversity in organizations 
as required by RFC3777, I hoped to reduce the work that Lynn had to do.
In the case the petition fails to get enough "signers" ISOC's work is no-op.

I will be happy when/if recall petition is submitted to include all the 
emails that I have got as "proof" that I did not
stuff the box, and publish the names of "signers",  and the integrity of 
the process can be challenged at that time.

     Olafur



From fred@cisco.com  Thu Nov  1 11:43:38 2012
Return-Path: <fred@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5842D21F8F72 for <ietf@ietfa.amsl.com>; Thu,  1 Nov 2012 11:43:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.52
X-Spam-Level: 
X-Spam-Status: No, score=-110.52 tagged_above=-999 required=5 tests=[AWL=-0.079, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, SUBJECT_FUZZY_TION=0.156, 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 kH7ujPne5YWk for <ietf@ietfa.amsl.com>; Thu,  1 Nov 2012 11:43:37 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by ietfa.amsl.com (Postfix) with ESMTP id 25B6B21F8EED for <ietf@ietf.org>; Thu,  1 Nov 2012 11:43:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2026; q=dns/txt; s=iport; t=1351795417; x=1353005017; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=v6+DmIUxA7camFKZV5xovSJNvFT9OZW2XqVerdBd/K8=; b=QB+RAYb7W7yuQeEHlK+eTV/F36cha8TQSyedb9BPtisoalpxRdvOQGgV ya948uworkVBrtvM68oHrucIPFJJY1XECtroKNJMFy7abP5cdW6PAA4I4 LXp0OT2CaM6Pp/EsOeoPAcEZfW+4yMlC7YoemvTgBfv0UOWeYAkoUBLdH 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EADnCklCtJV2a/2dsb2JhbABEw3SBCIIfAQEEEgFmEAIBCAQBHSQyJQIEAQ0NGodknFugLot7hVphA4glnCuBa4Jvghk
X-IronPort-AV: E=Sophos;i="4.80,695,1344211200";  d="scan'208,217";a="137862187"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-6.cisco.com with ESMTP; 01 Nov 2012 18:43:36 +0000
Received: from xhc-rcd-x13.cisco.com (xhc-rcd-x13.cisco.com [173.37.183.87]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id qA1IhaHf007798 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 1 Nov 2012 18:43:36 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.68]) by xhc-rcd-x13.cisco.com ([173.37.183.87]) with mapi id 14.02.0318.001; Thu, 1 Nov 2012 13:43:36 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>, Olafur Gudmundsson <ogud@ogud.com>
Subject: Re: Recall petition for Mr. Marshall Eubanks
Thread-Topic: Recall petition for Mr. Marshall Eubanks
Thread-Index: AQHNt63Vm0+lEVissk+4U43/3zMn0pfVgWaAgAAkpoA=
Date: Thu, 1 Nov 2012 18:43:35 +0000
Message-ID: <8C48B86A895913448548E6D15DA7553B190F1A@xmb-rcd-x09.cisco.com>
References: <50919671.6000605@ogud.com> <7F4FE714-DEDC-4D64-ADD8-AA6ECF53EABB@NLnetLabs.nl>
In-Reply-To: <7F4FE714-DEDC-4D64-ADD8-AA6ECF53EABB@NLnetLabs.nl>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.19.64.115]
x-tm-as-product-ver: SMEX-10.2.0.1135-7.000.1014-19328.001
x-tm-as-result: No--24.590500-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: multipart/alternative; boundary="_000_8C48B86A895913448548E6D15DA7553B190F1Axmbrcdx09ciscocom_"
MIME-Version: 1.0
Cc: IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Nov 2012 18:43:38 -0000

--_000_8C48B86A895913448548E6D15DA7553B190F1Axmbrcdx09ciscocom_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


On Nov 1, 2012, at 9:32 AM, Olaf Kolkman wrote:

I also offer my signature under the recall procedure, in case pragmatism do=
esn't prevail (see my other note).

My offer of signature should in no way be interpreted as reflecting an opin=
ion about Marshall's character.

Ditto, and Ditto.

--_000_8C48B86A895913448548E6D15DA7553B190F1Axmbrcdx09ciscocom_
Content-Type: text/html; charset="iso-8859-1"
Content-ID: <A374FB6A007F4C48AD848E852149A36B@cisco.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; ">
<br>
<div>
<div>On Nov 1, 2012, at 9:32 AM, Olaf Kolkman wrote:</div>
<br class=3D"Apple-interchange-newline">
<blockquote type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-=
collapse: separate; font-family: Helvetica; font-style: normal; font-varian=
t: normal; font-weight: normal; letter-spacing: normal; line-height: normal=
; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: n=
one; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-hori=
zontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-dec=
orations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stro=
ke-width: 0px; font-size: medium; ">
<div>
<div>I also offer my signature under the recall procedure, in case pragmati=
sm doesn't prevail (see my other note).</div>
</div>
<div><br>
</div>
<div>My offer of signature should in no way be interpreted as reflecting an=
 opinion about Marshall's character.</div>
</span></blockquote>
</div>
<br>
Ditto, and Ditto.&nbsp;
</body>
</html>

--_000_8C48B86A895913448548E6D15DA7553B190F1Axmbrcdx09ciscocom_--

From jaap@NLnetLabs.nl  Thu Nov  1 11:50:38 2012
Return-Path: <jaap@NLnetLabs.nl>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F5F321F92E4 for <ietf@ietfa.amsl.com>; Thu,  1 Nov 2012 11:50:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.443
X-Spam-Level: 
X-Spam-Status: No, score=-2.443 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SUBJECT_FUZZY_TION=0.156]
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 7Pf8Im10URR4 for <ietf@ietfa.amsl.com>; Thu,  1 Nov 2012 11:50:38 -0700 (PDT)
Received: from bela.nlnetlabs.nl (bela.nlnetlabs.nl [IPv6:2001:7b8:206:1:222:4dff:fe55:4ccb]) by ietfa.amsl.com (Postfix) with ESMTP id A930821F92DD for <ietf@ietf.org>; Thu,  1 Nov 2012 11:50:37 -0700 (PDT)
Received: from NLnetLabs.nl (localhost [127.0.0.1]) by bela.nlnetlabs.nl (8.14.5/8.14.5) with ESMTP id qA1IoWfN092224; Thu, 1 Nov 2012 19:50:33 +0100 (CET) (envelope-from jaap@NLnetLabs.nl)
Message-Id: <201211011850.qA1IoWfN092224@bela.nlnetlabs.nl>
To: Olafur Gudmundsson <ogud@ogud.com>, IETF-Discussion list <ietf@ietf.org>
Subject: Re: Recall petition for Mr. Marshall Eubanks
In-reply-to: <8C48B86A895913448548E6D15DA7553B190F1A@xmb-rcd-x09.cisco.com>
References: <50919671.6000605@ogud.com> <7F4FE714-DEDC-4D64-ADD8-AA6ECF53EABB@NLnetLabs.nl> <8C48B86A895913448548E6D15DA7553B190F1A@xmb-rcd-x09.cisco.com>
Comments: In-reply-to "Fred Baker (fred)" <fred@cisco.com> message dated "Thu, 01 Nov 2012 18:43:35 +0000."
Date: Thu, 01 Nov 2012 19:50:32 +0100
From: Jaap Akkerhuis <jaap@NLnetLabs.nl>
X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.7 (bela.nlnetlabs.nl [127.0.0.1]); Thu, 01 Nov 2012 19:50:35 +0100 (CET)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Nov 2012 18:50:38 -0000

    
    
    On Nov 1, 2012, at 9:32 AM, Olaf Kolkman wrote:

    I also offer my signature under the recall procedure, in case
    pragmatism doesn't prevail (see my other note).

    My offer of signature should in no way be interpreted as
    reflecting an opinion about Marshall's character.

The same offer from me.

	jaap

From jmpolk@cisco.com  Thu Nov  1 12:56:26 2012
Return-Path: <jmpolk@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB6E121F9580 for <ietf@ietfa.amsl.com>; Thu,  1 Nov 2012 12:56:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.521
X-Spam-Level: 
X-Spam-Status: No, score=-110.521 tagged_above=-999 required=5 tests=[AWL=-0.078, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, SUBJECT_FUZZY_TION=0.156, 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 xGd6mq9iPXpT for <ietf@ietfa.amsl.com>; Thu,  1 Nov 2012 12:56:26 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id 19A6B21F9537 for <ietf@ietf.org>; Thu,  1 Nov 2012 12:56:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=436; q=dns/txt; s=iport; t=1351799786; x=1353009386; h=message-id:date:to:from:subject:cc:in-reply-to: references:mime-version; bh=Fwu9sA+eLiwphR5yYqh0uMnQTFDzF4Z2hKrUwmZfm2o=; b=CZpmgN2KhwX3QNBN9HG8jFd+5cbFn0AOC2NWapyyBJQUKCcIHRv6xk/k RM/YLljC95okOo+YcR4Ptulq98qiClmgP2ZTWzaBQ+Ui6dlhoXLQtf2F/ 47Uo3Q8qXRVVJ7VadSmIXKXZMS2DzmU8fYFw4gZSZuSHK7ZX4oK3ytc4n w=;
X-IronPort-AV: E=Sophos;i="4.80,695,1344211200"; d="scan'208";a="137889479"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-5.cisco.com with ESMTP; 01 Nov 2012 19:56:26 +0000
Received: from jmpolk-WS.cisco.com (rcdn-jmpolk-8715.cisco.com [10.99.80.22]) (authenticated bits=0) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id qA1JuP3E001365 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 1 Nov 2012 19:56:25 GMT
Message-Id: <201211011956.qA1JuP3E001365@rcdn-core-1.cisco.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Thu, 01 Nov 2012 14:56:24 -0500
To: "Fred Baker (fred)" <fred@cisco.com>, "Olaf M. Kolkman" <olaf@NLnetLabs.nl>, Olafur Gudmundsson <ogud@ogud.com>
From: James Polk <jmpolk@cisco.com>
Subject: Re: Recall petition for Mr. Marshall Eubanks
In-Reply-To: <8C48B86A895913448548E6D15DA7553B190F1A@xmb-rcd-x09.cisco.c om>
References: <50919671.6000605@ogud.com> <7F4FE714-DEDC-4D64-ADD8-AA6ECF53EABB@NLnetLabs.nl> <8C48B86A895913448548E6D15DA7553B190F1A@xmb-rcd-x09.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Authenticated-User: jmpolk
Cc: IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Nov 2012 19:56:26 -0000

At 01:43 PM 11/1/2012, Fred Baker (fred) wrote:

>On Nov 1, 2012, at 9:32 AM, Olaf Kolkman wrote:
>
>>I also offer my signature under the recall procedure, in case 
>>pragmatism doesn't prevail (see my other note).
>>
>>My offer of signature should in no way be interpreted as reflecting 
>>an opinion about Marshall's character.

exactly how I feel, and I am Nomcom eligible (37 out of 39).

James


>Ditto, and Ditto.


From lear@cisco.com  Thu Nov  1 13:21:50 2012
Return-Path: <lear@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 17F0C21F96F8 for <ietf@ietfa.amsl.com>; Thu,  1 Nov 2012 13:21:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.521
X-Spam-Level: 
X-Spam-Status: No, score=-110.521 tagged_above=-999 required=5 tests=[AWL=-0.078, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, SUBJECT_FUZZY_TION=0.156, 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 NLCQpSXHsucu for <ietf@ietfa.amsl.com>; Thu,  1 Nov 2012 13:21:49 -0700 (PDT)
Received: from ams-iport-3.cisco.com (ams-iport-3.cisco.com [144.254.224.146]) by ietfa.amsl.com (Postfix) with ESMTP id 4BBF621F96F7 for <ietf@ietf.org>; Thu,  1 Nov 2012 13:21:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=288; q=dns/txt; s=iport; t=1351801309; x=1353010909; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=Bw7u609Si0jnpmWY5eMdcD2uillekjPP3ErQWYMb9Dc=; b=ebSVIiCECvi7xuz7tPDiDdiZ6N6qZr5cXQxPNpY6IePqkdoQg+O6JmIp mYeDcW97igkh3OD/wlfZXmMLDdiG0QX9UfiT+rNDShHZi4SZkICWqG9n8 /mfnTj90HCZpR+Y7VKguT/x/s2WltLl0o81yCj/dhCMQtOps65CarAnnt U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAFAHbYklCQ/khR/2dsb2JhbABEhhe9WIEIgh4BAQEEEgEQVQEQCxgCAgUWCwICCQMCAQIBRQYNAQcBAR6HZJxjjSmTBYEgkAOBEwOVeI5YgWuCcA
X-IronPort-AV: E=Sophos;i="4.80,695,1344211200";  d="scan'208";a="9275218"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by ams-iport-3.cisco.com with ESMTP; 01 Nov 2012 20:21:48 +0000
Received: from dhcp-10-55-86-143.cisco.com (dhcp-10-55-86-143.cisco.com [10.55.86.143]) by ams-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id qA1KLl4q026493 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 1 Nov 2012 20:21:48 GMT
Message-ID: <5092D9DB.4070602@cisco.com>
Date: Thu, 01 Nov 2012 21:21:47 +0100
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: Olaf Kolkman <olaf@NLnetLabs.nl>
Subject: Re: Recall petition for Mr. Marshall Eubanks
References: <50919671.6000605@ogud.com> <7F4FE714-DEDC-4D64-ADD8-AA6ECF53EABB@NLnetLabs.nl>
In-Reply-To: <7F4FE714-DEDC-4D64-ADD8-AA6ECF53EABB@NLnetLabs.nl>
X-Enigmail-Version: 1.4.5
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: 'IETF-Discussion list' <ietf@ietf.org>, Olafur Gudmundsson <ogud@ogud.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Nov 2012 20:21:50 -0000

+1.


On 11/1/12 5:32 PM, Olaf Kolkman wrote:
> I also offer my signature under the recall procedure, in case
> pragmatism doesn't prevail (see my other note).
>
> My offer of signature should in no way be interpreted as reflecting an
> opinion about Marshall's character.
>
>


From bob.hinden@gmail.com  Thu Nov  1 13:47:30 2012
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EA59821F9676 for <ietf@ietfa.amsl.com>; Thu,  1 Nov 2012 13:47:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.688
X-Spam-Level: 
X-Spam-Status: No, score=-103.688 tagged_above=-999 required=5 tests=[AWL=-0.089, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, 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 r1V8p9X+aUCf for <ietf@ietfa.amsl.com>; Thu,  1 Nov 2012 13:47:27 -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 C333121F9705 for <ietf@ietf.org>; Thu,  1 Nov 2012 13:47:27 -0700 (PDT)
Received: by mail-pb0-f44.google.com with SMTP id ro8so1987916pbb.31 for <ietf@ietf.org>; Thu, 01 Nov 2012 13:47:27 -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 :content-transfer-encoding:message-id:references:to:x-mailer; bh=dPsqSg4Kpl4YlgRToBHNvv4hLOR4AOZVP3MB+Z+KPng=; b=LzTY/fBs4jLNEbmezpEpEg7BLjyfeQ0xXZdkD30xvoTA62PP/7Iblz0VwYGEwA17Q6 2IdrAIP6JHLOjrl9PCrjC2KNIbMahGyHxhyNg9StOaB7NN8R1OdL6ypEqPbol8xlFasK GCB/yQ2HDsY1jD3mj/wt6b7fdPWcjTyDsVvlecMroUHyXQ+Q+I+QA/GpKgd1ikbovB7n 1pAOZZTbMa8qjXmjOTYWKJh0hwEKUQFNfTc5uAF5/ONO7GNMlJYKM97zb/Pg8Kjz6k2i 8GQh5czACYSS9sNxL8NqCecDxwHy3a3k91nfZ/GISvaVH31pzYzQ/QCjd7A858ODF2T9 xrcw==
Received: by 10.66.86.165 with SMTP id q5mr114135123paz.18.1351802847558; Thu, 01 Nov 2012 13:47:27 -0700 (PDT)
Received: from [172.16.224.219] ([209.97.127.34]) by mx.google.com with ESMTPS id pw2sm4525330pbb.59.2012.11.01.13.47.18 (version=SSLv3 cipher=OTHER); Thu, 01 Nov 2012 13:47:25 -0700 (PDT)
Subject: Re: IAOC Request for community feedback
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=us-ascii
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <201211011638.qA1GcEXI155593@shell01.TheWorld.com>
Date: Thu, 1 Nov 2012 13:47:17 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <31277F87-2C61-4598-AF05-730E4BDE59D2@gmail.com>
References: <201211011638.qA1GcEXI155593@shell01.TheWorld.com>
To: worley@ariadne.com (Dale R. Worley)
X-Mailer: Apple Mail (2.1283)
Cc: Bob Hinden <bob.hinden@gmail.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Nov 2012 20:47:31 -0000

Dale,

On Nov 1, 2012, at 9:38 AM, Dale R. Worley wrote:

> There seems to me to be a "constitutional" issue that has not been
> addressed, and may well bedevil us in the future:  In any collective
> body, there is a concept of a quorum, which is set high enough to
> ensure that the actions of any meeting represent the opinions of the
> body as a whole, and which is set low enough that the expected level
> of absences will not prevent business from being done.
>=20
> The current crisis is (apparently) due to the chronic absence of *one*
> member causing *chronic* failures of the IAOC to achieve a quorum.
> This suggests to me that the quorum of the IAOC is too high to allow
> it to reliably conduct business -- after all, any of a thousand
> accidents can cause one member to be absent for a long period of time.
>=20
> What are the quorum rules of the IAOC?  Should they be revised?

The rules for a quorum are defined in the IAOC administrative =
procedures.  They can be found in Section 3 at:

  http://iaoc.ietf.org/docs/IAOC-Administrative-Procedures-9-16-2010.pdf

The issue with a quorum is not if a single member can not attend a =
meeting, it is what happens if there are also a few members who for =
reasons like travel can not attend.  This has happened once since the =
last IETF meeting.  Having one person missing over a long period of time =
makes it harder to obtain a quorum, it doesn't make it impossible.  It =
would be a bigger problem if another member could not make a number of =
meetings (for whatever reason).

There are a number of other reasons why a missing member is a problem.  =
They may have specific responsibilities they are not performing (in this =
case, IAOC liaison to the NomCom and IETF Trust chair), membership on =
subcommittees, and, of course, one less voice in discussions in the IAOC =
and IETF trust.  Having fewer people increases the work load on everyone =
else and creates less diversity in views and expertise.

Bob Hinden
IAOC Chair





>=20
> Dale


From bob.hinden@gmail.com  Thu Nov  1 13:59:12 2012
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC03821F967D for <ietf@ietfa.amsl.com>; Thu,  1 Nov 2012 13:59:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.668
X-Spam-Level: 
X-Spam-Status: No, score=-103.668 tagged_above=-999 required=5 tests=[AWL=-0.069, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, 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 kZLPZkPSffbU for <ietf@ietfa.amsl.com>; Thu,  1 Nov 2012 13:59:12 -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 3DB3521F9632 for <ietf@ietf.org>; Thu,  1 Nov 2012 13:59:12 -0700 (PDT)
Received: by mail-pb0-f44.google.com with SMTP id ro8so1993098pbb.31 for <ietf@ietf.org>; Thu, 01 Nov 2012 13:59:11 -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 :content-transfer-encoding:message-id:references:to:x-mailer; bh=iWPgXjn8hhKsVxhyE0wLWkvJ+8Z9o6HiZOMWWNzzEZo=; b=B+oPs3e0X0npTLu8nd/k0Hn34/A7go1X0c8CYHFFz49OrMBaJQ/67IXKEq8a5zBAR7 XEffoJPmoCxkW9+vViR8gToOtJ10++rwI95PPYLSccg1jgIwbBMl4WulJ8iMDoe6OjtW lCxa+8XnmZ0ecI68X6yXHgQj4ZuFFH6e8B+mqHF8qSpiHs0+c2dxOIK4hPCYPGWw6s6+ FTAUSZQpU0Mnp6G1upVLPLIf3vA6YpDjO1U2c94UompCC0uqgeb3hjSercm6GxnMan/O sdDawfw9gTgmlfi0IHQ255npIKGygPE2FORNeUpSWPhhh6xgdCBk++W1H2/pnfZ/Y2X6 0oYw==
Received: by 10.68.189.102 with SMTP id gh6mr125589122pbc.37.1351803551911; Thu, 01 Nov 2012 13:59:11 -0700 (PDT)
Received: from [172.16.224.219] ([209.97.127.34]) by mx.google.com with ESMTPS id ay5sm4496200pab.1.2012.11.01.13.59.00 (version=SSLv3 cipher=OTHER); Thu, 01 Nov 2012 13:59:08 -0700 (PDT)
Subject: Re: IAOC Request for community feedback
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=iso-8859-1
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <CAJfR-+Pfo_fZGdetwq34OAuzZ=Jf4fcZ2cqaSn5doGtT2CthmQ@mail.gmail.com>
Date: Thu, 1 Nov 2012 13:58:59 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <10540DCC-E334-444D-BEB6-8ECD2FD7A32A@gmail.com>
References: <20121022234941.28301.7687.idtracker@ietfa.amsl.com> <7E81548C-33E5-46D0-B8F6-1F3602E2C34B@NLnetLabs.nl> <CAJfR-+Pfo_fZGdetwq34OAuzZ=Jf4fcZ2cqaSn5doGtT2CthmQ@mail.gmail.com>
To: Turchanyi Geza <turchanyi.geza@gmail.com>
X-Mailer: Apple Mail (2.1283)
Cc: Olafur Gudmundsson <ogud+shinkuro@ogud.com>, Bob Hinden <bob.hinden@gmail.com>, "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Nov 2012 20:59:12 -0000

G=E9za,

On Nov 1, 2012, at 10:58 AM, Turchanyi Geza wrote:

> Olaf and all,
>=20
>=20
> First: I cannot help to think there is a personal tragedy behind all =
this. I hope Marshall makes it back to this community because I will =
miss him.
>=20

Same here.

>=20
>=20
> Exactly. This is why I hope that some of his best freinds will try to =
contact him personally, or at least figure out when it would be possible =
to contact him personally.
>=20
> Should not we help Marshall to come back? Unfortunately, I can not, =
however, there are no others?


Russ Housley and Ray Pelletier were able to visit Marshall at his home =
last Friday.  They discussed the situation with Marshall including =
describing the discussion on the IETF list.  He confirmed he had not =
been reading his email since early August and said he would consider =
resigning. =20

We have not received any communication from him since then.

Bob



From dougb@dougbarton.us  Thu Nov  1 14:26:14 2012
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A54721F94D3 for <ietf@ietfa.amsl.com>; Thu,  1 Nov 2012 14:26:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.3
X-Spam-Level: 
X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 tests=[AWL=1.300, 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 fpcygMXFV0jN for <ietf@ietfa.amsl.com>; Thu,  1 Nov 2012 14:26:13 -0700 (PDT)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id 6B04221F9410 for <ietf@ietf.org>; Thu,  1 Nov 2012 14:26:13 -0700 (PDT)
Received: (qmail 26860 invoked by uid 399); 1 Nov 2012 21:25:58 -0000
Received: from unknown (HELO ?192.168.0.102?) (dougb@dougbarton.us@12.207.105.210) by mail2.fluidhosting.com with ESMTPAM; 1 Nov 2012 21:25:58 -0000
X-Originating-IP: 12.207.105.210
X-Sender: dougb@dougbarton.us
Message-ID: <5092E8F1.9060104@dougbarton.us>
Date: Thu, 01 Nov 2012 14:26:09 -0700
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1
MIME-Version: 1.0
To: Bob Hinden <bob.hinden@gmail.com>
Subject: Re: IAOC Request for community feedback
References: <20121022234941.28301.7687.idtracker@ietfa.amsl.com> <7E81548C-33E5-46D0-B8F6-1F3602E2C34B@NLnetLabs.nl> <CAJfR-+Pfo_fZGdetwq34OAuzZ=Jf4fcZ2cqaSn5doGtT2CthmQ@mail.gmail.com> <10540DCC-E334-444D-BEB6-8ECD2FD7A32A@gmail.com>
In-Reply-To: <10540DCC-E334-444D-BEB6-8ECD2FD7A32A@gmail.com>
X-Enigmail-Version: 1.4.4
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Nov 2012 21:26:14 -0000

On 11/01/2012 01:58 PM, Bob Hinden wrote:
> Russ Housley and Ray Pelletier were able to visit Marshall at his home last Friday.  They discussed the situation with Marshall including describing the discussion on the IETF list.  He confirmed he had not been reading his email since early August and said he would consider resigning.  
> 
> We have not received any communication from him since then.

Bob,

Thanks for providing this additional information. It's good to know that
Marshall is aware of the situation, alive and hopefully well, albeit
overburdened. With any kind of luck he will resign, and make the recall
moot. However given the continued lack of communication starting the
recall process now is a reasonable and appropriate step.

Regards,

Doug

From hartmans@mit.edu  Thu Nov  1 14:45:14 2012
Return-Path: <hartmans@mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3861121F92B0 for <ietf@ietfa.amsl.com>; Thu,  1 Nov 2012 14:45:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.443
X-Spam-Level: 
X-Spam-Status: No, score=-102.443 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SUBJECT_FUZZY_TION=0.156, 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 2te2rsxa+Myl for <ietf@ietfa.amsl.com>; Thu,  1 Nov 2012 14:45:13 -0700 (PDT)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id B929121F921F for <ietf@ietf.org>; Thu,  1 Nov 2012 14:45:13 -0700 (PDT)
Received: from carter-zimmerman.suchdamage.org (c-98-217-126-210.hsd1.ma.comcast.net [98.217.126.210]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.painless-security.com (Postfix) with ESMTPS id 0AC96201C1; Thu,  1 Nov 2012 17:44:29 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 1C20B412A; Thu,  1 Nov 2012 17:45:11 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Eliot Lear <lear@cisco.com>
Subject: Re: Recall petition for Mr. Marshall Eubanks
References: <50919671.6000605@ogud.com> <7F4FE714-DEDC-4D64-ADD8-AA6ECF53EABB@NLnetLabs.nl> <5092D9DB.4070602@cisco.com>
Date: Thu, 01 Nov 2012 17:45:11 -0400
In-Reply-To: <5092D9DB.4070602@cisco.com> (Eliot Lear's message of "Thu, 01 Nov 2012 21:21:47 +0100")
Message-ID: <tsltxt980bc.fsf@mit.edu>
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
Cc: 'IETF-Discussion list' <ietf@ietf.org>, Olafur Gudmundsson <ogud@ogud.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Nov 2012 21:45:14 -0000

I offer my signature to the recall petition. I am nomcom eligible.

At this point, I believe the recall process is the correct process to
follow unless there is an approved BCP update.
In a case where there's been no contact and there's an argument we've
found a gap in the procedures I can see the argument for creativity.
However, according to Bob's note, Marshall has been contacted and rather
than resigning, said he would consider resigning.
I hope he does.
Until he does, though, by considering resigning rather than resigning,
he has implied that there might be a reason not to resign.
In my mind that moves us out of a situation where creative
interpretations of vacancy are appropriate.
I think we're now in a position where there's a legitimate disagreement
between Marshall and some members of the community about whether
Marshall ought to be in his position.
I believe the recall process is the only existing tool we have for
resolving such a disagreement; I think permitting the IAOC to invent a
process for resolving such a disagreement without an approved BCP is
entirely inappropriate.

Again, I hope this can all be side stepped by a resignation.

From bob.hinden@gmail.com  Thu Nov  1 15:01:36 2012
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6BBC521F97BF for <ietf@ietfa.amsl.com>; Thu,  1 Nov 2012 15:01:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.573
X-Spam-Level: 
X-Spam-Status: No, score=-103.573 tagged_above=-999 required=5 tests=[AWL=-0.130, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, SUBJECT_FUZZY_TION=0.156, 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 2vSsDOmEcf8b for <ietf@ietfa.amsl.com>; Thu,  1 Nov 2012 15:01:35 -0700 (PDT)
Received: from mail-da0-f44.google.com (mail-da0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id DEEC921F97BC for <ietf@ietf.org>; Thu,  1 Nov 2012 15:01:35 -0700 (PDT)
Received: by mail-da0-f44.google.com with SMTP id h15so1355612dan.31 for <ietf@ietf.org>; Thu, 01 Nov 2012 15:01:35 -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 :content-transfer-encoding:message-id:references:to:x-mailer; bh=eeEwxg347ngJ1XC1qbsLtxqI7dLQPGkL1+cVx3hnLNM=; b=mQeoq11Xezw2+4mF39f65LgoqOF5cm7rkcSNxi911ti7e1lqbPGCZS5Rrkn9x02lRb +2YOx3djR6RjWn4ko6b6zSC2IL17FX3nIQCBD4iBZd+FUzhr0eh6H2Fsj3cwV1LHGLjO +s8HAw1R2cB7bwQoCfhdt6Jnt0vGnxLvG4PJL/IBBhL76orqtYFsLGs5IjPqYJMR1LI3 pZdM7SGnSH/SkWVg1F87MJZjHyXD9Ibmpw4tIhEPywc6ZAKU6RkZnpUyf6OvthE8+C+b KrX7gNpI3puNaB1UedFMzvH6R2RH9PTybIGoi5pSy/1DE2Nus9einnigRAsJlja1sshi QeVQ==
Received: by 10.68.225.68 with SMTP id ri4mr124870855pbc.115.1351807295699; Thu, 01 Nov 2012 15:01:35 -0700 (PDT)
Received: from [172.16.224.219] ([209.97.127.34]) by mx.google.com with ESMTPS id hs1sm4612089pbc.33.2012.11.01.15.01.33 (version=SSLv3 cipher=OTHER); Thu, 01 Nov 2012 15:01:34 -0700 (PDT)
Subject: Re: Recall petition for Mr. Marshall Eubanks
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=us-ascii
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <tsltxt980bc.fsf@mit.edu>
Date: Thu, 1 Nov 2012 15:01:32 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <3153B2FE-4B52-43AF-AD10-6701CFFE0AB8@gmail.com>
References: <50919671.6000605@ogud.com> <7F4FE714-DEDC-4D64-ADD8-AA6ECF53EABB@NLnetLabs.nl> <5092D9DB.4070602@cisco.com> <tsltxt980bc.fsf@mit.edu>
To: Sam Hartman <hartmans-ietf@mit.edu>
X-Mailer: Apple Mail (2.1283)
Cc: Olafur Gudmundsson <ogud@ogud.com>, Bob Hinden <bob.hinden@gmail.com>, 'IETF-Discussion list' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Nov 2012 22:01:36 -0000

Sam,

On Nov 1, 2012, at 2:45 PM, Sam Hartman wrote:

> I offer my signature to the recall petition. I am nomcom eligible.
>=20
> At this point, I believe the recall process is the correct process to
> follow unless there is an approved BCP update.
> In a case where there's been no contact and there's an argument we've
> found a gap in the procedures I can see the argument for creativity.
> However, according to Bob's note, Marshall has been contacted and =
rather
> than resigning, said he would consider resigning.
> I hope he does.
> Until he does, though, by considering resigning rather than resigning,
> he has implied that there might be a reason not to resign.
> In my mind that moves us out of a situation where creative
> interpretations of vacancy are appropriate.
> I think we're now in a position where there's a legitimate =
disagreement
> between Marshall and some members of the community about whether
> Marshall ought to be in his position.
> I believe the recall process is the only existing tool we have for
> resolving such a disagreement; I think permitting the IAOC to invent a
> process for resolving such a disagreement without an approved BCP is
> entirely inappropriate.
>=20
> Again, I hope this can all be side stepped by a resignation.


While the IAOC has not discussed this formally, I agree with you.  The =
situation did change when we were able to talk with Marshall.

I too hope he will resign.

Bob



From housley@vigilsec.com  Thu Nov  1 15:31:50 2012
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D982D21F96B2 for <ietf@ietfa.amsl.com>; Thu,  1 Nov 2012 15:31:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.585
X-Spam-Level: 
X-Spam-Status: No, score=-102.585 tagged_above=-999 required=5 tests=[AWL=0.014, 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 WzNrhvHniuya for <ietf@ietfa.amsl.com>; Thu,  1 Nov 2012 15:31:50 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id E5EAF21F968D for <ietf@ietf.org>; Thu,  1 Nov 2012 15:31:49 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 6BD0E9A400A; Thu,  1 Nov 2012 18:31:56 -0400 (EDT)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id s0eYlxIgRQ3X; Thu,  1 Nov 2012 18:31:41 -0400 (EDT)
Received: from [192.168.2.100] (pool-96-255-37-162.washdc.fios.verizon.net [96.255.37.162]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 3D22A9A4002; Thu,  1 Nov 2012 18:31:55 -0400 (EDT)
Subject: Re: Antitrust FAQ
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <B68EFB284B10C249835C566A0CE08AA2370EFDCD@TK5EX14MBXC263.redmond.corp.microsoft.com>
Date: Thu, 1 Nov 2012 18:31:47 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <468C102D-7640-4447-9E10-B6ED70381274@vigilsec.com>
References: <AFB9BEA6-579B-4E26-A512-BE271D234F85@ietf.org> <B68EFB284B10C249835C566A0CE08AA2370EFDCD@TK5EX14MBXC263.redmond.corp.microsoft.com>
To: David Rudin (LCA) <David.Rudin@microsoft.com>
X-Mailer: Apple Mail (2.1085)
Cc: IETF <ietf@ietf.org>, Jorge Contreras <contreraslegal@att.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Nov 2012 22:31:51 -0000

A formal policy requires IETF consensus, and it would be published as a =
BCP in the RFC series.

Russ


On Nov 1, 2012, at 5:23 PM, David Rudin (LCA) wrote:

> At a high level, I'm curious what the difference is between an FAQ and =
a formal policy?  I ask since Section 6 of the FAQ seems to be providing =
instructions on how IETF participants should conduct themselves, which =
seems more like a policy than an FAQ.
>=20
> Thanks,
>=20
> David
>=20
> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf =
Of IETF Chair
> Sent: Wednesday, October 10, 2012 8:41 PM
> To: IETF
> Cc: Jorge Contreras
> Subject: Antitrust FAQ
>=20
> The IETF does not have a formal antitrust policy.  In fact, the =
ANTITRUST BOF concluded that a formal policy was not needed.  However, =
educational material is needed so that all IETF participants are aware =
of the the law.  The first draft of a FAQ to fill this need has been =
developed.  Please review the FAQ, and if you discover any issues raise =
them in response to this message.
>=20
> http://www.ietf.org/playground/antitrust-faq.html
>=20
> Thanks,
>  Russ
>=20


From johnl@taugh.com  Thu Nov  1 15:57:08 2012
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B3F7E21F97C2 for <ietf@ietfa.amsl.com>; Thu,  1 Nov 2012 15:57:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.872
X-Spam-Level: 
X-Spam-Status: No, score=-1.872 tagged_above=-999 required=5 tests=[AWL=0.572,  BAYES_00=-2.599, NO_RELAYS=-0.001, SUBJECT_FUZZY_TION=0.156]
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 xB0IDzywR1qt for <ietf@ietfa.amsl.com>; Thu,  1 Nov 2012 15:57:08 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id ACEF221F9602 for <ietf@ietf.org>; Thu,  1 Nov 2012 15:57:06 -0700 (PDT)
Received: (qmail 48939 invoked from network); 1 Nov 2012 22:57:02 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:vbr-info:user-agent:cleverness; s=bf2a.5092fe3e.k1211; bh=DXh87FvvWkLHTohJJ7MlWdaGszmYO50KitpCwVEUg3A=; b=Is+i9QgovI6N8hWCnGL/w5Ib9n5RUufDAJaBBlqxW0OzvZEgVuHEbdFMLHEvhIrGpOKIxK0lFijK34TbrFt7SRF2RAAKbDYxD97bvlQhj7GlybtTRy/ZoYlD1/i78YSD7IKLtn4yR2eeGgQsJNLe4nHJcJcSatElodwTBdK4hII=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:vbr-info:user-agent:cleverness; s=bf2a.5092fe3e.k1211; bh=DXh87FvvWkLHTohJJ7MlWdaGszmYO50KitpCwVEUg3A=; b=ky4zklBwJc7gk8hEZjRSH7apEXiM/bibGlF+tN41Dl2YvtYLPFQ+tAS7ibXnPKA+1XJQSf8vXGT9CRDCtN5TyuNTStEC2jQeslWzwhss/jKJRDd9uNs0r/6qyS+xKR7PFm1MPs9mGnQEbKhLxkErvht3RSqThuGzN9DHmHkGRqc=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Received: (ofmipd 127.0.0.1); 1 Nov 2012 22:56:40 -0000
Date: 1 Nov 2012 18:57:02 -0400
Message-ID: <alpine.BSF.2.00.1211011822310.53893@joyce.lan>
From: "John R Levine" <johnl@taugh.com>
To: dcrocker@bbiw.net
Subject: Re: [IETF] Re: Recall petition for Mr. Marshall Eubanks
In-Reply-To: <5092BA96.9020909@dcrocker.net>
References: <5091CD21.3010504@gmail.com> <50919671.6000605@ogud.com> <CAJfR-+PDvsswi3yU-H5TsK_W8RNeSwNMD2Gcdc2SksKEG1xDYQ@mail.gmail.com> <1158F458-8810-4CD2-B874-3DE1A1B8B0B5@kumari.net> <20121101175249.D92C521F89A0@ietfa.amsl.com> <5092BA96.9020909@dcrocker.net>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: MULTIPART/signed; protocol="application/pkcs7-signature"; micalg=sha1; BOUNDARY="3825401791-1909160050-1351810622=:53893"
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Nov 2012 22:57:08 -0000

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--3825401791-1909160050-1351810622=:53893
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed

> As a small point of procedures, no one is sending an actual signature.
>
> It therefore would provide a modicum of better assurance for signatories to 
> send the email that declares their signature directly to the ISOC President 
> rather than to the person initiating the recall.

If you're concerned that some of the 20 people who Olafur says signed his 
petition did not actually do so, please say that.  If there's some other 
problem, what is it?

Or if you're worried about unsigned or forged mail, why are you assuming 
that any of the messages on this list are real?  The list software uses 
only the easily faked From: line to verify senders.

R's,
John
--3825401791-1909160050-1351810622=:53893
Content-Type: APPLICATION/pkcs7-signature; name=smime.p7s
Content-Transfer-Encoding: BASE64
Content-Description: S/MIME Cryptographic Signature
Content-Disposition: attachment; filename=smime.p7s

MIIIBgYJKoZIhvcNAQcCoIIH9zCCB/MCAQExCzAJBgUrDgMCGgUAMAsGCSqG
SIb3DQEHAaCCBSMwggUfMIIEB6ADAgECAhBqmDwY4viwyBNv7hg7djRHMA0G
CSqGSIb3DQEBBQUAMIGTMQswCQYDVQQGEwJHQjEbMBkGA1UECBMSR3JlYXRl
ciBNYW5jaGVzdGVyMRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01P
RE8gQ0EgTGltaXRlZDE5MDcGA1UEAxMwQ09NT0RPIENsaWVudCBBdXRoZW50
aWNhdGlvbiBhbmQgU2VjdXJlIEVtYWlsIENBMB4XDTExMDgyNzAwMDAwMFoX
DTEyMDgyNjIzNTk1OVowIDEeMBwGCSqGSIb3DQEJARYPam9obmxAdGF1Z2gu
Y29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEArjjY2CfvJ3My
a2g1aOrImd0uJVLaah8aKJ8PSJJZth2vTQsMq3ozNxcZWKKRROOUfMeJWQDa
xl0J7d0XCdVjK40s+ZWKvlqwxLHCyIn4Enzk8lkoMq2qQUqnGaGbNQBxQK11
4JINMKOLMkP1WZgOwfDcROBhlKnK7FgNFgXouNS0nFUzosqlKOfYW6Ryl5rV
cLInOqGv78O/ekb9YtzHMVlrF9sKC5D8ijis0RY5uvdb47YCoKvI/Pm5g2wK
EYeD+sJXhSUp3zPct5VLDG1jrN2zjQEVrSFDQ/Ny58EnaNkOSMdE1tRQ7/Nf
ckoMGXqJRedbx7d/H62kGaDb7QrAawIDAQABo4IB3zCCAdswHwYDVR0jBBgw
FoAUehNOAHRbxnhjZCfBL+KgW7x5xXswHQYDVR0OBBYEFFNpWjhcj0fXS96W
ENsvzag4QY9yMA4GA1UdDwEB/wQEAwIFoDAMBgNVHRMBAf8EAjAAMCAGA1Ud
JQQZMBcGCCsGAQUFBwMEBgsrBgEEAbIxAQMFAjARBglghkgBhvhCAQEEBAMC
BSAwRgYDVR0gBD8wPTA7BgwrBgEEAbIxAQIBAQEwKzApBggrBgEFBQcCARYd
aHR0cHM6Ly9zZWN1cmUuY29tb2RvLm5ldC9DUFMwVwYDVR0fBFAwTjBMoEqg
SIZGaHR0cDovL2NybC5jb21vZG9jYS5jb20vQ09NT0RPQ2xpZW50QXV0aGVu
dGljYXRpb25hbmRTZWN1cmVFbWFpbENBLmNybDCBiAYIKwYBBQUHAQEEfDB6
MFIGCCsGAQUFBzAChkZodHRwOi8vY3J0LmNvbW9kb2NhLmNvbS9DT01PRE9D
bGllbnRBdXRoZW50aWNhdGlvbmFuZFNlY3VyZUVtYWlsQ0EuY3J0MCQGCCsG
AQUFBzABhhhodHRwOi8vb2NzcC5jb21vZG9jYS5jb20wGgYDVR0RBBMwEYEP
am9obmxAdGF1Z2guY29tMA0GCSqGSIb3DQEBBQUAA4IBAQB1BxfCpqDbjmN/
bGxym680l1in8LQqE0Vr/zbbz9lcDIPDdaQRDxtRkEf5KdlSrfLk23R0Ri9x
UQanAmVsFpboEhR/rmSdECdkImgAHd+ruZwNpbwX5+U8T0yaU0/Y/Xm+Rdfa
KuEJTVFsO9S6KsKkgTyDoeMoCRIER6ChQyRE51QCyREk9xt6aw03Vj42mZBq
v4mYNVpqzFLs9JLCotV7C9oViKip1UzYj3khybTrC0wn8Q+c99qr03YCpdD5
G+fotgtPEBomtRW4UnUBmZ3foBBah5mTSwPkaBC6p1yN+2qEy075c5tzT/EH
xs7UzXgqn87a8S6cROUqPtykd+NGMYICqzCCAqcCAQEwgagwgZMxCzAJBgNV
BAYTAkdCMRswGQYDVQQIExJHcmVhdGVyIE1hbmNoZXN0ZXIxEDAOBgNVBAcT
B1NhbGZvcmQxGjAYBgNVBAoTEUNPTU9ETyBDQSBMaW1pdGVkMTkwNwYDVQQD
EzBDT01PRE8gQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBTZWN1cmUgRW1h
aWwgQ0ECEGqYPBji+LDIE2/uGDt2NEcwCQYFKw4DAhoFAKCB2DAYBgkqhkiG
9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xMjExMDEyMjU3
MDJaMCMGCSqGSIb3DQEJBDEWBBTbpkvMzPDU8iIdLLtwNWH2o/3cgTB5Bgkq
hkiG9w0BCQ8xbDBqMAsGCWCGSAFlAwQBKjALBglghkgBZQMEARYwCwYJYIZI
AWUDBAECMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDANBggqhkiG9w0D
AgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDANBgkqhkiG9w0BAQEFAASC
AQAlSUNdSqYWksp2zdsC6aVqvw3tK7n/2wl8ywA6oZFRp7AnH1nHoyR9X4zU
g0A4RsdH8AnyTME5rqh4rQHp2Ebaf+ZHZQKe79mEuHglIrafYFrh9pjgjG1E
13sRQOZVCvUBGPCTf9JRAWa0CezZePGWFNCPEwy5BfQySKYPMG+z8b/4z6/s
IwW01eSmvjPZuxNtDgA3Rlwb+CqRCrYvzqCuzfPGQyGQmTik+RjzaNMKSJgF
grQXLo7nK4vSu8wTdTumMJ6cI/n+BY0XnKBEjNEkQ+Tgg9lwuSWvIbbLcG7l
XWlct0y0Ca7c2shbCi/V38zNGwYah3vIss+XPAJV9Rd5

--3825401791-1909160050-1351810622=:53893--

From warren@kumari.net  Thu Nov  1 16:34:37 2012
Return-Path: <warren@kumari.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D441621F95EA for <ietf@ietfa.amsl.com>; Thu,  1 Nov 2012 16:34:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.443
X-Spam-Level: 
X-Spam-Status: No, score=-102.443 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SUBJECT_FUZZY_TION=0.156, 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 XiELhXDAYv-I for <ietf@ietfa.amsl.com>; Thu,  1 Nov 2012 16:34:37 -0700 (PDT)
Received: from vimes.kumari.net (smtp1.kumari.net [204.194.22.1]) by ietfa.amsl.com (Postfix) with ESMTP id 720AD21F95DE for <ietf@ietf.org>; Thu,  1 Nov 2012 16:34:37 -0700 (PDT)
Received: from [130.129.0.235] (unknown [130.129.0.235]) by vimes.kumari.net (Postfix) with ESMTPSA id 8100A1B40018; Thu,  1 Nov 2012 19:34:34 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: [IETF] Re: [IETF] Re: Recall petition for Mr. Marshall Eubanks
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <alpine.BSF.2.00.1211011822310.53893@joyce.lan>
Date: Thu, 1 Nov 2012 19:34:30 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <EEE14553-2207-4671-9D71-8421E04B9E99@kumari.net>
References: <5091CD21.3010504@gmail.com> <50919671.6000605@ogud.com> <CAJfR-+PDvsswi3yU-H5TsK_W8RNeSwNMD2Gcdc2SksKEG1xDYQ@mail.gmail.com> <1158F458-8810-4CD2-B874-3DE1A1B8B0B5@kumari.net> <20121101175249.D92C521F89A0@ietfa.amsl.com> <5092BA96.9020909@dcrocker.net> <alpine.BSF.2.00.1211011822310.53893@joyce.lan>
To: "John R Levine" <johnl@taugh.com>
X-Mailer: Apple Mail (2.1499)
Cc: dcrocker@bbiw.net, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Nov 2012 23:34:37 -0000

On Nov 1, 2012, at 6:57 PM, "John R Levine" <johnl@taugh.com> wrote:

>> As a small point of procedures, no one is sending an actual =
signature.
>>=20
>> It therefore would provide a modicum of better assurance for =
signatories to send the email that declares their signature directly to =
the ISOC President rather than to the person initiating the recall.
>=20
> If you're concerned that some of the 20 people who Olafur says signed =
his petition did not actually do so, please say that.  If there's some =
other problem, what is it?
>=20
> Or if you're worried about unsigned or forged mail, why are you =
assuming that any of the messages on this list are real?  The list =
software uses only the easily faked From: line to verify senders.




>=20
> R's,
> John

--
Some people are like Slinkies......Not really good for anything but they =
still bring a smile to your face when you push them down the stairs.




From mstjohns@comcast.net  Thu Nov  1 19:22:04 2012
Return-Path: <mstjohns@comcast.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 29B4221F96DD for <ietf@ietfa.amsl.com>; Thu,  1 Nov 2012 19:22:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.981
X-Spam-Level: 
X-Spam-Status: No, score=-99.981 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1, SUBJECT_FUZZY_TION=0.156, 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 efvaNBu0C6Gu for <ietf@ietfa.amsl.com>; Thu,  1 Nov 2012 19:22:03 -0700 (PDT)
Received: from qmta07.westchester.pa.mail.comcast.net (qmta07.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:64]) by ietfa.amsl.com (Postfix) with ESMTP id 9C7A721F96EC for <ietf@ietf.org>; Thu,  1 Nov 2012 19:22:03 -0700 (PDT)
Received: from omta09.westchester.pa.mail.comcast.net ([76.96.62.20]) by qmta07.westchester.pa.mail.comcast.net with comcast id JSK21k0010SCNGk57SN8Fl; Fri, 02 Nov 2012 02:22:08 +0000
Received: from Mike-T530.comcast.net ([68.83.212.126]) by omta09.westchester.pa.mail.comcast.net with comcast id JSNb1k00N2kB7pQ3VSNb7y; Fri, 02 Nov 2012 02:22:36 +0000
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Thu, 01 Nov 2012 22:22:11 -0400
To: Bob Hinden <bob.hinden@gmail.com>,Sam Hartman <hartmans-ietf@mit.edu>
From: Michael StJohns <mstjohns@comcast.net>
Subject: Re: Recall petition for Mr. Marshall Eubanks
In-Reply-To: <3153B2FE-4B52-43AF-AD10-6701CFFE0AB8@gmail.com>
References: <50919671.6000605@ogud.com> <7F4FE714-DEDC-4D64-ADD8-AA6ECF53EABB@NLnetLabs.nl> <5092D9DB.4070602@cisco.com> <tsltxt980bc.fsf@mit.edu> <3153B2FE-4B52-43AF-AD10-6701CFFE0AB8@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Message-Id: <20121102022203.9C7A721F96EC@ietfa.amsl.com>
Cc: Bob Hinden <bob.hinden@gmail.com>, 'IETF-Discussion list' <ietf@ietf.org>, Olafur Gudmundsson <ogud@ogud.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Nov 2012 02:22:04 -0000

At 06:01 PM 11/1/2012, Bob Hinden wrote:


>While the IAOC has not discussed this formally, I agree with you.  The situation did change when we were able to talk with Marshall.




I assume at this point the IAOC would like to pursue the recall option?  If not, please be very clear about it to the list as I haven't actually seen a request from the IAOC for that process to proceed as far as I can tell.

If you'd rather just wait from him to resign, if in fact he does, then please indicate that.  I believe neither you nor Dave Crocker nor Scott Bradner (the only IOAC members that I think have commented on this issue on list so far) have actually specifically asked for or signed the recall on the list. 

Mike





>I too hope he will resign.
>
>Bob



From joelja@bogus.com  Thu Nov  1 19:30:09 2012
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A77E221F9844 for <ietf@ietfa.amsl.com>; Thu,  1 Nov 2012 19:30:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.443
X-Spam-Level: 
X-Spam-Status: No, score=-102.443 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SUBJECT_FUZZY_TION=0.156, 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 j-Ao9CZNT-0I for <ietf@ietfa.amsl.com>; Thu,  1 Nov 2012 19:30:09 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 3F0F621F9843 for <ietf@ietf.org>; Thu,  1 Nov 2012 19:30:09 -0700 (PDT)
Received: from [10.71.7.128] (mobile-198-228-221-253.mycingular.net [198.228.221.253]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id qA22Twak070329 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Fri, 2 Nov 2012 02:30:02 GMT (envelope-from joelja@bogus.com)
References: <50919671.6000605@ogud.com> <7F4FE714-DEDC-4D64-ADD8-AA6ECF53EABB@NLnetLabs.nl> <5092D9DB.4070602@cisco.com> <tsltxt980bc.fsf@mit.edu> <3153B2FE-4B52-43AF-AD10-6701CFFE0AB8@gmail.com> <20121102022203.9C7A721F96EC@ietfa.amsl.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <20121102022203.9C7A721F96EC@ietfa.amsl.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <E7EA2D56-916D-41F9-A7F3-D43D3AF23226@bogus.com>
X-Mailer: iPhone Mail (10A403)
From: Joel Jaeggli <joelja@bogus.com>
Subject: Re: Recall petition for Mr. Marshall Eubanks
Date: Thu, 1 Nov 2012 19:29:49 -0700
To: Michael StJohns <mstjohns@comcast.net>
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Fri, 02 Nov 2012 02:30:02 +0000 (UTC)
Cc: Sam Hartman <hartmans-ietf@mit.edu>, Bob Hinden <bob.hinden@gmail.com>, IETF-Discussion list <ietf@ietf.org>, Olafur Gudmundsson <ogud@ogud.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Nov 2012 02:30:09 -0000

Mike,

A 3777 recall isn't dependent on the wishes of the IAOC...

Sent from my iPhone

On Nov 1, 2012, at 19:22, Michael StJohns <mstjohns@comcast.net> wrote:

> <mime-attachment.txt>

From ajs@anvilwalrusden.com  Thu Nov  1 20:45:34 2012
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B10521F98EA for <ietf@ietfa.amsl.com>; Thu,  1 Nov 2012 20:45:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.785
X-Spam-Level: 
X-Spam-Status: No, score=-0.785 tagged_above=-999 required=5 tests=[AWL=-0.100, BAYES_00=-2.599, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311, SUBJECT_FUZZY_TION=0.156]
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 dewpaISPCAPB for <ietf@ietfa.amsl.com>; Thu,  1 Nov 2012 20:45:33 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id 66C9F21F98E8 for <ietf@ietf.org>; Thu,  1 Nov 2012 20:45:32 -0700 (PDT)
Received: from mx1.yitter.info (69-196-144-227.dsl.teksavvy.com [69.196.144.227]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 9A0EB8A031; Fri,  2 Nov 2012 03:45:30 +0000 (UTC)
Date: Thu, 1 Nov 2012 23:45:26 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org, ogud@ogud.com
Subject: Re: Recall petition for Mr. Marshall Eubanks
Message-ID: <20121102034526.GB25144@mx1.yitter.info>
References: <50919671.6000605@ogud.com> <7F4FE714-DEDC-4D64-ADD8-AA6ECF53EABB@NLnetLabs.nl> <5092D9DB.4070602@cisco.com> <tsltxt980bc.fsf@mit.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <tsltxt980bc.fsf@mit.edu>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Nov 2012 03:45:34 -0000

On Thu, Nov 01, 2012 at 05:45:11PM -0400, Sam Hartman wrote:

> found a gap in the procedures I can see the argument for creativity.
> However, according to Bob's note, Marshall has been contacted and rather
> than resigning, said he would consider resigning.
[â€¦]
> In my mind that moves us out of a situation where creative
> interpretations of vacancy are appropriate.

I agree with Sam Hartman's reasoning, and so I unhappily add my name
to those willing to support recall.  I also hope continuing with this
can be avoided by the expedient of Marshall's resignation.  I am
Nomcom eligible.

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From housley@vigilsec.com  Thu Nov  1 20:45:37 2012
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 67ABC21F98F0 for <ietf@ietfa.amsl.com>; Thu,  1 Nov 2012 20:45:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.507
X-Spam-Level: 
X-Spam-Status: No, score=-102.507 tagged_above=-999 required=5 tests=[AWL=-0.064, BAYES_00=-2.599, SUBJECT_FUZZY_TION=0.156, 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 5M40Yu4PdWmJ for <ietf@ietfa.amsl.com>; Thu,  1 Nov 2012 20:45:36 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 617C921F98EB for <ietf@ietf.org>; Thu,  1 Nov 2012 20:45:36 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 3B37C9A400A; Thu,  1 Nov 2012 23:45:43 -0400 (EDT)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id lerDBbttcFa6; Thu,  1 Nov 2012 23:45:30 -0400 (EDT)
Received: from [192.168.2.100] (pool-96-255-37-162.washdc.fios.verizon.net [96.255.37.162]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id C8AE99A4002; Thu,  1 Nov 2012 23:45:40 -0400 (EDT)
Subject: Re: Recall petition for Mr. Marshall Eubanks
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <20121102022203.9C7A721F96EC@ietfa.amsl.com>
Date: Thu, 1 Nov 2012 23:45:31 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <34363E27-E2DE-4BEB-AB4F-3000CB571DA3@vigilsec.com>
References: <50919671.6000605@ogud.com> <7F4FE714-DEDC-4D64-ADD8-AA6ECF53EABB@NLnetLabs.nl> <5092D9DB.4070602@cisco.com> <tsltxt980bc.fsf@mit.edu> <3153B2FE-4B52-43AF-AD10-6701CFFE0AB8@gmail.com> <20121102022203.9C7A721F96EC@ietfa.amsl.com>
To: Michael StJohns <mstjohns@comcast.net>
X-Mailer: Apple Mail (2.1085)
Cc: IETF-Discussion list <ietf@ietf.org>, Olafur Gudmundsson <ogud@ogud.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Nov 2012 03:45:37 -0000

Mike:

As Joel already said, the recall process is not dependent on the wishes =
of the IAOC.

Further, please note that IAB, IESG, and IAOC members cannot be recall =
petition signers.  RFC 3777 says:

 1.  At any time, at least 20 members of the IETF community, who are
     qualified to be voting members of a nominating committee, may
     request by signed petition (email is acceptable) to the Internet
     Society President the recall of any sitting IAB or IESG member.

According to RFC 3777, sitting members of the IESG and IAB are not =
qualified to be voting members of NomCom.  And, there is a long-standing =
tradition that IAOC members will not serve on NomCom.  There is also an =
I-D that just finished IETF Last Call to formally exclude IAOC members =
from serving on NomCom.

Russ


On Nov 1, 2012, at 10:22 PM, Michael StJohns wrote:
> At 06:01 PM 11/1/2012, Bob Hinden wrote:
>> While the IAOC has not discussed this formally, I agree with you.  =
The situation did change when we were able to talk with Marshall.
>=20
> I assume at this point the IAOC would like to pursue the recall =
option?  If not, please be very clear about it to the list as I haven't =
actually seen a request from the IAOC for that process to proceed as far =
as I can tell.
>=20
> If you'd rather just wait from him to resign, if in fact he does, then =
please indicate that.  I believe neither you nor Dave Crocker nor Scott =
Bradner (the only IOAC members that I think have commented on this issue =
on list so far) have actually specifically asked for or signed the =
recall on the list.=20
>=20
> Mike


From mstjohns@comcast.net  Thu Nov  1 21:35:19 2012
Return-Path: <mstjohns@comcast.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1DF8E21F98EC for <ietf@ietfa.amsl.com>; Thu,  1 Nov 2012 21:35:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.883
X-Spam-Level: 
X-Spam-Status: No, score=-99.883 tagged_above=-999 required=5 tests=[AWL=0.554, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1, 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 z3xZKpFFR9e7 for <ietf@ietfa.amsl.com>; Thu,  1 Nov 2012 21:35:18 -0700 (PDT)
Received: from qmta13.westchester.pa.mail.comcast.net (qmta13.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:44:76:96:59:243]) by ietfa.amsl.com (Postfix) with ESMTP id 1574521F98DE for <ietf@ietf.org>; Thu,  1 Nov 2012 21:35:17 -0700 (PDT)
Received: from omta23.westchester.pa.mail.comcast.net ([76.96.62.74]) by qmta13.westchester.pa.mail.comcast.net with comcast id JUTG1k0041c6gX85DUbNWw; Fri, 02 Nov 2012 04:35:22 +0000
Received: from Mike-T530.comcast.net ([68.83.212.126]) by omta23.westchester.pa.mail.comcast.net with comcast id JUaG1k00B2kB7pQ3jUaVXY; Fri, 02 Nov 2012 04:34:29 +0000
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Fri, 02 Nov 2012 00:35:13 -0400
To: Russ Housley <housley@vigilsec.com>
From: Michael StJohns <mstjohns@comcast.net>
Subject: I* Member Removal Process
In-Reply-To: <34363E27-E2DE-4BEB-AB4F-3000CB571DA3@vigilsec.com>
References: <50919671.6000605@ogud.com> <7F4FE714-DEDC-4D64-ADD8-AA6ECF53EABB@NLnetLabs.nl> <5092D9DB.4070602@cisco.com> <tsltxt980bc.fsf@mit.edu> <3153B2FE-4B52-43AF-AD10-6701CFFE0AB8@gmail.com> <20121102022203.9C7A721F96EC@ietfa.amsl.com> <34363E27-E2DE-4BEB-AB4F-3000CB571DA3@vigilsec.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Message-Id: <20121102043518.1574521F98DE@ietfa.amsl.com>
Cc: IETF-Discussion list <ietf@ietf.org>, Olafur Gudmundsson <ogud@ogud.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Nov 2012 04:35:19 -0000

At 11:45 PM 11/1/2012, Russ Housley wrote:
>Mike:
>
>As Joel already said, the recall process is not dependent on the wishes of the IAOC.

Yup.  But I'd say their wishes would have a great deal of influence on whether or not this would go forward.  And I'd still like to get at least some indication that this is their desired outcome at this point.  I think, if nothing else, this needs to be part of whatever record considered by a recall committee.  If I heard that only 1 or 2 members were indicating support for removal, I probably would withdraw my name from the petition signature.


>Further, please note that IAB, IESG, and IAOC members cannot be recall petition signers.  RFC 3777 says:
>
> 1.  At any time, at least 20 members of the IETF community, who are
>     qualified to be voting members of a nominating committee, may
>     request by signed petition (email is acceptable) to the Internet
>     Society President the recall of any sitting IAB or IESG member.
>
>According to RFC 3777, sitting members of the IESG and IAB are not qualified to be voting members of NomCom.  And, there is a long-standing tradition that IAOC members will not serve on NomCom.  There is also an I-D that just finished IETF Last Call to formally exclude IAOC members from serving on NomCom.

Fair enough, I'd forgotten that little fillip in the rules. 

I think you've also just convinced me that there's a need for an Expulsion option in 3777bis.  This effort wasn't triggered by a desire of the IETF community to remove Marshall - we had no idea there was a problem (and some cases didn't agree that Marshall's absence was the greatest problem put forth).  This was triggered by the members of the IAOC.  To me it seems logical that a body should be able to initiate removal of its own members for whatever reasons it deems appropriate, but with a pretty high bar to completion.  


So for expulsion - I would propose that 2/3 of the remaining members concur to initiate the process.  And that we select one of two options for confirmation: 3777 recall committee or 2/3 of the confirming body to confirm the removal.  I would also proposed to prohibit more than one expulsion attempt for a member within a 6/9/12 month period.

One possible future optimization for selecting the recall committee might be to choose members from the remaining list from the most recent nomcom selection using the same random selection process and same constraints on number members from the same organization/company.  Also, stick the current nomcom "PAST chair" as the recall chair.

Mike



>Russ
>
>
>On Nov 1, 2012, at 10:22 PM, Michael StJohns wrote:
>> At 06:01 PM 11/1/2012, Bob Hinden wrote:
>>> While the IAOC has not discussed this formally, I agree with you.  The situation did change when we were able to talk with Marshall.
>> 
>> I assume at this point the IAOC would like to pursue the recall option?  If not, please be very clear about it to the list as I haven't actually seen a request from the IAOC for that process to proceed as far as I can tell.
>> 
>> If you'd rather just wait from him to resign, if in fact he does, then please indicate that.  I believe neither you nor Dave Crocker nor Scott Bradner (the only IOAC members that I think have commented on this issue on list so far) have actually specifically asked for or signed the recall on the list. 
>> 
>> Mike



From housley@vigilsec.com  Thu Nov  1 21:52:25 2012
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0FABD21F98CD for <ietf@ietfa.amsl.com>; Thu,  1 Nov 2012 21:52:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.584
X-Spam-Level: 
X-Spam-Status: No, score=-102.584 tagged_above=-999 required=5 tests=[AWL=0.015, 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 qVAfFI0ZZ6t9 for <ietf@ietfa.amsl.com>; Thu,  1 Nov 2012 21:52:24 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 5E73C21F95F3 for <ietf@ietf.org>; Thu,  1 Nov 2012 21:52:24 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 482D69A400A; Fri,  2 Nov 2012 00:52:54 -0400 (EDT)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id TNHgd7uk30cx; Fri,  2 Nov 2012 00:52:22 -0400 (EDT)
Received: from [192.168.2.100] (pool-96-255-37-162.washdc.fios.verizon.net [96.255.37.162]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 3E2E89A4002; Fri,  2 Nov 2012 00:52:53 -0400 (EDT)
Subject: Re: I* Member Removal Process
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <20121102043542.A69E39A4002@odin.smetech.net>
Date: Fri, 2 Nov 2012 00:52:21 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <9C68ED55-C21C-465A-9478-F0F165F0EC09@vigilsec.com>
References: <50919671.6000605@ogud.com> <7F4FE714-DEDC-4D64-ADD8-AA6ECF53EABB@NLnetLabs.nl> <5092D9DB.4070602@cisco.com> <tsltxt980bc.fsf@mit.edu> <3153B2FE-4B52-43AF-AD10-6701CFFE0AB8@gmail.com> <20121102022203.9C7A721F96EC@ietfa.amsl.com> <34363E27-E2DE-4BEB-AB4F-3000CB571DA3@vigilsec.com> <20121102043542.A69E39A4002@odin.smetech.net>
To: Michael StJohns <mstjohns@comcast.net>
X-Mailer: Apple Mail (2.1085)
Cc: IETF-Discussion list <ietf@ietf.org>, Olafur Gudmundsson <ogud@ogud.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Nov 2012 04:52:25 -0000

Mike:

> Yup.  But I'd say their wishes would have a great deal of influence on =
whether or not this would go forward.  And I'd still like to get at =
least some indication that this is their desired outcome at this point.  =
I think, if nothing else, this needs to be part of whatever record =
considered by a recall committee.  If I heard that only 1 or 2 members =
were indicating support for removal, I probably would withdraw my name =
from the petition signature.

The IAOC was unanimous (minus Marshall, of course) in asking the =
community to declare the seat vacant.  A vote was taken, and the minutes =
will confirm what I have stated here when they are published.

Many IAOC members have voiced a desire to vacate the seat in the least =
embarassing manner for Marshall.  Clearly, Marshall has not resigned, =
although he could still take that action.  And, the community does not =
have rough consensus for simply declaring his seat vacant under the =
current set of BCPs.  This leaves only one option: recall.

Russ






From narten@us.ibm.com  Thu Nov  1 21:53:21 2012
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A71F21F8AD9 for <ietf@ietfa.amsl.com>; Thu,  1 Nov 2012 21:53:21 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MA0IyXoTzlyv for <ietf@ietfa.amsl.com>; Thu,  1 Nov 2012 21:53:20 -0700 (PDT)
Received: from e34.co.us.ibm.com (e34.co.us.ibm.com [32.97.110.152]) by ietfa.amsl.com (Postfix) with ESMTP id 84C2F21F852D for <ietf@ietf.org>; Thu,  1 Nov 2012 21:53:07 -0700 (PDT)
Received: from /spool/local by e34.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Thu, 1 Nov 2012 22:53:07 -0600
Received: from d03dlp02.boulder.ibm.com (9.17.202.178) by e34.co.us.ibm.com (192.168.1.134) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Thu, 1 Nov 2012 22:53:05 -0600
Received: from d03relay05.boulder.ibm.com (d03relay05.boulder.ibm.com [9.17.195.107]) by d03dlp02.boulder.ibm.com (Postfix) with ESMTP id ED9F83E4003C for <ietf@ietf.org>; Thu,  1 Nov 2012 22:53:03 -0600 (MDT)
Received: from d03av06.boulder.ibm.com (d03av06.boulder.ibm.com [9.17.195.245]) by d03relay05.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id qA24r4Nx189532 for <ietf@ietf.org>; Thu, 1 Nov 2012 22:53:04 -0600
Received: from d03av06.boulder.ibm.com (loopback [127.0.0.1]) by d03av06.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id qA24snHR031462 for <ietf@ietf.org>; Thu, 1 Nov 2012 22:54:49 -0600
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.44.115.148]) by d03av06.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id qA24smQJ031456 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 1 Nov 2012 22:54:49 -0600
Received: from rotala.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.5/8.12.5) with ESMTP id qA24r38k018072 for <ietf@ietf.org>; Fri, 2 Nov 2012 00:53:03 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.5/8.14.5/Submit) id qA24r2SR018039 for ietf@ietf.org; Fri, 2 Nov 2012 00:53:02 -0400
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201211020453.qA24r2SR018039@rotala.raleigh.ibm.com>
Date: Fri, 02 Nov 2012 00:53:02 -0400
To: ietf@ietf.org
Subject: Weekly posting summary for ietf@ietf.org
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 12110204-2876-0000-0000-000001A24BA8
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Nov 2012 04:53:21 -0000

Total of 77 messages in the last 7 days.
 
script run at: Fri Nov  2 00:53:02 EDT 2012
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  6.49% |    5 |  6.78% |    37980 | lear@cisco.com
  6.49% |    5 |  6.33% |    35466 | mstjohns@comcast.net
  5.19% |    4 |  5.17% |    28952 | john-ietf@jck.com
  5.19% |    4 |  5.15% |    28826 | tglassey@earthlink.net
  2.60% |    2 |  6.58% |    36864 | olaf@nlnetlabs.nl
  3.90% |    3 |  3.79% |    21208 | bob.hinden@gmail.com
  3.90% |    3 |  3.57% |    20013 | brian.e.carpenter@gmail.com
  3.90% |    3 |  2.98% |    16665 | warren@kumari.net
  2.60% |    2 |  3.53% |    19752 | rbonica@juniper.net
  2.60% |    2 |  2.98% |    16692 | eburger-l@standardstrack.com
  2.60% |    2 |  2.82% |    15763 | rja.lists@gmail.com
  2.60% |    2 |  2.64% |    14784 | margaretw42@gmail.com
  2.60% |    2 |  2.58% |    14460 | turchanyi.geza@gmail.com
  2.60% |    2 |  2.35% |    13176 | housley@vigilsec.com
  2.60% |    2 |  2.33% |    13021 | dougb@dougbarton.us
  2.60% |    2 |  2.27% |    12730 | ogud@ogud.com
  2.60% |    2 |  2.05% |    11504 | hartmans-ietf@mit.edu
  2.60% |    2 |  2.00% |    11208 | joelja@bogus.com
  1.30% |    1 |  2.08% |    11654 | narten@us.ibm.com
  1.30% |    1 |  2.04% |    11416 | daedulus@btconnect.com
  1.30% |    1 |  1.72% |     9614 | dave@cridland.net
  1.30% |    1 |  1.71% |     9591 | johnl@taugh.com
  1.30% |    1 |  1.64% |     9210 | edj.etc@gmail.com
  1.30% |    1 |  1.50% |     8425 | d3e3e3@gmail.com
  1.30% |    1 |  1.44% |     8074 | rwfranks@gmail.com
  1.30% |    1 |  1.42% |     7977 | sm@resistor.net
  1.30% |    1 |  1.40% |     7830 | fred@cisco.com
  1.30% |    1 |  1.33% |     7427 | ted.ietf@gmail.com
  1.30% |    1 |  1.28% |     7164 | bert@secret-wg.org
  1.30% |    1 |  1.10% |     6173 | sob@sobco.com
  1.30% |    1 |  1.04% |     5815 | jmpolk@cisco.com
  1.30% |    1 |  1.04% |     5799 | spencer@wonderhamster.org
  1.30% |    1 |  1.02% |     5732 | jari.arkko@piuha.net
  1.30% |    1 |  1.01% |     5682 | dhc@dcrocker.net
  1.30% |    1 |  1.01% |     5634 | dwm@xpasc.com
  1.30% |    1 |  1.01% |     5633 | julian.reschke@gmx.de
  1.30% |    1 |  1.01% |     5628 | melinda.shore@gmail.com
  1.30% |    1 |  1.00% |     5617 | ford@isoc.org
  1.30% |    1 |  1.00% |     5615 | bertietf@bwijnen.net
  1.30% |    1 |  0.96% |     5393 | nomcom-chair@ietf.org
  1.30% |    1 |  0.95% |     5322 | worley@ariadne.com
  1.30% |    1 |  0.94% |     5277 | ajs@anvilwalrusden.com
  1.30% |    1 |  0.93% |     5220 | bortzmeyer@nic.fr
  1.30% |    1 |  0.89% |     4997 | jaap@nlnetlabs.nl
  1.30% |    1 |  0.84% |     4716 | acooper@cdt.org
  1.30% |    1 |  0.76% |     4245 | randy@psg.com
--------+------+--------+----------+------------------------
100.00% |   77 |100.00% |   559944 | Total


From brian.e.carpenter@gmail.com  Fri Nov  2 01:03:48 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5663921F92F3 for <ietf@ietfa.amsl.com>; Fri,  2 Nov 2012 01:03:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.563
X-Spam-Level: 
X-Spam-Status: No, score=-101.563 tagged_above=-999 required=5 tests=[AWL=-0.028, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, SUBJECT_FUZZY_TION=0.156, 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 PRTMmuYiYqhG for <ietf@ietfa.amsl.com>; Fri,  2 Nov 2012 01:03:48 -0700 (PDT)
Received: from mail-wg0-f44.google.com (mail-wg0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id B0C7E21F91B5 for <ietf@ietf.org>; Fri,  2 Nov 2012 01:03:47 -0700 (PDT)
Received: by mail-wg0-f44.google.com with SMTP id dr13so1575330wgb.13 for <ietf@ietf.org>; Fri, 02 Nov 2012 01:03:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=OaJOakCIQsD9ygVT4oKL/nk5D2DN+oqntzyW5hXTppU=; b=CPxnde0HJwAURaND/I2FpeLmEU4sMITwvprnvB0cXxA3RwKlwB1da9KeMZu2BfM7vx lAeuY/dOOuDYEThnz5pRg4W7YxAykRxKEtiZ+TgtgfJ71/ymnCl0ot+0+85K3DnzmKYW yeSi2bcuyB1kot+8f0xFTK/b2nwWGAhKrfrtRS1rHqSIZeP4s1S9NATWMnGEoa7zhUjP GikUgbgYYGU5QXcmw3dEgqBVSl7yJqHxhLEkyD/rte6g1FhgWCCHMXPQNjoaS9GCjKcp Y8imqjGcPmG9Snt4WxxIjkaFauW43iB7ya7xTyRGoqepla0+GrzvHmYlHr25MxLrarXo DbQA==
Received: by 10.180.80.104 with SMTP id q8mr1320391wix.6.1351843426653; Fri, 02 Nov 2012 01:03:46 -0700 (PDT)
Received: from [192.168.1.65] (host-2-102-219-241.as13285.net. [2.102.219.241]) by mx.google.com with ESMTPS id en20sm574674wid.4.2012.11.02.01.03.45 (version=SSLv3 cipher=OTHER); Fri, 02 Nov 2012 01:03:45 -0700 (PDT)
Message-ID: <50937E6F.1020805@gmail.com>
Date: Fri, 02 Nov 2012 08:03:59 +0000
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: 'IETF-Discussion list' <ietf@ietf.org>
Subject: Re: Recall petition for Mr. Marshall Eubanks
References: <50919671.6000605@ogud.com>	<7F4FE714-DEDC-4D64-ADD8-AA6ECF53EABB@NLnetLabs.nl>	<5092D9DB.4070602@cisco.com> <tsltxt980bc.fsf@mit.edu>
In-Reply-To: <tsltxt980bc.fsf@mit.edu>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Nov 2012 08:03:48 -0000

On 01/11/2012 21:45, Sam Hartman wrote:
...
> At this point, I believe the recall process is the correct process to
> follow unless there is an approved BCP update.
> In a case where there's been no contact and there's an argument we've
> found a gap in the procedures I can see the argument for creativity.
> However, according to Bob's note, Marshall has been contacted and rather
> than resigning, said he would consider resigning.
> I hope he does.
> Until he does, though, by considering resigning rather than resigning,
> he has implied that there might be a reason not to resign.
> In my mind that moves us out of a situation where creative
> interpretations of vacancy are appropriate.

I agree, with some sadness.

(I am, as it happens, not NomCom eligible right now.)

     Brian

From shanna@juniper.net  Fri Nov  2 02:29:16 2012
Return-Path: <shanna@juniper.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 217E921F949B for <ietf@ietfa.amsl.com>; Fri,  2 Nov 2012 02:29:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.389
X-Spam-Level: 
X-Spam-Status: No, score=-103.389 tagged_above=-999 required=5 tests=[AWL=-0.078, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SUBJECT_FUZZY_TION=0.156, UNRESOLVED_TEMPLATE=3.132, 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 UkkNfYtQ24li for <ietf@ietfa.amsl.com>; Fri,  2 Nov 2012 02:29:15 -0700 (PDT)
Received: from exprod7og112.obsmtp.com (exprod7og112.obsmtp.com [64.18.2.177]) by ietfa.amsl.com (Postfix) with ESMTP id 77D0C21F9497 for <ietf@ietf.org>; Fri,  2 Nov 2012 02:29:15 -0700 (PDT)
Received: from P-EMHUB03-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob112.postini.com ([64.18.6.12]) with SMTP ID DSNKUJOSa2/c1CsXmdpZafqDpIjcLOBjiiQm@postini.com; Fri, 02 Nov 2012 02:29:15 PDT
Received: from P-CLDFE02-HQ.jnpr.net (172.24.192.60) by P-EMHUB03-HQ.jnpr.net (172.24.192.37) with Microsoft SMTP Server (TLS) id 8.3.213.0; Fri, 2 Nov 2012 02:28:09 -0700
Received: from o365mail.juniper.net (207.17.137.149) by o365mail.juniper.net (172.24.192.60) with Microsoft SMTP Server id 14.1.355.2; Fri, 2 Nov 2012 02:28:08 -0700
Received: from ch1outboundpool.messaging.microsoft.com (216.32.181.185) by o365mail.juniper.net (207.17.137.149) with Microsoft SMTP Server (TLS) id 14.1.355.2; Fri, 2 Nov 2012 02:29:56 -0700
Received: from mail206-ch1-R.bigfish.com (10.43.68.241) by CH1EHSOBE003.bigfish.com (10.43.70.53) with Microsoft SMTP Server id 14.1.225.23; Fri, 2 Nov 2012 09:28:07 +0000
Received: from mail206-ch1 (localhost [127.0.0.1])	by mail206-ch1-R.bigfish.com (Postfix) with ESMTP id D0FBE1E02F3	for <ietf@ietf.org.FOPE.CONNECTOR.OVERRIDE>; Fri,  2 Nov 2012 09:28:07 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.236.101; KIP:(null); UIP:(null); (null); H:BY2PRD0510HT004.namprd05.prod.outlook.com; R:internal; EFV:INT
X-SpamScore: -1
X-BigFish: PS-1(zz4015Izz1de0h1202h1d1ah1d2ahzzz2dh2a8h668h839h93fhd25hf0ah1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh1155h)
Received: from mail206-ch1 (localhost.localdomain [127.0.0.1]) by mail206-ch1 (MessageSwitch) id 1351848485837932_22738; Fri,  2 Nov 2012 09:28:05 +0000 (UTC)
Received: from CH1EHSMHS033.bigfish.com (snatpool3.int.messaging.microsoft.com [10.43.68.228])	by mail206-ch1.bigfish.com (Postfix) with ESMTP id C11EF340096	for <ietf@ietf.org>; Fri,  2 Nov 2012 09:28:05 +0000 (UTC)
Received: from BY2PRD0510HT004.namprd05.prod.outlook.com (157.56.236.101) by CH1EHSMHS033.bigfish.com (10.43.70.33) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 2 Nov 2012 09:28:01 +0000
Received: from BY2PRD0510MB366.namprd05.prod.outlook.com ([169.254.6.143]) by BY2PRD0510HT004.namprd05.prod.outlook.com ([10.255.84.39]) with mapi id 14.16.0233.002; Fri, 2 Nov 2012 09:28:00 +0000
From: Stephen Hanna <shanna@juniper.net>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: Recall petition for Mr. Marshall Eubanks
Thread-Topic: Recall petition for Mr. Marshall Eubanks
Thread-Index: AQHNuHoqnKftacsyYU+EE+ahMoBe3ZfV6AgAgABfBUA=
Date: Fri, 2 Nov 2012 09:28:00 +0000
Message-ID: <F1DFC16DCAA7D3468651A5A776D5796E01FF9FF7@BY2PRD0510MB366.namprd05.prod.outlook.com>
References: <50919671.6000605@ogud.com> <7F4FE714-DEDC-4D64-ADD8-AA6ECF53EABB@NLnetLabs.nl> <5092D9DB.4070602@cisco.com> <tsltxt980bc.fsf@mit.edu> <20121102034526.GB25144@mx1.yitter.info>
In-Reply-To: <20121102034526.GB25144@mx1.yitter.info>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.232.2]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
X-FOPE-CONNECTOR: Id%12219$Dn%IETF.ORG$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Nov 2012 09:29:16 -0000

SSBhbHNvLCB3aXRoIHJlZ3JldCwgd291bGQgbGlrZSB0byBhZGQgbXkgbmFtZSB0byB0aGUgcmVj
YWxsDQpwZXRpdGlvbi4gSSBhbSBOb21Db20gZWxpZ2libGUuDQoNClRoYW5rcywNCg0KU3RldmUN
Cg0K


From turchanyi.geza@gmail.com  Fri Nov  2 02:37:06 2012
Return-Path: <turchanyi.geza@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 35C2021F994D for <ietf@ietfa.amsl.com>; Fri,  2 Nov 2012 02:37:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.331
X-Spam-Level: 
X-Spam-Status: No, score=-3.331 tagged_above=-999 required=5 tests=[AWL=0.111,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, SUBJECT_FUZZY_TION=0.156]
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 9ElNMGMA9pQ0 for <ietf@ietfa.amsl.com>; Fri,  2 Nov 2012 02:37:05 -0700 (PDT)
Received: from mail-pa0-f44.google.com (mail-pa0-f44.google.com [209.85.220.44]) by ietfa.amsl.com (Postfix) with ESMTP id 7F23C21F9941 for <ietf@ietf.org>; Fri,  2 Nov 2012 02:37:05 -0700 (PDT)
Received: by mail-pa0-f44.google.com with SMTP id fb11so2364753pad.31 for <ietf@ietf.org>; Fri, 02 Nov 2012 02:37:05 -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 :cc:content-type; bh=Ss15V1QVrYFtStSNqiP3y2UPyV0dSGejsdwtglIKmN0=; b=wF03pc6ERe6L69bQ9r0RmL5wPklg+BnFypWXViFIn69LD54KVsQlD9Kk7A6MLTwJQ/ QKAu/JhCYEzjBrgST5lY/peV8t8R1aLsEkM3nTVdPJOEkyBzsypgt+Eov+r7gvp/hIfJ gthAlR4EvJMUFYjmN1jpd62nXke5t5QujIxO3kmqitqmLJ+uN3eXl5/8E7OVqf8VEjQI 51XfWl6f2zaakPDpgL3bRPNJj506Qg4oh1qyCQlLPV/GK6vHW9bq6+Bta7d8Z7fvfwlG M2L2+I0V7HjaYFSueMqfFuycqVOW/dH9+FfXLs5pwLoEax470wWhOMg/OVGIPeTzSWeV UCow==
MIME-Version: 1.0
Received: by 10.68.115.75 with SMTP id jm11mr4505003pbb.28.1351849024942; Fri, 02 Nov 2012 02:37:04 -0700 (PDT)
Received: by 10.66.19.135 with HTTP; Fri, 2 Nov 2012 02:37:04 -0700 (PDT)
In-Reply-To: <50937E6F.1020805@gmail.com>
References: <50919671.6000605@ogud.com> <7F4FE714-DEDC-4D64-ADD8-AA6ECF53EABB@NLnetLabs.nl> <5092D9DB.4070602@cisco.com> <tsltxt980bc.fsf@mit.edu> <50937E6F.1020805@gmail.com>
Date: Fri, 2 Nov 2012 10:37:04 +0100
Message-ID: <CAJfR-+Og2RC1cMfV7AqRMsEKkneWPMR2Ptp-SW-as-+iphKq_w@mail.gmail.com>
Subject: Re: Recall petition for Mr. Marshall Eubanks
From: Turchanyi Geza <turchanyi.geza@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: multipart/alternative; boundary=e89a8ff24c4febf04c04cd7fe075
Cc: IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Nov 2012 09:37:06 -0000

--e89a8ff24c4febf04c04cd7fe075
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Brian,

I would like to express my sadness as well, adding that I am most probably
not NomCom eligible.

I was only 23 when one of my freinds, community activist in the students
circle of the university, committed a suicide. Three years later it
happened again, by one other freind of us.

I feel that there is a danger that this might happen again, especially in
this case.

Apparently Marshall still think that he could return to his IETF work in
the near future. How could we help him, this is my question, How can we
taylor the rules of our work, allowing to go for a sabbatical period and
return later, with quick reintegration?

=C1 bientot,

G=E9za




On Fri, Nov 2, 2012 at 9:03 AM, Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

> On 01/11/2012 21:45, Sam Hartman wrote:
> ...
> > At this point, I believe the recall process is the correct process to
> > follow unless there is an approved BCP update.
> > In a case where there's been no contact and there's an argument we've
> > found a gap in the procedures I can see the argument for creativity.
> > However, according to Bob's note, Marshall has been contacted and rathe=
r
> > than resigning, said he would consider resigning.
> > I hope he does.
> > Until he does, though, by considering resigning rather than resigning,
> > he has implied that there might be a reason not to resign.
> > In my mind that moves us out of a situation where creative
> > interpretations of vacancy are appropriate.
>
> I agree, with some sadness.
>
> (I am, as it happens, not NomCom eligible right now.)
>
>      Brian
>

--e89a8ff24c4febf04c04cd7fe075
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Brian,<br><br>I would like to express my sadness as well, adding that I am =
most probably not NomCom eligible.<br><br>I was only 23 when one of my frei=
nds, community activist in the students circle of the university, committed=
 a suicide. Three years later it happened again, by one other freind of us.=
<br>
<br>I feel that there is a danger that this might happen again, especially =
in this case.<br><br>Apparently Marshall still think that he could return t=
o his IETF work in the near future. How could we help him, this is my quest=
ion, How can we taylor the rules of our work, allowing to go for a sabbatic=
al period and return later, with quick reintegration?<br>
<br>=C1 bientot,<br><br>G=E9za<br><br><br><br><br><div class=3D"gmail_quote=
">On Fri, Nov 2, 2012 at 9:03 AM, Brian E Carpenter <span dir=3D"ltr">&lt;<=
a href=3D"mailto:brian.e.carpenter@gmail.com" target=3D"_blank">brian.e.car=
penter@gmail.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">On 01/11/2012 21:45, Sam Hartman wrote:<br>
...<br>
<div class=3D"im">&gt; At this point, I believe the recall process is the c=
orrect process to<br>
&gt; follow unless there is an approved BCP update.<br>
&gt; In a case where there&#39;s been no contact and there&#39;s an argumen=
t we&#39;ve<br>
&gt; found a gap in the procedures I can see the argument for creativity.<b=
r>
&gt; However, according to Bob&#39;s note, Marshall has been contacted and =
rather<br>
&gt; than resigning, said he would consider resigning.<br>
&gt; I hope he does.<br>
&gt; Until he does, though, by considering resigning rather than resigning,=
<br>
&gt; he has implied that there might be a reason not to resign.<br>
&gt; In my mind that moves us out of a situation where creative<br>
&gt; interpretations of vacancy are appropriate.<br>
<br>
</div>I agree, with some sadness.<br>
<br>
(I am, as it happens, not NomCom eligible right now.)<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
=A0 =A0 =A0Brian<br>
</font></span></blockquote></div><br>

--e89a8ff24c4febf04c04cd7fe075--

From henk.uijterwaal@gmail.com  Fri Nov  2 04:48:59 2012
Return-Path: <henk.uijterwaal@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D382721F9304 for <ietf@ietfa.amsl.com>; Fri,  2 Nov 2012 04:48:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.443
X-Spam-Level: 
X-Spam-Status: No, score=-3.443 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, SUBJECT_FUZZY_TION=0.156]
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 96qZDILLnxNB for <ietf@ietfa.amsl.com>; Fri,  2 Nov 2012 04:48:59 -0700 (PDT)
Received: from mail-bk0-f44.google.com (mail-bk0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id 829BF21F9287 for <ietf@ietf.org>; Fri,  2 Nov 2012 04:48:55 -0700 (PDT)
Received: by mail-bk0-f44.google.com with SMTP id jc3so1351615bkc.31 for <ietf@ietf.org>; Fri, 02 Nov 2012 04:48:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:reply-to:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=weyMWuawZjC7P3xqbodESfwAaILLAggM/3h53sgwdbM=; b=k4rdF+rqOwp1jkbYE5StO4RYiqfsoMHJRiCRE8Ldg2iW34ydY93yaU+Zhxce3BrqsO zon2aYSLM88nxTNJihYMTuN1lDWVoGndQo/RdBLIwFM8jnW2kIsZmfy+OosB07xkB7ni 91gDRTc77xVBaQoTLXaC3cjxoTqaOT23XhBxydRS1nPp2oW1Y7TXgJnHAzwa4wjg4YbB AWODqMbD/QqXrYv+69owy9Ct5u774TYLbN/VOYROJpvC7mHkDz3zjvip7fZRefNTyRsx ASysFGkjTx4JYmAwZchAPPqGFcphdVdFS+MYqdzlhhAm0pkndeylwY0+abiY1CH/vAGK uMPA==
Received: by 10.204.130.21 with SMTP id q21mr310833bks.5.1351856934452; Fri, 02 Nov 2012 04:48:54 -0700 (PDT)
Received: from geir.local ([2001:980:1203:1:7cea:7ae6:fb8a:6bd8]) by mx.google.com with ESMTPS id gy18sm6416817bkc.4.2012.11.02.04.48.51 (version=SSLv3 cipher=OTHER); Fri, 02 Nov 2012 04:48:53 -0700 (PDT)
Message-ID: <5093993A.4060003@gmail.com>
Date: Fri, 02 Nov 2012 10:58:18 +0100
From: Henk Uijterwaal <henk.uijterwaal@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Recall petition for Mr. Marshall Eubanks
References: <50919671.6000605@ogud.com> <7F4FE714-DEDC-4D64-ADD8-AA6ECF53EABB@NLnetLabs.nl> <8C48B86A895913448548E6D15DA7553B190F1A@xmb-rcd-x09.cisco.com>
In-Reply-To: <8C48B86A895913448548E6D15DA7553B190F1A@xmb-rcd-x09.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: henk@uijterwaal.nl
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Nov 2012 11:48:59 -0000

On 01/11/2012 19:43, Fred Baker (fred) wrote:
> 
> On Nov 1, 2012, at 9:32 AM, Olaf Kolkman wrote:
> 
>> I also offer my signature under the recall procedure, in case pragmatism
>> doesn't prevail (see my other note).
>>
>> My offer of signature should in no way be interpreted as reflecting an opinion
>> about Marshall's character.
> 
> Ditto, and Ditto. 

+1 and +1.

Henk


-- 
------------------------------------------------------------------------------
Henk Uijterwaal                           Email: henk(at)uijterwaal.nl
                                          http://www.uijterwaal.nl
                                          Phone: +31.6.55861746
------------------------------------------------------------------------------

Read my blog at http://www.uijterwaal.nl/henks_hands.html

From David.Rudin@microsoft.com  Thu Nov  1 14:24:14 2012
Return-Path: <David.Rudin@microsoft.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 16A4921F9405; Thu,  1 Nov 2012 14:24:14 -0700 (PDT)
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 2XgUYRS4b-7c; Thu,  1 Nov 2012 14:24:13 -0700 (PDT)
Received: from NA01-BL2-obe.outbound.protection.outlook.com (na01-bl2-obe.ptr.protection.outlook.com [65.55.169.23]) by ietfa.amsl.com (Postfix) with ESMTP id 49DC421F9412; Thu,  1 Nov 2012 14:24:11 -0700 (PDT)
Received: from BL2FFO11FD005.protection.gbl (10.173.161.204) by BL2FFO11HUB010.protection.gbl (10.173.161.112) with Microsoft SMTP Server (TLS) id 15.0.545.8; Thu, 1 Nov 2012 21:24:07 +0000
Received: from TK5EX14HUBC103.redmond.corp.microsoft.com (131.107.125.37) by BL2FFO11FD005.mail.protection.outlook.com (10.173.161.1) with Microsoft SMTP Server (TLS) id 15.0.545.8 via Frontend Transport; Thu, 1 Nov 2012 21:24:08 +0000
Received: from TK5EX14MBXC263.redmond.corp.microsoft.com ([169.254.3.178]) by TK5EX14HUBC103.redmond.corp.microsoft.com ([157.54.86.9]) with mapi id 14.02.0318.003; Thu, 1 Nov 2012 21:23:25 +0000
From: "David Rudin (LCA)" <David.Rudin@microsoft.com>
To: IETF Chair <chair@ietf.org>, IETF <ietf@ietf.org>
Subject: RE: Antitrust FAQ
Thread-Topic: Antitrust FAQ
Thread-Index: AQHNp2JYYOqB6ypQT0mA6Fv/PBEIlpfVncog
Date: Thu, 1 Nov 2012 21:23:24 +0000
Deferred-Delivery: Thu, 1 Nov 2012 21:23:17 +0000
Message-ID: <B68EFB284B10C249835C566A0CE08AA2370EFDCD@TK5EX14MBXC263.redmond.corp.microsoft.com>
References: <AFB9BEA6-579B-4E26-A512-BE271D234F85@ietf.org>
In-Reply-To: <AFB9BEA6-579B-4E26-A512-BE271D234F85@ietf.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.76]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(377454001)(13464001)(164054002)(48376001)(47446002)(5343655001)(74662001)(51856001)(46102001)(49866001)(16406001)(76482001)(53806001)(31966008)(4396001)(50986001)(44976002)(15202345001)(47976001)(47736001)(54316001)(550184003)(54356001)(74502001)(50466001)(47776002)(33656001); DIR:OUT; LANG:en; 
X-OriginatorOrg: microsoft.onmicrosoft.com
X-Forefront-PRVS: 0652EA5565
X-Mailman-Approved-At: Fri, 02 Nov 2012 08:14:00 -0700
Cc: Jorge Contreras <contreraslegal@att.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Nov 2012 21:24:15 -0000

At a high level, I'm curious what the difference is between an FAQ and a fo=
rmal policy?  I ask since Section 6 of the FAQ seems to be providing instru=
ctions on how IETF participants should conduct themselves, which seems more=
 like a policy than an FAQ.

Thanks,

David

-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of IET=
F Chair
Sent: Wednesday, October 10, 2012 8:41 PM
To: IETF
Cc: Jorge Contreras
Subject: Antitrust FAQ

The IETF does not have a formal antitrust policy.  In fact, the ANTITRUST B=
OF concluded that a formal policy was not needed.  However, educational mat=
erial is needed so that all IETF participants are aware of the the law.  Th=
e first draft of a FAQ to fill this need has been developed.  Please review=
 the FAQ, and if you discover any issues raise them in response to this mes=
sage.

http://www.ietf.org/playground/antitrust-faq.html

Thanks,
  Russ

From paitken@cisco.com  Thu Nov  1 13:20:53 2012
Return-Path: <paitken@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4404921F96B1; Thu,  1 Nov 2012 13:20:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.476
X-Spam-Level: 
X-Spam-Status: No, score=-10.476 tagged_above=-999 required=5 tests=[AWL=0.123, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 pSo95KN78kM4; Thu,  1 Nov 2012 13:20:52 -0700 (PDT)
Received: from ams-iport-4.cisco.com (ams-iport-4.cisco.com [144.254.224.147]) by ietfa.amsl.com (Postfix) with ESMTP id C063F21F96B8; Thu,  1 Nov 2012 13:20:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=262; q=dns/txt; s=iport; t=1351801249; x=1353010849; h=message-id:date:from:mime-version:to:subject: content-transfer-encoding; bh=mVLJLJfEXQcZBiWpE5hJNQZb93ktscf/y51NiuXQT9c=; b=eDA+h1m6iIW3v/IYQwNxseUz1ifjDCCQ6aXIA6SfwY7EFsim0aYEbF9V Bidh/jOGZu1bjcbywkPLNQ3RkxA9JxZDPq9cNw3KZIl/tr6DjaIV3cMA+ ke+oisGeKmO0n82+hivychdQRvqyc7xmUTFxFfdA/FMyXQ1dhEvjHmPme 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAHbYklCQ/khN/2dsb2JhbABEgyzAQ4EIgjcBFBE2Cj0PBxgDAgECAUwMCAEBHodknGOgLo8UgyIDlXiFaohugWuCbw
X-IronPort-AV: E=Sophos;i="4.80,695,1344211200";  d="scan'208";a="9284774"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-4.cisco.com with ESMTP; 01 Nov 2012 20:20:47 +0000
Received: from [10.61.102.64] (dhcp-10-61-102-64.cisco.com [10.61.102.64]) by ams-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id qA1KKkAt000828; Thu, 1 Nov 2012 20:20:46 GMT
Message-ID: <5092D99F.3070601@cisco.com>
Date: Thu, 01 Nov 2012 20:20:47 +0000
From: Paul Aitken <paitken@cisco.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:15.0) Gecko/20120912 Thunderbird/15.0.1
MIME-Version: 1.0
To: ietf@ietf.org, mailman-owner@ietf.org
Subject: mailing list memberships reminder -> passwords in the clear
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Fri, 02 Nov 2012 08:20:32 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Nov 2012 20:20:53 -0000

Why does the "mailing list memberships reminder" send passwords in the 
clear?

For everything else I'm subscribed to, if I forget my details, one click 
sends a one-time password-reset link.
Passwords are never mailed out, and never shown.

Thanks,
P.

From johnl@iecc.com  Fri Nov  2 08:25:11 2012
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 93E9F21F89AD for <ietf@ietfa.amsl.com>; Fri,  2 Nov 2012 08:25:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.698
X-Spam-Level: 
X-Spam-Status: No, score=-111.698 tagged_above=-999 required=5 tests=[AWL=0.501, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, RCVD_IN_DNSWL_LOW=-1, 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 FqD7cJ3Gvlxx for <ietf@ietfa.amsl.com>; Fri,  2 Nov 2012 08:25:10 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id DF97021F87C3 for <ietf@ietf.org>; Fri,  2 Nov 2012 08:25:09 -0700 (PDT)
Received: (qmail 9125 invoked from network); 2 Nov 2012 15:25:07 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 2 Nov 2012 15:25:07 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=5093e5d3.xn--i8sz2z.k1211; i=johnl@user.iecc.com; bh=aRfTnDU9PUoIVaz/9nRxPlbYfa2+JWF7VeBGlL33C9g=; b=RDSq9v27vxPSWl1Yc4SwXmrpnoDWpEZrCoNuBSpQ/W4UdduYvlsu1D4mUDkWLiP511gx8FtMQ26YQKk40+sTGnAB3e9PHcZaiGWon/wdciGBV/diZ6T7FhqtN95qmkbdTXfUhI0l2pdWtFNGmbB53qqbJJlW9oS/4eo8epFQp0A=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=5093e5d3.xn--i8sz2z.k1211; olt=johnl@user.iecc.com; bh=aRfTnDU9PUoIVaz/9nRxPlbYfa2+JWF7VeBGlL33C9g=; b=EWgbJR91ccfXXmpzWCuzotYtFSCzEzyQKGl9sb4+wonNqYSVttm4HREoCIGTmSKV8ww0xaYzuUKrc9tTI7eyr+Jxaa8Azp0SvsKiNuWI7RDTs7qRB5whgTnRXt2IxhoXRxsW49amUCyVKx6VBUd58MugaptUowoWQIfSNJLQ+oI=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 2 Nov 2012 15:24:45 -0000
Message-ID: <20121102152445.92153.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: mailing list memberships reminder -> passwords in the clear
In-Reply-To: <5092D99F.3070601@cisco.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Cc: paitken@cisco.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Nov 2012 15:25:11 -0000

In article <5092D99F.3070601@cisco.com> you write:
>Why does the "mailing list memberships reminder" send passwords in the 
>clear?

Because that's what Mailman does.  Send code.

-- 
Regards,
John Levine, johnl@iecc.com, Primary Perpetrator of "The Internet for Dummies",
Please consider the environment before reading this e-mail. http://jl.ly

From listsebby@me.com  Fri Nov  2 08:39:22 2012
Return-Path: <listsebby@me.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A6FD21F8BBE; Fri,  2 Nov 2012 08:39:22 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3Fs7R6CqWAiL; Fri,  2 Nov 2012 08:39:21 -0700 (PDT)
Received: from nk11p04mm-asmtp006.mac.com (nk11p04mm-asmtp006.mac.com [17.158.236.241]) by ietfa.amsl.com (Postfix) with ESMTP id BE1B521F8B74; Fri,  2 Nov 2012 08:39:21 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII
Received: from [192.168.1.5] (natbox.sabahattin-gucukoglu.com [213.123.192.30]) by nk11p04mm-asmtp006.mac.com (Oracle Communications Messaging Server 7u4-24.01(7.0.4.24.0) 64bit (built Jan 3 2012)) with ESMTPSA id <0MCV00KJBA560A60@nk11p04mm-asmtp006.mac.com>; Fri, 02 Nov 2012 15:39:08 +0000 (GMT)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.7.7855,1.0.431,0.0.0000 definitions=2012-11-02_03:2012-11-02, 2012-11-02, 1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 suspectscore=2 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=6.0.2-1203120001 definitions=main-1211020145
Subject: Re: mailing list memberships reminder -> passwords in the clear
From: Sabahattin Gucukoglu <listsebby@me.com>
In-reply-to: <5092D99F.3070601@cisco.com>
Date: Fri, 02 Nov 2012 15:39:05 +0000
Message-id: <C94D122B-A7AB-4676-93B3-52BA925C72EA@me.com>
References: <5092D99F.3070601@cisco.com>
To: Paul Aitken <paitken@cisco.com>
X-Mailer: Apple Mail (2.1499)
Cc: mailman-owner@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Nov 2012 15:39:22 -0000

On 1 Nov 2012, at 20:20, Paul Aitken <paitken@cisco.com> wrote:
> Why does the "mailing list memberships reminder" send passwords in the clear?

Because mailman is brain-dead stupid.  See:
http://www.jwz.org/doc/mailman.html

Sadly, and despite my best efforts to find alternative mailing list software, mailman wins on popularity (ugh) and hence support with practically no competition.  Only majordomo2, which has been unmaintained for a while now (and it's author calls it "Dead" holds much of a chance, but I doubt it would work for the IETF in its current condition.

But have hope!  The IETF serves the mailman interface over TLS, and it is an option that you can exercise *not* to have passwords mailed to you.  Go to your membership options page, and in the group containing the option to turn off the membership reminders, check the checkbox to make it global.  Later, you can have the password mailed to you on demand, or unsubscribe without needing a password at all (email confirmation loop).

> For everything else I'm subscribed to, if I forget my details, one click sends a one-time password-reset link.
> Passwords are never mailed out, and never shown.

Yes.  Sadly this isn't possible with mailman; you will always be mailed your password if you need it and can't remember it.

HTH.

Cheers,
Sabahattin


From brescia74@verizon.net  Fri Nov  2 09:56:35 2012
Return-Path: <brescia74@verizon.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE0C921F8DE5 for <ietf@ietfa.amsl.com>; Fri,  2 Nov 2012 09:56:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.56
X-Spam-Level: 
X-Spam-Status: No, score=-0.56 tagged_above=-999 required=5 tests=[AWL=2.039,  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 t2M2GiBAc7T8 for <ietf@ietfa.amsl.com>; Fri,  2 Nov 2012 09:56:34 -0700 (PDT)
Received: from vms173009pub.verizon.net (vms173009pub.verizon.net [206.46.173.9]) by ietfa.amsl.com (Postfix) with ESMTP id 84F4521F896F for <ietf@ietf.org>; Fri,  2 Nov 2012 09:56:34 -0700 (PDT)
Received: from danteb.home ([unknown] [173.76.32.111]) by vms173009.mailsrvcs.net (Sun Java(tm) System Messaging Server 7u2-7.02 32bit (built Apr 16 2009)) with ESMTPA id <0MCV008BTDPY8F90@vms173009.mailsrvcs.net> for ietf@ietf.org; Fri, 02 Nov 2012 11:56:23 -0500 (CDT)
Content-type: text/plain; charset=us-ascii
MIME-version: 1.0 (Apple Message framework v1085)
Subject: Re: mailing list memberships reminder -> passwords in the clear
From: Mike Brescia <brescia74@verizon.net>
In-reply-to: <20121102152445.92153.qmail@joyce.lan>
Date: Fri, 02 Nov 2012 12:56:21 -0400
Content-transfer-encoding: quoted-printable
Message-id: <CC06371D-FBC5-449E-BCD6-C23553444FF6@verizon.net>
References: <20121102152445.92153.qmail@joyce.lan>
To: ietf@ietf.org
X-Mailer: Apple Mail (2.1085)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Nov 2012 16:56:36 -0000

Apparently no need to "send code".  Mailman project claims this is fixed =
in development version 3 (not yet released)

discussion on plain text passwords
http://mail.python.org/pipermail/mailman-users/2010-July/069844.html

project todo list
http://wiki.list.org/display/DEV/Mailman+3.0
(down under privacy, claims passwords will not be /en clair/)

On Nov 2, 2012, at 11:24 AM, John Levine wrote:

> In article <5092D99F.3070601@cisco.com> you write:
>> Why does the "mailing list memberships reminder" send passwords in =
the=20
>> clear?
>=20
> Because that's what Mailman does.  Send code.
>=20
> --=20
> Regards,
> John Levine, johnl@iecc.com, Primary Perpetrator of "The Internet for =
Dummies",
> Please consider the environment before reading this e-mail. =
http://jl.ly


From daedulus@btconnect.com  Fri Nov  2 11:07:12 2012
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE5891F0C5C for <ietf@ietfa.amsl.com>; Fri,  2 Nov 2012 11:07:12 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Fxt71TnogdIj for <ietf@ietfa.amsl.com>; Fri,  2 Nov 2012 11:07:12 -0700 (PDT)
Received: from va3outboundpool.messaging.microsoft.com (va3ehsobe003.messaging.microsoft.com [216.32.180.13]) by ietfa.amsl.com (Postfix) with ESMTP id E1D7B21F8858 for <ietf@ietf.org>; Fri,  2 Nov 2012 11:07:11 -0700 (PDT)
Received: from mail216-va3-R.bigfish.com (10.7.14.249) by VA3EHSOBE004.bigfish.com (10.7.40.24) with Microsoft SMTP Server id 14.1.225.23; Fri, 2 Nov 2012 18:07:10 +0000
Received: from mail216-va3 (localhost [127.0.0.1])	by mail216-va3-R.bigfish.com (Postfix) with ESMTP id 22A9B8402A5	for <ietf@ietf.org>; Fri,  2 Nov 2012 18:07:10 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.253.197; KIP:(null); UIP:(null); IPV:NLI; H:DBXPRD0710HT005.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -24
X-BigFish: PS-24(zz9371I936eI542M1432Izz1de0h1202h1d1ah1d2ahzz1033IL17326ah8275dhz2dh2a8h5a9h668h839hd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h304l1155h)
Received: from mail216-va3 (localhost.localdomain [127.0.0.1]) by mail216-va3 (MessageSwitch) id 1351879627361084_27597; Fri,  2 Nov 2012 18:07:07 +0000 (UTC)
Received: from VA3EHSMHS027.bigfish.com (unknown [10.7.14.251])	by mail216-va3.bigfish.com (Postfix) with ESMTP id 4B777180053	for <ietf@ietf.org>; Fri,  2 Nov 2012 18:07:07 +0000 (UTC)
Received: from DBXPRD0710HT005.eurprd07.prod.outlook.com (157.56.253.197) by VA3EHSMHS027.bigfish.com (10.7.99.37) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 2 Nov 2012 18:07:02 +0000
Received: from AMSPRD0510HT004.eurprd05.prod.outlook.com (157.56.248.53) by pod51017.outlook.com (10.255.79.168) with Microsoft SMTP Server (TLS) id 14.16.233.3; Fri, 2 Nov 2012 18:06:39 +0000
Message-ID: <028101cdb924$b77260a0$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: <ietf@ietf.org>
References: <20121024213116.29724.2375.idtracker@ietfa.amsl.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-ipv6-pw-lsp-ping-03.txt> (LabelSwitched Path (LSP) Ping for IPv6 Pseudowire FECs) toProposed Standard
Date: Fri, 2 Nov 2012 18:05:53 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [157.56.248.53]
X-OriginatorOrg: btconnect.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Nov 2012 18:07:12 -0000

I worry about the allocation of sub-TLVs in this I-D.

It calls for
"The following Sub-TLV changes, which comprise three updates and two
   additions, are made for two TLV Types in the aforementioned sub-
   registry: TLV Type 1 for "Target FEC Stack", and TLV Type 21 for
   "Reply Path"."
and it is the Type 21 that worries me.

IANA has, for Type 21,

Reply Path (TEMPORARY - expires 2012-01-20)
[draft-ietf-mpls-return-path-specified-lsp-ping]

and I am unclear what the rules are about updates to expired, TEMPORARY,
allocations.

I worry too that
[draft-ietf-mpls-return-path-specified-lsp-ping]
while confirming the reservation of Type 21 takes a different tack for
sub-TLVs, namely
"
According to the guidelines defined in [RFC5226], the sub-TLV range
   of Reply Path TLV are partitioned as following:
   0-31743 - Reserved, and MUST NOT be allocated."
so quite what this I-D will do to that I-D worries me.

And I worry yet more that other I-Ds, such as
draft-zjns-mpls-lsp-ping-relay-reply-00
are heading down the track with further updates in this area of the MPLS
namespace (except that this particular one seems to have abandoned
sub-TLVs).

Tom Petch

----- Original Message -----
From: "The IESG" <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
Cc: <mpls@ietf.org>
Sent: Wednesday, October 24, 2012 9:31 PM

>
> The IESG has received a request from the Multiprotocol Label Switching
WG
> (mpls) to consider the following document:
> - 'Label Switched Path (LSP) Ping for IPv6 Pseudowire FECs'
>   <draft-ietf-mpls-ipv6-pw-lsp-ping-03.txt> as Proposed Standard
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2012-11-09. Exceptionally, comments may
be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>
> Abstract
>
>    Multi-Protocol Label Switching (MPLS) Label Switched Path (LSP)
Ping
>    and traceroute mechanisms are commonly used to detect and isolate
>    data plane failures in all MPLS LSPs including Pseudowire (PW)
LSPs.
>    The PW LSP Ping and traceroute elements, however, are not specified
>    for IPv6 address usage.
>
>    This document extends the PW LSP Ping and traceroute mechanisms so
>    they can be used with IPv6 PWs, and updates RFC 4379.
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-mpls-ipv6-pw-lsp-ping/
>
> IESG discussion can be tracked via
>
http://datatracker.ietf.org/doc/draft-ietf-mpls-ipv6-pw-lsp-ping/ballot/
>
>
> No IPR declarations have been submitted directly on this I-D.
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
>



From jnc@mercury.lcs.mit.edu  Fri Nov  2 12:09:32 2012
Return-Path: <jnc@mercury.lcs.mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0CBCF1F0C7F for <ietf@ietfa.amsl.com>; Fri,  2 Nov 2012 12:09:32 -0700 (PDT)
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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jR340nOFgty9 for <ietf@ietfa.amsl.com>; Fri,  2 Nov 2012 12:09:31 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 8F0531F0C59 for <ietf@ietf.org>; Fri,  2 Nov 2012 12:09:31 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 94B2A18C0DC; Fri,  2 Nov 2012 15:09:30 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: I* Member Removal Process
Message-Id: <20121102190930.94B2A18C0DC@mercury.lcs.mit.edu>
Date: Fri,  2 Nov 2012 15:09:30 -0400 (EDT)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Nov 2012 19:09:32 -0000

    > From: Russ Housley <housley@vigilsec.com>

    > And, the community does not have rough consensus for simply declaring
    > his seat vacant under the current set of BCPs. 

Why not, I cannot fathom, because as SM has pointed out (hat tip), RFC 4333,
"IAOC Member Selection Guidelines and Process", has text which is exactly on
point:

    >> "if the appointed member is unable to serve the full two-year term,
    >> the selecting body may, at its discretion, immediately select a
    >> replacement to serve the remainder of the term using the interim
    >> process defined in Section 3.5.1."

The document doesn't define in detail what constitutes "unable to serve", but
it clearly means via some form of incapacitation (death, severe illness,
etc). Obviously, the intent of leaving un-stated exactly what constituted
"unable to serve the full two-year term" was that it would be determined by
common sense, applying the "unable to serve" test to the facts at hand.

He's clearly "unable to serve". I find it hard to see how someone who will
not respond to _any_ form of communication, over a period of months, is
'[]able to serve'.

If the _only_ way to determine that someone is "unable to serve the full
two-year term" is via the recall process, why didn't the document say that?
There is just the bald statement that 'if someone is "unable to serve", a
replacment can be selected using the same process that selected them'.

And he's definitely "unable to serve". But I guess the IETF would rather
deploy the most onerous, heavy-weight bureacratic process it can find (one
intended for entirely different circumstances), as opposed to using the
capability _already in its process documents exactly for cases like this_.

	Noel

From dhc@dcrocker.net  Fri Nov  2 12:21:16 2012
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF93F1F0C69 for <ietf@ietfa.amsl.com>; Fri,  2 Nov 2012 12:21:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.878
X-Spam-Level: 
X-Spam-Status: No, score=-4.878 tagged_above=-999 required=5 tests=[AWL=0.078,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, RCVD_IN_NJABL_PROXY=1.643]
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 2hIPK4FCoW9b for <ietf@ietfa.amsl.com>; Fri,  2 Nov 2012 12:21:16 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 2E6011F0C61 for <ietf@ietf.org>; Fri,  2 Nov 2012 12:21:16 -0700 (PDT)
Received: from [192.168.1.9] (adsl-67-127-56-94.dsl.pltn13.pacbell.net [67.127.56.94]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id qA2JLE8o006276 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 2 Nov 2012 12:21:14 -0700
Message-ID: <50941D22.6090309@dcrocker.net>
Date: Fri, 02 Nov 2012 12:21:06 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Subject: Re: I* Member Removal Process
References: <20121102190930.94B2A18C0DC@mercury.lcs.mit.edu>
In-Reply-To: <20121102190930.94B2A18C0DC@mercury.lcs.mit.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Fri, 02 Nov 2012 12:21:15 -0700 (PDT)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Nov 2012 19:21:17 -0000

On 11/2/2012 12:09 PM, Noel Chiappa wrote:
>      >> "if the appointed member is unable to serve the full two-year term,
>      >> the selecting body may, at its discretion, immediately select a
>      >> replacement to serve the remainder of the term using the interim
>      >> process defined in Section 3.5.1."
>
> The document doesn't define in detail what constitutes "unable to serve", but

Rhat is the specific and entire point.  We have a substantial set of 
formal details, but we don't have that one.


> it clearly means via some form of incapacitation (death, severe illness,
> etc). Obviously, the intent of leaving un-stated exactly what constituted
> "unable to serve the full two-year term" was that it would be determined by
> common sense, applying the "unable to serve" test to the facts at hand.

Your certitude about the intent of the framers and ratifiers of these 
formal documents is appealing, but unfortunately unfounded, since there 
is no documentation about that intent.

Worse, it's not clear to me that even knowing their/our intent would 
suffice, in terms of being subject to external review for due process.


> He's clearly "unable to serve".

So you believe.  I might also.  He might or might not.


> I find it hard to see how someone who will
> not respond to _any_ form of communication, over a period of months, is
> '[]able to serve'.

And more's the pity that our documents didn't cover such constructive 
resignation by voluntary vacancy.


> If the _only_ way to determine that someone is "unable to serve the full
> two-year term" is via the recall process, why didn't the document say that?
> There is just the bald statement that 'if someone is "unable to serve", a
> replacment can be selected using the same process that selected them'.

The problem is that the document doesn't specify anything about the 
conditions that define being unable to serve.  The nature of this sort 
of formal document requires such specificity.

d/
-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From cpignata@cisco.com  Fri Nov  2 12:21:49 2012
Return-Path: <cpignata@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 885721F0C91 for <ietf@ietfa.amsl.com>; Fri,  2 Nov 2012 12:21:49 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JIDV8BFWDzxs for <ietf@ietfa.amsl.com>; Fri,  2 Nov 2012 12:21:48 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id 953BF1F0C92 for <ietf@ietf.org>; Fri,  2 Nov 2012 12:21:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3746; q=dns/txt; s=iport; t=1351884108; x=1353093708; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=X0L8yO1swy8fpnNqx1VX46QbPcvNApimQqzV5eBcZQs=; b=WJTm1Jz4Mym07ZkPmXw3ba08g3YSnBvqUuQtgXNOqJY823nZDdAnxwJG bdjYnGuxTdHD+/8ZdOPyo8Aetn6NCJVDgIiZdHR+ftGaecnr16TzFL6PY 8JUxQpyRTiGyrgyxQug8L4rXrBhHeHF8XqCZYqNYpMN7WsarOIW1F+uNd U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EALUclFCtJXHA/2dsb2JhbABEw0OBCIIeAQEBAwEBAQEPAVsLBQcEAgEIFQEMGQsnCyUCBA4FCBqHYgYLm3ugFIwAhVphA4gljnCNPYFrgm+BWyAEGg
X-IronPort-AV: E=Sophos;i="4.80,701,1344211200"; d="scan'208";a="138327821"
Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by rcdn-iport-4.cisco.com with ESMTP; 02 Nov 2012 19:21:48 +0000
Received: from xhc-aln-x05.cisco.com (xhc-aln-x05.cisco.com [173.36.12.79]) by rcdn-core2-5.cisco.com (8.14.5/8.14.5) with ESMTP id qA2JLmVA016907 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 2 Nov 2012 19:21:48 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.217]) by xhc-aln-x05.cisco.com ([173.36.12.79]) with mapi id 14.02.0318.001; Fri, 2 Nov 2012 14:21:47 -0500
From: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
To: "t.p." <daedulus@btconnect.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-ipv6-pw-lsp-ping-03.txt> (LabelSwitched Path (LSP) Ping for IPv6 Pseudowire FECs) toProposed Standard
Thread-Topic: [mpls] Last Call: <draft-ietf-mpls-ipv6-pw-lsp-ping-03.txt> (LabelSwitched Path (LSP) Ping for IPv6 Pseudowire FECs) toProposed Standard
Thread-Index: AQHNuS9MVc5AuOc7m0iTDidpCmaHwg==
Date: Fri, 2 Nov 2012 19:21:46 +0000
Message-ID: <95067C434CE250468B77282634C96ED320D66DBC@xmb-aln-x02.cisco.com>
References: <20121024213116.29724.2375.idtracker@ietfa.amsl.com> <028101cdb924$b77260a0$4001a8c0@gateway.2wire.net>
In-Reply-To: <028101cdb924$b77260a0$4001a8c0@gateway.2wire.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.150.54.2]
x-tm-as-product-ver: SMEX-10.2.0.1135-7.000.1014-19332.000
x-tm-as-result: No--65.701700-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <7BB4EB349C65504E8EBAF49071E765F3@cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Nov 2012 19:21:49 -0000

Tom,

On Nov 2, 2012, at 2:05 PM, t.p. <daedulus@btconnect.com> wrote:

> I worry about the allocation of sub-TLVs in this I-D.
>=20

Thanks for the comments. I share worries about keeping synchronicity betwee=
n sub-registries in this fashion.

> It calls for
> "The following Sub-TLV changes, which comprise three updates and two
>   additions, are made for two TLV Types in the aforementioned sub-
>   registry: TLV Type 1 for "Target FEC Stack", and TLV Type 21 for
>   "Reply Path"."
> and it is the Type 21 that worries me.
>=20

Right -- the allocations under Type 1 are straightforward. But the allocati=
ons under Type 21 seem to be standing over quicksand.

> IANA has, for Type 21,
>=20
> Reply Path (TEMPORARY - expires 2012-01-20)
> [draft-ietf-mpls-return-path-specified-lsp-ping]
>=20
> and I am unclear what the rules are about updates to expired, TEMPORARY,
> allocations.
>=20
> I worry too that
> [draft-ietf-mpls-return-path-specified-lsp-ping]
> while confirming the reservation of Type 21 takes a different tack for
> sub-TLVs, namely
> "
> According to the guidelines defined in [RFC5226], the sub-TLV range
>   of Reply Path TLV are partitioned as following:
>   0-31743 - Reserved, and MUST NOT be allocated."
> so quite what this I-D will do to that I-D worries me.
>=20

Perhaps the best approach is to decouple. Have all Type 21 allocations unde=
r draft-ietf-mpls-return-path-specified-lsp-ping and have that point to the=
 RFC from draft-ietf-mpls-ipv6-pw-lsp-ping if needed (and it can take a sna=
pshot of the sub-registry when it will be stable.)

Thanks,

-- Carlos.

> And I worry yet more that other I-Ds, such as
> draft-zjns-mpls-lsp-ping-relay-reply-00
> are heading down the track with further updates in this area of the MPLS
> namespace (except that this particular one seems to have abandoned
> sub-TLVs).
>=20
> Tom Petch
>=20
> ----- Original Message -----
> From: "The IESG" <iesg-secretary@ietf.org>
> To: "IETF-Announce" <ietf-announce@ietf.org>
> Cc: <mpls@ietf.org>
> Sent: Wednesday, October 24, 2012 9:31 PM
>=20
>>=20
>> The IESG has received a request from the Multiprotocol Label Switching
> WG
>> (mpls) to consider the following document:
>> - 'Label Switched Path (LSP) Ping for IPv6 Pseudowire FECs'
>>  <draft-ietf-mpls-ipv6-pw-lsp-ping-03.txt> as Proposed Standard
>>=20
>> The IESG plans to make a decision in the next few weeks, and solicits
>> final comments on this action. Please send substantive comments to the
>> ietf@ietf.org mailing lists by 2012-11-09. Exceptionally, comments may
> be
>> sent to iesg@ietf.org instead. In either case, please retain the
>> beginning of the Subject line to allow automated sorting.
>>=20
>> Abstract
>>=20
>>   Multi-Protocol Label Switching (MPLS) Label Switched Path (LSP)
> Ping
>>   and traceroute mechanisms are commonly used to detect and isolate
>>   data plane failures in all MPLS LSPs including Pseudowire (PW)
> LSPs.
>>   The PW LSP Ping and traceroute elements, however, are not specified
>>   for IPv6 address usage.
>>=20
>>   This document extends the PW LSP Ping and traceroute mechanisms so
>>   they can be used with IPv6 PWs, and updates RFC 4379.
>>=20
>>=20
>> The file can be obtained via
>> http://datatracker.ietf.org/doc/draft-ietf-mpls-ipv6-pw-lsp-ping/
>>=20
>> IESG discussion can be tracked via
>>=20
> http://datatracker.ietf.org/doc/draft-ietf-mpls-ipv6-pw-lsp-ping/ballot/
>>=20
>>=20
>> No IPR declarations have been submitted directly on this I-D.
>> _______________________________________________
>> mpls mailing list
>> mpls@ietf.org
>> https://www.ietf.org/mailman/listinfo/mpls
>>=20
>=20
>=20


From turchanyi.geza@gmail.com  Fri Nov  2 12:22:18 2012
Return-Path: <turchanyi.geza@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 46D0D11E80E2 for <ietf@ietfa.amsl.com>; Fri,  2 Nov 2012 12:22:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.446
X-Spam-Level: 
X-Spam-Status: No, score=-3.446 tagged_above=-999 required=5 tests=[AWL=0.152,  BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 v3jKWqvKxgic for <ietf@ietfa.amsl.com>; Fri,  2 Nov 2012 12:22:17 -0700 (PDT)
Received: from mail-da0-f44.google.com (mail-da0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id 51BAA11E80DC for <ietf@ietf.org>; Fri,  2 Nov 2012 12:22:17 -0700 (PDT)
Received: by mail-da0-f44.google.com with SMTP id h15so1772302dan.31 for <ietf@ietf.org>; Fri, 02 Nov 2012 12:22:12 -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 :cc:content-type; bh=Ntf5KNpuGY1+6CAwcOD62SBftps2JF1QkUA/NO2BeoM=; b=uVbNh3XO/yPMx0Sluy5t7t7dhEuQsFAzbub4quB8bPsEPwx1MTkYX2VOFYULdOb7Ws QT3asojVqjRZdhtUTgLFmfLsrK74Z7AI59tPc/1t2u2XOO3HRh9UAmvObr2om+fGb4CM 9WDn3ZXrlQyeOFecO8iicGdLEVY+hGWLH5yeJSsNhfX28MVftd/fXI/77nNyx5FEGttI q1cnC20MN6KCegAzlguDulPEWuejj9Rqtuq2GHf+dDVR7r9QmtTPWf6wzZuwnNgZ6LuM MkfNS/rpGIJ5913SbDOp6yrNiOHtRNyibpKL1kj+n21MXM+BIoyFSlSms9Kpsv5PnC5y dY6g==
MIME-Version: 1.0
Received: by 10.68.190.71 with SMTP id go7mr9071886pbc.66.1351884132534; Fri, 02 Nov 2012 12:22:12 -0700 (PDT)
Received: by 10.66.19.135 with HTTP; Fri, 2 Nov 2012 12:22:12 -0700 (PDT)
In-Reply-To: <20121102190930.94B2A18C0DC@mercury.lcs.mit.edu>
References: <20121102190930.94B2A18C0DC@mercury.lcs.mit.edu>
Date: Fri, 2 Nov 2012 20:22:12 +0100
Message-ID: <CAJfR-+N9pU4cp6pWWFyoce+01v4ukOMc8gukt3Sayzy21jSKZw@mail.gmail.com>
Subject: Re: I* Member Removal Process
From: Turchanyi Geza <turchanyi.geza@gmail.com>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Content-Type: multipart/alternative; boundary=e89a8ff1cb367f48c604cd880d4b
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Nov 2012 19:22:18 -0000

--e89a8ff1cb367f48c604cd880d4b
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Noel,

On Fri, Nov 2, 2012 at 8:09 PM, Noel Chiappa <jnc@mercury.lcs.mit.edu>wrote=
:

>
>
....


> And he's definitely "unable to serve". But I guess the IETF would rather
> deploy the most onerous, heavy-weight bureacratic process it can find (on=
e
> intended for entirely different circumstances), as opposed to using the
> capability _already in its process documents exactly for cases like this_=
.
>
>         Noel
>

Marshall was clearly unable to serve in the past three months. The question
is: Would it be possible for him to return within a couple of weeks, or not=
.

I wish he could. However, this is unclear for me and I has no information
at all.

Best,

G=E9za

--e89a8ff1cb367f48c604cd880d4b
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Noel,<br><br><div class=3D"gmail_quote">On Fri, Nov 2, 2012 at 8:09 PM, Noe=
l Chiappa <span dir=3D"ltr">&lt;<a href=3D"mailto:jnc@mercury.lcs.mit.edu" =
target=3D"_blank">jnc@mercury.lcs.mit.edu</a>&gt;</span> wrote:<br><blockqu=
ote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc s=
olid;padding-left:1ex">
=A0=A0 <br></blockquote><div>....<br>=A0<br></div><blockquote class=3D"gmai=
l_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left=
:1ex">
And he&#39;s definitely &quot;unable to serve&quot;. But I guess the IETF w=
ould rather<br>
deploy the most onerous, heavy-weight bureacratic process it can find (one<=
br>
intended for entirely different circumstances), as opposed to using the<br>
capability _already in its process documents exactly for cases like this_.<=
br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
=A0 =A0 =A0 =A0 Noel<br>
</font></span></blockquote></div><br>Marshall was clearly unable to serve i=
n the past three months. The question is: Would it be possible for him to r=
eturn within a couple of weeks, or not.<br><br>I wish he could. However, th=
is is unclear for me and I has no information at all. <br>
<br>Best,<br><br>G=E9za<br>

--e89a8ff1cb367f48c604cd880d4b--

From johnl@taugh.com  Fri Nov  2 12:56:38 2012
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7DE3011E80E2 for <ietf@ietfa.amsl.com>; Fri,  2 Nov 2012 12:56:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.256
X-Spam-Level: 
X-Spam-Status: No, score=-2.256 tagged_above=-999 required=5 tests=[AWL=0.345,  BAYES_00=-2.599, NO_RELAYS=-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 cApHOCtsZ4nD for <ietf@ietfa.amsl.com>; Fri,  2 Nov 2012 12:56:38 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id A1CAA11E80BF for <ietf@ietf.org>; Fri,  2 Nov 2012 12:56:37 -0700 (PDT)
Received: (qmail 97430 invoked from network); 2 Nov 2012 19:56:36 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:vbr-info:user-agent:cleverness; s=17c94.50942574.k1211; bh=WUIKVnnvqBY1TZBUVmZzS7O6LcUgB2nbgo+uo33rWME=; b=E2fr1azV3T0NgoRFBlY3F6oErEPySvwzOUEWnLkG5ElGs8ORAr9d6Ixq0Q0/rxn3VgQqvAbf3OxS3XZ1JbYY9D+hqfxDrMkckuJKLRz6i5LF/ocS8HDcC7H7fLcqi3qu7D2Vw0QZKQZoz1Ah7N2FV1Crag7Az5B+5R95yrN1eIU=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:vbr-info:user-agent:cleverness; s=17c94.50942574.k1211; bh=WUIKVnnvqBY1TZBUVmZzS7O6LcUgB2nbgo+uo33rWME=; b=IxEMmr5mM0sG9d9xYL931gwgcH24QLQQ68pfvs8/gBJMsd2768rXPtDZrwcdD3x1PXWXAPxU5A9KQLz7Ef2/GNpGRhfiTsW1NNZ0dy0NdgpNCM4LlvVYnokL1q4B30R+YuXIZi5M4rBDB3K/IUCdDcJQ14M5tROQ+xsX7FguL2k=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Received: (ofmipd 127.0.0.1); 2 Nov 2012 19:56:13 -0000
Date: 2 Nov 2012 15:56:35 -0400
Message-ID: <alpine.BSF.2.00.1211021552460.97859@joyce.lan>
From: "John R Levine" <johnl@taugh.com>
To: "Paul Aitken" <paitken@cisco.com>
Subject: Re: mailing list memberships reminder -> passwords in the clear
In-Reply-To: <5094215B.6000502@cisco.com>
References: <20121102152445.92153.qmail@joyce.lan> <5094215B.6000502@cisco.com>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Nov 2012 19:56:38 -0000

>>> Why does the "mailing list memberships reminder" send passwords in the 
>>> clear?
>> Because that's what Mailman does.  Send code.
>
> And that's acceptable to the IETF? You're kidding me, right?

I can't speak for the IETF, but I do note that the same password notices 
have been going out on the first of every month for years.  You just 
noticed iit now?

And once again, if you think it should do something else, send code. 
We're volunteers here.  Assertions that it is very important for someone 
else to do work that you're not prepared to do are rarely effective.

R's,
John


From bob.hinden@gmail.com  Fri Nov  2 13:28:43 2012
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 546BF21F9A32 for <ietf@ietfa.amsl.com>; Fri,  2 Nov 2012 13:28:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.635
X-Spam-Level: 
X-Spam-Status: No, score=-103.635 tagged_above=-999 required=5 tests=[AWL=-0.036, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, 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 ZCnGgBZZVyrD for <ietf@ietfa.amsl.com>; Fri,  2 Nov 2012 13:28:42 -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 C43B021F9A30 for <ietf@ietf.org>; Fri,  2 Nov 2012 13:28:42 -0700 (PDT)
Received: by mail-pb0-f44.google.com with SMTP id ro8so2688764pbb.31 for <ietf@ietf.org>; Fri, 02 Nov 2012 13:28:42 -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 :content-transfer-encoding:message-id:references:to:x-mailer; bh=hohEtgKeDVNnjhHypoHaV0Lmk5+I9b/JmdZKkDUoBfY=; b=vOPfPHTiet6vhYpdkuQvQrgjyq67eyvlLqFTIJWH2hgWfqHEUUSG4m0ItVmMge/BHw wPJaBuN8VilZg3WeO2x81oEABwRAeSrzwIXlJn20tOTzeSH7qDaO9B2MkuANUCk07vgg RznKrv7wRfrOBSwcUhp0FfuUV7PT0OZ3aYaD+he/BWzeUg+myDl7tmkrDC/QFo6ZnpOm 3NpPg7RbMVXakjeRFXhfDPUT5l3De3mjvorVaDmcH8noWdzblmcXDf/SBcV3raNVL1Sj Ha2RkkyztKOGRFNW66R6JiVTVVy2dnGrBwOJlmYkUs6lAs1eB7hQ5S+Xi4dkV+g5LImv LoUg==
Received: by 10.68.193.163 with SMTP id hp3mr9501775pbc.21.1351888122575; Fri, 02 Nov 2012 13:28:42 -0700 (PDT)
Received: from [172.16.224.219] ([209.97.127.34]) by mx.google.com with ESMTPS id uh10sm1501067pbc.35.2012.11.02.13.28.40 (version=SSLv3 cipher=OTHER); Fri, 02 Nov 2012 13:28:41 -0700 (PDT)
Subject: Re: I* Member Removal Process
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=us-ascii
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <9C68ED55-C21C-465A-9478-F0F165F0EC09@vigilsec.com>
Date: Fri, 2 Nov 2012 13:28:39 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <82C6DD58-5479-4729-B03C-D04DAA6DFD94@gmail.com>
References: <50919671.6000605@ogud.com> <7F4FE714-DEDC-4D64-ADD8-AA6ECF53EABB@NLnetLabs.nl> <5092D9DB.4070602@cisco.com> <tsltxt980bc.fsf@mit.edu> <3153B2FE-4B52-43AF-AD10-6701CFFE0AB8@gmail.com> <20121102022203.9C7A721F96EC@ietfa.amsl.com> <34363E27-E2DE-4BEB-AB4F-3000CB571DA3@vigilsec.com> <20121102043542.A69E39A4002@odin.smetech.net> <9C68ED55-C21C-465A-9478-F0F165F0EC09@vigilsec.com>
To: Russ Housley <housley@vigilsec.com>
X-Mailer: Apple Mail (2.1283)
Cc: Bob Hinden <bob.hinden@gmail.com>, IETF-Discussion list <ietf@ietf.org>, Olafur Gudmundsson <ogud@ogud.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Nov 2012 20:28:43 -0000

On Nov 1, 2012, at 9:52 PM, Russ Housley wrote:

> Mike:
>=20
>> Yup.  But I'd say their wishes would have a great deal of influence =
on whether or not this would go forward.  And I'd still like to get at =
least some indication that this is their desired outcome at this point.  =
I think, if nothing else, this needs to be part of whatever record =
considered by a recall committee.  If I heard that only 1 or 2 members =
were indicating support for removal, I probably would withdraw my name =
from the petition signature.
>=20
> The IAOC was unanimous (minus Marshall, of course) in asking the =
community to declare the seat vacant.  A vote was taken, and the minutes =
will confirm what I have stated here when they are published.

The results of the E-Vote taking this action are included below.  As =
stated these will be included in the minutes of the 25 October 2012 IAOC =
call.

Bob


>=20
> From: Bob Hinden <bob.hinden@gmail.com>
> Subject: Results of IAOC E-Vote to Approve sending an email about the =
IAOC Vacancy to IETF Announce
> Date: October 22, 2012 8:08:27 AM PDT
> To: iaoc@ietf.org
> Cc: Bob Hinden <bob.hinden@gmail.com>
>=20
> The results of the E-Vote to Approve sending an email about the IAOC =
Vacancy to IETF Announce mailing list are:
>=20
> Ole Jacobsen       [YES]   October 17, 2012 11:30:31 PM GMT+02:00
> Scott Bradner      [YES]   October 17, 2012 11:46:31 PM GMT+02:00
> Russ Housley       [YES]   October 18, 2012 12:02:00 AM GMT+02:00
> Bob Hinden         [YES]   October 18, 2012 6:18:34 AM GMT+02:00
> Bernard Aboba      [YES]   October 18, 2012 7:22:48 PM GMT+02:00
> Dave Crocker       [YES]   October 18, 2012 7:24:17 PM GMT+02:00
> Lynn St. Amour     [YES]   October 19, 2012 6:55:06 PM EDT
> Marshall Eubanks   [   ]
>=20
> The E-Vote passes.  The results of the e-vote will be recorded in the =
minutes of the IAOC call being scheduled for 25 October 2012.
>=20
> The IOAC chair is authorized to send the attached email to the IETF =
announce list on Monday October 22, 2012.
>=20
> Bob Hinden
> IAOC Chair=20
>=20
>=20
> On Oct 17, 2012, at 11:24 PM, Bob Hinden wrote:
>=20
>> IAOC,
>>=20
>> This is an official IAOC E-Vote, to close on Monday 22 October 2012 =
at 10am EST.  A minimum of a 3/4 majority of the IAOC voting Yes is =
required for the motion to pass.
>>=20
>> RESOLUTION
>>=20
>>  The IAOC approves send a message to the IETF-Announce list asking =
the community to
>>  declare Marshall Eubanks position on the IAOC vacant.  A draft of =
the email is
>>  attached to this E-Vote.
>>=20
>> Please let me know your vote by responding to this message to the =
full IAOC list.
>>=20
>> You may vote Yes (in favor approving the resolution), No (opposed), =
or you may formally abstain. =20
>>=20
>> Passing the resolution requires both a quorum and a 3/4 majority of =
the IAOC voting Yes.  The motion will pass if this is reached on or =
before the closing date.  The results of the E-Vote will be recorded =
into the minutes of the next IAOC meeting.
>>=20
>> Regards,
>>=20
>> Bob Hinden
>> IAOC Chair
>>=20
>>=20
>> Bernard Aboba      [ ]
>> Lynn St. Amour     [ ]
>> Scott Bradner      [ ]
>> Dave Crocker       [ ]
>> Marshall Eubanks   [ ]
>> Bob Hinden         [ ]
>> Russ Housley       [ ]
>> Ole Jacobsen       [ ]
>>=20
>>=20
>> --------------
>>=20
>=20

From johnl@iecc.com  Fri Nov  2 14:51:59 2012
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B259621F9AC7 for <ietf@ietfa.amsl.com>; Fri,  2 Nov 2012 14:51:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.841
X-Spam-Level: 
X-Spam-Status: No, score=-111.841 tagged_above=-999 required=5 tests=[AWL=0.358, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, RCVD_IN_DNSWL_LOW=-1, 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 Ks+hPyjog5hv for <ietf@ietfa.amsl.com>; Fri,  2 Nov 2012 14:51:59 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id D98D421F9AC6 for <ietf@ietf.org>; Fri,  2 Nov 2012 14:51:58 -0700 (PDT)
Received: (qmail 32046 invoked from network); 2 Nov 2012 21:51:56 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 2 Nov 2012 21:51:56 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=5094407c.xn--yuvv84g.k1211; i=johnl@user.iecc.com; bh=4kUEwwN8Xm3ufwTGjM6pckzXs2yckBk5TaMen7MX7Ug=; b=1IobSBAmTI9BnkwZ0Q34TPcz6RrRcGYtLGLv5NPAlZyBMIM9Dgf2wIf60UYHiKimftAQmd2tJ4m3vmHrEmVtQkv2T96GTjtqlFvyza0oJHMvIst1B1pG1wxrGv4IajEG8fy6MQL14SdwQa3JYMaiyEulTIPan2A8594HsSsilVo=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=5094407c.xn--yuvv84g.k1211; olt=johnl@user.iecc.com; bh=4kUEwwN8Xm3ufwTGjM6pckzXs2yckBk5TaMen7MX7Ug=; b=P44iafUAUi5EgKX8feGTN+tE8/s4LvArfGi+Vf+PEYWvk0K3lHHvWCnh9dWCVTSAQknfo7zdtrj5hT2np5CgJV22fwLQ9A6JMj0Bu9N2mIxlVa0xpjQdu1Na43DtZri1Ck2BVzVBdLzqZ+6dcxTP8h88t2G7+5R1q7hu4FB+5i4=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 2 Nov 2012 21:51:34 -0000
Message-ID: <20121102215134.5156.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: mailing list memberships reminder -> passwords in the clear
In-Reply-To: <C94D122B-A7AB-4676-93B3-52BA925C72EA@me.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Nov 2012 21:51:59 -0000

> Only majordomo2, which has been unmaintained for a while now (and
>it's author calls it "Dead" holds much of a chance, but I doubt it
?would work for the IETF in its current condition.

Actually, MJ2 works great, I've been using it in production for years,
but I agree that we'd need to locate a perl weenie willing to make
tweaks, and it's probably not enough better than MM to be worth the
pain of switching.

> Sadly this isn't possible with mailman; you will always be mailed
> your password if you need it and can't remember it.

If you use a high value password for your IETF list subscriptions, you
have deeper security issues than a few tweaks to mail software can fix.

R's,
John

PS: I saw a description of mailman2 by one of the developers last week.
It's really not that different, although he mentioned that the monthly
reminders are now off by default.


From sm@elandsys.com  Fri Nov  2 15:05:43 2012
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC51A11E80F9 for <ietf@ietfa.amsl.com>; Fri,  2 Nov 2012 15:05:43 -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=-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 2pPgplSclBmu; Fri,  2 Nov 2012 15:05:42 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id D575711E80F1; Fri,  2 Nov 2012 15:05:41 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.226.235.33]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id qA2M5T6m013359 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 2 Nov 2012 15:05:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1351893940; bh=zoGhfuFhwAdm90IXTDJgImqfO7wAgxwGKmElwqnWUF8=; h=Date:To:From:Subject:Cc; b=z2OPclTQXcwBrTIC/ZBKTFSh5WX9jIKkCjDoAEO89hc7ZcDiPgbZGfpNIQXlRDOIl ugH16bt68dZvMARryhPJO0kFGRpHQdoKqe5l9fgeAWqQpvuTSujxDfZ6tic7DHKG7w MQaOamHbryP+rBezUAsTCxhFFrq7bwk3LzhcUwsk=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1351893940; i=@elandsys.com; bh=zoGhfuFhwAdm90IXTDJgImqfO7wAgxwGKmElwqnWUF8=; h=Date:To:From:Subject:Cc; b=xfAJ/XiF+W6PRquprK57lSSd+pA90Y3qOYTUyjXvMmP2ZguVknHkDU7bnB/Z4bjqK /E+yM/eg935toZtWS6NmIxDwMJ36ra7dDpjwkCuq/uAVd6elG4Pqd02iZltJeN/B1L 8fKoP4ycW82yKGLhL5fmo+meOdPcJyTaADqzB78Q=
Message-Id: <6.2.5.6.2.20121102140657.0ae94a28@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 02 Nov 2012 14:47:30 -0700
To: nomcom-chair@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Selection of a replacement IAOC member
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Nov 2012 22:05:44 -0000

Hello,

The IAOC Chair posted a message about the IAOC appointing a 
replacement liaison to the IETF NomCom after learning from the NomCom 
chair that Marshall had not responded to emails from the NomCom chair. [1]

According to BCP 113:

   "However, if the appointed member is unable to serve the full
    two-year term, the selecting body may, at its discretion,
    immediately select a replacement to serve the remainder of the
    term using the interim process defined in Section 3.5.1."

Mr Marshall Eubanks was selected by the 2011-2012 IETF Nominating 
Committee [2].  Given that Mr Marshall Eubanks has not responded to 
emails from the NomCom Chair it would appreciated if NomCom could determine:

  (a) Whether the appointed member is unable to serve the full two-year term

  (b) Select a replacement to serve the remainder of the term using the
      interim process

Regards,
S. Moonesamy

1. http://www.ietf.org/mail-archive/web/ietf-announce/current/msg10812.html
2. https://datatracker.ietf.org/ann/nomcom/3291/


From barryleiba.mailing.lists@gmail.com  Fri Nov  2 17:15:51 2012
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 74BF01F0C90 for <ietf@ietfa.amsl.com>; Fri,  2 Nov 2012 17:15:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.088
X-Spam-Level: 
X-Spam-Status: No, score=-103.088 tagged_above=-999 required=5 tests=[AWL=-0.112, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, 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 orr2IYWwXxVU; Fri,  2 Nov 2012 17:15:50 -0700 (PDT)
Received: from mail-la0-f44.google.com (mail-la0-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id 4D8361F0C8F; Fri,  2 Nov 2012 17:15:50 -0700 (PDT)
Received: by mail-la0-f44.google.com with SMTP id b11so3194004lam.31 for <multiple recipients>; Fri, 02 Nov 2012 17:15:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=9VYY/4qWKnUd4Y176x0yLXadPl8/iZeH6F1iZ0tZFZQ=; b=Z+hRlQ/f0QxobRoAE/rn3sTaQY/AZBhvpHyfuItCwdMZa9+OY45+61OFOMWImISWh+ 14jtznwMxjwp0RDbtM06zRziqwCcziqIv3NoOs6tF4K8pR+25tNMgaSI/H8M2ORAUifC Gdv26Ds1Ld1O4f9xlxJQLV6y3YiKJUz16/4hDX2tnxQStjzsRm3H+RLR0ucJwzSGH1/d P9N2Pcm63ItOQbYxwwsYlrtt35CyVD8YC7y2NppdkDlOMXGLdTVQLQ+kIIItB/hiBv6D /NbXLXhFKseyAE3rJXQO2N2qRc1RZ5TKAPsMorvHKB1/ic/qNZOJ2LZpWmUyG910/ibk Nwxw==
MIME-Version: 1.0
Received: by 10.112.101.133 with SMTP id fg5mr1418577lbb.3.1351901749097; Fri, 02 Nov 2012 17:15:49 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.112.99.131 with HTTP; Fri, 2 Nov 2012 17:15:49 -0700 (PDT)
In-Reply-To: <6.2.5.6.2.20121102140657.0ae94a28@elandnews.com>
References: <6.2.5.6.2.20121102140657.0ae94a28@elandnews.com>
Date: Fri, 2 Nov 2012 20:15:49 -0400
X-Google-Sender-Auth: AE1OBrxKWg-a4bRweLl6gMpqVAU
Message-ID: <CAC4RtVDbMYGtvpaHLNXvAAE6oYpvopqmKssgCZ5FN0kC=69mtA@mail.gmail.com>
Subject: Re: Selection of a replacement IAOC member
From: Barry Leiba <barryleiba@computer.org>
To: S Moonesamy <sm+ietf@elandsys.com>
Content-Type: multipart/alternative; boundary=f46d040169fd86b6c304cd8c274b
Cc: "ietf@ietf.org" <ietf@ietf.org>, "nomcom-chair@ietf.org" <nomcom-chair@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Nov 2012 00:15:51 -0000

--f46d040169fd86b6c304cd8c274b
Content-Type: text/plain; charset=ISO-8859-1

>
>  it would appreciated if NomCom could determine:
>
>  (a) Whether the appointed member is unable to serve the full two-year term
>

This is decidedly NOT something that any process empowers the NomCom chair
to do.  Matt could certainly give his opinion as an individual, but I can't
see under what process it would have any official weight.

Barry

--f46d040169fd86b6c304cd8c274b
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">=A0it would appreciated if NomCom could dete=
rmine:<br>
<br>
=A0(a) Whether the appointed member is unable to serve the full two-year te=
rm<br>
</blockquote><div><br></div><div>This is decidedly NOT something that any p=
rocess empowers the NomCom chair to do. =A0Matt could certainly give his op=
inion as an individual, but I can&#39;t see under what process it would hav=
e any official weight.</div>
<div><br></div><div>Barry=A0<span></span></div>

--f46d040169fd86b6c304cd8c274b--

From sm@elandsys.com  Fri Nov  2 18:29:12 2012
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B0B961F0C97 for <ietf@ietfa.amsl.com>; Fri,  2 Nov 2012 18:29:12 -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=[AWL=0.000, 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 quGJkwwWmv6Q for <ietf@ietfa.amsl.com>; Fri,  2 Nov 2012 18:29:12 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 260201F0C5F for <ietf@ietf.org>; Fri,  2 Nov 2012 18:29:12 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.226.235.33]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id qA31Sso3025151 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 2 Nov 2012 18:29:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1351906145; bh=55kKiEijEHrxBkAJjbJt1GcNGSQ1F5ewWDysTxGjq9c=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=4O2D65RbfdtUOwdLBqeM5gKdvFzut7lEtrjPXBUPECf8jvZOzoqVYNdRyCIUnf3di 6rl1BB785q9nFM7637W1JSaLitnZFCZVAdR1GHgPunZN7Z5nH+nr4GTISbrQFlKuw5 p5VnW2DeJumLPwDwkCm9pB/4WiwxRBXy4bxXPLpk=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1351906145; i=@elandsys.com; bh=55kKiEijEHrxBkAJjbJt1GcNGSQ1F5ewWDysTxGjq9c=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=j8+4EeyBJ9nt4Gdv1D9+dwff8nSAfiwANXnOzndbKbiQ459Soxk9yasaEAvTOX8ge Z/Ti9Ri/MvcRrcFCj3GxAFQ3LS70ijrbz4gdTw5zLsfANVX+NK3ul0LuqGU7VZPOSJ 8zxchy56SdcJZ4GYi0+/oFPNQgUKyamu63vSBdHw=
Message-Id: <6.2.5.6.2.20121102172404.0a671538@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 02 Nov 2012 18:14:55 -0700
To: Barry Leiba <barryleiba@computer.org>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Selection of a replacement IAOC member
In-Reply-To: <CAC4RtVDbMYGtvpaHLNXvAAE6oYpvopqmKssgCZ5FN0kC=69mtA@mail.g mail.com>
References: <6.2.5.6.2.20121102140657.0ae94a28@elandnews.com> <CAC4RtVDbMYGtvpaHLNXvAAE6oYpvopqmKssgCZ5FN0kC=69mtA@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Nov 2012 01:29:12 -0000

Hi Barry,
At 17:15 02-11-2012, Barry Leiba wrote:
>This is decidedly NOT something that any process empowers the NomCom 
>chair to do.  Matt could certainly give his opinion as an 
>individual, but I can't see under what process it would have any 
>official weight.

I mentioned NomCom instead of NomCom Chair as that's the selecting 
body.  These individuals have been selected according to the 
algorithm from RFC 3797 [1].  None of these individuals are members 
of the IAB, IESG or IAOC.

My request does not prevent the Member Recall petition from being 
pursued.  For the sake of disclosure, I do not have any interest in 
common with the IAOC member except for IETF participation.  The 
request was not discussed with anybody.  I am deferring to the 
nominating committee to see whether BCP 113 is applicable, and if so, 
take whatever action it deems appropriate.

Regards,
S. Moonesamy

1. https://datatracker.ietf.org/ann/nomcom/50952/


From dhc@dcrocker.net  Fri Nov  2 19:38:47 2012
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0AE611F0CA1 for <ietf@ietfa.amsl.com>; Fri,  2 Nov 2012 19:38:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.93
X-Spam-Level: 
X-Spam-Status: No, score=-4.93 tagged_above=-999 required=5 tests=[AWL=0.026,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, RCVD_IN_NJABL_PROXY=1.643]
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 WB8G6VlXnDi1; Fri,  2 Nov 2012 19:38:46 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 3648C1F0C9C; Fri,  2 Nov 2012 19:38:46 -0700 (PDT)
Received: from [192.168.1.9] (adsl-67-127-56-94.dsl.pltn13.pacbell.net [67.127.56.94]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id qA32cXMS013376 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 2 Nov 2012 19:38:33 -0700
Message-ID: <509483A2.6080608@dcrocker.net>
Date: Fri, 02 Nov 2012 19:38:26 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Selection of a replacement IAOC member
References: <6.2.5.6.2.20121102140657.0ae94a28@elandnews.com>
In-Reply-To: <6.2.5.6.2.20121102140657.0ae94a28@elandnews.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Fri, 02 Nov 2012 19:38:34 -0700 (PDT)
Cc: ietf@ietf.org, nomcom-chair@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Nov 2012 02:38:47 -0000

On 11/2/2012 2:47 PM, S Moonesamy wrote:
>  it would appreciated if NomCom could
> determine:
>
>   (a) Whether the appointed member is unable to serve the full two-year
> term


Nomcom has no authority to make that determination.


d/

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From sob@sobco.com  Sat Nov  3 05:39:44 2012
Return-Path: <sob@sobco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0327E21F97C5 for <ietf@ietfa.amsl.com>; Sat,  3 Nov 2012 05:39:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.06
X-Spam-Level: 
X-Spam-Status: No, score=-0.06 tagged_above=-999 required=5 tests=[AWL=0.279,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  RDNS_NONE=0.1, SUBJECT_FUZZY_TION=0.156]
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 n9qO9cfrMpLb for <ietf@ietfa.amsl.com>; Sat,  3 Nov 2012 05:39:43 -0700 (PDT)
Received: from sobco.sobco.com (unknown [136.248.127.164]) by ietfa.amsl.com (Postfix) with ESMTP id 660AC21F976D for <ietf@ietf.org>; Sat,  3 Nov 2012 05:39:43 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by sobco.sobco.com (Postfix) with ESMTP id 1F97E339A0A; Sat,  3 Nov 2012 08:39:42 -0400 (EDT)
X-Virus-Scanned: amavisd-new at sobco.com
Received: from sobco.sobco.com ([127.0.0.1]) by localhost (sobco.sobco.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dkAVdkNeYW1T; Sat,  3 Nov 2012 08:39:41 -0400 (EDT)
Received: from golem.sobco.com (golem.sobco.com [136.248.127.162]) by sobco.sobco.com (Postfix) with ESMTPSA id 9E8D73399FB; Sat,  3 Nov 2012 08:39:41 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: Recall petition for Mr. Marshall Eubanks
From: Scott O Bradner <sob@sobco.com>
In-Reply-To: <20121102022203.9C7A721F96EC@ietfa.amsl.com>
Date: Sat, 3 Nov 2012 08:39:41 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <EAC8CA28-6A93-41C7-93B3-035DC4EE2293@sobco.com>
References: <50919671.6000605@ogud.com> <7F4FE714-DEDC-4D64-ADD8-AA6ECF53EABB@NLnetLabs.nl> <5092D9DB.4070602@cisco.com> <tsltxt980bc.fsf@mit.edu> <3153B2FE-4B52-43AF-AD10-6701CFFE0AB8@gmail.com> <20121102022203.9C7A721F96EC@ietfa.amsl.com>
To: Michael StJohns <mstjohns@comcast.net>
X-Mailer: Apple Mail (2.1499)
Cc: IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Nov 2012 12:39:44 -0000

I have not "signed" the petition because I did not think it was proper =
to do so (as a IAOC member - see Russ's message and RFC 3777)

but, that aside, I do support the petition - I feel that the IAOC has =
given Marshal
the full opportunity to start participating again or to resign and he =
has done neither -
it is time to move

Scott

On Nov 1, 2012, at 10:22 PM, Michael StJohns <mstjohns@comcast.net> =
wrote:

> At 06:01 PM 11/1/2012, Bob Hinden wrote:
>=20
>=20
>> While the IAOC has not discussed this formally, I agree with you.  =
The situation did change when we were able to talk with Marshall.
>=20
>=20
>=20
>=20
> I assume at this point the IAOC would like to pursue the recall =
option?  If not, please be very clear about it to the list as I haven't =
actually seen a request from the IAOC for that process to proceed as far =
as I can tell.
>=20
> If you'd rather just wait from him to resign, if in fact he does, then =
please indicate that.  I believe neither you nor Dave Crocker nor Scott =
Bradner (the only IOAC members that I think have commented on this issue =
on list so far) have actually specifically asked for or signed the =
recall on the list.=20
>=20
> Mike
>=20
>=20
>=20
>=20
>=20
>> I too hope he will resign.
>>=20
>> Bob
>=20
>=20


From bob.hinden@gmail.com  Sat Nov  3 06:04:45 2012
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E59221F9C69 for <ietf@ietfa.amsl.com>; Sat,  3 Nov 2012 06:04:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.521
X-Spam-Level: 
X-Spam-Status: No, score=-103.521 tagged_above=-999 required=5 tests=[AWL=-0.078, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, SUBJECT_FUZZY_TION=0.156, 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 Bee-bW0L54Nx for <ietf@ietfa.amsl.com>; Sat,  3 Nov 2012 06:04:44 -0700 (PDT)
Received: from mail-wg0-f44.google.com (mail-wg0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id 9C84921F9C67 for <ietf@ietf.org>; Sat,  3 Nov 2012 06:04:38 -0700 (PDT)
Received: by mail-wg0-f44.google.com with SMTP id dr13so2087725wgb.13 for <ietf@ietf.org>; Sat, 03 Nov 2012 06:04:37 -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 :content-transfer-encoding:message-id:references:to:x-mailer; bh=xs5YZVGZXF2RuJsZ8a0FRs8XsHDJy+tUvG0pLAFMhOg=; b=UqRa/wpFadbwEl6oKho4EAxZ6JYfyLC9vKpXiCczMblemywmqstlP9B3TlJ6L/PHrH cIwT2bkYKymQyDyJtzdEjnek1JLOGXJvLk/JMbBIqqAeoOBdEA0A3h50LPW/SGl/6HNs HtfozxO+9xdfs5zQ0+qs1ctQKb/v0sebfzegomhkmB4QCgYUtvz9Rj5+Hd7kLuIZbVNI YlfQJGyyeSyg6tO7M7/RnjvFlXkGtDTtuNlTZhTnO9bJge3xpePXn/X1eMHTGqlxA0QI zQv0aWjheSaNDH+Jt6YIwYUHmCPPKuZRtV5t8NcjNjS6URFbmjyBSkvbAniMRkX3uz+n yvzg==
Received: by 10.180.77.38 with SMTP id p6mr6354794wiw.1.1351947877625; Sat, 03 Nov 2012 06:04:37 -0700 (PDT)
Received: from ?IPv6:2601:9:4080:10:95f8:94cc:2698:2929? ([2601:9:4080:10:95f8:94cc:2698:2929]) by mx.google.com with ESMTPS id fp6sm2332097wib.0.2012.11.03.06.04.35 (version=SSLv3 cipher=OTHER); Sat, 03 Nov 2012 06:04:37 -0700 (PDT)
Subject: Re: Recall petition for Mr. Marshall Eubanks
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=us-ascii
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <EAC8CA28-6A93-41C7-93B3-035DC4EE2293@sobco.com>
Date: Sat, 3 Nov 2012 06:04:34 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <7ACF3421-C206-4DC1-845F-9C9041B74C62@gmail.com>
References: <50919671.6000605@ogud.com> <7F4FE714-DEDC-4D64-ADD8-AA6ECF53EABB@NLnetLabs.nl> <5092D9DB.4070602@cisco.com> <tsltxt980bc.fsf@mit.edu> <3153B2FE-4B52-43AF-AD10-6701CFFE0AB8@gmail.com> <20121102022203.9C7A721F96EC@ietfa.amsl.com> <EAC8CA28-6A93-41C7-93B3-035DC4EE2293@sobco.com>
To: Scott O Bradner <sob@sobco.com>
X-Mailer: Apple Mail (2.1283)
Cc: Bob Hinden <bob.hinden@gmail.com>, IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Nov 2012 13:04:45 -0000

On Nov 3, 2012, at 5:39 AM, Scott O Bradner wrote:

>=20
> I have not "signed" the petition because I did not think it was proper =
to do so (as a IAOC member - see Russ's message and RFC 3777)
>=20
> but, that aside, I do support the petition - I feel that the IAOC has =
given Marshal
> the full opportunity to start participating again or to resign and he =
has done neither -
> it is time to move

+1

Bob


>=20
> Scott
>=20
> On Nov 1, 2012, at 10:22 PM, Michael StJohns <mstjohns@comcast.net> =
wrote:
>=20
>> At 06:01 PM 11/1/2012, Bob Hinden wrote:
>>=20
>>=20
>>> While the IAOC has not discussed this formally, I agree with you.  =
The situation did change when we were able to talk with Marshall.
>>=20
>>=20
>>=20
>>=20
>> I assume at this point the IAOC would like to pursue the recall =
option?  If not, please be very clear about it to the list as I haven't =
actually seen a request from the IAOC for that process to proceed as far =
as I can tell.
>>=20
>> If you'd rather just wait from him to resign, if in fact he does, =
then please indicate that.  I believe neither you nor Dave Crocker nor =
Scott Bradner (the only IOAC members that I think have commented on this =
issue on list so far) have actually specifically asked for or signed the =
recall on the list.=20
>>=20
>> Mike
>>=20
>>=20
>>=20
>>=20
>>=20
>>> I too hope he will resign.
>>>=20
>>> Bob
>>=20
>>=20
>=20


From john-ietf@jck.com  Sat Nov  3 06:07:28 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 04FFB21F9C6A for <ietf@ietfa.amsl.com>; Sat,  3 Nov 2012 06:07:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.374
X-Spam-Level: 
X-Spam-Status: No, score=-101.374 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DATE_IN_PAST_06_12=1.069, SUBJECT_FUZZY_TION=0.156, 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 zIQPsM+u3eaf for <ietf@ietfa.amsl.com>; Sat,  3 Nov 2012 06:07:27 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 8266521F9C64 for <ietf@ietf.org>; Sat,  3 Nov 2012 06:07:27 -0700 (PDT)
Received: from localhost ([::1]) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1TUdRY-000FpU-7p; Sat, 03 Nov 2012 09:07:20 -0400
Date: Fri, 02 Nov 2012 22:03:08 -0400
From: John C Klensin <john-ietf@jck.com>
To: Michael StJohns <mstjohns@comcast.net>, Bob Hinden <bob.hinden@gmail.com>,  Sam Hartman <hartmans-ietf@mit.edu>
Subject: Re: Recall petition for Mr. Marshall Eubanks
Message-ID: <1F2808D4F3783CA802322A8F@JCK-EEE10>
In-Reply-To: <20121102022203.9C7A721F96EC@ietfa.amsl.com>
References: <50919671.6000605@ogud.com> <7F4FE714-DEDC-4D64-ADD8-AA6ECF53EABB@NLnetLabs.nl> <5092D9DB.4070602@cisco.com> <tsltxt980bc.fsf@mit.edu> <3153B2FE-4B52-43AF-AD10-6701CFFE0AB8@gmail.com> <20121102022203.9C7A721F96EC@ietfa.amsl.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: 'IETF-Discussion list' <ietf@ietf.org>, Olafur Gudmundsson <ogud@ogud.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Nov 2012 13:07:28 -0000

--On Thursday, 01 November, 2012 22:22 -0400 Michael StJohns
<mstjohns@comcast.net> wrote:

> I assume at this point the IAOC would like to pursue the
> recall option?  If not, please be very clear about it to the
> list as I haven't actually seen a request from the IAOC for
> that process to proceed as far as I can tell.

Because I am personally very reluctant to see this handled by
recall, I want to ask a slightly different question:  Are the
people who met with Marshall convinced that he understood that,
if he did not resign, a recall was almost certain to be
initiated as our next step.  If the answer is "yes", he's made
his choice and I am ok with signing the petition.   If not, it
is possible that more discussion would be in order after the
petition process is complete.

I hope that, when Lynn accepts the petitions, another effort (or
several) will be made to et Marshall's attention -- it
presumably is not too late for him to resign until after the
relevant committee is appointed.

   john






From warren@kumari.net  Sat Nov  3 06:54:48 2012
Return-Path: <warren@kumari.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F2C1E21F9C35 for <ietf@ietfa.amsl.com>; Sat,  3 Nov 2012 06:54:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.521
X-Spam-Level: 
X-Spam-Status: No, score=-102.521 tagged_above=-999 required=5 tests=[AWL=0.078, 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 g0mei72n32Kd for <ietf@ietfa.amsl.com>; Sat,  3 Nov 2012 06:54:47 -0700 (PDT)
Received: from vimes.kumari.net (smtp1.kumari.net [204.194.22.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A0DB21F981A for <ietf@ietf.org>; Sat,  3 Nov 2012 06:54:47 -0700 (PDT)
Received: from dhcp-6418.meeting.ietf.org (unknown [130.129.100.24]) by vimes.kumari.net (Postfix) with ESMTPSA id 121E21B404E9; Sat,  3 Nov 2012 09:54:42 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: [IETF] Re: mailing list memberships reminder -> passwords in the clear
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <alpine.BSF.2.00.1211021552460.97859@joyce.lan>
Date: Sat, 3 Nov 2012 09:54:38 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <E9E028C3-F874-42BF-B5DD-8C14D43ACC8F@kumari.net>
References: <20121102152445.92153.qmail@joyce.lan> <5094215B.6000502@cisco.com> <alpine.BSF.2.00.1211021552460.97859@joyce.lan>
To: "John R Levine" <johnl@taugh.com>
X-Mailer: Apple Mail (2.1499)
Cc: Paul Aitken <paitken@cisco.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Nov 2012 13:54:48 -0000

On Nov 2, 2012, at 3:56 PM, "John R Levine" <johnl@taugh.com> wrote:

>>>> Why does the "mailing list memberships reminder" send passwords in =
the clear?
>>> Because that's what Mailman does.  Send code.
>>=20
>> And that's acceptable to the IETF? You're kidding me, right?
>=20
> I can't speak for the IETF, but I do note that the same password =
notices have been going out on the first of every month for years.  You =
just noticed iit now?
>=20

The mailman webUI (e.g: https://www.ietf.org/mailman/listinfo/ietf ) =
says:

"You may enter a privacy password below. This provides only mild =
security, but should prevent others from messing with your subscription. =
Do not use a valuable password as it will occasionally be emailed back =
to you in cleartext.

If you choose not to enter a password, one will be automatically =
generated for you, and it will be sent to you once you've confirmed your =
subscription. You can always request a mail-back of your password when =
you edit your personal options. Once a month, your password will be =
emailed to you as a reminder."

W

> And once again, if you think it should do something else, send code. =
We're volunteers here.  Assertions that it is very important for someone =
else to do work that you're not prepared to do are rarely effective.
>=20
> R's,
> John
>=20

--
Don't be impressed with unintelligible stuff said condescendingly.
    -- Radia Perlman.






From paitken@cisco.com  Fri Nov  2 12:39:11 2012
Return-Path: <paitken@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9BD111F0C8B for <ietf@ietfa.amsl.com>; Fri,  2 Nov 2012 12:39:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.523
X-Spam-Level: 
X-Spam-Status: No, score=-10.523 tagged_above=-999 required=5 tests=[AWL=0.076, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 evhoR7RzmWtk for <ietf@ietfa.amsl.com>; Fri,  2 Nov 2012 12:39:10 -0700 (PDT)
Received: from ams-iport-3.cisco.com (ams-iport-3.cisco.com [144.254.224.146]) by ietfa.amsl.com (Postfix) with ESMTP id EAF1D1F0C7E for <ietf@ietf.org>; Fri,  2 Nov 2012 12:39:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=210; q=dns/txt; s=iport; t=1351885150; x=1353094750; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=sIZ7vKVt6mnazR3CGqDyyKhG7fPzDHB+W7ZspyLywUE=; b=WBUQ6PXT+dkgtOaAmSPxFDscoznCXYe2a1HdkuUwAumsSFp/iKSEPTCz +KeVLcD2ZkgXmqyGtrYa+X3M9P5APDKiqhRA1t9ZRC/1ll8/ltEq2o0W4 UzwleJeVsmhwQJbZK4jDuGQ3d+EiC9KXFFTygSGeKRgy/G++nN7+qbP4E U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAFAB8glFCQ/khM/2dsb2JhbABEhhe9LIEIgh4BAQEDARIBEAQRNgoBEAsaAgUWCwICCQMCAQIBRQYNAQcBAR6HYgacAI0pkmmBIJAIgRMDlXmFa4hugWuCbw
X-IronPort-AV: E=Sophos;i="4.80,701,1344211200";  d="scan'208";a="9301337"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-3.cisco.com with ESMTP; 02 Nov 2012 19:39:07 +0000
Received: from [10.61.101.56] (dhcp-10-61-101-56.cisco.com [10.61.101.56]) by ams-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id qA2Jd7UJ009910; Fri, 2 Nov 2012 19:39:07 GMT
Message-ID: <5094215B.6000502@cisco.com>
Date: Fri, 02 Nov 2012 19:39:07 +0000
From: Paul Aitken <paitken@cisco.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:15.0) Gecko/20120912 Thunderbird/15.0.1
MIME-Version: 1.0
To: John Levine <johnl@taugh.com>
Subject: Re: mailing list memberships reminder -> passwords in the clear
References: <20121102152445.92153.qmail@joyce.lan>
In-Reply-To: <20121102152445.92153.qmail@joyce.lan>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Sat, 03 Nov 2012 08:24:21 -0700
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Nov 2012 19:39:11 -0000

John,

>> Why does the "mailing list memberships reminder" send passwords in the clear?
> Because that's what Mailman does.  Send code.

And that's acceptable to the IETF? You're kidding me, right?

P.

From paitken@cisco.com  Fri Nov  2 12:39:34 2012
Return-Path: <paitken@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C5BD51F0C71; Fri,  2 Nov 2012 12:39:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.529
X-Spam-Level: 
X-Spam-Status: No, score=-10.529 tagged_above=-999 required=5 tests=[AWL=0.070, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 ESxzQ0bDOZTo; Fri,  2 Nov 2012 12:39:34 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by ietfa.amsl.com (Postfix) with ESMTP id B64B71F0C61; Fri,  2 Nov 2012 12:39:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1779; q=dns/txt; s=iport; t=1351885174; x=1353094774; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=FrQ3olyvYMlR7AaOPV2eL1xGvla+s5RUXE6j0VwNfcg=; b=TMEzqtvaIIfdt/4Dus/2kNT9l9ZAOp5zBBgLQCKjr7TqqMw8ZcRrk0ws r8m2Ji96We48WYJ1842ODgipCVgdngI1vFDw1MXW9U8jdS2V4hMbB/Eu/ vIeqIolhXPmICKLwIzl1bJSGkVRFc7OsxXee4pSmtdd71dI0Lxw92VchI g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAFAIgglFCQ/khR/2dsb2JhbABEw0OBCIIeAQEBAwESARQRFiAKAQULCw4KCQ8HDwkDAgECAR8mBg0BBQIBAQUUBAGHYgYLm3CgEowAgxmDIgOVeYVriG6Ba4JvgWQX
X-IronPort-AV: E=Sophos;i="4.80,701,1344211200"; d="scan'208";a="146212549"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by ams-iport-1.cisco.com with ESMTP; 02 Nov 2012 19:39:32 +0000
Received: from [10.61.101.56] (dhcp-10-61-101-56.cisco.com [10.61.101.56]) by ams-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id qA2JdWAr005879; Fri, 2 Nov 2012 19:39:32 GMT
Message-ID: <50942174.9010609@cisco.com>
Date: Fri, 02 Nov 2012 19:39:32 +0000
From: Paul Aitken <paitken@cisco.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:15.0) Gecko/20120912 Thunderbird/15.0.1
MIME-Version: 1.0
To: Sabahattin Gucukoglu <listsebby@me.com>
Subject: Re: mailing list memberships reminder -> passwords in the clear
References: <5092D99F.3070601@cisco.com> <C94D122B-A7AB-4676-93B3-52BA925C72EA@me.com>
In-Reply-To: <C94D122B-A7AB-4676-93B3-52BA925C72EA@me.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Sat, 03 Nov 2012 08:24:22 -0700
Cc: mailman-owner@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Nov 2012 19:39:34 -0000

Sabahattin,

Thanks for the detailed info.

I've been getting passwords mailed to me monthly for years. Someone 
pointed out the disable option just yesterday.

So I've selected the option, but that's hardly the point: the option 
should default to OFF and not be enable-able so passwords are never sent 
in the clear.

I find it hard to understand that this is acceptable to the IETF.

Thanks,
P.


> On 1 Nov 2012, at 20:20, Paul Aitken <paitken@cisco.com> wrote:
>> Why does the "mailing list memberships reminder" send passwords in the clear?
> Because mailman is brain-dead stupid.  See:
> http://www.jwz.org/doc/mailman.html
>
> Sadly, and despite my best efforts to find alternative mailing list software, mailman wins on popularity (ugh) and hence support with practically no competition.  Only majordomo2, which has been unmaintained for a while now (and it's author calls it "Dead" holds much of a chance, but I doubt it would work for the IETF in its current condition.
>
> But have hope!  The IETF serves the mailman interface over TLS, and it is an option that you can exercise *not* to have passwords mailed to you.  Go to your membership options page, and in the group containing the option to turn off the membership reminders, check the checkbox to make it global.  Later, you can have the password mailed to you on demand, or unsubscribe without needing a password at all (email confirmation loop).
>
>> For everything else I'm subscribed to, if I forget my details, one click sends a one-time password-reset link.
>> Passwords are never mailed out, and never shown.
> Yes.  Sadly this isn't possible with mailman; you will always be mailed your password if you need it and can't remember it.
>
> HTH.
>
> Cheers,
> Sabahattin


From paitken@cisco.com  Fri Nov  2 14:12:19 2012
Return-Path: <paitken@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5ACB21F0C8C for <ietf@ietfa.amsl.com>; Fri,  2 Nov 2012 14:12:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.533
X-Spam-Level: 
X-Spam-Status: No, score=-10.533 tagged_above=-999 required=5 tests=[AWL=0.066, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 IoAbKhHTbRjB for <ietf@ietfa.amsl.com>; Fri,  2 Nov 2012 14:12:18 -0700 (PDT)
Received: from ams-iport-3.cisco.com (ams-iport-3.cisco.com [144.254.224.146]) by ietfa.amsl.com (Postfix) with ESMTP id 41F231F0C80 for <ietf@ietf.org>; Fri,  2 Nov 2012 14:12:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=759; q=dns/txt; s=iport; t=1351890738; x=1353100338; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=bkOfm7Bcu6hJgYledNjZAUnuo08hS18F4Uu7Urbx+0I=; b=bLwPDOceErgbtoHQNXZH+wVc279k5+160szFwmcuN2Xzzr85V5zgzyre c377VEpbICZaSIHBLEDvh9fvMMKL0cIznAam0QYJo4QVqyWcub/eQTrzY 2MA8t5Q2No+lW0tSJujDqu083g3R7xuZolkXv/IKOxkRXPh0E7f8atwDH 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhwFAMc1lFCQ/khR/2dsb2JhbABEhVC9d4EIgh4BAQEDARIBFBE2CgEFCwshDwcPCQMCAQIBRQYNAQcBAR6HYgYLm26gDo8ZgyIDlXmBHIRPiG6Ba4Jv
X-IronPort-AV: E=Sophos;i="4.80,701,1344211200";  d="scan'208";a="9303287"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by ams-iport-3.cisco.com with ESMTP; 02 Nov 2012 21:12:17 +0000
Received: from [10.61.101.56] (dhcp-10-61-101-56.cisco.com [10.61.101.56]) by ams-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id qA2LCGYj025933; Fri, 2 Nov 2012 21:12:17 GMT
Message-ID: <50943730.4020607@cisco.com>
Date: Fri, 02 Nov 2012 21:12:16 +0000
From: Paul Aitken <paitken@cisco.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:15.0) Gecko/20120912 Thunderbird/15.0.1
MIME-Version: 1.0
To: John R Levine <johnl@taugh.com>
Subject: Re: mailing list memberships reminder -> passwords in the clear
References: <20121102152445.92153.qmail@joyce.lan> <5094215B.6000502@cisco.com> <alpine.BSF.2.00.1211021552460.97859@joyce.lan>
In-Reply-To: <alpine.BSF.2.00.1211021552460.97859@joyce.lan>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Sat, 03 Nov 2012 08:24:22 -0700
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Nov 2012 21:12:19 -0000

John,

> I can't speak for the IETF, but I do note that the same password 
> notices have been going out on the first of every month for years.  
> You just noticed iit now?

No, I've been getting the passwords for years. However I just finished a 
crypto class and really wondered what the history is here.


> And once again, if you think it should do something else, send code. 
> We're volunteers here.  Assertions that it is very important for 
> someone else to do work that you're not prepared to do are rarely 
> effective.

It seems that this was fixed in 2007:

http://blog.tigertech.net/posts/mailman-monthly-password-reminders-not-recommended
     http://wiki.list.org/display/DEV/2007/01/13/Passwords+done+right

Thanks,
P.

From smb@cs.columbia.edu  Sat Nov  3 08:34:19 2012
Return-Path: <smb@cs.columbia.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2844421F9055 for <ietf@ietfa.amsl.com>; Sat,  3 Nov 2012 08:34:19 -0700 (PDT)
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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i8zHivoiVSXQ for <ietf@ietfa.amsl.com>; Sat,  3 Nov 2012 08:34:18 -0700 (PDT)
Received: from salak.cc.columbia.edu (salak.cc.columbia.edu [128.59.29.6]) by ietfa.amsl.com (Postfix) with ESMTP id 501EC21F9C79 for <ietf@ietf.org>; Sat,  3 Nov 2012 08:34:18 -0700 (PDT)
Received: from v230.vpn.iad.rg.net (v230.vpn.iad.rg.net [198.180.150.230]) (user=smb2132 mech=PLAIN bits=0) by salak.cc.columbia.edu (8.14.4/8.14.3) with ESMTP id qA3FYERq010698 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Sat, 3 Nov 2012 11:34:14 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: mailing list memberships reminder -> passwords in the clear
From: Steven Bellovin <smb@cs.columbia.edu>
In-Reply-To: <5094215B.6000502@cisco.com>
Date: Sat, 3 Nov 2012 11:34:13 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <83AB905E-CE0A-4A80-B3CF-F9B32B58FCBD@cs.columbia.edu>
References: <20121102152445.92153.qmail@joyce.lan> <5094215B.6000502@cisco.com>
To: Paul Aitken <paitken@cisco.com>
X-Mailer: Apple Mail (2.1499)
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.68 on 128.59.29.6
Cc: John Levine <johnl@taugh.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Nov 2012 15:34:19 -0000

On Nov 2, 2012, at 3:39 PM, Paul Aitken <paitken@cisco.com> wrote:

> John,
>=20
>>> Why does the "mailing list memberships reminder" send passwords in =
the clear?
>> Because that's what Mailman does.  Send code.
>=20
> And that's acceptable to the IETF? You're kidding me, right?
>=20
Because the security is compatible with the risk.

These are open mailing lists; anyone can join, and anyone can read the
archives without subscribing.  This means that the resource being =
protected
is of low value -- very low value.  Sending out a randomly-generated =
password
in the clear is perfectly acceptable for that situation.

Having that off by default would be reasonable, but to reduce annoyance,
not because it produces any real increase in security.

For a private, sensitive mailing list, the analysis would be different.


		--Steve Bellovin, https://www.cs.columbia.edu/~smb






From housley@vigilsec.com  Sat Nov  3 08:36:53 2012
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E6EC021F9C4D for <ietf@ietfa.amsl.com>; Sat,  3 Nov 2012 08:36:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.521
X-Spam-Level: 
X-Spam-Status: No, score=-102.521 tagged_above=-999 required=5 tests=[AWL=-0.078, BAYES_00=-2.599, SUBJECT_FUZZY_TION=0.156, 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 fo9jnxgFUE7L for <ietf@ietfa.amsl.com>; Sat,  3 Nov 2012 08:36:53 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 327AB21F9283 for <ietf@ietf.org>; Sat,  3 Nov 2012 08:36:53 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 44FC59A4002; Sat,  3 Nov 2012 11:37:00 -0400 (EDT)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id l3eBBIM4BB5g; Sat,  3 Nov 2012 11:36:43 -0400 (EDT)
Received: from dhcp-5421.meeting.ietf.org (unknown [130.129.84.33]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 610139A4001; Sat,  3 Nov 2012 11:36:59 -0400 (EDT)
Subject: Re: Recall petition for Mr. Marshall Eubanks
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <1F2808D4F3783CA802322A8F@JCK-EEE10>
Date: Sat, 3 Nov 2012 11:36:49 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <41DE1FC7-345F-4F79-A679-BD573295022F@vigilsec.com>
References: <50919671.6000605@ogud.com> <7F4FE714-DEDC-4D64-ADD8-AA6ECF53EABB@NLnetLabs.nl> <5092D9DB.4070602@cisco.com> <tsltxt980bc.fsf@mit.edu> <3153B2FE-4B52-43AF-AD10-6701CFFE0AB8@gmail.com> <20121102022203.9C7A721F96EC@ietfa.amsl.com> <1F2808D4F3783CA802322A8F@JCK-EEE10>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1085)
Cc: IETF-Discussion list <ietf@ietf.org>, Olafur Gudmundsson <ogud@ogud.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Nov 2012 15:36:54 -0000

John:

>> I assume at this point the IAOC would like to pursue the
>> recall option?  If not, please be very clear about it to the
>> list as I haven't actually seen a request from the IAOC for
>> that process to proceed as far as I can tell.
>=20
> Because I am personally very reluctant to see this handled by
> recall, I want to ask a slightly different question:  Are the
> people who met with Marshall convinced that he understood that,
> if he did not resign, a recall was almost certain to be
> initiated as our next step.  If the answer is "yes", he's made
> his choice and I am ok with signing the petition.   If not, it
> is possible that more discussion would be in order after the
> petition process is complete.
>=20
> I hope that, when Lynn accepts the petitions, another effort (or
> several) will be made to et Marshall's attention -- it
> presumably is not too late for him to resign until after the
> relevant committee is appointed.

At the end of our visit, I believe that Marshall understood that there =
were three possibilities:

1) Tell the community that he intends to resume participation;
2) Resign;
3) Do nothing, which would very likely result in a recall.

Russ=

From paul.hoffman@vpnc.org  Sat Nov  3 11:21:49 2012
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8AAB121F9C90 for <ietf@ietfa.amsl.com>; Sat,  3 Nov 2012 11:21:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.521
X-Spam-Level: 
X-Spam-Status: No, score=-102.521 tagged_above=-999 required=5 tests=[AWL=-0.078, BAYES_00=-2.599, SUBJECT_FUZZY_TION=0.156, 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 37PgaGsIeS22 for <ietf@ietfa.amsl.com>; Sat,  3 Nov 2012 11:21:49 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 1E84121F9C81 for <ietf@ietf.org>; Sat,  3 Nov 2012 11:21:49 -0700 (PDT)
Received: from [192.168.65.155] ([207.239.114.206]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id qA3ILkU9087423 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <ietf@ietf.org>; Sat, 3 Nov 2012 11:21:47 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: Recall petition for Mr. Marshall Eubanks
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <F1DFC16DCAA7D3468651A5A776D5796E01FF9FF7@BY2PRD0510MB366.namprd05.prod.outlook.com>
Date: Sat, 3 Nov 2012 11:21:49 -0700
Content-Transfer-Encoding: 7bit
Message-Id: <01523424-4CBE-4986-81E0-4972323D2AAF@vpnc.org>
References: <50919671.6000605@ogud.com> <7F4FE714-DEDC-4D64-ADD8-AA6ECF53EABB@NLnetLabs.nl> <5092D9DB.4070602@cisco.com> <tsltxt980bc.fsf@mit.edu> <20121102034526.GB25144@mx1.yitter.info> <F1DFC16DCAA7D3468651A5A776D5796E01FF9FF7@BY2PRD0510MB366.namprd05.prod.outlook.com>
To: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-Mailer: Apple Mail (2.1499)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Nov 2012 18:21:49 -0000

I am NomCom-eligible and I "sign" this petition.

--Paul Hoffman

From turchanyi.geza@gmail.com  Sat Nov  3 11:33:58 2012
Return-Path: <turchanyi.geza@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5BD5A21F99CC for <ietf@ietfa.amsl.com>; Sat,  3 Nov 2012 11:33:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.406
X-Spam-Level: 
X-Spam-Status: No, score=-3.406 tagged_above=-999 required=5 tests=[AWL=0.036,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, SUBJECT_FUZZY_TION=0.156]
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 16cpuo+t0gap for <ietf@ietfa.amsl.com>; Sat,  3 Nov 2012 11:33:57 -0700 (PDT)
Received: from mail-da0-f44.google.com (mail-da0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id E049021F8DE5 for <ietf@ietf.org>; Sat,  3 Nov 2012 11:33:57 -0700 (PDT)
Received: by mail-da0-f44.google.com with SMTP id h15so2088917dan.31 for <ietf@ietf.org>; Sat, 03 Nov 2012 11:33:57 -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 :cc:content-type; bh=hYTw8kU/T5AI6n/8ft6GbQCLdrUWgSeuQFUJa7wcTqU=; b=jt6FcP55+vdEYjCi3UxtSsFkoA0gUxzqplB2cn87PHbRuAcVx4VUWehCWHfgYyIkF8 hCOzXxarUtHdnTzpiEuVnMWzWGYFWCeBjr4L1TMyLIAFjpi/w7WGCTOl80z6SGUU34vF c9Jo5PZUJ/lrC56U0zXj1Xr5rcq4wKXG++BBNvtKtcZkI4klMPh6FArWXC+f97Qdhc31 Xmq77NhMTqXd+1dFnxZiX54CARfJ3mAgr3KUXXp10nn9lXNyL+yqM9/6VNNV3SlHD+Hh uoEjlmm9yzMDfVP9PhVygPWeiWh6zIIGbYOyrjshB52MxqRP4mqdPAoACEjppdWFv1Y+ TBqA==
MIME-Version: 1.0
Received: by 10.68.189.138 with SMTP id gi10mr16853976pbc.165.1351967637708; Sat, 03 Nov 2012 11:33:57 -0700 (PDT)
Received: by 10.66.19.135 with HTTP; Sat, 3 Nov 2012 11:33:57 -0700 (PDT)
In-Reply-To: <41DE1FC7-345F-4F79-A679-BD573295022F@vigilsec.com>
References: <50919671.6000605@ogud.com> <7F4FE714-DEDC-4D64-ADD8-AA6ECF53EABB@NLnetLabs.nl> <5092D9DB.4070602@cisco.com> <tsltxt980bc.fsf@mit.edu> <3153B2FE-4B52-43AF-AD10-6701CFFE0AB8@gmail.com> <20121102022203.9C7A721F96EC@ietfa.amsl.com> <1F2808D4F3783CA802322A8F@JCK-EEE10> <41DE1FC7-345F-4F79-A679-BD573295022F@vigilsec.com>
Date: Sat, 3 Nov 2012 19:33:57 +0100
Message-ID: <CAJfR-+PtOxK1jHQ7uTCmObyaZu10V8CBtcdr4SBsPNCfTu615A@mail.gmail.com>
Subject: Re: Recall petition for Mr. Marshall Eubanks
From: Turchanyi Geza <turchanyi.geza@gmail.com>
To: Russ Housley <housley@vigilsec.com>
Content-Type: multipart/alternative; boundary=e89a8fb2091ecb1ecd04cd9b7e98
Cc: John C Klensin <john-ietf@jck.com>, IETF-Discussion list <ietf@ietf.org>, Olafur Gudmundsson <ogud@ogud.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Nov 2012 18:33:58 -0000

--e89a8fb2091ecb1ecd04cd9b7e98
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

All,

Many tahanks for the clarification, the situation is clear enough.

On Sat, Nov 3, 2012 at 4:36 PM, Russ Housley <housley@vigilsec.com> wrote:

> John:
> ....
>
> At the end of our visit, I believe that Marshall understood that there
> were three possibilities:
>
> 1) Tell the community that he intends to resume participation;
> 2) Resign;
> 3) Do nothing, which would very likely result in a recall.
>
> Russ


There will be enough people to sign the petition, and the sanity of the
IETF will be kept.

Will be any one helping Marshall Eubanks to recover from his shocked state?

I would be very gratefull,

G=E9za

--e89a8fb2091ecb1ecd04cd9b7e98
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

All,<br><br>Many tahanks for the clarification, the situation is clear enou=
gh.<br><br><div class=3D"gmail_quote">On Sat, Nov 3, 2012 at 4:36 PM, Russ =
Housley <span dir=3D"ltr">&lt;<a href=3D"mailto:housley@vigilsec.com" targe=
t=3D"_blank">housley@vigilsec.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">John:<br>
<div><div class=3D"h5">....<br>
<br>
</div></div>At the end of our visit, I believe that Marshall understood tha=
t there were three possibilities:<br>
<br>
1) Tell the community that he intends to resume participation;<br>
2) Resign;<br>
3) Do nothing, which would very likely result in a recall.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Russ</font></span></blockquote></div><br>There will be enough people to sig=
n the petition, and the sanity of the IETF will be kept.<br><br>Will be any=
 one helping Marshall Eubanks to recover from his shocked state?<br><br>
I would be very gratefull,<br><br>G=E9za<br>

--e89a8fb2091ecb1ecd04cd9b7e98--

From listsebby@me.com  Sat Nov  3 13:09:33 2012
Return-Path: <listsebby@me.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B903421F9CA4 for <ietf@ietfa.amsl.com>; Sat,  3 Nov 2012 13:09:33 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g28l-TpTm9OZ for <ietf@ietfa.amsl.com>; Sat,  3 Nov 2012 13:09:33 -0700 (PDT)
Received: from nk11p04mm-asmtp003.mac.com (nk11p04mm-asmtp003.mac.com [17.158.236.238]) by ietfa.amsl.com (Postfix) with ESMTP id 54F7221F9CA3 for <ietf@ietf.org>; Sat,  3 Nov 2012 13:09:32 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII
Received: from [192.168.1.5] (natbox.sabahattin-gucukoglu.com [213.123.192.30]) by nk11p04mm-asmtp003.mac.com (Oracle Communications Messaging Server 7u4-24.01(7.0.4.24.0) 64bit (built Jan 3 2012)) with ESMTPSA id <0MCX00K0THBTDH70@nk11p04mm-asmtp003.mac.com> for ietf@ietf.org; Sat, 03 Nov 2012 20:09:32 +0000 (GMT)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.7.7855,1.0.431,0.0.0000 definitions=2012-11-03_06:2012-11-03, 2012-11-03, 1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 suspectscore=0 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=6.0.2-1203120001 definitions=main-1211030240
Subject: Re: mailing list memberships reminder -> passwords in the clear
From: Sabahattin Gucukoglu <listsebby@me.com>
In-reply-to: <20121102215134.5156.qmail@joyce.lan>
Date: Sat, 03 Nov 2012 20:09:29 +0000
Message-id: <68243AD7-EB74-402C-94B1-E0006DEA2100@me.com>
References: <20121102215134.5156.qmail@joyce.lan>
To: John Levine <johnl@taugh.com>
X-Mailer: Apple Mail (2.1499)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Nov 2012 20:09:33 -0000

On 2 Nov 2012, at 21:51, John Levine <johnl@taugh.com> wrote:
>> Only majordomo2, which has been unmaintained for a while now (and
>> it's author calls it "Dead" holds much of a chance, but I doubt it
> ?would work for the IETF in its current condition.
> 
> Actually, MJ2 works great, I've been using it in production for years,

I completely agree that it's excellent software.

> but I agree that we'd need to locate a perl weenie willing to make
> tweaks, and it's probably not enough better than MM to be worth the
> pain of switching.

I think it's the difference between night and day, personally.  MJ2 is technically superior and emphasises the task of actually managing mailing lists in a very clean, black-box way.  OTOH, it seems clear that Mailman has won over all the web hosters and whatnot because it's "User-friendly".  I guess "Integrated with the web" is an adequate sell, even if it practically means "Has a simple, inflexible interface that's only accessible using a web browser from lynx up.  Certainly, the IETF could benefit from MJ2's more techie features (not least, the means to do absolutely everything by email).  Moderators, in particular.  But it still boils down to having and using supported software.

> Sadly this isn't possible with mailman; you will always be mailed
>> your password if you need it and can't remember it.
> 
> If you use a high value password for your IETF list subscriptions, you
> have deeper security issues than a few tweaks to mail software can fix.

Unfortunately though, it happens quite often.  Users want all the benefits without any of the inconveniences.  So they use their easy-to-remember/crack/used-everywhere-else passwords.

Cheers,
Sabahattin


From vesely@tana.it  Sat Nov  3 16:49:35 2012
Return-Path: <vesely@tana.it>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C643C21F9C8A for <ietf@ietfa.amsl.com>; Sat,  3 Nov 2012 16:49:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.719
X-Spam-Level: 
X-Spam-Status: No, score=-4.719 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_DNSWL_MED=-4]
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 0SiMTf4fD3oS for <ietf@ietfa.amsl.com>; Sat,  3 Nov 2012 16:49:35 -0700 (PDT)
Received: from wmail.tana.it (wmail.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id 12A0321F9C35 for <ietf@ietf.org>; Sat,  3 Nov 2012 16:49:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=beta; t=1351986573; bh=1Yqk0Iwa7/BOvN0Mf0Hu2Nh/t/sVwI4xluUgoy94hYc=; l=856; h=Date:From:To:References:In-Reply-To; b=KZVJB/P5Uz8XJNaD8uHf9K3xsa1Unz7wJbo2UtT8yuM9ZJE9B/FjE4BuNqY3zi+gc GikjjeyqLKMKM2tWhl1pNcCzZV5pPPS16dQpJzpcYcHNYWR/vfJGhpRg91ipyUaB4y 42t+vSIkqtvD4L5kBMGtIoRQ+h2ryW6mEUxa87vM=
Received: from [130.129.65.111] (softdnserr [130.129.65.111]) (AUTH: PLAIN uXDGrn@SYT0/k, TLS: TLS1.0,256bits,RSA_AES_256_CBC_SHA1) by wmail.tana.it with ESMTPSA; Sun, 04 Nov 2012 00:49:31 +0100 id 00000000005DC039.000000005095AD8C.00001B78
Message-ID: <5095AD86.8010009@tana.it>
Date: Sat, 03 Nov 2012 19:49:26 -0400
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (Windows NT 6.0; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Antitrust FAQ
References: <AFB9BEA6-579B-4E26-A512-BE271D234F85@ietf.org> <B68EFB284B10C249835C566A0CE08AA2370EFDCD@TK5EX14MBXC263.redmond.corp.microsoft.com> <468C102D-7640-4447-9E10-B6ED70381274@vigilsec.com>
In-Reply-To: <468C102D-7640-4447-9E10-B6ED70381274@vigilsec.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Nov 2012 23:49:35 -0000

On Thu 01/Nov/2012 18:31:47 -0400 Russ Housley wrote:
> A formal policy requires IETF consensus, and it would be published
> as a BCP in the RFC series.

Isn't that's something the IETF will have do in any case, sooner or later?

AFAICU, standardization is about establishing the competition rules.
Key concepts, such as open and fair participation to such activity,
are already treated in some BCPs.  Why would antitrust be exempted?

> Please review the FAQ, and if you discover any issues raise them in
> response to this message.

Technical details of new protocols are an example of competitive
information.  When patents are involved, that would belong to the last
bullet of question 3, "procurement and purchasing".  Thus, sharing
such info might sound as a precursor to collusion.  However, question
6 cannot be applied to this case.


From john-ietf@jck.com  Sat Nov  3 22:13:59 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9DE7621F9B09 for <ietf@ietfa.amsl.com>; Sat,  3 Nov 2012 22:13:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.909
X-Spam-Level: 
X-Spam-Status: No, score=-101.909 tagged_above=-999 required=5 tests=[AWL=0.534, BAYES_00=-2.599, SUBJECT_FUZZY_TION=0.156, 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 OOPQtddBBXUF for <ietf@ietfa.amsl.com>; Sat,  3 Nov 2012 22:13:59 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 1A7FD21F8AC2 for <ietf@ietf.org>; Sat,  3 Nov 2012 22:13:59 -0700 (PDT)
Received: from localhost ([::1]) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1TUsWy-000HH3-J5; Sun, 04 Nov 2012 01:13:56 -0400
Date: Sun, 04 Nov 2012 01:13:56 -0400
From: John C Klensin <john-ietf@jck.com>
To: Russ Housley <housley@vigilsec.com>
Subject: Re: Recall petition for Mr. Marshall Eubanks
Message-ID: <6F07B89BEBB1CE180D94EB5E@JCK-EEE10>
In-Reply-To: <41DE1FC7-345F-4F79-A679-BD573295022F@vigilsec.com>
References: <50919671.6000605@ogud.com> <7F4FE714-DEDC-4D64-ADD8-AA6ECF53EABB@NLnetLabs.nl> <5092D9DB.4070602@cisco.com> <tsltxt980bc.fsf@mit.edu> <3153B2FE-4B52-43AF-AD10-6701CFFE0AB8@gmail.com> <20121102022203.9C7A721F96EC@ietfa.amsl.com> <1F2808D4F3783CA802322A8F@JCK-EEE10> <41DE1FC7-345F-4F79-A679-BD573295022F@vigilsec.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: IETF-Discussion list <ietf@ietf.org>, Olafur Gudmundsson <ogud@ogud.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 04 Nov 2012 05:13:59 -0000

Russ,
Thanks very much for the clarification.

Olafur,
Go ahead and add me to the signature list.  I am Nomcom-eligible.
    john


--On Saturday, 03 November, 2012 11:36 -0400 Russ Housley
<housley@vigilsec.com> wrote:

> John:
> 
>>> I assume at this point the IAOC would like to pursue the
>>> recall option?  If not, please be very clear about it to the
>>> list as I haven't actually seen a request from the IAOC for
>>> that process to proceed as far as I can tell.
>> 
>> Because I am personally very reluctant to see this handled by
>> recall, I want to ask a slightly different question:  Are the
>> people who met with Marshall convinced that he understood
>> that, if he did not resign, a recall was almost certain to be
>> initiated as our next step.  If the answer is "yes", he's made
>> his choice and I am ok with signing the petition.   If not, it
>> is possible that more discussion would be in order after the
>> petition process is complete.
>> 
>> I hope that, when Lynn accepts the petitions, another effort
>> (or several) will be made to et Marshall's attention -- it
>> presumably is not too late for him to resign until after the
>> relevant committee is appointed.
> 
> At the end of our visit, I believe that Marshall understood
> that there were three possibilities:
> 
> 1) Tell the community that he intends to resume participation;
> 2) Resign;
> 3) Do nothing, which would very likely result in a recall.
> 
> Russ





From bertietf@bwijnen.net  Sun Nov  4 06:15:21 2012
Return-Path: <bertietf@bwijnen.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D873221F86B7 for <ietf@ietfa.amsl.com>; Sun,  4 Nov 2012 06:15:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.521
X-Spam-Level: 
X-Spam-Status: No, score=-102.521 tagged_above=-999 required=5 tests=[AWL=-0.078, BAYES_00=-2.599, SUBJECT_FUZZY_TION=0.156, 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 Pf0qnvaPbncH for <ietf@ietfa.amsl.com>; Sun,  4 Nov 2012 06:15:21 -0800 (PST)
Received: from postgirl.ripe.net (postgirl.ipv6.ripe.net [IPv6:2001:67c:2e8:11::c100:1342]) by ietfa.amsl.com (Postfix) with ESMTP id 2F4D621F86AF for <ietf@ietf.org>; Sun,  4 Nov 2012 06:15:21 -0800 (PST)
Received: from ayeaye.ripe.net ([193.0.23.5]) by postgirl.ripe.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from <bertietf@bwijnen.net>) id 1TV0yr-0005h7-Jp; Sun, 04 Nov 2012 15:15:18 +0100
Received: from cat.ripe.net ([193.0.1.249] helo=dhcp-5420.meeting.ietf.org) by ayeaye.ripe.net with esmtp (Exim 4.72) (envelope-from <bertietf@bwijnen.net>) id 1TV0yr-0002bA-9w; Sun, 04 Nov 2012 15:15:17 +0100
Message-ID: <50967874.4070300@bwijnen.net>
Date: Sun, 04 Nov 2012 09:15:16 -0500
From: "Bert Wijnen (IETF)" <bertietf@bwijnen.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: Olafur Gudmundsson <ogud@ogud.com>
Subject: Re: Recall petition for Mr. Marshall Eubanks
References: <50919671.6000605@ogud.com> <7F4FE714-DEDC-4D64-ADD8-AA6ECF53EABB@NLnetLabs.nl> <5092D9DB.4070602@cisco.com> <tsltxt980bc.fsf@mit.edu> <3153B2FE-4B52-43AF-AD10-6701CFFE0AB8@gmail.com> <20121102022203.9C7A721F96EC@ietfa.amsl.com> <1F2808D4F3783CA802322A8F@JCK-EEE10> <41DE1FC7-345F-4F79-A679-BD573295022F@vigilsec.com> <6F07B89BEBB1CE180D94EB5E@JCK-EEE10>
In-Reply-To: <6F07B89BEBB1CE180D94EB5E@JCK-EEE10>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Anti-Virus: Kaspersky Anti-Virus for Linux Mail Server 5.6.48/RELEASE, bases: 20120425 #7816575, check: 20121104 clean
X-RIPE-Spam-Level: --
X-RIPE-Spam-Report: Spam Total Points:   -2.9 points pts rule name              description ---- ---------------------- ------------------------------------ -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP -1.9 BAYES_00               BODY: Bayes spam probability is 0 to 1% [score: 0.0000]
X-RIPE-Signature: 86ab03e524994f79ca2c75a176445dd4db130b2f0de56a6832ea76b9e2a5c8e6
Cc: IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 04 Nov 2012 14:15:22 -0000

Thanks for extra info.

You can add me to the list who sign the request for recall.

Bert

> --On Saturday, 03 November, 2012 11:36 -0400 Russ Housley
> <housley@vigilsec.com> wrote:
>
>> John:
>>
>>>> I assume at this point the IAOC would like to pursue the
>>>> recall option?  If not, please be very clear about it to the
>>>> list as I haven't actually seen a request from the IAOC for
>>>> that process to proceed as far as I can tell.
>>>
>>> Because I am personally very reluctant to see this handled by
>>> recall, I want to ask a slightly different question:  Are the
>>> people who met with Marshall convinced that he understood
>>> that, if he did not resign, a recall was almost certain to be
>>> initiated as our next step.  If the answer is "yes", he's made
>>> his choice and I am ok with signing the petition.   If not, it
>>> is possible that more discussion would be in order after the
>>> petition process is complete.
>>>
>>> I hope that, when Lynn accepts the petitions, another effort
>>> (or several) will be made to et Marshall's attention -- it
>>> presumably is not too late for him to resign until after the
>>> relevant committee is appointed.
>>
>> At the end of our visit, I believe that Marshall understood
>> that there were three possibilities:
>>
>> 1) Tell the community that he intends to resume participation;
>> 2) Resign;
>> 3) Do nothing, which would very likely result in a recall.
>>
>> Russ
>
>
>
>
>

From joelja@bogus.com  Sun Nov  4 07:20:20 2012
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CDB0221F85DD for <ietf@ietfa.amsl.com>; Sun,  4 Nov 2012 07:20:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.445
X-Spam-Level: 
X-Spam-Status: No, score=-102.445 tagged_above=-999 required=5 tests=[AWL=0.154, 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 CD8bGkeqRP5c for <ietf@ietfa.amsl.com>; Sun,  4 Nov 2012 07:20:20 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 1DC3021F85DA for <ietf@ietf.org>; Sun,  4 Nov 2012 07:20:20 -0800 (PST)
Received: from dhcp-6038.meeting.ietf.org (dhcp-6038.meeting.ietf.org [130.129.96.56]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id qA4FKHu3006085 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Sun, 4 Nov 2012 15:20:17 GMT (envelope-from joelja@bogus.com)
Message-ID: <509687B0.2000606@bogus.com>
Date: Sun, 04 Nov 2012 10:20:16 -0500
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: ietf <ietf@ietf.org>
Subject: IETF85 Streaming Reminder
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Sun, 04 Nov 2012 15:20:18 +0000 (UTC)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 04 Nov 2012 15:20:20 -0000

Greetings,

For those interested in monitoring sessions or participating remotely the
following information may prove useful.

For general remote participation including meetecho support see:

http://www.ietf.org/meeting/85/remote-participation.html

-Audio Streaming-

All 8 parallel tracks at the IETF 88 meeting will be broadcast starting
with the commencement of working group sessions on Monday, Nov 5 2012
at 0900 EST (UTC-5) and continue until the close of sessions on Friday,
Nov18th .

Because we have been asked several times in the past, note that if you
wish to use the rooms that are being recorded for impromptu meeting
during unscheduled sessions or lunch breaks that you can invite remote
participants to tune in to the appropriate stream. Recording cannot be
guaranteed for unscheduled sessions. Conversely, it should never be
assumed that recording or observation is not occurring on open
microphones, they are after all connected to the Internet.

The links for streaming sources and the schedule are best retrieved from
the IETF tools agenda, which as per standard operating procedure will be
located here:

http://tools.ietf.org/agenda/85/  

-Jabber/XMPP-

For information on IETF Jabber participation see:

http://www.ietf.org/jabber/index.html

or click on the Jabber links in the tools team agenda once you have a
properly configured jabber/xmpp messaging client.

-Webex-

Webex screen sharing participation is possible for a limited number of
sessions. Consult with your working-group chair or the secretariat for
more information.

-Ticketing-

For prompt access to the meeting trouble desk, the email address is:

mtd@ietf.org

For streaming related issues please send email toietf-streaming@verilan.com  
with info including the current time and affected streaming channel.


From arturo.servin@gmail.com  Sun Nov  4 08:45:35 2012
Return-Path: <arturo.servin@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A71A21F8615 for <ietf@ietfa.amsl.com>; Sun,  4 Nov 2012 08:45:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.443
X-Spam-Level: 
X-Spam-Status: No, score=-3.443 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, SUBJECT_FUZZY_TION=0.156]
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 wl9yBrALcfvL for <ietf@ietfa.amsl.com>; Sun,  4 Nov 2012 08:45:34 -0800 (PST)
Received: from mail-da0-f44.google.com (mail-da0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id BEB8221F8632 for <ietf@ietf.org>; Sun,  4 Nov 2012 08:45:31 -0800 (PST)
Received: by mail-da0-f44.google.com with SMTP id h15so2322229dan.31 for <ietf@ietf.org>; Sun, 04 Nov 2012 08:45:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=B+kBEanTNzG69GHJpdre0W4/KavUBJulmYHyWPt2MBI=; b=t6zX/39VY6EZYIUoCQlAqNfSt4q/OiXUQ6E7hLsc8vxQdcPnDjjmz7R2geDSp9aPVi 9UZfVlW4/TJiV646DxqduZJRVGN4/wGcZGAp+I4Ce5ECYpsWGT8e6y98mQ5uEv079cb4 QkAlDXKqjaCmIm4hMTve+ysMr07cjnI1N7ZeYgcHYBDczCJYOOyNJE7iyJahDAUXTC1J Qe8p6l2fXWgiNv+4/UJ39/am3TzFnvMRcFmRkDv6wpAvLgKrz0yYMei9TT8GxFjJ7F/C C/ZFv9QSrtZTeYgZyCX/rY5kfZspXQvTO9dsAfI3cFfH7OfdSEmhltYwZiod5No5Hr0D lcyg==
Received: by 10.66.81.199 with SMTP id c7mr21852675pay.19.1352047531461; Sun, 04 Nov 2012 08:45:31 -0800 (PST)
Received: from dhcp-16f2.meeting.ietf.org (dhcp-16f2.meeting.ietf.org. [130.129.22.242]) by mx.google.com with ESMTPS id rg9sm8275135pbc.46.2012.11.04.08.45.29 (version=SSLv3 cipher=OTHER); Sun, 04 Nov 2012 08:45:30 -0800 (PST)
Message-ID: <50969BAA.1090805@gmail.com>
Date: Sun, 04 Nov 2012 14:45:30 -0200
From: Arturo Servin <arturo.servin@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Recall petition for Mr. Marshall Eubanks
References: <50919671.6000605@ogud.com> <7F4FE714-DEDC-4D64-ADD8-AA6ECF53EABB@NLnetLabs.nl> <5092D9DB.4070602@cisco.com> <tsltxt980bc.fsf@mit.edu> <3153B2FE-4B52-43AF-AD10-6701CFFE0AB8@gmail.com> <20121102022203.9C7A721F96EC@ietfa.amsl.com> <1F2808D4F3783CA802322A8F@JCK-EEE10> <41DE1FC7-345F-4F79-A679-BD573295022F@vigilsec.com> <6F07B89BEBB1CE180D94EB5E@JCK-EEE10> <50967874.4070300@bwijnen.net>
In-Reply-To: <50967874.4070300@bwijnen.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 04 Nov 2012 16:45:35 -0000

	Thanks for the information to have a better decision.

	I am Nomcom-eligible and you can add me to the signature list.


/Arturo Servin


On 04/11/2012 12:15, Bert Wijnen (IETF) wrote:
> Thanks for extra info.
> 
> You can add me to the list who sign the request for recall.
> 
> Bert
> 
>> --On Saturday, 03 November, 2012 11:36 -0400 Russ Housley
>> <housley@vigilsec.com> wrote:
>>
>>> John:
>>>
>>>>> I assume at this point the IAOC would like to pursue the
>>>>> recall option?  If not, please be very clear about it to the
>>>>> list as I haven't actually seen a request from the IAOC for
>>>>> that process to proceed as far as I can tell.
>>>>
>>>> Because I am personally very reluctant to see this handled by
>>>> recall, I want to ask a slightly different question:  Are the
>>>> people who met with Marshall convinced that he understood
>>>> that, if he did not resign, a recall was almost certain to be
>>>> initiated as our next step.  If the answer is "yes", he's made
>>>> his choice and I am ok with signing the petition.   If not, it
>>>> is possible that more discussion would be in order after the
>>>> petition process is complete.
>>>>
>>>> I hope that, when Lynn accepts the petitions, another effort
>>>> (or several) will be made to et Marshall's attention -- it
>>>> presumably is not too late for him to resign until after the
>>>> relevant committee is appointed.
>>>
>>> At the end of our visit, I believe that Marshall understood
>>> that there were three possibilities:
>>>
>>> 1) Tell the community that he intends to resume participation;
>>> 2) Resign;
>>> 3) Do nothing, which would very likely result in a recall.
>>>
>>> Russ
>>
>>
>>
>>
>>

From housley@vigilsec.com  Sun Nov  4 12:22:35 2012
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6676621F85C8; Sun,  4 Nov 2012 12:22:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.592
X-Spam-Level: 
X-Spam-Status: No, score=-102.592 tagged_above=-999 required=5 tests=[AWL=0.007, 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 pRiRhz8al2zO; Sun,  4 Nov 2012 12:22:35 -0800 (PST)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id E251A21F867B; Sun,  4 Nov 2012 12:22:34 -0800 (PST)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 856769A4003; Sun,  4 Nov 2012 15:22:37 -0500 (EST)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id C7piHCSzBhnA; Sun,  4 Nov 2012 15:22:29 -0500 (EST)
Received: from dhcp-5421.meeting.ietf.org (dhcp-5421.meeting.ietf.org [130.129.84.33]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 609C09A4002; Sun,  4 Nov 2012 15:22:36 -0500 (EST)
Subject: Re: Antitrust FAQ
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <5095AD86.8010009@tana.it>
Date: Sun, 4 Nov 2012 15:22:32 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <EBCE0491-BED2-45BC-9D6F-3BA603F5F6D2@vigilsec.com>
References: <AFB9BEA6-579B-4E26-A512-BE271D234F85@ietf.org> <B68EFB284B10C249835C566A0CE08AA2370EFDCD@TK5EX14MBXC263.redmond.corp.microsoft.com> <468C102D-7640-4447-9E10-B6ED70381274@vigilsec.com> <5095AD86.8010009@tana.it>
To: Alessandro Vesely <vesely@tana.it>
X-Mailer: Apple Mail (2.1085)
Cc: chair@ietf.org, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 04 Nov 2012 20:22:35 -0000

Alessandro:

No.  We held a BOF to answer exactly that question.  The conclusion was =
that no new policies were needed, but that educational material was =
desirable.

Russ



On Nov 3, 2012, at 7:49 PM, Alessandro Vesely wrote:

> On Thu 01/Nov/2012 18:31:47 -0400 Russ Housley wrote:
>> A formal policy requires IETF consensus, and it would be published
>> as a BCP in the RFC series.
>=20
> Isn't that's something the IETF will have do in any case, sooner or =
later?
>=20
> AFAICU, standardization is about establishing the competition rules.
> Key concepts, such as open and fair participation to such activity,
> are already treated in some BCPs.  Why would antitrust be exempted?
>=20
>> Please review the FAQ, and if you discover any issues raise them in
>> response to this message.
>=20
> Technical details of new protocols are an example of competitive
> information.  When patents are involved, that would belong to the last
> bullet of question 3, "procurement and purchasing".  Thus, sharing
> such info might sound as a precursor to collusion.  However, question
> 6 cannot be applied to this case.
>=20


From ynir@checkpoint.com  Sun Nov  4 12:52:54 2012
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 69B3C21F88A1 for <ietf@ietfa.amsl.com>; Sun,  4 Nov 2012 12:52:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 JSpYJ-2jfpJk for <ietf@ietfa.amsl.com>; Sun,  4 Nov 2012 12:52:51 -0800 (PST)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id BFC8A21F88E5 for <ietf@ietf.org>; Sun,  4 Nov 2012 12:52:47 -0800 (PST)
Received: from il-ex01.ad.checkpoint.com (il-ex01.ad.checkpoint.com [194.29.34.26]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id qA4KqM2T024830; Sun, 4 Nov 2012 22:52:22 +0200
X-CheckPoint: {5096D2EE-3-1B221DC2-2FFFF}
Received: from il-ex03.ad.checkpoint.com (194.29.34.71) by il-ex01.ad.checkpoint.com (194.29.34.26) with Microsoft SMTP Server (TLS) id 8.3.213.0; Sun, 4 Nov 2012 22:52:22 +0200
Received: from il-ex01.ad.checkpoint.com ([194.29.34.26]) by il-ex03.ad.checkpoint.com ([194.29.34.71]) with mapi; Sun, 4 Nov 2012 22:52:22 +0200
From: Yoav Nir <ynir@checkpoint.com>
To: Tero Kivinen <kivinen@iki.fi>, IETF list <ietf@ietf.org>
Date: Sun, 4 Nov 2012 22:52:21 +0200
Subject: Re: Comments to the draft-nir-ipsecme-erx-07.txt
Thread-Topic: Comments to the draft-nir-ipsecme-erx-07.txt
Thread-Index: Ac26zkkSYynkyGp/SDSs6WJrSnBdHA==
Message-ID: <C4507F8C-10C6-4FA9-B4E0-F6935C784489@checkpoint.com>
References: <20629.53860.721523.621998@fireball.kivinen.iki.fi>
In-Reply-To: <20629.53860.721523.621998@fireball.kivinen.iki.fi>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-KSE-AntiSpam-Interceptor-Info: protection disabled
Cc: "sunseawq@huawei.com Wu" <sunseawq@huawei.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 04 Nov 2012 20:52:54 -0000

Forwarding to the IETF mailing list, which is the proper home for this disc=
ussion.

On Nov 3, 2012, at 10:26 PM, Tero Kivinen wrote:

> In Introduction section (1) there is text saying:
>=20
> ----------------------------------------------------------------------
>   Bringing these two technologies together allows a remote access IPsec
>   client to create multiple tunnels with different gateways that belong
>   to a single domain, as well as using the keys from other contexts of
>   using EAP, such as network access within the same domain, to
>   transparently connect to VPN gateways within this domain.
> ----------------------------------------------------------------------
>=20
> I think that is missing one possible use for the EAP Re-authentication
> Protocol, then one that has been proposed for example in the IEEE
> 802.11ai. I.e the possibility that the client does full EAP with AAA
> backend only once, and then reuses that authentication later to
> recreate the IPsec connection when it was lost for some reason
> (network problems, device suspending, going out of range etc).
>=20
> I.e. use it in similar ways as resumption protocol can be used, but
> now the state is stored in the AAA backend, not in the SGW.
>=20
> In section "3. Protocol Outline" there is text saying:
>=20
> ----------------------------------------------------------------------
>   The responder sends the EAP payload content to a backend AAA server,
>   and receives the rMSK and an EAP-Finish/Re-auth message.  It then
>   forwards the EAP-Finish/Re-auth message to the Initiator in an EAP
>   payload within the first IKE_AUTH response.
> ----------------------------------------------------------------------
>=20
> There is possibility that even when the client has ERX connection
> still up, but the backend AAA server might have already destroyed it.
> This means that it is possible that when initiator sends the first
> EAP_Initiate/Re-Auth message to the SGW, which forwards it to the AAA
> server, the AAA server will NOT respond with EAP-Finish/Re-auth
> message, but simply starts normal full EAP. This should be explained
> here. It does not really change the actual protocol flow, as AAA
> server will send EAP packet back, and then the initiator and responder
> will exchange some number of EAP packets before responder sends the
> EAP-Finish to initiator and they do the final AUTH exchange.
>=20
> If it is not mentioned here, some implementations might assume they
> always get EAP-Finish/Re-auth back and not work if the AAA server goes
> through the full EAP exchange.
>=20
> In section "4. ERX_SUPPORTED Notification" there is text saying:
>=20
> ----------------------------------------------------------------------
>   o  Protocol ID (1 octet) MUST be 1, as this message is related to an
>      IKE SA.
> ----------------------------------------------------------------------
>=20
> This is wrong. The RFC 5996 in section 3.10 says:
>=20
> ----------------------------------------------------------------------
>   o  Protocol ID (1 octet) - If this notification concerns an existing
>      SA whose SPI is given in the SPI field, this field indicates the
>      type of that SA.  For notifications concerning Child SAs, this
>      field MUST contain either (2) to indicate AH or (3) to indicate
>      ESP.  Of the notifications defined in this document, the SPI is
>      included only with INVALID_SELECTORS and REKEY_SA.  If the SPI
>      field is empty, this field MUST be sent as zero and MUST be
>      ignored on receipt.
> ----------------------------------------------------------------------
>=20
> I.e. the Protocol ID MUST be sent as zero if the SPI field is empty.=20
> --=20
> kivinen@iki.fi
>=20
> Scanned by Check Point Total Security Gateway.


From jason_livingood@cable.comcast.com  Sun Nov  4 14:59:10 2012
Return-Path: <jason_livingood@cable.comcast.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D986E21F875E for <ietf@ietfa.amsl.com>; Sun,  4 Nov 2012 14:59:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.075
X-Spam-Level: 
X-Spam-Status: No, score=-105.075 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HOST_EQ_MODEMCABLE=1.368, RCVD_IN_DNSWL_MED=-4, SUBJECT_FUZZY_TION=0.156, 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 EvF0lVedc53N for <ietf@ietfa.amsl.com>; Sun,  4 Nov 2012 14:59:10 -0800 (PST)
Received: from cable.comcast.com (copdcavout01.cable.comcast.com [76.96.32.253]) by ietfa.amsl.com (Postfix) with ESMTP id EC7CC21F85C8 for <ietf@ietf.org>; Sun,  4 Nov 2012 14:59:09 -0800 (PST)
Received: from ([24.40.56.116]) by copdcavout01.cable.comcast.com with ESMTP  id C7WM3M1.40409660; Sun, 04 Nov 2012 15:34:46 -0700
Received: from PACDCEXMB06.cable.comcast.com ([169.254.8.91]) by pacdcexhub03.cable.comcast.com ([fe80::5527:6d6b:29a7:f414%13]) with mapi id 14.02.0318.001; Sun, 4 Nov 2012 17:59:08 -0500
From: "Livingood, Jason" <Jason_Livingood@cable.comcast.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Recall petition for Mr. Marshall Eubanks
Thread-Topic: Recall petition for Mr. Marshall Eubanks
Thread-Index: AQHNuHoqcvZwM4mNR0SMiIcKaEKed5fVywEAgABI04CAAY0CAIAA41eAgAD1EQCAAJc/AIAAKfkA///xfIA=
Date: Sun, 4 Nov 2012 22:59:07 +0000
Message-ID: <10229F86C86EB444898E629583FD41712A0AB414@PACDCEXMB06.cable.comcast.com>
In-Reply-To: <50969BAA.1090805@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.4.120824
x-originating-ip: [24.40.55.72]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <AEB501B5C83B434085229AEFC86AD61E@cable.comcast.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 04 Nov 2012 22:59:11 -0000

Same here. I'm noncom-eligible and suppose the recall.


Jason Livingood

On 11/4/12 11:45 AM, "Arturo Servin" <arturo.servin@gmail.com> wrote:

>
>	Thanks for the information to have a better decision.
>
>	I am Nomcom-eligible and you can add me to the signature list.
>
>
>/Arturo Servin
>
>
>On 04/11/2012 12:15, Bert Wijnen (IETF) wrote:
>> Thanks for extra info.
>>=20
>> You can add me to the list who sign the request for recall.
>>=20
>> Bert
>>=20
>>> --On Saturday, 03 November, 2012 11:36 -0400 Russ Housley
>>> <housley@vigilsec.com> wrote:
>>>
>>>> John:
>>>>
>>>>>> I assume at this point the IAOC would like to pursue the
>>>>>> recall option?  If not, please be very clear about it to the
>>>>>> list as I haven't actually seen a request from the IAOC for
>>>>>> that process to proceed as far as I can tell.
>>>>>
>>>>> Because I am personally very reluctant to see this handled by
>>>>> recall, I want to ask a slightly different question:  Are the
>>>>> people who met with Marshall convinced that he understood
>>>>> that, if he did not resign, a recall was almost certain to be
>>>>> initiated as our next step.  If the answer is "yes", he's made
>>>>> his choice and I am ok with signing the petition.   If not, it
>>>>> is possible that more discussion would be in order after the
>>>>> petition process is complete.
>>>>>
>>>>> I hope that, when Lynn accepts the petitions, another effort
>>>>> (or several) will be made to et Marshall's attention -- it
>>>>> presumably is not too late for him to resign until after the
>>>>> relevant committee is appointed.
>>>>
>>>> At the end of our visit, I believe that Marshall understood
>>>> that there were three possibilities:
>>>>
>>>> 1) Tell the community that he intends to resume participation;
>>>> 2) Resign;
>>>> 3) Do nothing, which would very likely result in a recall.
>>>>
>>>> Russ
>>>
>>>
>>>
>>>
>>>


From mehmet.ersue@nsn.com  Sun Nov  4 19:15:24 2012
Return-Path: <mehmet.ersue@nsn.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 589FD21F8987 for <ietf@ietfa.amsl.com>; Sun,  4 Nov 2012 19:15:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.548
X-Spam-Level: 
X-Spam-Status: No, score=-106.548 tagged_above=-999 required=5 tests=[AWL=-0.105, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SUBJECT_FUZZY_TION=0.156, 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 H9ZETYZWhDOv for <ietf@ietfa.amsl.com>; Sun,  4 Nov 2012 19:15:22 -0800 (PST)
Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [93.183.12.31]) by ietfa.amsl.com (Postfix) with ESMTP id 4305821F897F for <ietf@ietf.org>; Sun,  4 Nov 2012 19:15:22 -0800 (PST)
Received: from demuprx016.emea.nsn-intra.net ([10.150.129.55]) by demumfd002.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id qA53FKV8019826 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 5 Nov 2012 04:15:20 +0100
Received: from demuexc023.nsn-intra.net (demuexc023.nsn-intra.net [10.150.128.36]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id qA53FHvb012244; Mon, 5 Nov 2012 04:15:20 +0100
Received: from DEMUEXC006.nsn-intra.net ([10.150.128.18]) by demuexc023.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 5 Nov 2012 04:15:17 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Recall petition for Mr. Marshall Eubanks
Date: Mon, 5 Nov 2012 04:15:16 +0100
Message-ID: <80A0822C5E9A4440A5117C2F4CD36A64045B677B@DEMUEXC006.nsn-intra.net>
In-Reply-To: <50967874.4070300@bwijnen.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Recall petition for Mr. Marshall Eubanks
Thread-Index: Ac26luXejJpA683hTTCfLr7ZnAcxrwAbNJIA
References: <50919671.6000605@ogud.com><7F4FE714-DEDC-4D64-ADD8-AA6ECF53EABB@NLnetLabs.nl><5092D9DB.4070602@cisco.com> <tsltxt980bc.fsf@mit.edu><3153B2FE-4B52-43AF-AD10-6701CFFE0AB8@gmail.com><20121102022203.9C7A721F96EC@ietfa.amsl.com><1F2808D4F3783CA802322A8F@JCK-EEE10><41DE1FC7-345F-4F79-A679-BD573295022F@vigilsec.com><6F07B89BEBB1CE180D94EB5E@JCK-EEE10> <50967874.4070300@bwijnen.net>
From: "Ersue, Mehmet (NSN - DE/Munich)" <mehmet.ersue@nsn.com>
To: "ext Bert Wijnen (IETF)" <bertietf@bwijnen.net>, "Olafur Gudmundsson" <ogud@ogud.com>
X-OriginalArrivalTime: 05 Nov 2012 03:15:17.0794 (UTC) FILETIME=[C7F9B820:01CDBB03]
X-purgate-type: clean
X-purgate-Ad: Categorized by eleven eXpurgate (R) http://www.eleven.de
X-purgate: clean
X-purgate: This mail is considered clean (visit http://www.eleven.de for further information)
X-purgate-size: 1979
X-purgate-ID: 151667::1352085320-00006DFC-FA43CE8F/0-0/0-0
Cc: IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Nov 2012 03:15:24 -0000

Same here. The decision is independent of Marshall's previous
contributions.

Cheers,=20
Mehmet=20


> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf
Of ext Bert
> Wijnen (IETF)
> Sent: Sunday, November 04, 2012 3:15 PM
> To: Olafur Gudmundsson
> Cc: IETF-Discussion list
> Subject: Re: Recall petition for Mr. Marshall Eubanks
>=20
> Thanks for extra info.
>=20
> You can add me to the list who sign the request for recall.
>=20
> Bert
>=20
> > --On Saturday, 03 November, 2012 11:36 -0400 Russ Housley
> > <housley@vigilsec.com> wrote:
> >
> >> John:
> >>
> >>>> I assume at this point the IAOC would like to pursue the
> >>>> recall option?  If not, please be very clear about it to the
> >>>> list as I haven't actually seen a request from the IAOC for
> >>>> that process to proceed as far as I can tell.
> >>>
> >>> Because I am personally very reluctant to see this handled by
> >>> recall, I want to ask a slightly different question:  Are the
> >>> people who met with Marshall convinced that he understood
> >>> that, if he did not resign, a recall was almost certain to be
> >>> initiated as our next step.  If the answer is "yes", he's made
> >>> his choice and I am ok with signing the petition.   If not, it
> >>> is possible that more discussion would be in order after the
> >>> petition process is complete.
> >>>
> >>> I hope that, when Lynn accepts the petitions, another effort
> >>> (or several) will be made to et Marshall's attention -- it
> >>> presumably is not too late for him to resign until after the
> >>> relevant committee is appointed.
> >>
> >> At the end of our visit, I believe that Marshall understood
> >> that there were three possibilities:
> >>
> >> 1) Tell the community that he intends to resume participation;
> >> 2) Resign;
> >> 3) Do nothing, which would very likely result in a recall.
> >>
> >> Russ
> >
> >
> >
> >
> >

From jason_livingood@cable.comcast.com  Sun Nov  4 20:15:44 2012
Return-Path: <jason_livingood@cable.comcast.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4853221F89CB for <ietf@ietfa.amsl.com>; Sun,  4 Nov 2012 20:15:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.908
X-Spam-Level: 
X-Spam-Status: No, score=-102.908 tagged_above=-999 required=5 tests=[AWL=-2.167, BAYES_00=-2.599, HOST_EQ_MODEMCABLE=1.368, IP_NOT_FRIENDLY=0.334, SUBJECT_FUZZY_TION=0.156, 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 MQVJPIkdsgXN for <ietf@ietfa.amsl.com>; Sun,  4 Nov 2012 20:15:43 -0800 (PST)
Received: from cable.comcast.com (pacdcavout01.cable.comcast.com [69.241.43.119]) by ietfa.amsl.com (Postfix) with ESMTP id B776621F8996 for <ietf@ietf.org>; Sun,  4 Nov 2012 20:15:43 -0800 (PST)
Received: from ([24.40.56.114]) by pacdcavout01.cable.comcast.com with ESMTP  id 97wm3m1.32923332; Sun, 04 Nov 2012 23:07:50 -0500
Received: from PACDCEXMB06.cable.comcast.com ([169.254.8.91]) by PACDCEXHUB01.cable.comcast.com ([fe80::84e8:95f3:f13b:169e%12]) with mapi id 14.02.0318.001; Sun, 4 Nov 2012 23:15:40 -0500
From: "Livingood, Jason" <Jason_Livingood@cable.comcast.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Recall petition for Mr. Marshall Eubanks
Thread-Topic: Recall petition for Mr. Marshall Eubanks
Thread-Index: AQHNuHoqcvZwM4mNR0SMiIcKaEKed5fVywEAgABI04CAAY0CAIAA41eAgAD1EQCAAJc/AIAAKfkA///xfICAAHuCAA==
Date: Mon, 5 Nov 2012 04:15:39 +0000
Message-ID: <10229F86C86EB444898E629583FD41712A0AC4E9@PACDCEXMB06.cable.comcast.com>
In-Reply-To: <10229F86C86EB444898E629583FD41712A0AB414@PACDCEXMB06.cable.comcast.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.4.120824
x-originating-ip: [24.40.55.71]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <431EF97AA6E6AE41B9262400E08605F8@cable.comcast.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Nov 2012 04:15:44 -0000

suppose =3D support (if you were an auto-correct program)


Grrrr...

On 11/4/12 5:59 PM, "Livingood, Jason" <Jason_Livingood@cable.comcast.com>
wrote:

>Same here. I'm noncom-eligible and suppose the recall.
>
>
>Jason Livingood
>
>On 11/4/12 11:45 AM, "Arturo Servin" <arturo.servin@gmail.com> wrote:
>
>>
>>	Thanks for the information to have a better decision.
>>
>>	I am Nomcom-eligible and you can add me to the signature list.
>>
>>
>>/Arturo Servin
>>
>>
>>On 04/11/2012 12:15, Bert Wijnen (IETF) wrote:
>>> Thanks for extra info.
>>>=20
>>> You can add me to the list who sign the request for recall.
>>>=20
>>> Bert
>>>=20
>>>> --On Saturday, 03 November, 2012 11:36 -0400 Russ Housley
>>>> <housley@vigilsec.com> wrote:
>>>>
>>>>> John:
>>>>>
>>>>>>> I assume at this point the IAOC would like to pursue the
>>>>>>> recall option?  If not, please be very clear about it to the
>>>>>>> list as I haven't actually seen a request from the IAOC for
>>>>>>> that process to proceed as far as I can tell.
>>>>>>
>>>>>> Because I am personally very reluctant to see this handled by
>>>>>> recall, I want to ask a slightly different question:  Are the
>>>>>> people who met with Marshall convinced that he understood
>>>>>> that, if he did not resign, a recall was almost certain to be
>>>>>> initiated as our next step.  If the answer is "yes", he's made
>>>>>> his choice and I am ok with signing the petition.   If not, it
>>>>>> is possible that more discussion would be in order after the
>>>>>> petition process is complete.
>>>>>>
>>>>>> I hope that, when Lynn accepts the petitions, another effort
>>>>>> (or several) will be made to et Marshall's attention -- it
>>>>>> presumably is not too late for him to resign until after the
>>>>>> relevant committee is appointed.
>>>>>
>>>>> At the end of our visit, I believe that Marshall understood
>>>>> that there were three possibilities:
>>>>>
>>>>> 1) Tell the community that he intends to resume participation;
>>>>> 2) Resign;
>>>>> 3) Do nothing, which would very likely result in a recall.
>>>>>
>>>>> Russ
>>>>
>>>>
>>>>
>>>>
>>>>
>


From aalain@trstech.net  Sun Nov  4 23:26:36 2012
Return-Path: <aalain@trstech.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1166521F8B36 for <ietf@ietfa.amsl.com>; Sun,  4 Nov 2012 23:26:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.136
X-Spam-Level: 
X-Spam-Status: No, score=0.136 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_SORBS_WEB=0.619, SUBJECT_FUZZY_TION=0.156]
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 x0E2QOG37t5r for <ietf@ietfa.amsl.com>; Sun,  4 Nov 2012 23:26:35 -0800 (PST)
Received: from trstech.net (afribone.trstech.net [196.200.57.137]) by ietfa.amsl.com (Postfix) with ESMTP id A523121F89EB for <ietf@ietf.org>; Sun,  4 Nov 2012 23:26:32 -0800 (PST)
Received: from [41.207.162.253] (helo=[192.168.3.151]) by trstech.net with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.80) (envelope-from <aalain@trstech.net>) id 1TVH5F-0003Am-5U for ietf@ietf.org; Mon, 05 Nov 2012 07:26:58 +0000
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1085)
From: ALAIN AINA <aalain@trstech.net>
In-Reply-To: <01523424-4CBE-4986-81E0-4972323D2AAF@vpnc.org>
Date: Mon, 5 Nov 2012 11:26:20 +0400
Content-Transfer-Encoding: 7bit
Message-Id: <9E2954C8-DA24-4E39-8B57-F0748EBB805F@trstech.net>
References: <50919671.6000605@ogud.com> <7F4FE714-DEDC-4D64-ADD8-AA6ECF53EABB@NLnetLabs.nl> <5092D9DB.4070602@cisco.com> <tsltxt980bc.fsf@mit.edu> <20121102034526.GB25144@mx1.yitter.info> <F1DFC16DCAA7D3468651A5A776D5796E01FF9FF7@BY2PRD0510MB366.namprd05.prod.outlook.com> <01523424-4CBE-4986-81E0-4972323D2AAF@vpnc.org>
To: IETF <ietf@ietf.org>
X-Mailer: Apple Mail (2.1085)
X-SA-Exim-Connect-IP: 41.207.162.253
X-SA-Exim-Mail-From: aalain@trstech.net
Subject: Re: Recall petition for Mr. Marshall Eubanks
X-SA-Exim-Version: 4.2.1 (built Fri, 28 Sep 2012 15:58:25 +0000)
X-SA-Exim-Scanned: Yes (on trstech.net)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Nov 2012 07:26:36 -0000

Olafur,

Add me to the  signature list. I am NomCom elligible

--Alain



From tglassey@earthlink.net  Mon Nov  5 06:53:32 2012
Return-Path: <tglassey@earthlink.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E95F321F8431 for <ietf@ietfa.amsl.com>; Mon,  5 Nov 2012 06:53:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.41
X-Spam-Level: 
X-Spam-Status: No, score=-2.41 tagged_above=-999 required=5 tests=[AWL=0.189,  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 goHlQ2Z1yT8G for <ietf@ietfa.amsl.com>; Mon,  5 Nov 2012 06:53:31 -0800 (PST)
Received: from elasmtp-junco.atl.sa.earthlink.net (elasmtp-junco.atl.sa.earthlink.net [209.86.89.63]) by ietfa.amsl.com (Postfix) with ESMTP id D68CE21F845A for <ietf@ietf.org>; Mon,  5 Nov 2012 06:53:29 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=nqJzRr96TnLeI5AsGtxgzSDJ3MA8bMQaW4dr4wdhfriLHZLvaxm65UxMJDKHZQDL; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [67.180.133.21] (helo=[192.168.15.2]) by elasmtp-junco.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <tglassey@earthlink.net>) id 1TVO3L-00010F-Gi for ietf@ietf.org; Mon, 05 Nov 2012 09:53:27 -0500
Message-ID: <5097D2EA.40506@earthlink.net>
Date: Mon, 05 Nov 2012 06:53:30 -0800
From: tglassey <tglassey@earthlink.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Antitrust FAQ
References: <AFB9BEA6-579B-4E26-A512-BE271D234F85@ietf.org> <B68EFB284B10C249835C566A0CE08AA2370EFDCD@TK5EX14MBXC263.redmond.corp.microsoft.com> <468C102D-7640-4447-9E10-B6ED70381274@vigilsec.com> <5095AD86.8010009@tana.it> <EBCE0491-BED2-45BC-9D6F-3BA603F5F6D2@vigilsec.com>
In-Reply-To: <EBCE0491-BED2-45BC-9D6F-3BA603F5F6D2@vigilsec.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec79f3f50ada5a7a6f8af05c1d88757947d5350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 67.180.133.21
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Nov 2012 14:53:32 -0000

On 11/4/2012 12:22 PM, Russ Housley wrote:
> Alessandro:
>
> No.  We held a BOF to answer exactly that question.  The conclusion was that no new policies were needed, but that educational material was desirable.
>
> Russ

Which is in fact asking the 'burglars whether they should be held 
accountable for burglarizing things"... nice oversight you have created 
- oh wait, there is no oversight here, this is the IETF...

Todd
>
>
>
> On Nov 3, 2012, at 7:49 PM, Alessandro Vesely wrote:
>
>> On Thu 01/Nov/2012 18:31:47 -0400 Russ Housley wrote:
>>> A formal policy requires IETF consensus, and it would be published
>>> as a BCP in the RFC series.
>> Isn't that's something the IETF will have do in any case, sooner or later?
>>
>> AFAICU, standardization is about establishing the competition rules.
>> Key concepts, such as open and fair participation to such activity,
>> are already treated in some BCPs.  Why would antitrust be exempted?
>>
>>> Please review the FAQ, and if you discover any issues raise them in
>>> response to this message.
>> Technical details of new protocols are an example of competitive
>> information.  When patents are involved, that would belong to the last
>> bullet of question 3, "procurement and purchasing".  Thus, sharing
>> such info might sound as a precursor to collusion.  However, question
>> 6 cannot be applied to this case.
>>
>


-- 
Regards TSG
"Ex-Cruce-Leo"

//Confidential Mailing - Please destroy this if you are not the intended recipient.


From tobias.gondrom@gondrom.org  Mon Nov  5 06:58:04 2012
Return-Path: <tobias.gondrom@gondrom.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D39C21F87A0 for <ietf@ietfa.amsl.com>; Mon,  5 Nov 2012 06:58:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -95.206
X-Spam-Level: 
X-Spam-Status: No, score=-95.206 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FM_DDDD_TIMES_2=1.999, HELO_DYNAMIC_IPADDR=2.426, HELO_EQ_DE=0.35, RDNS_DYNAMIC=0.1, SUBJECT_FUZZY_TION=0.156, 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 FF739oyHDC+Y for <ietf@ietfa.amsl.com>; Mon,  5 Nov 2012 06:58:04 -0800 (PST)
Received: from lvps176-28-13-69.dedicated.hosteurope.de (lvps176-28-13-69.dedicated.hosteurope.de [176.28.13.69]) by ietfa.amsl.com (Postfix) with ESMTP id 7B05221F8798 for <ietf@ietf.org>; Mon,  5 Nov 2012 06:58:03 -0800 (PST)
DomainKey-Signature: a=rsa-sha1;  q=dns; c=nofws; s=default; d=gondrom.org; b=db+RBR+GgOeKSGtYur7dxIAP0fV6wl3urlSE8YGgcYrwPR65BO/ewDcvatiV60PsW5nR+abSxHBl5bJ/lokaqKYaMYlI390LZwFmRykNWMXePCclNWyh404WGTMyb4Q2; h=Received:Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding;
Received: (qmail 7882 invoked from network); 5 Nov 2012 15:58:01 +0100
Received: from dhcp-546c.meeting.ietf.org (HELO ?130.129.84.108?) (130.129.84.108) by lvps176-28-13-69.dedicated.hosteurope.de with ESMTPSA (DHE-RSA-AES256-SHA encrypted, authenticated); 5 Nov 2012 15:58:00 +0100
Message-ID: <5097D3F1.9060505@gondrom.org>
Date: Mon, 05 Nov 2012 09:57:53 -0500
From: Tobias Gondrom <tobias.gondrom@gondrom.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121028 Thunderbird/16.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Recall petition for Mr. Marshall Eubanks
References: <50919671.6000605@ogud.com> <7F4FE714-DEDC-4D64-ADD8-AA6ECF53EABB@NLnetLabs.nl> <5092D9DB.4070602@cisco.com> <tsltxt980bc.fsf@mit.edu> <3153B2FE-4B52-43AF-AD10-6701CFFE0AB8@gmail.com> <20121102022203.9C7A721F96EC@ietfa.amsl.com> <1F2808D4F3783CA802322A8F@JCK-EEE10> <41DE1FC7-345F-4F79-A679-BD573295022F@vigilsec.com> <6F07B89BEBB1CE180D94EB5E@JCK-EEE10> <50967874.4070300@bwijnen.net>
In-Reply-To: <50967874.4070300@bwijnen.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Nov 2012 14:58:04 -0000

Thank you Russ for the clarification and info.

I am Nomcom-eligible and you can add me to the signature list, i.e. I 
support the recall.

Best regards, Tobias




On 04/11/12 09:15, Bert Wijnen (IETF) wrote:
> Thanks for extra info.
>
> You can add me to the list who sign the request for recall.
>
> Bert
>
>> --On Saturday, 03 November, 2012 11:36 -0400 Russ Housley
>> <housley@vigilsec.com> wrote:
>>
>>> John:
>>>
>>>>> I assume at this point the IAOC would like to pursue the
>>>>> recall option?  If not, please be very clear about it to the
>>>>> list as I haven't actually seen a request from the IAOC for
>>>>> that process to proceed as far as I can tell.
>>>>
>>>> Because I am personally very reluctant to see this handled by
>>>> recall, I want to ask a slightly different question:  Are the
>>>> people who met with Marshall convinced that he understood
>>>> that, if he did not resign, a recall was almost certain to be
>>>> initiated as our next step.  If the answer is "yes", he's made
>>>> his choice and I am ok with signing the petition.   If not, it
>>>> is possible that more discussion would be in order after the
>>>> petition process is complete.
>>>>
>>>> I hope that, when Lynn accepts the petitions, another effort
>>>> (or several) will be made to et Marshall's attention -- it
>>>> presumably is not too late for him to resign until after the
>>>> relevant committee is appointed.
>>>
>>> At the end of our visit, I believe that Marshall understood
>>> that there were three possibilities:
>>>
>>> 1) Tell the community that he intends to resume participation;
>>> 2) Resign;
>>> 3) Do nothing, which would very likely result in a recall.
>>>
>>> Russ
>>
>>
>>
>>
>>


From afarrel@juniper.net  Sun Nov  4 09:43:52 2012
Return-Path: <afarrel@juniper.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B99721F8774 for <ietf@ietfa.amsl.com>; Sun,  4 Nov 2012 09:43:52 -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 T4l4GIRmaPSP for <ietf@ietfa.amsl.com>; Sun,  4 Nov 2012 09:43:49 -0800 (PST)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) by ietfa.amsl.com (Postfix) with ESMTP id CAB4F21F8712 for <ietf@ietf.org>; Sun,  4 Nov 2012 09:43:48 -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 qA4HhjDg029706;  Sun, 4 Nov 2012 17:43:45 GMT
Received: from 950129200 (dhcp-13b5.meeting.ietf.org [130.129.19.181]) (authenticated bits=0) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id qA4HhhUn029689 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sun, 4 Nov 2012 17:43:45 GMT
From: "Adrian Farrel" <afarrel@juniper.net>
To: "'t.p.'" <daedulus@btconnect.com>, <ietf@ietf.org>
References: <20121030154625.13482.31090.idtracker@ietfa.amsl.com> <005801cdb813$894c97c0$4001a8c0@gateway.2wire.net>
In-Reply-To: <005801cdb813$894c97c0$4001a8c0@gateway.2wire.net>
Subject: RE: WG Action: Rechartered Bidirectional Forwarding Detection (bfd)
Date: Sun, 4 Nov 2012 17:43:44 -0000
Message-ID: <00bb01cdbab3$f104fa40$d30eeec0$@juniper.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQHhniOh4evmUXLYFBRFMmjGM5g1JQFaLxJpl6dZTJA=
Content-Language: en-gb
X-Mailman-Approved-At: Mon, 05 Nov 2012 07:09:39 -0800
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: afarrel@juniper.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 04 Nov 2012 17:43:52 -0000

Hello Tom.

Charter text is distinct from milestones.
The charter is discussed by IESG and put out for community review.
Milestones are set by the chairs in discussion with their AD.
The process for handling the updates is also different.

The BFD chairs agreed with me that they would update the milestones once the new
charter text was posted, so I hope we'll see that "soon".

Cheers,
Adrian

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of t.p.
> Sent: 01 November 2012 09:28
> To: ietf@ietf.org
> Subject: Re: WG Action: Rechartered Bidirectional Forwarding Detection (bfd)
> 
> I realise that the timekeeping of the IETF is not on a par with its
> engineering, but it seems a shame to promulgate a new charter for which
> every milestone is already several months in arrears.
> 
> Tom Petch
> 
> 
> ----- Original Message -----
> From: "The IESG" <iesg-secretary@ietf.org>
> To: "IETF-Announce" <ietf-announce@ietf.org>
> Cc: "bfd WG" <rtg-bfd@ietf.org>
> Sent: Tuesday, October 30, 2012 3:46 PM
> 
> > The Bidirectional Forwarding Detection (bfd) working group in the
> Routing
> > Area of the IETF has been rechartered. For additional information
> please
> > contact the Area Directors or the WG Chairs.
> >
> > Bidirectional Forwarding Detection (bfd)
> > ------------------------------------------------
> > Current Status: Active Working Group
> >
> > Chairs:
> >   David Ward <dward@cisco.com>
> >   Jeffrey Haas <jhaas@pfrc.org>
> >
> > Technical advisors:
> >   Dave Katz <dkatz@juniper.net>
> >
> > Assigned Area Director:
> >   Adrian Farrel <adrian@olddog.co.uk>
> >
> > Mailing list
> >   Address: rtg-bfd@ietf.org
> >   To Subscribe: rtg-bfd-request@ietf.org
> >   Archive: http://www.ietf.org/mail-archive/web/rtg-bfd/
> >
> > Charter of Working Group:
> >
> > The BFD Working Group is chartered to standardize and support the
> > bidirectional forwarding detection protocol (BFD) and its extensions.
> A
> > core goal of the working group is to standardize BFD in the context of
> IP
> > routing, or protocols such as MPLS that are based on IP routing, in a
> way
> > that will encourage multiple, inter-operable vendor implementations.
> The
> > Working Group will also provide advice and guidance on BFD to other
> > working groups or standards bodies as requested.
> >
> > BFD is a protocol intended to detect faults in the bidirectional path
> > between two forwarding engines, including physical interfaces,
> > subinterfaces, data link(s), and to the extent possible the forwarding
> > engines themselves, with potentially very low latency. It operates
> > independently of media, data protocols, and routing protocols. An
> > additional goal is to provide a single mechanism that can be used for
> > liveness detection over any media, at any protocol layer, with
> > a wide range of detection times and overhead, to avoid a proliferation
> > of different methods.
> >
> > Important characteristics of BFD include:
> >
> > - Simple, fixed-field encoding to facilitate implementations in
> hardware.
> >
> > - Independence of the data protocol being forwarded between two
> systems.
> >   BFD packets are carried as the payload of whatever encapsulating
> >   protocol is appropriate for the medium and network.
> >
> > - Path independence: BFD can provide failure detection on any kind of
> >   path between systems, including direct physical links, virtual
> circuits,
> >   tunnels, MPLS LSPs, multihop routed paths, and unidirectional links
> (so
> >   long as there is some return path, of course).
> >
> > - Ability to be bootstrapped by any other protocol that automatically
> >   forms peer, neighbor or adjacency relationships to seed BFD endpoint
> >   discovery.
> >
> > The working group is chartered to complete the following work items:
> >
> > 1. Develop the MIB module for BFD and submit it to the IESG for
> > publication as a Proposed Standard.
> >
> > 2a. Provide a generic keying-based cryptographic authentication
> mechanism
> > for the BFD protocol in discussion with the KARP working group.  This
> > mechanism will support authentication through a key identifier for the
> BFD
> > session's Security Association rather than specifying new
> authentication
> > extensions.
> >
> > 2b. Provide extensions to the BFD MIB in support of the generic
> > keying-based cryptographic authentication mechanism.
> >
> > 2c. Specify cryptographic authentication procedures for the BFD
> protocol
> > using HMAC-SHA-256 (possibly truncated to a smaller integrity check
> > value) using the generic keying-based cryptographic authentication
> mechanism.
> >
> > 3. Provide an extension to the BFD core protocol in support of
> point-to-
> > multipoint links and networks.
> >
> > 4. Assist the MPLS working group in the standardization of the BFD
> > protocol for MPLS-TP.  The preferred solution will be interoperable
> with the
> > current BFD specification.
> >
> > 5. Provide one or more mechanisms to run BFD over Link Aggregation
> Group
> > Interfaces.
> >
> > The working group will maintain a relationship with the KARP and MPLS
> > working groups, and will communicate with the IEEE with respect to BFD
> > over LAGs.
> >
> > Milestones:
> >   Done     - Submit the base protocol specification to the IESG to be
> > considered as a Proposed Standard
> >   Done     - Submit BFD encapsulation and usage profile for single-hop
> > IPv4 and IPv6 adjacencies to the IESG to be considered as a Proposed
> > Standard
> >   Done     - Submit BFD encapsulation and usage profile for MPLS LSPs
> to
> > the IESG to be considered as a Proposed Standard
> >   Done     - Submit BFD encapsulation and usage profile for multi-hop
> > IPv4 and IPv6 adjacencies to the IESG to be considered as a Proposed
> > Standard
> >   Sep 2011 - Submit the BFD MIB to the IESG to be considered as a
> > Proposed Standard
> >   Dec 2011 - Submit the generic keying based cryptographic
> authentication
> > mechanism to the IESG to be considered as a Proposed Standard
> >   Dec 2011 - Submit a BFD MIB extension in support of the generic
> keying
> > document to the IESG to be considered as a Proposed Standard
> >   Dec 2011 - Submit the cryptographic authentication procedures for
> BFD
> > to the IESG to be considered as a Proposed Standard
> >   Mar 2012 - Submit the the document on BFD point-to-multipoint
> support
> > to the IESG to be considered as a Proposed Standard
> >   Jun 2012 - Submit the bootstrapping mechanism for BFD using DHCP to
> the
> > IESG to be considered as a Proposed Standard
> >



From tglassey@earthlink.net  Mon Nov  5 08:04:24 2012
Return-Path: <tglassey@earthlink.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1DA2821F8728 for <ietf@ietfa.amsl.com>; Mon,  5 Nov 2012 08:04:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[AWL=0.151,  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 mZlFXaHQQuLQ for <ietf@ietfa.amsl.com>; Mon,  5 Nov 2012 08:04:23 -0800 (PST)
Received: from elasmtp-dupuy.atl.sa.earthlink.net (elasmtp-dupuy.atl.sa.earthlink.net [209.86.89.62]) by ietfa.amsl.com (Postfix) with ESMTP id 151E821F871C for <ietf@ietf.org>; Mon,  5 Nov 2012 08:04:23 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=lq11uISr2bUjo41QaTBjem4D+kRfL254Or3wRbOfLRjMskwbiBuftkmZscE8M1He; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [67.180.133.21] (helo=[192.168.15.2]) by elasmtp-dupuy.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <tglassey@earthlink.net>) id 1TVP9y-00048h-KG for ietf@ietf.org; Mon, 05 Nov 2012 11:04:22 -0500
Message-ID: <5097E389.8070803@earthlink.net>
Date: Mon, 05 Nov 2012 08:04:25 -0800
From: tglassey <tglassey@earthlink.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Antitrust FAQ
References: <AFB9BEA6-579B-4E26-A512-BE271D234F85@ietf.org> <B68EFB284B10C249835C566A0CE08AA2370EFDCD@TK5EX14MBXC263.redmond.corp.microsoft.com> <468C102D-7640-4447-9E10-B6ED70381274@vigilsec.com> <5095AD86.8010009@tana.it>
In-Reply-To: <5095AD86.8010009@tana.it>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec791299f86f17344b0465e6a635cf9e5f40350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 67.180.133.21
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Nov 2012 16:04:24 -0000

On 11/3/2012 4:49 PM, Alessandro Vesely wrote:
> On Thu 01/Nov/2012 18:31:47 -0400 Russ Housley wrote:
>> A formal policy requires IETF consensus, and it would be published
>> as a BCP in the RFC series.
> Isn't that's something the IETF will have do in any case, sooner or later?
>
> AFAICU, standardization is about establishing the competition rules.
> Key concepts, such as open and fair participation to such activity,
> are already treated in some BCPs.  Why would antitrust be exempted?
Antitrust cannot be exempted. Whether the IETF wants to allow the rule 
of law into its process or not that rule exists and sooner or later this 
chicken will come home to roost and there will be a major change in the 
IETF. Like it will become legally accountable for the damages it creates 
with these actions.

This isnt about stopping innovation - its about making the Innovators 
and particularly their sponsors accountable for the transparency which 
doesnt exist in the IETF's processes and damages to any number of 
participants therein.

Sorry, this is about playing fair - with everyone!

Todd
>> Please review the FAQ, and if you discover any issues raise them in
>> response to this message.
> Technical details of new protocols are an example of competitive
> information.  When patents are involved, that would belong to the last
> bullet of question 3, "procurement and purchasing".  Thus, sharing
> such info might sound as a precursor to collusion.  However, question
> 6 cannot be applied to this case.
>
>


-- 
Regards TSG
"Ex-Cruce-Leo"

//Confidential Mailing - Please destroy this if you are not the intended recipient.


From sm@resistor.net  Mon Nov  5 08:27:42 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F0F6F21F8861 for <ietf@ietfa.amsl.com>; Mon,  5 Nov 2012 08:27:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.327
X-Spam-Level: 
X-Spam-Status: No, score=-102.327 tagged_above=-999 required=5 tests=[AWL=0.116, BAYES_00=-2.599, SUBJECT_FUZZY_TION=0.156, 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 J4kXoCz-aRFn for <ietf@ietfa.amsl.com>; Mon,  5 Nov 2012 08:27:42 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2063121F869C for <ietf@ietf.org>; Mon,  5 Nov 2012 08:27:42 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id qA5GRZnJ012588; Mon, 5 Nov 2012 08:27:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1352132860; bh=9k61p6xrpp96PEpZY0l2fz1jYYYXEHzzpxgrpGgBtMU=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=ZFvw9ZgKIWa5oz62qEqLnpumy/dS08zAgQoZROLVwJ5AEtwirKqyzCYKSUkw3OflT 2QEtuwsp2Hb92VTMBkH6wSa+XrZ/odoDl8acBys6XFctvm59gxYO5BodBp4btkaoII X4UVdBQUuX3NKhCvEn3xI1ExqY2+f75mT00sedfI=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1352132860; i=@resistor.net; bh=9k61p6xrpp96PEpZY0l2fz1jYYYXEHzzpxgrpGgBtMU=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=VMneVwo05y2vQF77Lln+uco+3/UGYfd+DvcvoB3U/afInk16Xnbh2rCPpTVq1+LEl UxAcN49+v21wiMLkuEPStTwAlaUw080YnGLWdWSrAc54cY04G9NLuV7XWswo20Ggmg BZ+6DKqrTXrtM18WcM7OwVq0p8Pg+WOvMv/uSreQ=
Message-Id: <6.2.5.6.2.20121105081856.0b22e7c8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 05 Nov 2012 08:27:01 -0800
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: [IETF] Re: Recall petition for Mr. Marshall Eubanks
In-Reply-To: <5092C1C5.4090006@ogud.com>
References: <50919671.6000605@ogud.com> <5091CD21.3010504@gmail.com> <1158F458-8810-4CD2-B874-3DE1A1B8B0B5@kumari.net> <CAJfR-+PDvsswi3yU-H5TsK_W8RNeSwNMD2Gcdc2SksKEG1xDYQ@mail.gmail.com> <20121101175249.D92C521F89A0@ietfa.amsl.com> <5092BA96.9020909@dcrocker.net> <5092C1C5.4090006@ogud.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: Olafur Gudmundsson <ogud@ogud.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Nov 2012 16:27:43 -0000

At 10:39 01-11-2012, Olafur Gudmundsson wrote:
>As this never been attempted before, by collecting the "signatures" 
>myself, checking the NomCom eligibility and diversity in 
>organizations as required by RFC3777, I hoped to

There seems to be some misunderstanding about NomCom eligibility.  It 
might help Olafur if people double-check RFC 3777 to ensure that they 
fulfill the requirements for NomCom eligibility.  There is also the 
"oral tradition" side ...

Regards,
-sm 


From chair@ietf.org  Mon Nov  5 09:50:28 2012
Return-Path: <chair@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E1E121F8998; Mon,  5 Nov 2012 09:50:27 -0800 (PST)
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=-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 xYhsJrfsg-Us; Mon,  5 Nov 2012 09:50:27 -0800 (PST)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:123a::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id 1CF0121F8901; Mon,  5 Nov 2012 09:50:27 -0800 (PST)
Received: from localhost (c8a.amsl.com [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 16342124620; Mon,  5 Nov 2012 09:50:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E6UiLn2DvtrY; Mon,  5 Nov 2012 09:50:26 -0800 (PST)
Received: from [IPv6:2001:df8::80:6233:4bff:fe20:eb18] (unknown [IPv6:2001:df8:0:80:6233:4bff:fe20:eb18]) by c8a.amsl.com (Postfix) with ESMTPSA id B6C1312461E; Mon,  5 Nov 2012 09:50:26 -0800 (PST)
From: IETF Chair <chair@ietf.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Tao of the IETF
Date: Mon, 5 Nov 2012 12:50:25 -0500
Message-Id: <8714882D-2B29-4906-BA6B-4E88344F5714@ietf.org>
To: IETF Announce <ietf-announce@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1085)
X-Mailer: Apple Mail (2.1085)
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Nov 2012 17:50:28 -0000

As described in RFC 6722, the Tao of the IETF is published as a web =
page.  It can be found at http://www.ietf.org/tao.html.

In addition, five translations of the Tao are now available at =
http://www.ietf.org/tao-translations.html.  These languages represent =
the top five non-English languages spoken by people that attended recent =
IETF meetings.

I hope that these documents help new IETF attendees learn about the IETF =
culture.

Thanks,
Russ=

From finlayson@live555.com  Mon Nov  5 10:40:13 2012
Return-Path: <finlayson@live555.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A839C21F89EA for <ietf@ietfa.amsl.com>; Mon,  5 Nov 2012 10:40:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.996
X-Spam-Level: 
X-Spam-Status: No, score=-1.996 tagged_above=-999 required=5 tests=[AWL=0.604,  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 K39DUt40bHDd for <ietf@ietfa.amsl.com>; Mon,  5 Nov 2012 10:40:12 -0800 (PST)
Received: from ns.live555.com (ns.live555.com [4.79.217.242]) by ietfa.amsl.com (Postfix) with ESMTP id 1E50F21F89DB for <ietf@ietf.org>; Mon,  5 Nov 2012 10:40:03 -0800 (PST)
Received: from [127.0.0.1] (localhost.live555.com [127.0.0.1]) by ns.live555.com (8.14.4/8.14.4) with ESMTP id qA5Ie2hg022038 for <ietf@ietf.org>; Mon, 5 Nov 2012 10:40:03 -0800 (PST) (envelope-from finlayson@live555.com)
From: Ross Finlayson <finlayson@live555.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Why are there two different "agenda" web pages for each working group?
Message-Id: <D4AF21D8-67E2-448C-AC21-7E16ACAE07CA@live555.com>
Date: Mon, 5 Nov 2012 13:40:03 -0500
To: ietf@ietf.org
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
X-Mailer: Apple Mail (2.1499)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Nov 2012 18:40:13 -0000

The IETF85 Meeting agenda web page - =
https://datatracker.ietf.org/meeting/85/agenda.html - has links to =
"agenda" web pages for each working group.  E.g., for "avtcore", there =
is a link to:
	https://datatracker.ietf.org/meeting/85/agenda/avtcore/

However, each working group also has a second "agenda" web page, at =
http://tools.ietf.org/wg/<wg-name>/agenda .  For example, for "avtcore", =
this page is:
	http://tools.ietf.org/wg/avtcore/agenda

This second web page is usually more comprehensive than the first.  =
E.g., the second web page often contains links to slides, whereas the =
first does not.

Why are there two different "agenda" web pages?  Why not have only the =
"tools.ietf.org" web pages, and have the main agenda web page link to =
those pages instead?

	Ross.


From ogud@ogud.com  Mon Nov  5 12:15:24 2012
Return-Path: <ogud@ogud.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB33821F84E2 for <ietf@ietfa.amsl.com>; Mon,  5 Nov 2012 12:15:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.793
X-Spam-Level: 
X-Spam-Status: No, score=-103.793 tagged_above=-999 required=5 tests=[AWL=-0.350, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, SUBJECT_FUZZY_TION=0.156, 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 8uV-H9Jfdbc4 for <ietf@ietfa.amsl.com>; Mon,  5 Nov 2012 12:15:24 -0800 (PST)
Received: from smtp197.iad.emailsrvr.com (smtp197.iad.emailsrvr.com [207.97.245.197]) by ietfa.amsl.com (Postfix) with ESMTP id 0EDA421F84DA for <ietf@ietf.org>; Mon,  5 Nov 2012 12:15:24 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp29.relay.iad1a.emailsrvr.com (SMTP Server) with ESMTP id 4733014922E; Mon,  5 Nov 2012 15:15:23 -0500 (EST)
X-Virus-Scanned: OK
Received: by smtp29.relay.iad1a.emailsrvr.com (Authenticated sender: ogud-AT-ogud.com) with ESMTPSA id 12AE914921A;  Mon,  5 Nov 2012 15:15:22 -0500 (EST)
Message-ID: <50981E59.3090404@ogud.com>
Date: Mon, 05 Nov 2012 15:15:21 -0500
From: Olafur Gudmundsson <ogud@ogud.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: "Lynn St.Amour" <st.amour@isoc.org>
Subject: Recall Petition Submission
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: 'IETF-Discussion list' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Nov 2012 20:15:24 -0000

Lynn St. Amour ISOC president,

   In accordance with the rules in RFC 3777 Section 7, I request that 
you start recall proceedings  against Mr. Marshall Eubanks as member of 
the IAOC as well as IETF Trustee, due to his total disappearance from 
the IAOC and IETF Trust for over 3 months, and either inability or 
refusal to resign.

Evidence to this effect was presented by Bob Hinden [1], as well as 
further evidence that the IETF Trust ousted Mr. Eubanks as  chair of the 
IETF Trust[2] , due to his prolonged absence in that body as well .

I as an IETF member in good standing (having attended over 50 meetings 
since 1987, including 9 of the last 10 meetings), regrettably request 
that you start the recall procedure. Below are listed statements of 
support for this recall petition from  more than 20 other NomCom 
eligible IETF participants.
The IETF participants below all meet the NomCom criteria as well as the 
diversity of organizations set forth in RFC3777,
furthermore none is a current member of IETF/IAB/IRTF/IAOC/ISOC board.

Thanks

       Olafur Gudmundsson

[1] 
https://www.ietf.org/ibin/c5i?mid=6&rid=49&gid=0&k1=934&k2=11277&tid=1351092666 

[2] 
https://www.ietf.org/ibin/c5i?mid=6&rid=49&gid=0&k1=933&k2=65510&tid=1351272565 




Signatories:
Olafur Gudmundsson ogud@ogud.com  Shinkuro
Joel Jaeggeli joelja@bogus.com    Zynga inc.
Mike StJohns mstjohns@ comcast.net   ninethpermutation
Warren Kumari <warren@kumari.net>  Google
Margaret Wasserman margaretw42@gmail.com  Painless Security, LLC

Olaf Kolkman olaf@nlnetlabs.nl NlNetLabs
Melinda Shore melinda.shore@gmail.com No Mountain Software
Fred Baker fred@cisco.com   Cisco
Jaap Akkerhuis jaap@NLnetLabs.nl NlNetLabs
James Polk jmpolk@cisco.com   Cisco

Sam Hartman hartmans-ietf@mit.edu   Painless Security, LLC.
Andrew Sullivan ajs@anvilwalrusden.com   Dyn Inc.
Stephen Hanna <shanna@juniper.net>   Jupiter
Henk Uijterwaal henk.uijerwaal@gmail.com Netherlands Forensics Institute
Paul Hoffman <paul.hoffman@vpnc.org>    VPNC

John Klensin john-ietf@jck.com  Self
Mehmet Ersue mehmet.esue@nsn.com  Nokia Siemens Networks
Tobias Gondrom tobias.gondrom@gondrom.org  Thames Stanley
Yiu Lee Yiu_Lee@Cable.Comcast.com  Comcast
Tero Kivinen kivinen@iki.fi  AuthenTec Oy


From touch@isi.edu  Mon Nov  5 13:24:28 2012
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2697021F8676 for <ietf@ietfa.amsl.com>; Mon,  5 Nov 2012 13:24:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.379
X-Spam-Level: 
X-Spam-Status: No, score=-103.379 tagged_above=-999 required=5 tests=[AWL=-0.780, 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 g4N9TuAcAtl1 for <ietf@ietfa.amsl.com>; Mon,  5 Nov 2012 13:24:27 -0800 (PST)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by ietfa.amsl.com (Postfix) with ESMTP id 8A81C21F8620 for <ietf@ietf.org>; Mon,  5 Nov 2012 13:24:27 -0800 (PST)
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 qA5LNeT3019363 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 5 Nov 2012 13:23:41 -0800 (PST)
Message-ID: <50982E5C.30808@isi.edu>
Date: Mon, 05 Nov 2012 13:23:40 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: IETF discussion list <ietf@ietf.org>
Subject: CFP -  2nd IEEE Workshop On Telecommunications Standards
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Nov 2012 21:24:28 -0000

Hi, all,

The following is hopefully of interest to the IETF community.

Joe

----------------------------------

                CALL FOR PAPERS
       2nd IEEE Workshop On Telecommunications Standards
              “From Research to Standards”

           June 9-13, 2013, Budapest, Hungary
             Co-located with IEEE ICC 2013

                   http://www.research2standards.net/

Paper abstract deadline Jan 4, 2013
Paper submission deadline Jan 11, 2013

Building on the success of the first edition of the IEEE Workshop on 
Telecommunications Standards: "From Research to Standards" (which won 
the Best IEEE ComSoc Workshop Award at IEEE ICC 2012), we are happy to 
announce the organization of its second edition in Budapest, Hungary, 
collocated with IEEE ICC 2013.

The goal of this Workshop is to bridge the gap between researchers, 
scientists, and standards experts in both academia and industry and to 
promote standardization as an important vehicle for information sharing 
and cooperation between academia and industry. An additional goal is to 
  bring together experts from different standardization bodies, 
providing opportunities for closer understanding and collaboration; 
catalyzing development of more interoperable standards and more 
efficient and effective communication systems.

The Workshop technical program will deliver high quality technical as 
well as visionary papers that will be reviewed and selected by an 
international program committee representing both academia and industry 
with a strong standardization background. All submissions are required 
to comply with ICC’s guidelines. Accepted papers will appear in IEEE Xplore.

Looking forward your submissions to the 2nd IEEE Workshop on 
Telecommunications Standards: "From Research to Standards".

Kind regards,

Workshop Official Website: http://www.research2standards.net

Workshop General Chair
• Dr. Tarik Taleb, NEC Europe, Germany
TPC co-Chairs
• Dr. Tuncer Baykas, Tohoku University, Japan
• Dr. Alex Reznik, InterDigital, USA
• Dr. Konstantinos Samdanis , NEC Europe, Germany
Publicity co-chairs
• Prof. Joe Touch, Univ. of Southern California, USA
• Dr. Periklis Chatzimisios, Alexander TEI of Thessaloniki, Greece

IMPORTANT DATES
PAPER REGISTRATION: Jan. 04, 2013 SUBMISSION DEADLINE: Jan. 11, 2013 
ACCEPTANCE NOTIFICATION: Feb. 22, 2013 FINAL MANUSCRIPT: Mar. 08, 2013

From carlosm3011@gmail.com  Mon Nov  5 16:11:04 2012
Return-Path: <carlosm3011@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A630A1F0C54 for <ietf@ietfa.amsl.com>; Mon,  5 Nov 2012 16:11:04 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f2IdBYKkt5RS for <ietf@ietfa.amsl.com>; Mon,  5 Nov 2012 16:11:04 -0800 (PST)
Received: from mail-pa0-f44.google.com (mail-pa0-f44.google.com [209.85.220.44]) by ietfa.amsl.com (Postfix) with ESMTP id 96DDA1F0C49 for <ietf@ietf.org>; Mon,  5 Nov 2012 16:11:01 -0800 (PST)
Received: by mail-pa0-f44.google.com with SMTP id fb11so4297727pad.31 for <ietf@ietf.org>; Mon, 05 Nov 2012 16:11:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=YrarDQtyAGouStO1oYNa5l7JFglwUpMy9dn8zzKnHC0=; b=09eWvXZuD1P8+iYrKrq2wtCdkO1nXsjPGugI5sbErWGsWmS/Q6iIgX/rdC9uolFY4G XooOVoQBcpuoQ8+uExEDXFvZZ9R5gswCwRtdDeIcW/YTGAFnL/1jdNp7kkSAuTF31rPG qUU9NDEI+QFSVVADFPEwAdDfonhoUnheYf5wuUkUZDr6VUrsSI2k1hzM0K8oS9ztL5+6 9vzcJ3rOQb/94QXA3YumR+Tn3K5jsbsaRI9Ilc8EhkSLWDNRKVP4t9CiV2tqRIZRHuME MX5LXLi4e1VRf7CAh+wcNJjT3zZlhMqvxyRxTsJjjmkVMgpkXlSqIwJi08mC0Vmx3bZC Sfjg==
Received: by 10.68.251.197 with SMTP id zm5mr34918663pbc.30.1352160661361; Mon, 05 Nov 2012 16:11:01 -0800 (PST)
Received: from ?IPv6:2001:df8:0:16:1472:c52:6039:f5a2? ([2001:df8:0:16:1472:c52:6039:f5a2]) by mx.google.com with ESMTPS id jw14sm11298311pbb.36.2012.11.05.16.10.56 (version=SSLv3 cipher=OTHER); Mon, 05 Nov 2012 16:10:57 -0800 (PST)
Message-ID: <50985590.5080507@gmail.com>
Date: Mon, 05 Nov 2012 19:10:56 -0500
From: "Carlos M. martinez" <carlosm3011@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Is there ongoing work on SNMP IPv6 mibs ?
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Nov 2012 00:11:04 -0000

Other than the CGN-mib we discussed today in sunset4, I wondered whether
is there ongoing work on this topic.

regards

Carlos

From simon.perreault@viagenie.ca  Mon Nov  5 16:18:51 2012
Return-Path: <simon.perreault@viagenie.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8DEAA11E80AD for <ietf@ietfa.amsl.com>; Mon,  5 Nov 2012 16:18:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, NO_RELAYS=-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 Erud1H3tSE5N for <ietf@ietfa.amsl.com>; Mon,  5 Nov 2012 16:18:51 -0800 (PST)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id 0002F21F84DF for <ietf@ietf.org>; Mon,  5 Nov 2012 16:18:50 -0800 (PST)
Received: from porto.nomis80.org (unknown [IPv6:2001:df8:0:16:3d84:372:9328:b7f]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 66885415AF for <ietf@ietf.org>; Mon,  5 Nov 2012 19:18:50 -0500 (EST)
Message-ID: <50985769.1040704@viagenie.ca>
Date: Mon, 05 Nov 2012 19:18:49 -0500
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121016 Thunderbird/16.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Is there ongoing work on SNMP IPv6 mibs ?
References: <50985590.5080507@gmail.com>
In-Reply-To: <50985590.5080507@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Nov 2012 00:18:51 -0000

Le 2012-11-05 19:10, Carlos M. martinez a écrit :
> Other than the CGN-mib we discussed today in sunset4, I wondered whether
> is there ongoing work on this topic.

What do you mean exactly? Because there is nothing IPv6-specific in the 
CGN MIB (or NAT MIB), it's all address-family agnostic...

Simon
-- 
DTN made easy, lean, and smart --> http://postellation.viagenie.ca
NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
STUN/TURN server               --> http://numb.viagenie.ca

From carlosm3011@gmail.com  Mon Nov  5 16:21:42 2012
Return-Path: <carlosm3011@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 958271F0C67 for <ietf@ietfa.amsl.com>; Mon,  5 Nov 2012 16:21:42 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AJ7RYql3fK5i for <ietf@ietfa.amsl.com>; Mon,  5 Nov 2012 16:21:42 -0800 (PST)
Received: from mail-pa0-f44.google.com (mail-pa0-f44.google.com [209.85.220.44]) by ietfa.amsl.com (Postfix) with ESMTP id 221211F0C61 for <ietf@ietf.org>; Mon,  5 Nov 2012 16:21:42 -0800 (PST)
Received: by mail-pa0-f44.google.com with SMTP id fb11so4302729pad.31 for <ietf@ietf.org>; Mon, 05 Nov 2012 16:21:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=zGz7XH7eSoF+udC/31EJUnFWmwtFVAdiIvhWjLCDMsg=; b=VzkeHI0/uRXvhoYYAUxc8NeT6jK0UO7RZeUz18uMydV1vhXxIkDNlLpXOT79iBuA8g GuKQ0ykbAgwiTOyGvBRFGPqTExPRHFZNthewjZ4L5q2UVZ3VYHG329kAsfWud90VaSsi znsGyVA/gcE+x4Yd5e0X+DVA5aUXlSYniDujX9/EO4ikjpAWjY6uRgg8Xczxe90VJeLw ED4jylekaL3fYc8oWnCxXk04HW5NfsjOU5kFlZlJ60/u06HLGgWN7umlAiO0jm4PvMUc lGhcEajhRAbbol5WLkBPsSwyu7A1Ct7kNl14+5hwjirGd3QEVRj7P1wmZ0kzfKtJzcxT D1Cw==
Received: by 10.66.88.136 with SMTP id bg8mr27872941pab.54.1352161301698; Mon, 05 Nov 2012 16:21:41 -0800 (PST)
Received: from ?IPv6:2001:df8:0:16:1472:c52:6039:f5a2? ([2001:df8:0:16:1472:c52:6039:f5a2]) by mx.google.com with ESMTPS id vs3sm11305397pbc.61.2012.11.05.16.21.39 (version=SSLv3 cipher=OTHER); Mon, 05 Nov 2012 16:21:40 -0800 (PST)
Message-ID: <50985812.1020905@gmail.com>
Date: Mon, 05 Nov 2012 19:21:38 -0500
From: "Carlos M. martinez" <carlosm3011@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: Simon Perreault <simon.perreault@viagenie.ca>
Subject: Re: Is there ongoing work on SNMP IPv6 mibs ?
References: <50985590.5080507@gmail.com> <50985769.1040704@viagenie.ca>
In-Reply-To: <50985769.1040704@viagenie.ca>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Nov 2012 00:21:42 -0000

Right, I have this thing that mentions to CGN somehow mean 'ipv6' to me,
or rather, 'i don't want to do ipv6'

But you are right, there is nothing specific to ipv6 in your work.

~Carlos

On 11/5/2012 7:18 PM, Simon Perreault wrote:
> Le 2012-11-05 19:10, Carlos M. martinez a écrit :
>> Other than the CGN-mib we discussed today in sunset4, I wondered whether
>> is there ongoing work on this topic.
> 
> What do you mean exactly? Because there is nothing IPv6-specific in the
> CGN MIB (or NAT MIB), it's all address-family agnostic...
> 
> Simon

From stephen.farrell@cs.tcd.ie  Tue Nov  6 06:39:39 2012
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 36B5321F898E for <ietf@ietfa.amsl.com>; Tue,  6 Nov 2012 06:39:39 -0800 (PST)
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=[AWL=0.000, 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 7hOc69q5JtFV for <ietf@ietfa.amsl.com>; Tue,  6 Nov 2012 06:39:33 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id AF96021F859F for <ietf@ietf.org>; Tue,  6 Nov 2012 06:39:33 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 90785BE4C for <ietf@ietf.org>; Tue,  6 Nov 2012 14:39:10 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cxuMKGcvtwCN for <ietf@ietf.org>; Tue,  6 Nov 2012 14:39:06 +0000 (GMT)
Received: from [130.129.96.58] (dhcp-603a.meeting.ietf.org [130.129.96.58]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id B74A1BE49 for <ietf@ietf.org>; Tue,  6 Nov 2012 14:39:05 +0000 (GMT)
Message-ID: <50992108.4080604@cs.tcd.ie>
Date: Tue, 06 Nov 2012 14:39:04 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121028 Thunderbird/16.0.2
MIME-Version: 1.0
To: IETF-Discussion <ietf@ietf.org>
Subject: sec ADs office hours
X-Enigmail-Version: 1.4.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Nov 2012 14:39:39 -0000

Hi,

Some area directors do "office hours" where they're available
in case folks want to chat about a discuss or other topic. Sean
and I haven't been doing that to date but have decided to give
it a try this time.

So the SEC ADs will be available in room 202 on Thursday from
1300-1500, if you want to come along to talk about some security
thing.

Cheers & sorry for the late notice,
S.

From chair@ietf.org  Tue Nov  6 07:01:00 2012
Return-Path: <chair@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D59621F8957; Tue,  6 Nov 2012 07:01:00 -0800 (PST)
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=-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 hgFc1ZVbrPQF; Tue,  6 Nov 2012 07:01:00 -0800 (PST)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:123a::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id 21BBB21F8953; Tue,  6 Nov 2012 07:00:58 -0800 (PST)
Received: from localhost (c8a.amsl.com [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 0B2A21249BA; Tue,  6 Nov 2012 07:00:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JrDqgc1Rix3C; Tue,  6 Nov 2012 07:00:57 -0800 (PST)
Received: from [IPv6:2001:df8::80:6233:4bff:fe20:eb18] (unknown [IPv6:2001:df8:0:80:6233:4bff:fe20:eb18]) by c8a.amsl.com (Postfix) with ESMTPSA id B26B41249B8; Tue,  6 Nov 2012 07:00:57 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Subject: IESG Considering a Revision to NOTE WELL
Mime-Version: 1.0 (Apple Message framework v1085)
From: IETF Chair <chair@ietf.org>
Date: Tue, 6 Nov 2012 10:00:56 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <55D046F8-5DD2-42E8-9B8C-36C612C4B3F8@ietf.org>
To: IETF Announce <ietf-announce@ietf.org>
X-Mailer: Apple Mail (2.1085)
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: IETF <ietf@ietf.org>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Nov 2012 15:01:00 -0000

The IESG is considering a revision to the NOTE WELL text.  Please review =
and comment.

Russ



=3D=3D=3D Proposed Revised NOTE WELL Text =3D=3D=3D

Note Well

This summary is only meant to point you in the right direction, and
doesn't have all the nuances. The IETF's IPR Policy is set forth in
BCP 79; please read it carefully.

The brief summary:
  - By participating with the IETF, you agree to follow IETF processes.
  - If you are aware that a contribution of yours (something you write,
    say, or discuss in any IETF context) is covered by patents or patent
    applications, you need to disclose that fact.
  - You understand that meetings might be recorded, broadcast, and
   publicly archived.

For further information: Talk to a chair, ask an Area Director, or
review  BCP 9 (on the Internet Standards Process), BCP 25 (on the
Working Group processes), BCP 78 (on the IETF Trust), and BCP 79 (on
Intellectual Property Rights in the IETF).=

From ted.ietf@gmail.com  Tue Nov  6 07:14:46 2012
Return-Path: <ted.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E104F21F884B; Tue,  6 Nov 2012 07:14:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.372
X-Spam-Level: 
X-Spam-Status: No, score=-3.372 tagged_above=-999 required=5 tests=[AWL=0.227,  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 wOAOuihNFXyr; Tue,  6 Nov 2012 07:14:46 -0800 (PST)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 2381F21F8958; Tue,  6 Nov 2012 07:14:46 -0800 (PST)
Received: by mail-vb0-f44.google.com with SMTP id fc26so542528vbb.31 for <multiple recipients>; Tue, 06 Nov 2012 07:14:34 -0800 (PST)
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 :cc:content-type; bh=Q2PI2FdaTtX/AEJzX4dW8wrSXKtcWt5Em+zta1XFNDA=; b=B8sUvLhrpKhSgGgnl6PlNXMGW1cuRQq3bmyYhD1Rqr2WJoswnJ7OiL7bsZg43y33HP s3lPUaNzDebYl2MF4HSYC+KG0y3feiGh9rI9NEirUEGHn23uWO2y1uVjP3VklOzBuDyh qU3R9AFDZfbOrJLmA1AHmngTC5FVjLDXI/W+MAR5cp/6h2kNL3wfACEnqza6SYEqMg5k X8qn7XGKRnFFj5GgM8QcusIrBNrcUIaHCw16rhpiUWxDGAThCw6qm46PhQ2Esn5aCl3V byJYN36DQjQkg61QDBBxe+vkpRKbKhKdw2l9tbcLRgCIKFjcGL3jNtAS2jKH1yY2Fgda msQw==
MIME-Version: 1.0
Received: by 10.52.37.103 with SMTP id x7mr997745vdj.61.1352214873917; Tue, 06 Nov 2012 07:14:33 -0800 (PST)
Received: by 10.58.164.35 with HTTP; Tue, 6 Nov 2012 07:14:33 -0800 (PST)
In-Reply-To: <55D046F8-5DD2-42E8-9B8C-36C612C4B3F8@ietf.org>
References: <55D046F8-5DD2-42E8-9B8C-36C612C4B3F8@ietf.org>
Date: Tue, 6 Nov 2012 10:14:33 -0500
Message-ID: <CA+9kkMD6qRuW1xOEv-wj5h8aXkdcMZppGbK4dg=D=OGdwcQUug@mail.gmail.com>
Subject: Re: IESG Considering a Revision to NOTE WELL
From: Ted Hardie <ted.ietf@gmail.com>
To: IETF <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Cc: IETF Announce <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Nov 2012 15:14:47 -0000

On Tue, Nov 6, 2012 at 10:00 AM, IETF Chair <chair@ietf.org> wrote
> The IESG is considering a revision to the NOTE WELL text.  Please review and comment.
>
> Russ
>
>
This same text would read better to me if reordered:

"NOTE WELL

- By participating with the IETF, you agree to follow IETF processes.
  - If you are aware that a contribution of yours (something you write,
    say, or discuss in any IETF context) is covered by patents or patent
    applications, you need to disclose that fact.
  - You understand that meetings might be recorded, broadcast, and
   publicly archived.

This summary is only meant to point you in the right direction, and
doesn't have all the nuances. The IETF's IPR Policy is set forth in
BCP 79; please read it carefully.

For further information: Talk to a chair, ask an Area Director, or
review  BCP 9 (on the Internet Standards Process), BCP 25 (on the
Working Group processes), BCP 78 (on the IETF Trust), and BCP 79 (on
Intellectual Property Rights in the IETF)."

That puts the most important information higher up the text and, to my
eyes at least,
makes it more prominent.

My two cents,

Ted Hardie


>
> === Proposed Revised NOTE WELL Text ===
>
> Note Well
>
> This summary is only meant to point you in the right direction, and
> doesn't have all the nuances. The IETF's IPR Policy is set forth in
> BCP 79; please read it carefully.
>
> The brief summary:
>   - By participating with the IETF, you agree to follow IETF processes.
>   - If you are aware that a contribution of yours (something you write,
>     say, or discuss in any IETF context) is covered by patents or patent
>     applications, you need to disclose that fact.
>   - You understand that meetings might be recorded, broadcast, and
>    publicly archived.
>
> For further information: Talk to a chair, ask an Area Director, or
> review  BCP 9 (on the Internet Standards Process), BCP 25 (on the
> Working Group processes), BCP 78 (on the IETF Trust), and BCP 79 (on
> Intellectual Property Rights in the IETF).

From brian.e.carpenter@gmail.com  Tue Nov  6 07:25:33 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 78FDC21F8957 for <ietf@ietfa.amsl.com>; Tue,  6 Nov 2012 07:25:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.576
X-Spam-Level: 
X-Spam-Status: No, score=-103.576 tagged_above=-999 required=5 tests=[AWL=0.023, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, 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 Fi3DkAXSSJbY for <ietf@ietfa.amsl.com>; Tue,  6 Nov 2012 07:25:33 -0800 (PST)
Received: from mail-da0-f44.google.com (mail-da0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id EA5A221F8953 for <ietf@ietf.org>; Tue,  6 Nov 2012 07:25:32 -0800 (PST)
Received: by mail-da0-f44.google.com with SMTP id h15so254630dan.31 for <ietf@ietf.org>; Tue, 06 Nov 2012 07:25:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=P1lm/ibs1dsCqBXxhGReCm80Ife+hkLXVlJl0qkmstE=; b=khaqt+EfqrZbSkC06RPlz8vNYBHOLLNH755TPP6Mv8A8AgZ34JGy936IoCryHRLX4f fDt2VBw1ld7cSxg0AvT7L+ss9Q7oEvDgSgaSBItPPupC7tT8IPYeAxZHdAqepP4CU/k5 C0tyJCo63u3plgxH+OZ/YybeVtNu2BX3VIzwEgJv7fPQ/xjiNHxIWfHZO58GpATPQkGx xLLwph2/oM9C8PiuD4asylZvnLeStsQeZ61HLoGuTQToTmNAN/eYhlugsRkpEEjwrYv8 nDfQGVzfVN5agy+Rz0Ih2xwvzvGMZXJnF9NdxM5SoGCJOBa7ELsj7H+IExBJet2qNNFc aETw==
Received: by 10.66.79.166 with SMTP id k6mr3621319pax.25.1352215532535; Tue, 06 Nov 2012 07:25:32 -0800 (PST)
Received: from [130.129.19.51] (dhcp-1333.meeting.ietf.org. [130.129.19.51]) by mx.google.com with ESMTPS id mz10sm12493692pbc.37.2012.11.06.07.25.30 (version=SSLv3 cipher=OTHER); Tue, 06 Nov 2012 07:25:31 -0800 (PST)
Message-ID: <50992BEF.9000803@gmail.com>
Date: Tue, 06 Nov 2012 15:25:35 +0000
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: IETF <ietf@ietf.org>
Subject: Re: IESG Considering a Revision to NOTE WELL
References: <55D046F8-5DD2-42E8-9B8C-36C612C4B3F8@ietf.org>
In-Reply-To: <55D046F8-5DD2-42E8-9B8C-36C612C4B3F8@ietf.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Nov 2012 15:25:33 -0000

I don't much like the change in approach. I think it will be too easy
to brush off; the current approach has enough substance that people
who brush it off put themselves in a very weak position.

The old text was written with legal advice. What does counsel say
about the new proposal?

Regards
   Brian Carpenter
   Cell phone during IETF85: +1 847 219 0880

On 06/11/2012 15:00, IETF Chair wrote:
> The IESG is considering a revision to the NOTE WELL text.  Please review and comment.
> 
> Russ
> 
> 
> 
> === Proposed Revised NOTE WELL Text ===
> 
> Note Well
> 
> This summary is only meant to point you in the right direction, and
> doesn't have all the nuances. The IETF's IPR Policy is set forth in
> BCP 79; please read it carefully.
> 
> The brief summary:
>   - By participating with the IETF, you agree to follow IETF processes.
>   - If you are aware that a contribution of yours (something you write,
>     say, or discuss in any IETF context) is covered by patents or patent
>     applications, you need to disclose that fact.
>   - You understand that meetings might be recorded, broadcast, and
>    publicly archived.
> 
> For further information: Talk to a chair, ask an Area Director, or
> review  BCP 9 (on the Internet Standards Process), BCP 25 (on the
> Working Group processes), BCP 78 (on the IETF Trust), and BCP 79 (on
> Intellectual Property Rights in the IETF).

From johnl@iecc.com  Tue Nov  6 07:26:03 2012
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E45FE21F8998 for <ietf@ietfa.amsl.com>; Tue,  6 Nov 2012 07:26:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.971
X-Spam-Level: 
X-Spam-Status: No, score=-111.971 tagged_above=-999 required=5 tests=[AWL=0.228, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, RCVD_IN_DNSWL_LOW=-1, 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 2VuCiK0eNRTh for <ietf@ietfa.amsl.com>; Tue,  6 Nov 2012 07:26:01 -0800 (PST)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 7268821F8955 for <ietf@ietf.org>; Tue,  6 Nov 2012 07:26:01 -0800 (PST)
Received: (qmail 63184 invoked from network); 6 Nov 2012 15:26:00 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 6 Nov 2012 15:26:00 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=50992c08.xn--i8sz2z.k1211; i=johnl@user.iecc.com; bh=MB4eHbLboruP9Qrc49MJER8zKwq1bGV+qFrfsfpIt8s=; b=JgA2INmPkwqmnTEjww1vR+nYsvwXxjJUdSdpQ96nLHf2JjRe/JwPKsJUlbZgHL5dK6kKZV5yLyoQE7nEQHwMTTiNP6DCNJBiJRfMvtVCpPKPIYJBZ/kUhWilDM+5r72fmASGmZUxRK+1L41XSoZFQkFbalVYaVnobQFBDUDgjyE=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=50992c08.xn--i8sz2z.k1211; olt=johnl@user.iecc.com; bh=MB4eHbLboruP9Qrc49MJER8zKwq1bGV+qFrfsfpIt8s=; b=l05HCloH+BlfUlvxY3C2kbwdNJm8+NShiTvBLY+6hmFY+BpKH7yvVK4EFBDGUEt4bmUsIpcmHv9vP6ksfcYnLPNDit6IFy4/z8sBvza6yIucXxhTSfdETrCYROQMmA2S08kfkZhmuQ/sVr/rEaPejsgWkcHCyy9L12YZFXO8mdY=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 6 Nov 2012 15:25:38 -0000
Message-ID: <20121106152538.4562.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: IESG Considering a Revision to NOTE WELL
In-Reply-To: <55D046F8-5DD2-42E8-9B8C-36C612C4B3F8@ietf.org>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Nov 2012 15:26:03 -0000

Looks much better, people might even read it.

>  - If you are aware that a contribution of yours (something you write,
>    say, or discuss in any IETF context) is covered by patents or patent
>    applications, you need to disclose that fact.

Perhaps "disclose that fact promptly."

Pete's been reminding us that postponing IPR disclosures until last
call or IESG review is not good.

R's,
John

From lars@netapp.com  Tue Nov  6 07:33:43 2012
Return-Path: <lars@netapp.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A22C921F879A for <ietf@ietfa.amsl.com>; Tue,  6 Nov 2012 07:33:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.504
X-Spam-Level: 
X-Spam-Status: No, score=-10.504 tagged_above=-999 required=5 tests=[AWL=0.095, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 h7utU9it-r9X for <ietf@ietfa.amsl.com>; Tue,  6 Nov 2012 07:33:43 -0800 (PST)
Received: from mx12.netapp.com (mx12.netapp.com [216.240.18.77]) by ietfa.amsl.com (Postfix) with ESMTP id 384AE21F87EA for <ietf@ietf.org>; Tue,  6 Nov 2012 07:33:43 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.80,722,1344236400";  d="p7s'?scan'208";a="278983003"
Received: from smtp2.corp.netapp.com ([10.57.159.114]) by mx12-out.netapp.com with ESMTP; 06 Nov 2012 07:33:42 -0800
Received: from vmwexceht05-prd.hq.netapp.com (exchsmtp.hq.netapp.com [10.106.77.35]) by smtp2.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id qA6FXfR0021722; Tue, 6 Nov 2012 07:33:42 -0800 (PST)
Received: from VMWEXCEHT06-PRD.hq.netapp.com (10.106.77.104) by vmwexceht05-prd.hq.netapp.com (10.106.77.35) with Microsoft SMTP Server (TLS) id 14.2.318.1; Tue, 6 Nov 2012 07:33:42 -0800
Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.216]) by vmwexceht06-prd.hq.netapp.com ([10.106.77.104]) with mapi id 14.02.0318.001; Tue, 6 Nov 2012 07:33:41 -0800
From: "Eggert, Lars" <lars@netapp.com>
To: John Levine <johnl@taugh.com>
Subject: Re: IESG Considering a Revision to NOTE WELL
Thread-Topic: IESG Considering a Revision to NOTE WELL
Thread-Index: AQHNvC+NwCxX9AtBsECZ3UxC2YYnj5fdc68AgAACPoA=
Date: Tue, 6 Nov 2012 15:32:49 +0000
Message-ID: <D4D47BCFFE5A004F95D707546AC0D7E9185DB94C@SACEXCMBX01-PRD.hq.netapp.com>
References: <20121106152538.4562.qmail@joyce.lan>
In-Reply-To: <20121106152538.4562.qmail@joyce.lan>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.104.60.116]
Content-Type: multipart/signed; boundary="Apple-Mail=_785A78A3-27E5-4E91-8CCB-65E99DAD71CE"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
Cc: "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Nov 2012 15:33:43 -0000

--Apple-Mail=_785A78A3-27E5-4E91-8CCB-65E99DAD71CE
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Nov 6, 2012, at 10:25, John Levine <johnl@taugh.com> wrote:
> Perhaps "disclose that fact promptly."

+1

Since not everyone is aware of what's going on in the IRTF: we recently =
made a minor modification to our IPR statement to that effect. See =
https://www.irtf.org/ipr

One possibility would be that the IESG adopt what we did for the IRTF =
also for the IRTF...

Lars=

--Apple-Mail=_785A78A3-27E5-4E91-8CCB-65E99DAD71CE
Content-Disposition: attachment; filename="smime.p7s"
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIMQDCCBUow
ggQyoAMCAQICEFcfSRTG0jNknqb9LV9GuFkwDQYJKoZIhvcNAQEFBQAwgd0xCzAJBgNVBAYTAlVT
MRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29y
azE7MDkGA1UECxMyVGVybXMgb2YgdXNlIGF0IGh0dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9ycGEg
KGMpMDkxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZhbGlkYXRlZDE3MDUGA1UEAxMuVmVyaVNpZ24g
Q2xhc3MgMSBJbmRpdmlkdWFsIFN1YnNjcmliZXIgQ0EgLSBHMzAeFw0xMTEyMTAwMDAwMDBaFw0x
MjEyMDkyMzU5NTlaMIIBDTEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlT
aWduIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9S
UEEgSW5jb3JwLiBieSBSZWYuLExJQUIuTFREKGMpOTgxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZh
bGlkYXRlZDEzMDEGA1UECxMqRGlnaXRhbCBJRCBDbGFzcyAxIC0gTmV0c2NhcGUgRnVsbCBTZXJ2
aWNlMRQwEgYDVQQDFAtMYXJzIEVnZ2VydDEeMBwGCSqGSIb3DQEJARYPbGFyc0BuZXRhcHAuY29t
MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAokrhJTcXt6J/VEpZOicLoguBlYTjXP9v
Ze4HuuhXnURUS8YouAfgaqA0zYbt5yd6fh4PBMdAaEWr5yJyHuFykXlrCumjUWSpLuqTS2A+pt4q
cZaAQk9iLDN/UVd3SpkUuvWbxXlqzG7/BSqa3VNObBzCmyh+V7aXxri+30CT//DSsNRC4VFy6sn6
dMgSaFenXLwe/FBwY0qTMfICT1PrrX6Sw1S8OfH9rykLlZXbmfkFExxQngp1DJH9xMHeODHGbCv/
ty5gdxMOrLe+vENxFEcy1YQWBZd1kNL4UObugF8A/jE/s+Oa3H1VFH8ghqZTdqGDysVxmtKHuNFx
6jIBSQIDAQABo4HSMIHPMAkGA1UdEwQCMAAwRAYDVR0gBD0wOzA5BgtghkgBhvhFAQcXATAqMCgG
CCsGAQUFBwIBFhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBhMAsGA1UdDwQEAwIFoDAdBgNV
HSUEFjAUBggrBgEFBQcDBAYIKwYBBQUHAwIwUAYDVR0fBEkwRzBFoEOgQYY/aHR0cDovL2luZGMx
ZGlnaXRhbGlkLWczLWNybC52ZXJpc2lnbi5jb20vSW5kQzFEaWdpdGFsSUQtRzMuY3JsMA0GCSqG
SIb3DQEBBQUAA4IBAQBA7q6tR92qpd7xo7VBsrOfGCWzoxIVfTc7t0RhB/Oz/+c3lnhYnNScIuKN
JmyZvznmVxqB9BJ72+NkvmdB/hnILSBTRawL2tyLo9PkBtN0nRt4gS6wjpWnD8G83hlJLE7r25jk
7HkRev61dTIXsANFpJKF02C4XSoDfEzNV6MpuEvHvcgHCqMrlwWwfKc7+NoDnE8PBuRzwSXvlD5L
mswCY2iiOsd7ImNO4OzTCxETvKTDu92+FTIbRJJpYjVNv1UF7e3w9Kq65BkZJErUH19beUeQl0Wh
2BJQE6/15rQyCnP0iJ/Nmx2/kI6M0PWunEsI6FMs0MbosreaWGHlQmomMIIG7jCCBdagAwIBAgIQ
cRVmBUrkkSFN6bxE+azT3DANBgkqhkiG9w0BAQUFADCByjELMAkGA1UEBhMCVVMxFzAVBgNVBAoT
DlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTowOAYDVQQL
EzEoYykgMTk5OSBWZXJpU2lnbiwgSW5jLiAtIEZvciBhdXRob3JpemVkIHVzZSBvbmx5MUUwQwYD
VQQDEzxWZXJpU2lnbiBDbGFzcyAxIFB1YmxpYyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9y
aXR5IC0gRzMwHhcNMDkwNTAxMDAwMDAwWhcNMTkwNDMwMjM1OTU5WjCB3TELMAkGA1UEBhMCVVMx
FzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3Jr
MTswOQYDVQQLEzJUZXJtcyBvZiB1c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAo
YykwOTEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBD
bGFzcyAxIEluZGl2aWR1YWwgU3Vic2NyaWJlciBDQSAtIEczMIIBIjANBgkqhkiG9w0BAQEFAAOC
AQ8AMIIBCgKCAQEA7cRH3yooHXwGa7vXITLJbBOP6bGNQU4099oL42r6ZYggCxET6ZvgSU6Lb9UB
0F8NR5GKWkx0Pj/GkQm7TDSejW6hglFi92l2WJYHr54UGAdPWr2f0jGyVBlzRmoZQhHsEnMhjfXc
MM3l2VYKMcU2bSkUl70t2olHGYjYSwQ967Y8Zx50ABMN0Ibak2f4MwOuGjxraXj2wCyO4YM/d/mZ
//6fUlrCtIcK2GypR8FUKWVDPkrAlh/Brfd3r2yxBF6+wbaULZeQLSfSux7pg2qE9sSyriMGZSal
J1grByK0b6ZiSBp38tVQJ5op05b7KPW6JHZi44xZ6/tu1ULEvkHH9QIDAQABo4ICuTCCArUwNAYI
KwYBBQUHAQEEKDAmMCQGCCsGAQUFBzABhhhodHRwOi8vb2NzcC52ZXJpc2lnbi5jb20wEgYDVR0T
AQH/BAgwBgEB/wIBADBwBgNVHSAEaTBnMGUGC2CGSAGG+EUBBxcBMFYwKAYIKwYBBQUHAgEWHGh0
dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9jcHMwKgYIKwYBBQUHAgIwHhocaHR0cHM6Ly93d3cudmVy
aXNpZ24uY29tL3JwYTA0BgNVHR8ELTArMCmgJ6AlhiNodHRwOi8vY3JsLnZlcmlzaWduLmNvbS9w
Y2ExLWczLmNybDAOBgNVHQ8BAf8EBAMCAQYwbgYIKwYBBQUHAQwEYjBgoV6gXDBaMFgwVhYJaW1h
Z2UvZ2lmMCEwHzAHBgUrDgMCGgQUS2u5KJYGDLvQUjibKaxLB4shBRgwJhYkaHR0cDovL2xvZ28u
dmVyaXNpZ24uY29tL3ZzbG9nbzEuZ2lmMC4GA1UdEQQnMCWkIzAhMR8wHQYDVQQDExZQcml2YXRl
TGFiZWw0LTIwNDgtMTE4MB0GA1UdDgQWBBR5R2EIQf04BKJL57XM9UP2SSsR+DCB8QYDVR0jBIHp
MIHmoYHQpIHNMIHKMQswCQYDVQQGEwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNV
BAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsxOjA4BgNVBAsTMShjKSAxOTk5IFZlcmlTaWduLCBJ
bmMuIC0gRm9yIGF1dGhvcml6ZWQgdXNlIG9ubHkxRTBDBgNVBAMTPFZlcmlTaWduIENsYXNzIDEg
UHVibGljIFByaW1hcnkgQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkgLSBHM4IRAItbdVaEVIULAM+v
OEjOsaQwDQYJKoZIhvcNAQEFBQADggEBADlNz0GZgbWpBbVSOOk5hIls5DSoWufYbAlMJBq6WaSH
O3Mh8ZOBz79oY1pn/jWFK6HDXaNKwjoZ3TDWzE3v8dKBl8pUWkO/N4t6jhmND0OojPKvYLMVirOV
nDzgnrMnmKQ1chfl/Cpdh9OKDcLRRSr4wPSsKpM61a4ScAjr+zvid+zoK2Q1ds262uDRyxTWcVib
vtU+fbbZ6CTFJGZMXZEfdrMXPn8NxiGJL7M3uKH/XLJtSd5lUkL7DojS7Uodv0vj+Mxy+kgOZY5J
yNb4mZg7t5Q+MXEGh/psWVMu198r7V9jAKwV7QO4VRaMxmgD5yKocwuxvKDaUljdCg5/wYIxggSL
MIIEhwIBATCB8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYD
VQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJtcyBvZiB1c2UgYXQgaHR0
cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFs
aWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1YWwgU3Vic2NyaWJlciBD
QSAtIEczAhBXH0kUxtIzZJ6m/S1fRrhZMAkGBSsOAwIaBQCgggJtMBgGCSqGSIb3DQEJAzELBgkq
hkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTEyMTEwNjE1MzM0MFowIwYJKoZIhvcNAQkEMRYEFHkY
0e/avLrumNOG4sHpd7PiprCqMIIBAwYJKwYBBAGCNxAEMYH1MIHyMIHdMQswCQYDVQQGEwJVUzEX
MBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsx
OzA5BgNVBAsTMlRlcm1zIG9mIHVzZSBhdCBodHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBhIChj
KTA5MR4wHAYDVQQLExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxNzA1BgNVBAMTLlZlcmlTaWduIENs
YXNzIDEgSW5kaXZpZHVhbCBTdWJzY3JpYmVyIENBIC0gRzMCEFcfSRTG0jNknqb9LV9GuFkwggEF
BgsqhkiG9w0BCRACCzGB9aCB8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJ
bmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJtcyBvZiB1
c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMVUGVyc29u
YSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1YWwgU3Vi
c2NyaWJlciBDQSAtIEczAhBXH0kUxtIzZJ6m/S1fRrhZMA0GCSqGSIb3DQEBAQUABIIBABz8QM1d
HrcoOa3BZgEojVjymXwbxwvnzW9SnGiqh57ne7V4mF/LmkikBVq42vdiBUZg2v6kcu9INsTCaOl/
C5GCR4GElwXGpEN6WKwqLOJ1sW/i+WpTQzhYQYhgZrGMhU/26FWdc2oV81LKYLCjpoRM12EX3BXx
/UfanfmWjrG6xlRU8EUDZZcYHXbZT1IR4sjI9SILdPXDzWAF0JFfKT5IchoqSZSY++UbKBzS/V6Y
9Old9lpKDUS2gfemKVP28vNbK+6D4gGHojO9FbDHhQk7TQc0lNKPkJyY0b1zCmvWX/SdrZwgs+Fs
IoNFa2S5EQ4AiqH+Y0/sJAVJv9WxVZAAAAAAAAA=

--Apple-Mail=_785A78A3-27E5-4E91-8CCB-65E99DAD71CE--

From fred@cisco.com  Tue Nov  6 07:34:21 2012
Return-Path: <fred@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EFED121F8951 for <ietf@ietfa.amsl.com>; Tue,  6 Nov 2012 07:34:21 -0800 (PST)
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=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, 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 rZQQIHeCq5YY for <ietf@ietfa.amsl.com>; Tue,  6 Nov 2012 07:34:21 -0800 (PST)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id 3FE5021F879A for <ietf@ietf.org>; Tue,  6 Nov 2012 07:34:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2201; q=dns/txt; s=iport; t=1352216061; x=1353425661; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=KgcUGE6RzbT9h7EqhYD8X8quQYob8FUtW1otMJhxTEw=; b=L5Pq1iEAewPRs35qOFWSndujyvpt5ypYg1ZQ6O80csB643lRdHDm3ehJ CokVvbS/Ubvw7gPT+i96+m8l2iBpTZvQGrAH+Xdt8aZFiaxdYV0coYPN2 COFb5JKfEiWVUnhJK/l8Ckka9lNXd+CHJR/dHn6VEVxcGya0Kv04qR/RE A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EAKEtmVCtJXHA/2dsb2JhbABEwy+BCIIeAQEBAwESASdECwIBCCIUEDIlAgQbARmHYgYLm3KPZJBSjAOFdGEDlxeNPYFrgm+CGQ
X-IronPort-AV: E=Sophos;i="4.80,722,1344211200"; d="scan'208";a="139382814"
Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by rcdn-iport-4.cisco.com with ESMTP; 06 Nov 2012 15:34:20 +0000
Received: from xhc-aln-x03.cisco.com (xhc-aln-x03.cisco.com [173.36.12.77]) by rcdn-core2-5.cisco.com (8.14.5/8.14.5) with ESMTP id qA6FYKmD009754 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <ietf@ietf.org>; Tue, 6 Nov 2012 15:34:20 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.68]) by xhc-aln-x03.cisco.com ([173.36.12.77]) with mapi id 14.02.0318.001; Tue, 6 Nov 2012 09:34:20 -0600
From: "Fred Baker (fred)" <fred@cisco.com>
To: IETF <ietf@ietf.org>
Subject: Re: IESG Considering a Revision to NOTE WELL
Thread-Topic: IESG Considering a Revision to NOTE WELL
Thread-Index: AQHNvC+VWiYDihsXvkeZTv41jvoOVpfdVJWA
Date: Tue, 6 Nov 2012 15:34:20 +0000
Message-ID: <8C48B86A895913448548E6D15DA7553B197F04@xmb-rcd-x09.cisco.com>
References: <55D046F8-5DD2-42E8-9B8C-36C612C4B3F8@ietf.org>
In-Reply-To: <55D046F8-5DD2-42E8-9B8C-36C612C4B3F8@ietf.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.82.211.206]
x-tm-as-product-ver: SMEX-10.2.0.1135-7.000.1014-19344.002
x-tm-as-result: No--32.319100-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: text/plain; charset="us-ascii"
Content-ID: <BA8FE992D4DFFF4DBF175CC3B1CC226A@cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Nov 2012 15:34:22 -0000

This note is rather lighter in weight and tone than its predecessor, and se=
ems like a good direction.

One suggestion: it would be good for the reference to BCP 79 be accompanied=
, at least in the web page in question, with a link to the BCP (http://www.=
ietf.org/rfc/rfc3979.txt). I could imagine someone unfamiliar with the IETF=
 thinking that this was a reference to the Book of Common Prayer or some su=
ch thing.

There is a point of disagreement between IRTF and IETF IPR Policy, or at le=
ast there appeared to be yesterday in ICCRG. http://tools.ietf.org/html/rfc=
3979#section-6.1.3 states that a person who knows that someone else has IPR=
 on something is not required, but is encouraged, to make it known. The "no=
te well" used in ICCRG yesterday said that someone that knew of IPR belongi=
ng to someone else was required to disclose it. I'm not sure what should be=
 done about that, but the difference seems unhelpful.

On Nov 6, 2012, at 10:00 AM, IETF Chair wrote:

> The IESG is considering a revision to the NOTE WELL text.  Please review =
and comment.
>=20
> Russ
>=20
>=20
>=20
> =3D=3D=3D Proposed Revised NOTE WELL Text =3D=3D=3D
>=20
> Note Well
>=20
> This summary is only meant to point you in the right direction, and
> doesn't have all the nuances. The IETF's IPR Policy is set forth in
> BCP 79; please read it carefully.
>=20
> The brief summary:
>  - By participating with the IETF, you agree to follow IETF processes.
>  - If you are aware that a contribution of yours (something you write,
>    say, or discuss in any IETF context) is covered by patents or patent
>    applications, you need to disclose that fact.
>  - You understand that meetings might be recorded, broadcast, and
>   publicly archived.
>=20
> For further information: Talk to a chair, ask an Area Director, or
> review  BCP 9 (on the Internet Standards Process), BCP 25 (on the
> Working Group processes), BCP 78 (on the IETF Trust), and BCP 79 (on
> Intellectual Property Rights in the IETF).

----------------------------------------------------
The ignorance of how to use new knowledge stockpiles exponentially.=20
   - Marshall McLuhan


From brian.e.carpenter@gmail.com  Tue Nov  6 07:35:17 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8EF3921F87EA for <ietf@ietfa.amsl.com>; Tue,  6 Nov 2012 07:35:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.578
X-Spam-Level: 
X-Spam-Status: No, score=-103.578 tagged_above=-999 required=5 tests=[AWL=0.021, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, 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 GvMf0usWdoOs for <ietf@ietfa.amsl.com>; Tue,  6 Nov 2012 07:35:17 -0800 (PST)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id 12D8E21F879A for <ietf@ietf.org>; Tue,  6 Nov 2012 07:35:17 -0800 (PST)
Received: by mail-pb0-f44.google.com with SMTP id ro8so499045pbb.31 for <ietf@ietf.org>; Tue, 06 Nov 2012 07:35:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=+YmkiR2d13Vsh+llQ374+4f6lF7ndDqsnJw2Yrwihto=; b=q2x4jQiiS3fjjh//ybbor+ZWEWZ327Niu7m9Hx1XX1QruAQh0jP4DyKvn2oI+ZmNhi Z6rKbE5SdkAq6U6tf6KYEB16GyE/X8BiTv+I6ctg/u1AprPqHPWa4Bm0CcSvtcoxd7j8 JniOtM4lgoR6JPuq2ZXClibEBg+hLa38Uv3mDX7beR3dDChewgwIutOs7CCwE/zF/Y78 cu6hEY/FtwseTM5BNSGoHEtjIbYNyeUHtDWtqkDeR14gAWfDdRgzYGsZEUikJQCqA2OY G9GAps0S7frFYkraJ4nYn0ea5gGE2GdKdkwQ0GKvT/tc3QZsQ4fY7HEYSGm/U/ob/VqP 2BVg==
Received: by 10.66.73.230 with SMTP id o6mr3611160pav.45.1352216116856; Tue, 06 Nov 2012 07:35:16 -0800 (PST)
Received: from [130.129.19.51] (dhcp-1333.meeting.ietf.org. [130.129.19.51]) by mx.google.com with ESMTPS id o5sm12620132paz.32.2012.11.06.07.35.15 (version=SSLv3 cipher=OTHER); Tue, 06 Nov 2012 07:35:16 -0800 (PST)
Message-ID: <50992E38.3070305@gmail.com>
Date: Tue, 06 Nov 2012 15:35:20 +0000
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: John Levine <johnl@taugh.com>
Subject: Re: IESG Considering a Revision to NOTE WELL
References: <20121106152538.4562.qmail@joyce.lan>
In-Reply-To: <20121106152538.4562.qmail@joyce.lan>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Nov 2012 15:35:17 -0000

On 06/11/2012 15:25, John Levine wrote:
> Looks much better, people might even read it.
> 
>>  - If you are aware that a contribution of yours (something you write,
>>    say, or discuss in any IETF context) is covered by patents or patent
>>    applications, you need to disclose that fact.
> 
> Perhaps "disclose that fact promptly."
> 
> Pete's been reminding us that postponing IPR disclosures until last
> call or IESG review is not good.

Yes, and the above paragraph would make a very useful preamble to
the existing NOTE WELL, which doesn't make that point explicitly.

    Brian

From lars@netapp.com  Tue Nov  6 07:39:48 2012
Return-Path: <lars@netapp.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9394A21F89D4 for <ietf@ietfa.amsl.com>; Tue,  6 Nov 2012 07:39:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.323
X-Spam-Level: 
X-Spam-Status: No, score=-6.323 tagged_above=-999 required=5 tests=[AWL=-3.724, 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 7ooguEkLYICw for <ietf@ietfa.amsl.com>; Tue,  6 Nov 2012 07:39:48 -0800 (PST)
Received: from mx11.netapp.com (mx11.netapp.com [216.240.18.76]) by ietfa.amsl.com (Postfix) with ESMTP id 19FA321F870D for <ietf@ietf.org>; Tue,  6 Nov 2012 07:39:48 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.80,722,1344236400";  d="p7s'?scan'208";a="324103134"
Received: from smtp2.corp.netapp.com ([10.57.159.114]) by mx11-out.netapp.com with ESMTP; 06 Nov 2012 07:39:47 -0800
Received: from vmwexceht01-prd.hq.netapp.com (exchsmtp.hq.netapp.com [10.106.76.239]) by smtp2.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id qA6FdlMD001169; Tue, 6 Nov 2012 07:39:47 -0800 (PST)
Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.216]) by vmwexceht01-prd.hq.netapp.com ([10.106.76.239]) with mapi id 14.02.0318.001; Tue, 6 Nov 2012 07:39:47 -0800
From: "Eggert, Lars" <lars@netapp.com>
To: "Fred Baker (fred)" <fred@cisco.com>
Subject: Re: IESG Considering a Revision to NOTE WELL
Thread-Topic: IESG Considering a Revision to NOTE WELL
Thread-Index: AQHNvC+NwCxX9AtBsECZ3UxC2YYnj5fddh0AgAABhIA=
Date: Tue, 6 Nov 2012 15:38:55 +0000
Message-ID: <D4D47BCFFE5A004F95D707546AC0D7E9185DBA8A@SACEXCMBX01-PRD.hq.netapp.com>
References: <55D046F8-5DD2-42E8-9B8C-36C612C4B3F8@ietf.org> <8C48B86A895913448548E6D15DA7553B197F04@xmb-rcd-x09.cisco.com>
In-Reply-To: <8C48B86A895913448548E6D15DA7553B197F04@xmb-rcd-x09.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.104.60.116]
Content-Type: multipart/signed; boundary="Apple-Mail=_E5063B51-9319-4106-BA45-2AFC33CCCEDB"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Nov 2012 15:39:48 -0000

--Apple-Mail=_E5063B51-9319-4106-BA45-2AFC33CCCEDB
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi,

On Nov 6, 2012, at 10:34, Fred Baker (fred) <fred@cisco.com> wrote:
> There is a point of disagreement between IRTF and IETF IPR Policy, or =
at least there appeared to be yesterday in ICCRG. =
http://tools.ietf.org/html/rfc3979#section-6.1.3 states that a person =
who knows that someone else has IPR on something is not required, but is =
encouraged, to make it known. The "note well" used in ICCRG yesterday =
said that someone that knew of IPR belonging to someone else was =
required to disclose it. I'm not sure what should be done about that, =
but the difference seems unhelpful.

the IRTF statement is at https://www.irtf.org/ipr. For the case you =
mention, it says:

"Finally, the IRTF requests that you file an IPR disclosure with the =
IETF if you recognize IPR owned by others in any IRTF contribution."

"Requests" does not mean "required."

Lars=

--Apple-Mail=_E5063B51-9319-4106-BA45-2AFC33CCCEDB
Content-Disposition: attachment; filename="smime.p7s"
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIMQDCCBUow
ggQyoAMCAQICEFcfSRTG0jNknqb9LV9GuFkwDQYJKoZIhvcNAQEFBQAwgd0xCzAJBgNVBAYTAlVT
MRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29y
azE7MDkGA1UECxMyVGVybXMgb2YgdXNlIGF0IGh0dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9ycGEg
KGMpMDkxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZhbGlkYXRlZDE3MDUGA1UEAxMuVmVyaVNpZ24g
Q2xhc3MgMSBJbmRpdmlkdWFsIFN1YnNjcmliZXIgQ0EgLSBHMzAeFw0xMTEyMTAwMDAwMDBaFw0x
MjEyMDkyMzU5NTlaMIIBDTEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlT
aWduIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9S
UEEgSW5jb3JwLiBieSBSZWYuLExJQUIuTFREKGMpOTgxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZh
bGlkYXRlZDEzMDEGA1UECxMqRGlnaXRhbCBJRCBDbGFzcyAxIC0gTmV0c2NhcGUgRnVsbCBTZXJ2
aWNlMRQwEgYDVQQDFAtMYXJzIEVnZ2VydDEeMBwGCSqGSIb3DQEJARYPbGFyc0BuZXRhcHAuY29t
MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAokrhJTcXt6J/VEpZOicLoguBlYTjXP9v
Ze4HuuhXnURUS8YouAfgaqA0zYbt5yd6fh4PBMdAaEWr5yJyHuFykXlrCumjUWSpLuqTS2A+pt4q
cZaAQk9iLDN/UVd3SpkUuvWbxXlqzG7/BSqa3VNObBzCmyh+V7aXxri+30CT//DSsNRC4VFy6sn6
dMgSaFenXLwe/FBwY0qTMfICT1PrrX6Sw1S8OfH9rykLlZXbmfkFExxQngp1DJH9xMHeODHGbCv/
ty5gdxMOrLe+vENxFEcy1YQWBZd1kNL4UObugF8A/jE/s+Oa3H1VFH8ghqZTdqGDysVxmtKHuNFx
6jIBSQIDAQABo4HSMIHPMAkGA1UdEwQCMAAwRAYDVR0gBD0wOzA5BgtghkgBhvhFAQcXATAqMCgG
CCsGAQUFBwIBFhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBhMAsGA1UdDwQEAwIFoDAdBgNV
HSUEFjAUBggrBgEFBQcDBAYIKwYBBQUHAwIwUAYDVR0fBEkwRzBFoEOgQYY/aHR0cDovL2luZGMx
ZGlnaXRhbGlkLWczLWNybC52ZXJpc2lnbi5jb20vSW5kQzFEaWdpdGFsSUQtRzMuY3JsMA0GCSqG
SIb3DQEBBQUAA4IBAQBA7q6tR92qpd7xo7VBsrOfGCWzoxIVfTc7t0RhB/Oz/+c3lnhYnNScIuKN
JmyZvznmVxqB9BJ72+NkvmdB/hnILSBTRawL2tyLo9PkBtN0nRt4gS6wjpWnD8G83hlJLE7r25jk
7HkRev61dTIXsANFpJKF02C4XSoDfEzNV6MpuEvHvcgHCqMrlwWwfKc7+NoDnE8PBuRzwSXvlD5L
mswCY2iiOsd7ImNO4OzTCxETvKTDu92+FTIbRJJpYjVNv1UF7e3w9Kq65BkZJErUH19beUeQl0Wh
2BJQE6/15rQyCnP0iJ/Nmx2/kI6M0PWunEsI6FMs0MbosreaWGHlQmomMIIG7jCCBdagAwIBAgIQ
cRVmBUrkkSFN6bxE+azT3DANBgkqhkiG9w0BAQUFADCByjELMAkGA1UEBhMCVVMxFzAVBgNVBAoT
DlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTowOAYDVQQL
EzEoYykgMTk5OSBWZXJpU2lnbiwgSW5jLiAtIEZvciBhdXRob3JpemVkIHVzZSBvbmx5MUUwQwYD
VQQDEzxWZXJpU2lnbiBDbGFzcyAxIFB1YmxpYyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9y
aXR5IC0gRzMwHhcNMDkwNTAxMDAwMDAwWhcNMTkwNDMwMjM1OTU5WjCB3TELMAkGA1UEBhMCVVMx
FzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3Jr
MTswOQYDVQQLEzJUZXJtcyBvZiB1c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAo
YykwOTEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBD
bGFzcyAxIEluZGl2aWR1YWwgU3Vic2NyaWJlciBDQSAtIEczMIIBIjANBgkqhkiG9w0BAQEFAAOC
AQ8AMIIBCgKCAQEA7cRH3yooHXwGa7vXITLJbBOP6bGNQU4099oL42r6ZYggCxET6ZvgSU6Lb9UB
0F8NR5GKWkx0Pj/GkQm7TDSejW6hglFi92l2WJYHr54UGAdPWr2f0jGyVBlzRmoZQhHsEnMhjfXc
MM3l2VYKMcU2bSkUl70t2olHGYjYSwQ967Y8Zx50ABMN0Ibak2f4MwOuGjxraXj2wCyO4YM/d/mZ
//6fUlrCtIcK2GypR8FUKWVDPkrAlh/Brfd3r2yxBF6+wbaULZeQLSfSux7pg2qE9sSyriMGZSal
J1grByK0b6ZiSBp38tVQJ5op05b7KPW6JHZi44xZ6/tu1ULEvkHH9QIDAQABo4ICuTCCArUwNAYI
KwYBBQUHAQEEKDAmMCQGCCsGAQUFBzABhhhodHRwOi8vb2NzcC52ZXJpc2lnbi5jb20wEgYDVR0T
AQH/BAgwBgEB/wIBADBwBgNVHSAEaTBnMGUGC2CGSAGG+EUBBxcBMFYwKAYIKwYBBQUHAgEWHGh0
dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9jcHMwKgYIKwYBBQUHAgIwHhocaHR0cHM6Ly93d3cudmVy
aXNpZ24uY29tL3JwYTA0BgNVHR8ELTArMCmgJ6AlhiNodHRwOi8vY3JsLnZlcmlzaWduLmNvbS9w
Y2ExLWczLmNybDAOBgNVHQ8BAf8EBAMCAQYwbgYIKwYBBQUHAQwEYjBgoV6gXDBaMFgwVhYJaW1h
Z2UvZ2lmMCEwHzAHBgUrDgMCGgQUS2u5KJYGDLvQUjibKaxLB4shBRgwJhYkaHR0cDovL2xvZ28u
dmVyaXNpZ24uY29tL3ZzbG9nbzEuZ2lmMC4GA1UdEQQnMCWkIzAhMR8wHQYDVQQDExZQcml2YXRl
TGFiZWw0LTIwNDgtMTE4MB0GA1UdDgQWBBR5R2EIQf04BKJL57XM9UP2SSsR+DCB8QYDVR0jBIHp
MIHmoYHQpIHNMIHKMQswCQYDVQQGEwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNV
BAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsxOjA4BgNVBAsTMShjKSAxOTk5IFZlcmlTaWduLCBJ
bmMuIC0gRm9yIGF1dGhvcml6ZWQgdXNlIG9ubHkxRTBDBgNVBAMTPFZlcmlTaWduIENsYXNzIDEg
UHVibGljIFByaW1hcnkgQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkgLSBHM4IRAItbdVaEVIULAM+v
OEjOsaQwDQYJKoZIhvcNAQEFBQADggEBADlNz0GZgbWpBbVSOOk5hIls5DSoWufYbAlMJBq6WaSH
O3Mh8ZOBz79oY1pn/jWFK6HDXaNKwjoZ3TDWzE3v8dKBl8pUWkO/N4t6jhmND0OojPKvYLMVirOV
nDzgnrMnmKQ1chfl/Cpdh9OKDcLRRSr4wPSsKpM61a4ScAjr+zvid+zoK2Q1ds262uDRyxTWcVib
vtU+fbbZ6CTFJGZMXZEfdrMXPn8NxiGJL7M3uKH/XLJtSd5lUkL7DojS7Uodv0vj+Mxy+kgOZY5J
yNb4mZg7t5Q+MXEGh/psWVMu198r7V9jAKwV7QO4VRaMxmgD5yKocwuxvKDaUljdCg5/wYIxggSL
MIIEhwIBATCB8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYD
VQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJtcyBvZiB1c2UgYXQgaHR0
cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFs
aWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1YWwgU3Vic2NyaWJlciBD
QSAtIEczAhBXH0kUxtIzZJ6m/S1fRrhZMAkGBSsOAwIaBQCgggJtMBgGCSqGSIb3DQEJAzELBgkq
hkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTEyMTEwNjE1Mzk0NlowIwYJKoZIhvcNAQkEMRYEFBSY
01YWInqo9bpGb8RgQtYBlF+1MIIBAwYJKwYBBAGCNxAEMYH1MIHyMIHdMQswCQYDVQQGEwJVUzEX
MBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsx
OzA5BgNVBAsTMlRlcm1zIG9mIHVzZSBhdCBodHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBhIChj
KTA5MR4wHAYDVQQLExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxNzA1BgNVBAMTLlZlcmlTaWduIENs
YXNzIDEgSW5kaXZpZHVhbCBTdWJzY3JpYmVyIENBIC0gRzMCEFcfSRTG0jNknqb9LV9GuFkwggEF
BgsqhkiG9w0BCRACCzGB9aCB8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJ
bmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJtcyBvZiB1
c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMVUGVyc29u
YSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1YWwgU3Vi
c2NyaWJlciBDQSAtIEczAhBXH0kUxtIzZJ6m/S1fRrhZMA0GCSqGSIb3DQEBAQUABIIBAGXykn6H
Dby5YzLNNxFa2inOHelfL+qInSo/s9w1XPCP481k6ktTpxkyjYQ569vrZeMyvBGjw8p4mERG/SG2
iuBHOj0nsnFX22G9QK3ijhiXK1bTYelP8mpPtHJKtnLCufPFSa55BH1vfgR/3RYLEfCD2J+y8tFn
TE9O90ZCFcNRq+IxR9oOx7rDV2qfy1bNI3DCruBtPYNgOTyGcpdDTerdnXvx8Z08TJfmHZ5yvPue
AEgIXXpBpp3gQ67TjqAryDb1VqCLl/9FTu6Xm5SJJ0pClxpsvG4g9PBPm89sKVtmceOHu25+1H39
RbPu9SLogzOr9ae5EJ74E4AfMBtNnOcAAAAAAAA=

--Apple-Mail=_E5063B51-9319-4106-BA45-2AFC33CCCEDB--

From paul@cypherpunks.ca  Tue Nov  6 07:43:42 2012
Return-Path: <paul@cypherpunks.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E1B1F21F8453 for <ietf@ietfa.amsl.com>; Tue,  6 Nov 2012 07:43:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.67
X-Spam-Level: 
X-Spam-Status: No, score=-1.67 tagged_above=-999 required=5 tests=[AWL=0.930,  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 rLQszUfJWyF8 for <ietf@ietfa.amsl.com>; Tue,  6 Nov 2012 07:43:42 -0800 (PST)
Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) by ietfa.amsl.com (Postfix) with ESMTP id 530C921F8427 for <ietf@ietf.org>; Tue,  6 Nov 2012 07:43:42 -0800 (PST)
Received: by bofh.nohats.ca (Postfix, from userid 500) id 1D95582B5B; Tue,  6 Nov 2012 10:42:56 -0500 (EST)
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id 0B61D80318; Tue,  6 Nov 2012 10:42:56 -0500 (EST)
Date: Tue, 6 Nov 2012 10:42:55 -0500 (EST)
From: Paul Wouters <paul@cypherpunks.ca>
X-X-Sender: paul@bofh.nohats.ca
To: "Fred Baker (fred)" <fred@cisco.com>
Subject: Re: IESG Considering a Revision to NOTE WELL
In-Reply-To: <8C48B86A895913448548E6D15DA7553B197F04@xmb-rcd-x09.cisco.com>
Message-ID: <alpine.LFD.2.02.1211061040400.16141@bofh.nohats.ca>
References: <55D046F8-5DD2-42E8-9B8C-36C612C4B3F8@ietf.org> <8C48B86A895913448548E6D15DA7553B197F04@xmb-rcd-x09.cisco.com>
User-Agent: Alpine 2.02 (LFD 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Nov 2012 15:43:43 -0000

On Tue, 6 Nov 2012, Fred Baker (fred) wrote:

> This note is rather lighter in weight and tone than its predecessor, and seems like a good direction.

Can you explain your reasoning why this seems like "a good direction".

For example, how would the new Note Well improve our situation in
the Versign DNSSEC case?

Link to patent: http://domainnamewire.com/2012/10/05/verisign-files-patent-application-for-way-of-transfering-hosting-on-dnssec-domains/

Comparison of Patent vs IETF work: http://ubuntuone.com/4Bz1BqOsGMkTUQgViEL0rz

Paul

From fred@cisco.com  Tue Nov  6 07:54:40 2012
Return-Path: <fred@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C99721F89D2 for <ietf@ietfa.amsl.com>; Tue,  6 Nov 2012 07:54:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.588
X-Spam-Level: 
X-Spam-Status: No, score=-110.588 tagged_above=-999 required=5 tests=[AWL=0.011, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, 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 tbJ5eK5eXHAp for <ietf@ietfa.amsl.com>; Tue,  6 Nov 2012 07:54:38 -0800 (PST)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by ietfa.amsl.com (Postfix) with ESMTP id 3A92521F8508 for <ietf@ietf.org>; Tue,  6 Nov 2012 07:54:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1875; q=dns/txt; s=iport; t=1352217278; x=1353426878; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=QjVSBbupfjfJq6rcl/HZhuLwsfr02H0Sr1TbHZ6C30k=; b=hvWweeRzhEb8WdArelbPC3XwnO8f7qV33ZQoKTvXJ2wErwHfOyTG8DIb WWhL7kaqBs6JwAHj5AUUmPnlPLz6CM9BHO3MOgGjxKyY/cR6R6B7B4SpE NqNRgF/6EliQOFp1UK61Kb84SlHnAj9gKHUe3Au0VMCS53iXBIvCepSPR s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EAJ4xmVCtJV2a/2dsb2JhbABEwy+BCIIeAQEBAwESASc/BQsCAQgYChQQMiUCBAoEDRqHYgYLm3CPZJBTjAOFdGEDlxeNPYFrgm+CGQ
X-IronPort-AV: E=Sophos;i="4.80,722,1344211200"; d="scan'208";a="139344940"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-6.cisco.com with ESMTP; 06 Nov 2012 15:54:38 +0000
Received: from xhc-rcd-x04.cisco.com (xhc-rcd-x04.cisco.com [173.37.183.78]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id qA6Fsb3A022918 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 6 Nov 2012 15:54:37 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.68]) by xhc-rcd-x04.cisco.com ([173.37.183.78]) with mapi id 14.02.0318.001; Tue, 6 Nov 2012 09:54:31 -0600
From: "Fred Baker (fred)" <fred@cisco.com>
To: Paul Wouters <paul@cypherpunks.ca>
Subject: Re: IESG Considering a Revision to NOTE WELL
Thread-Topic: IESG Considering a Revision to NOTE WELL
Thread-Index: AQHNvC+VWiYDihsXvkeZTv41jvoOVpfdVJWAgAACZ4CAAAM6AA==
Date: Tue, 6 Nov 2012 15:54:30 +0000
Message-ID: <8C48B86A895913448548E6D15DA7553B197FCD@xmb-rcd-x09.cisco.com>
References: <55D046F8-5DD2-42E8-9B8C-36C612C4B3F8@ietf.org> <8C48B86A895913448548E6D15DA7553B197F04@xmb-rcd-x09.cisco.com> <alpine.LFD.2.02.1211061040400.16141@bofh.nohats.ca>
In-Reply-To: <alpine.LFD.2.02.1211061040400.16141@bofh.nohats.ca>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.82.211.206]
x-tm-as-product-ver: SMEX-10.2.0.1135-7.000.1014-19344.002
x-tm-as-result: No--27.863800-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: text/plain; charset="us-ascii"
Content-ID: <0BA8470F8AB4664E85D7A207E5477885@cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Nov 2012 15:54:40 -0000

On Nov 6, 2012, at 10:42 AM, Paul Wouters wrote:

> On Tue, 6 Nov 2012, Fred Baker (fred) wrote:
>=20
>> This note is rather lighter in weight and tone than its predecessor, and=
 seems like a good direction.
>=20
> Can you explain your reasoning why this seems like "a good direction".

Not being a lawyer, I can't comment on the legal details of IPR cases. What=
 I am looking at is the understandability of a statement. A lawyer that I w=
as speaking with recently told me that the IETF IPR policy is ambiguous; on=
e must file IPR statements for standards, but not for informational documen=
ts. We wound up wandering through the details of legal statements, in which=
 I felt he was working pretty hard to make words stand on their heads.

To my small and non-legal mind, the simplest statement is the clearest, and=
 what the average IETFer needs is clarity. The policy is, as far as I know,=
 that if I have or personally and reasonably know that my company has IPR o=
n a document or statement of any category, I need to say so and encourage m=
y company to say so; if someone else does, I am encouraged to make the fact=
 known. Making that statement in any more complex way gives the appearance =
of complexity of thought, and this particular lawyer was finding complexity=
/ambiguity where no complexity/ambiguity exists.=20

KISS.

> For example, how would the new Note Well improve our situation in
> the Versign DNSSEC case?
>=20
> Link to patent: http://domainnamewire.com/2012/10/05/verisign-files-paten=
t-application-for-way-of-transfering-hosting-on-dnssec-domains/
>=20
> Comparison of Patent vs IETF work: http://ubuntuone.com/4Bz1BqOsGMkTUQgVi=
EL0rz
>=20
> Paul

----------------------------------------------------
The ignorance of how to use new knowledge stockpiles exponentially.=20
   - Marshall McLuhan


From dhc@dcrocker.net  Tue Nov  6 08:26:03 2012
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE75621F8932; Tue,  6 Nov 2012 08:26:03 -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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sV8AFAjuNdmH; Tue,  6 Nov 2012 08:26:02 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 54EC321F892C; Tue,  6 Nov 2012 08:26:02 -0800 (PST)
Received: from [130.129.17.128] (dhcp-1180.meeting.ietf.org [130.129.17.128]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id qA6GPvWa012836 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 6 Nov 2012 08:25:59 -0800
Message-ID: <50993A11.1090707@dcrocker.net>
Date: Tue, 06 Nov 2012 11:25:53 -0500
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: IETF <ietf@ietf.org>
Subject: Re: IESG Considering a Revision to NOTE WELL
References: <55D046F8-5DD2-42E8-9B8C-36C612C4B3F8@ietf.org>
In-Reply-To: <55D046F8-5DD2-42E8-9B8C-36C612C4B3F8@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Tue, 06 Nov 2012 08:26:02 -0800 (PST)
Cc: IETF Chair <chair@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Nov 2012 16:26:03 -0000

On 11/6/2012 10:00 AM, IETF Chair wrote:
> The IESG is considering a revision to the NOTE WELL text.  Please review and comment.
>
> Russ
>
>
>
> === Proposed Revised NOTE WELL Text ===
>
> Note Well
>
> This summary is only meant to point you in the right direction, and
> doesn't have all the nuances. The IETF's IPR Policy is set forth in

IPR -> Intellectual Property Rights


> BCP 79; please read it carefully.
>
> The brief summary:
>    - By participating with the IETF, you agree to follow IETF processes.

{ BCP 79 does not describe IETF processes, so you need an additional 
citation. /d }


>    - If you are aware that a contribution of yours (something you write,
>      say, or discuss in any IETF context) is covered by patents or patent
>      applications, you need to disclose that fact.


{ the directive here is remarkably soft.  much too soft, IMO.  a 
sentence structure that's a bit too complicated.  so...}

A contribution by you consists of anything you write, say or discuss in 
any IETF context.  If you are aware that any contribution you make is 
covered by a patent or a patent application, you are REQUIRED to 
disclose that fact IMMEDIATELY.


>    - You understand that meetings might be recorded, broadcast, and
>     publicly archived.
>
> For further information: Talk to a chair, ask an Area Director, or
> review  BCP 9 (on the Internet Standards Process), BCP 25 (on the
> Working Group processes), BCP 78 (on the IETF Trust), and BCP 79 (on
> Intellectual Property Rights in the IETF).
>


d/
-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From yiu_lee@cable.comcast.com  Mon Nov  5 08:12:50 2012
Return-Path: <yiu_lee@cable.comcast.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 01FAA21F87E0 for <ietf@ietfa.amsl.com>; Mon,  5 Nov 2012 08:12:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.454
X-Spam-Level: 
X-Spam-Status: No, score=-104.454 tagged_above=-999 required=5 tests=[AWL=0.620, BAYES_00=-2.599, HOST_EQ_MODEMCABLE=1.368, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, SUBJECT_FUZZY_TION=0.156, 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 uhCaPGU0OikI for <ietf@ietfa.amsl.com>; Mon,  5 Nov 2012 08:12:49 -0800 (PST)
Received: from cable.comcast.com (copdcavout01.cable.comcast.com [76.96.32.253]) by ietfa.amsl.com (Postfix) with ESMTP id 4D97521F87C6 for <ietf@ietf.org>; Mon,  5 Nov 2012 08:12:49 -0800 (PST)
Received: from ([24.40.56.115]) by copdcavout01.cable.comcast.com with ESMTP  id C7WM3M1.40480176; Mon, 05 Nov 2012 08:48:20 -0700
Received: from PACDCEXMB05.cable.comcast.com ([169.254.7.131]) by PACDCEXHUB02.cable.comcast.com ([fe80::492e:3fa1:c2ad:e04e%13]) with mapi id 14.02.0318.001; Mon, 5 Nov 2012 11:12:45 -0500
From: "Lee, Yiu" <Yiu_Lee@Cable.Comcast.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Recall petition for Mr. Marshall Eubanks
Thread-Topic: Recall petition for Mr. Marshall Eubanks
Thread-Index: AQHNu3BMLzJFQQwdhkOI6yCCNbI5bA==
Date: Mon, 5 Nov 2012 16:12:43 +0000
Message-ID: <E3FAB1F4F41F3A45B287E8D9C53522FD453A8317@PACDCEXMB05.cable.comcast.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.4.120824
x-originating-ip: [24.40.55.71]
Content-Type: multipart/alternative; boundary="_000_E3FAB1F4F41F3A45B287E8D9C53522FD453A8317PACDCEXMB05cabl_"
MIME-Version: 1.0
X-Mailman-Approved-At: Tue, 06 Nov 2012 09:25:42 -0800
Cc: "ogud@ogud.com" <ogud@ogud.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Nov 2012 16:12:50 -0000

--_000_E3FAB1F4F41F3A45B287E8D9C53522FD453A8317PACDCEXMB05cabl_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I am noncom-eligible. After hearing the situation of Mr. Eubanks, I support=
 the recall.

Regards,
Yiu



--_000_E3FAB1F4F41F3A45B287E8D9C53522FD453A8317PACDCEXMB05cabl_
Content-Type: text/html; charset="us-ascii"
Content-ID: <261C8E688F499D4780307C52BD472266@cable.comcast.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami=
ly: Calibri, sans-serif; ">
<div>I am noncom-eligible. After hearing the situation of Mr. Eubanks, I su=
pport the recall.</div>
<div><br>
</div>
<div>Regards,</div>
<div>Yiu</div>
<div><br>
</div>
<div><br>
</div>
</body>
</html>

--_000_E3FAB1F4F41F3A45B287E8D9C53522FD453A8317PACDCEXMB05cabl_--

From vincent.roca@inria.fr  Tue Nov  6 07:39:03 2012
Return-Path: <vincent.roca@inria.fr>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8323821F870D; Tue,  6 Nov 2012 07:39:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.249
X-Spam-Level: 
X-Spam-Status: No, score=-110.249 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8, 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 aFXf1pjor8Qa; Tue,  6 Nov 2012 07:39:02 -0800 (PST)
Received: from mail1-relais-roc.national.inria.fr (mail1-relais-roc.national.inria.fr [192.134.164.82]) by ietfa.amsl.com (Postfix) with ESMTP id 0FFBF21F86A6; Tue,  6 Nov 2012 07:39:01 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.80,722,1344204000"; d="scan'208";a="180385135"
Received: from ral126r.vpn.inria.fr ([128.93.178.126]) by mail1-relais-roc.national.inria.fr with ESMTP/TLS/AES128-SHA; 06 Nov 2012 16:38:59 +0100
Subject: Re: [Fecframe] Last Call: <draft-ietf-fecframe-simple-rs-04.txt> (Simple	Reed-Solomon Forward Error Correction (FEC) Scheme for	FECFRAME) to Proposed Standard
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=windows-1252
From: Vincent Roca <vincent.roca@inria.fr>
In-Reply-To: <20121008141129.10923.33854.idtracker@ietfa.amsl.com>
Date: Tue, 6 Nov 2012 16:38:58 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <0C779DC7-564A-4EEA-BEAA-AD9168863FF0@inria.fr>
References: <20121008141129.10923.33854.idtracker@ietfa.amsl.com>
To: Michael Luby <luby@qti.qualcomm.com>
X-Mailer: Apple Mail (2.1085)
X-Mailman-Approved-At: Tue, 06 Nov 2012 09:25:42 -0800
Cc: Vincent Roca <vincent.roca@inria.fr>, ietf@ietf.org, fecframe@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Nov 2012 15:39:03 -0000

Mike,

Thanks for your comments. It seems your email didn't show up in the =
fecframe
list (it's not in the mailing list archive either) which explains why we =
didn't answer
so far.


Concerning (1), you're right and here is the way we address it both in =
the
introduction and section 5.3.

** Introduction:

OLD:
   More specifically, the [RFC5510] document introduced such Reed-
   Solomon codes and several associated FEC schemes that are compatible
   with the [RFC5052] framework.  The present document inherits from
   [RFC5510] the specification of the core Reed-Solomon codes based on
   Vandermonde matrices, and specifies a simple FEC scheme that is
   compatible with the FECFRAME framework [RFC6363].  Therefore this
   document specifies only the information specific to the FECFRAME
   context and refers to [RFC5510] for the core specifications of the
   codes.  To that purpose, the present document introduces:

   o  the Fully-Specified FEC Scheme with FEC Encoding ID XXX that
      specifies a simple way of using of Reed-Solomon codes over
      GF(2^^m), with 2 <=3D m <=3D 16, with a simple FEC encoding for
      arbitrary packet flows;


NEW:
   More specifically, the [RFC5510] document introduced such Reed-
   Solomon codes and several associated FEC schemes that are compatible
   with the [RFC5052] framework.  The present document inherits from
   [RFC5510], Section 8 "Reed-Solomon Codes Specification for the
   Erasure Channel", the specifications of the core Reed-Solomon codes
   based on Vandermonde matrices, and specifies a simple FEC scheme that
   is compatible with the FECFRAME framework [RFC6363]:

   o  the Fully-Specified FEC Scheme with FEC Encoding ID XXX that
      specifies a simple way of using of Reed-Solomon codes over
      GF(2^^m), with 2 <=3D m <=3D 16, with a simple FEC encoding for
      arbitrary packet flows;

   Therefore sections 4, 5, 6 and 7 of [RFC5510], that define [RFC5052]
   specific Formats and Procedures, are not considered and are replaced
   by FECFRAME specific Formats and Procedures.

** Section 5.3:

OLD:

   The present document inherits from [RFC5510] the specification of the
   core Reed-Solomon codes based on Vandermonde matrices for a packet
   transmission channel.

NEW:

   The present document inherits from [RFC5510], Section 8 "Reed-Solomon
   Codes Specification for the Erasure Channel", the specifications of
   the core Reed-Solomon codes based on Vandermonde matrices.


As soon as possible, I'll update the LDPC document as well, unlike
what I said previously, in the same manner. Saying that all the Formats
and Procedures of RFC5170 are replaced by FECFRAME variants
can clarify a little bit the document.


Concerning (2), same answer than for the LDPC document (it's not
an exhaustive list).


Cheers,

    Vincent, on behalf of the authors


---
	=95 From: "Luby, Michael" <luby at qti.qualcomm.com>
	=95 To: "ietf at ietf.org" <ietf at ietf.org>
	=95 Cc: "Luby, Michael" <luby at qti.qualcomm.com>, "fecframe at =
ietf.org" <fecframe at ietf.org>
	=95 Date: Thu, 11 Oct 2012 17:30:31 +0000
	=95 In-reply-to: <20121008141129.10923.33854.idtracker at =
ietfa.amsl.com>

Some quick comments.

(1) This proposal relies upon parts of RFC 5510 for the definition of =
the
underlying Reed-Solomon code.  However, it isn't completely explicit in
this proposal about what exact parts/sections of RFC 5510 are to be used
in this proposal and how.  It would seem that explicit references to the
particular sections of RFC 5510 that are being used, and exactly how =
these
parts of RFC 5510 are being inherited and used, would be useful =
(probably
necessary).

(2) This proposal references RFC 5170 and RFC 5053, and makes some
comparisons.  However, there is also RFC 6330 that is relevant and is =
not
mentioned or referenced in this proposal.  It would seem appropriate to =
do
so.

Thanks, Mike


On Oct 8, 2012, 16:11, The IESG wrote:
>=20
> The IESG has received a request from the FEC Framework WG (fecframe) =
to
> consider the following document:
> - 'Simple Reed-Solomon Forward Error Correction (FEC) Scheme for
> FECFRAME'
>  <draft-ietf-fecframe-simple-rs-04.txt> as Proposed Standard
>=20
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2012-10-22. Exceptionally, comments may =
be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>=20
> Abstract
>=20
>=20
>   This document describes a fully-specified simple FEC scheme for =
Reed-
>   Solomon codes over GF(2^^m), with 2 <=3D m <=3D 16, that can be used =
to
>   protect arbitrary media streams along the lines defined by the
>   FECFRAME framework.  Reed-Solomon codes belong to the class of
>   Maximum Distance Separable (MDS) codes which means they offer =
optimal
>   protection against packet erasures.  They are also systematic codes,
>   which means that the source symbols are part of the encoding =
symbols.
>   The price to pay is a limit on the maximum source block size, on the
>   maximum number of encoding symbols, and a computational complexity
>   higher than that of LDPC codes for instance.
>=20
>=20
>=20
>=20
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-fecframe-simple-rs/
>=20
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-fecframe-simple-rs/ballot/
>=20
>=20
> No IPR declarations have been submitted directly on this I-D.
>=20
>=20
> _______________________________________________
> Fecframe mailing list
> Fecframe@ietf.org
> https://www.ietf.org/mailman/listinfo/fecframe


From luby@qti.qualcomm.com  Tue Nov  6 08:10:28 2012
Return-Path: <luby@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5624721F89F1; Tue,  6 Nov 2012 08:10:28 -0800 (PST)
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=-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 XNf+kaJHKAaH; Tue,  6 Nov 2012 08:10:27 -0800 (PST)
Received: from sabertooth01.qualcomm.com (sabertooth01.qualcomm.com [65.197.215.72]) by ietfa.amsl.com (Postfix) with ESMTP id 3CF6221F8A32; Tue,  6 Nov 2012 08:10:18 -0800 (PST)
X-IronPort-AV: E=McAfee;i="5400,1158,6887"; a="4501293"
Received: from ironmsg03-r.qualcomm.com ([172.30.46.17]) by sabertooth01.qualcomm.com with ESMTP; 06 Nov 2012 07:55:44 -0800
X-IronPort-AV: E=Sophos;i="4.80,722,1344236400"; d="scan'208";a="364925826"
Received: from nasanexhc09.na.qualcomm.com ([172.30.39.8]) by Ironmsg03-R.qualcomm.com with ESMTP/TLS/RC4-SHA; 06 Nov 2012 08:10:09 -0800
Received: from NASANEXD02C.na.qualcomm.com ([169.254.6.25]) by nasanexhc09.na.qualcomm.com ([172.30.39.8]) with mapi id 14.02.0318.001; Tue, 6 Nov 2012 08:10:08 -0800
From: "Luby, Michael" <luby@qti.qualcomm.com>
To: Vincent Roca <vincent.roca@inria.fr>, "Luby, Michael" <luby@qti.qualcomm.com>
Subject: Re: [Fecframe] Last Call: <draft-ietf-fecframe-simple-rs-04.txt> (Simple Reed-Solomon Forward Error Correction (FEC) Scheme for FECFRAME) to Proposed Standard
Thread-Topic: [Fecframe] Last Call: <draft-ietf-fecframe-simple-rs-04.txt> (Simple Reed-Solomon Forward Error Correction (FEC) Scheme for FECFRAME) to Proposed Standard
Thread-Index: AQHNvDkwzEWyMByYtk6ne5/OlWimww==
Date: Tue, 6 Nov 2012 16:10:07 +0000
Message-ID: <BAE0CC0CAB9C9C4AAE57C71E55C451D820BE07A1@NASANEXD02C.na.qualcomm.com>
In-Reply-To: <0C779DC7-564A-4EEA-BEAA-AD9168863FF0@inria.fr>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.4.120824
x-originating-ip: [199.106.115.132]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <2A90BDEB9954634A89BA38ECC3D02776@qualcomm.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Tue, 06 Nov 2012 09:25:42 -0800
Cc: "ietf@ietf.org" <ietf@ietf.org>, "fecframe@ietf.org" <fecframe@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Nov 2012 16:10:28 -0000

Vincent,=20
Thanks, I think this will help the document.
Mike

On 11/6/12 4:38 PM, "Vincent Roca" <vincent.roca@inria.fr> wrote:

>Mike,
>
>Thanks for your comments. It seems your email didn't show up in the
>fecframe
>list (it's not in the mailing list archive either) which explains why we
>didn't answer
>so far.
>
>
>Concerning (1), you're right and here is the way we address it both in the
>introduction and section 5.3.
>
>** Introduction:
>
>OLD:
>   More specifically, the [RFC5510] document introduced such Reed-
>   Solomon codes and several associated FEC schemes that are compatible
>   with the [RFC5052] framework.  The present document inherits from
>   [RFC5510] the specification of the core Reed-Solomon codes based on
>   Vandermonde matrices, and specifies a simple FEC scheme that is
>   compatible with the FECFRAME framework [RFC6363].  Therefore this
>   document specifies only the information specific to the FECFRAME
>   context and refers to [RFC5510] for the core specifications of the
>   codes.  To that purpose, the present document introduces:
>
>   o  the Fully-Specified FEC Scheme with FEC Encoding ID XXX that
>      specifies a simple way of using of Reed-Solomon codes over
>      GF(2^^m), with 2 <=3D m <=3D 16, with a simple FEC encoding for
>      arbitrary packet flows;
>
>
>NEW:
>   More specifically, the [RFC5510] document introduced such Reed-
>   Solomon codes and several associated FEC schemes that are compatible
>   with the [RFC5052] framework.  The present document inherits from
>   [RFC5510], Section 8 "Reed-Solomon Codes Specification for the
>   Erasure Channel", the specifications of the core Reed-Solomon codes
>   based on Vandermonde matrices, and specifies a simple FEC scheme that
>   is compatible with the FECFRAME framework [RFC6363]:
>
>   o  the Fully-Specified FEC Scheme with FEC Encoding ID XXX that
>      specifies a simple way of using of Reed-Solomon codes over
>      GF(2^^m), with 2 <=3D m <=3D 16, with a simple FEC encoding for
>      arbitrary packet flows;
>
>   Therefore sections 4, 5, 6 and 7 of [RFC5510], that define [RFC5052]
>   specific Formats and Procedures, are not considered and are replaced
>   by FECFRAME specific Formats and Procedures.
>
>** Section 5.3:
>
>OLD:
>
>   The present document inherits from [RFC5510] the specification of the
>   core Reed-Solomon codes based on Vandermonde matrices for a packet
>   transmission channel.
>
>NEW:
>
>   The present document inherits from [RFC5510], Section 8 "Reed-Solomon
>   Codes Specification for the Erasure Channel", the specifications of
>   the core Reed-Solomon codes based on Vandermonde matrices.
>
>
>As soon as possible, I'll update the LDPC document as well, unlike
>what I said previously, in the same manner. Saying that all the Formats
>and Procedures of RFC5170 are replaced by FECFRAME variants
>can clarify a little bit the document.
>
>
>Concerning (2), same answer than for the LDPC document (it's not
>an exhaustive list).
>
>
>Cheers,
>
>    Vincent, on behalf of the authors
>
>
>---
>	=80 From: "Luby, Michael" <luby at qti.qualcomm.com>
>	=80 To: "ietf at ietf.org" <ietf at ietf.org>
>	=80 Cc: "Luby, Michael" <luby at qti.qualcomm.com>, "fecframe at ietf.org=
"
><fecframe at ietf.org>
>	=80 Date: Thu, 11 Oct 2012 17:30:31 +0000
>	=80 In-reply-to: <20121008141129.10923.33854.idtracker at ietfa.amsl.com>
>
>Some quick comments.
>
>(1) This proposal relies upon parts of RFC 5510 for the definition of the
>underlying Reed-Solomon code.  However, it isn't completely explicit in
>this proposal about what exact parts/sections of RFC 5510 are to be used
>in this proposal and how.  It would seem that explicit references to the
>particular sections of RFC 5510 that are being used, and exactly how these
>parts of RFC 5510 are being inherited and used, would be useful (probably
>necessary).
>
>(2) This proposal references RFC 5170 and RFC 5053, and makes some
>comparisons.  However, there is also RFC 6330 that is relevant and is not
>mentioned or referenced in this proposal.  It would seem appropriate to do
>so.
>
>Thanks, Mike
>
>
>On Oct 8, 2012, 16:11, The IESG wrote:
>>=20
>> The IESG has received a request from the FEC Framework WG (fecframe) to
>> consider the following document:
>> - 'Simple Reed-Solomon Forward Error Correction (FEC) Scheme for
>> FECFRAME'
>>  <draft-ietf-fecframe-simple-rs-04.txt> as Proposed Standard
>>=20
>> The IESG plans to make a decision in the next few weeks, and solicits
>> final comments on this action. Please send substantive comments to the
>> ietf@ietf.org mailing lists by 2012-10-22. Exceptionally, comments may
>>be
>> sent to iesg@ietf.org instead. In either case, please retain the
>> beginning of the Subject line to allow automated sorting.
>>=20
>> Abstract
>>=20
>>=20
>>   This document describes a fully-specified simple FEC scheme for Reed-
>>   Solomon codes over GF(2^^m), with 2 <=3D m <=3D 16, that can be used t=
o
>>   protect arbitrary media streams along the lines defined by the
>>   FECFRAME framework.  Reed-Solomon codes belong to the class of
>>   Maximum Distance Separable (MDS) codes which means they offer optimal
>>   protection against packet erasures.  They are also systematic codes,
>>   which means that the source symbols are part of the encoding symbols.
>>   The price to pay is a limit on the maximum source block size, on the
>>   maximum number of encoding symbols, and a computational complexity
>>   higher than that of LDPC codes for instance.
>>=20
>>=20
>>=20
>>=20
>> The file can be obtained via
>> http://datatracker.ietf.org/doc/draft-ietf-fecframe-simple-rs/
>>=20
>> IESG discussion can be tracked via
>> http://datatracker.ietf.org/doc/draft-ietf-fecframe-simple-rs/ballot/
>>=20
>>=20
>> No IPR declarations have been submitted directly on this I-D.
>>=20
>>=20
>> _______________________________________________
>> Fecframe mailing list
>> Fecframe@ietf.org
>> https://www.ietf.org/mailman/listinfo/fecframe
>


From ted.ietf@gmail.com  Tue Nov  6 09:38:56 2012
Return-Path: <ted.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D72D21F88DB; Tue,  6 Nov 2012 09:38:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.391
X-Spam-Level: 
X-Spam-Status: No, score=-3.391 tagged_above=-999 required=5 tests=[AWL=0.208,  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 6lPFdfcpyinp; Tue,  6 Nov 2012 09:38:55 -0800 (PST)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id E4E6B21F8850; Tue,  6 Nov 2012 09:38:54 -0800 (PST)
Received: by mail-vc0-f172.google.com with SMTP id fl11so701920vcb.31 for <multiple recipients>; Tue, 06 Nov 2012 09:38:54 -0800 (PST)
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 :cc:content-type; bh=W13sI154u+Y+lM+mXC1nM+aR1dDtp8uZPHs7240eFMA=; b=AlcLUCs8X8tPeEjG3qKe2LpHXBTnCZb/TBJYVdhERfHbg6Bd3pptiULKKqe9z0y6uV kKvWSbuZhNmF2W/0ZYHiFZR8+QBf56OOFRl90lg8PJd+0gfN4vD5h1S1ac7PuinKf3XP aa7NZ0ZGr/e+zM0Qt4zrA37tOatCztoYNms2SCgBaiev9IgBUvPpRkiUiIHhOmB3AOEn oUmdb2hJOyL28z4s544tTnX2gR6o9JWrcRm5C0tS16nNmGHDpM+LoUoj3xbctWd3fzfG qQ3YHeH6DNSjahxe7vfpF+2cXCAOOdMNJKpXsvDdzgWTjrk4H6yTD7q3chyFJyIJXtVZ APJg==
MIME-Version: 1.0
Received: by 10.52.90.212 with SMTP id by20mr1408635vdb.118.1352223533969; Tue, 06 Nov 2012 09:38:53 -0800 (PST)
Received: by 10.58.164.35 with HTTP; Tue, 6 Nov 2012 09:38:53 -0800 (PST)
In-Reply-To: <50993A11.1090707@dcrocker.net>
References: <55D046F8-5DD2-42E8-9B8C-36C612C4B3F8@ietf.org> <50993A11.1090707@dcrocker.net>
Date: Tue, 6 Nov 2012 12:38:53 -0500
Message-ID: <CA+9kkMBop-z36eiuSz0aG4=ZLB61Bs7tE=RWm1WNStNreACZ-A@mail.gmail.com>
Subject: Re: IESG Considering a Revision to NOTE WELL
From: Ted Hardie <ted.ietf@gmail.com>
To: dcrocker@bbiw.net
Content-Type: text/plain; charset=ISO-8859-1
Cc: IETF Chair <chair@ietf.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Nov 2012 17:38:56 -0000

On Tue, Nov 6, 2012 at 11:25 AM, Dave Crocker <dhc@dcrocker.net> wrote:
>
>
> { the directive here is remarkably soft.  much too soft, IMO.  a sentence
> structure that's a bit too complicated.  so...}
>
> A contribution by you consists of anything you write, say or discuss in any
> IETF context.  If you are aware that any contribution you make is covered by
> a patent or a patent application, you are REQUIRED to disclose that fact
> IMMEDIATELY.
>

I note that this is not the same language as is in BCP 79, which says:
" as  soon as reasonably possible " instead of IMMEDIATELY.  I don't
believe the NOTE WELL should disagree with the BCP on that point.  If
this changes, it should change in the BCP first/simultaneously.

regards,

Ted Hardie

From housley@vigilsec.com  Tue Nov  6 09:43:41 2012
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 648C921F87DE for <ietf@ietfa.amsl.com>; Tue,  6 Nov 2012 09:43:41 -0800 (PST)
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=0.050, 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 x8lzPf6tLFIA for <ietf@ietfa.amsl.com>; Tue,  6 Nov 2012 09:43:40 -0800 (PST)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 927C321F87AB for <ietf@ietf.org>; Tue,  6 Nov 2012 09:43:40 -0800 (PST)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 5D6B79A4003; Tue,  6 Nov 2012 12:43:52 -0500 (EST)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id PtWnNDSDuP1h; Tue,  6 Nov 2012 12:43:29 -0500 (EST)
Received: from dhcp-5421.meeting.ietf.org (dhcp-5421.meeting.ietf.org [130.129.84.33]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 464469A400B; Tue,  6 Nov 2012 12:43:51 -0500 (EST)
Subject: Re: IESG Considering a Revision to NOTE WELL
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <50992BEF.9000803@gmail.com>
Date: Tue, 6 Nov 2012 12:43:37 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <C66E7DEF-EEE8-4678-91C1-1FD46854312C@vigilsec.com>
References: <55D046F8-5DD2-42E8-9B8C-36C612C4B3F8@ietf.org> <50992BEF.9000803@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1085)
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Nov 2012 17:43:41 -0000

Brian:

Jorge has reviewed this text.  He says that the current text and this =
proposed text are both summaries.  Both say that it is important to read =
the BCP to get all of the details.

Russ


On Nov 6, 2012, at 10:25 AM, Brian E Carpenter wrote:

> I don't much like the change in approach. I think it will be too easy
> to brush off; the current approach has enough substance that people
> who brush it off put themselves in a very weak position.
>=20
> The old text was written with legal advice. What does counsel say
> about the new proposal?
>=20
> Regards
>   Brian Carpenter
>   Cell phone during IETF85: +1 847 219 0880
>=20
> On 06/11/2012 15:00, IETF Chair wrote:
>> The IESG is considering a revision to the NOTE WELL text.  Please =
review and comment.
>>=20
>> Russ
>>=20
>>=20
>>=20
>> =3D=3D=3D Proposed Revised NOTE WELL Text =3D=3D=3D
>>=20
>> Note Well
>>=20
>> This summary is only meant to point you in the right direction, and
>> doesn't have all the nuances. The IETF's IPR Policy is set forth in
>> BCP 79; please read it carefully.
>>=20
>> The brief summary:
>>  - By participating with the IETF, you agree to follow IETF =
processes.
>>  - If you are aware that a contribution of yours (something you =
write,
>>    say, or discuss in any IETF context) is covered by patents or =
patent
>>    applications, you need to disclose that fact.
>>  - You understand that meetings might be recorded, broadcast, and
>>   publicly archived.
>>=20
>> For further information: Talk to a chair, ask an Area Director, or
>> review  BCP 9 (on the Internet Standards Process), BCP 25 (on the
>> Working Group processes), BCP 78 (on the IETF Trust), and BCP 79 (on
>> Intellectual Property Rights in the IETF).


From stewe@stewe.org  Tue Nov  6 10:28:00 2012
Return-Path: <stewe@stewe.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D2A921F8A91 for <ietf@ietfa.amsl.com>; Tue,  6 Nov 2012 10:28:00 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VirJKJ1HJ11c for <ietf@ietfa.amsl.com>; Tue,  6 Nov 2012 10:28:00 -0800 (PST)
Received: from co1outboundpool.messaging.microsoft.com (co1ehsobe003.messaging.microsoft.com [216.32.180.186]) by ietfa.amsl.com (Postfix) with ESMTP id F02D721F8A6E for <ietf@ietf.org>; Tue,  6 Nov 2012 10:27:59 -0800 (PST)
Received: from mail180-co1-R.bigfish.com (10.243.78.235) by CO1EHSOBE012.bigfish.com (10.243.66.75) with Microsoft SMTP Server id 14.1.225.23; Tue, 6 Nov 2012 18:27:59 +0000
Received: from mail180-co1 (localhost [127.0.0.1])	by mail180-co1-R.bigfish.com (Postfix) with ESMTP id 416BA840114	for <ietf@ietf.org>; Tue,  6 Nov 2012 18:27:59 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.240.133; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0710HT005.namprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -19
X-BigFish: PS-19(zz98dI1432Izz1de0h1202h1d1ah1d2ah1082kzz1033IL8275dhz2fh2a8h668h839h944hd25hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh1155h)
Received-SPF: pass (mail180-co1: domain of stewe.org designates 157.56.240.133 as permitted sender) client-ip=157.56.240.133; envelope-from=stewe@stewe.org; helo=BL2PRD0710HT005.namprd07.prod.outlook.com ; .outlook.com ; 
Received: from mail180-co1 (localhost.localdomain [127.0.0.1]) by mail180-co1 (MessageSwitch) id 1352226476846981_18359; Tue,  6 Nov 2012 18:27:56 +0000 (UTC)
Received: from CO1EHSMHS026.bigfish.com (unknown [10.243.78.246])	by mail180-co1.bigfish.com (Postfix) with ESMTP id C1A8EA200B5	for <ietf@ietf.org>; Tue,  6 Nov 2012 18:27:56 +0000 (UTC)
Received: from BL2PRD0710HT005.namprd07.prod.outlook.com (157.56.240.133) by CO1EHSMHS026.bigfish.com (10.243.66.36) with Microsoft SMTP Server (TLS) id 14.1.225.23; Tue, 6 Nov 2012 18:27:56 +0000
Received: from BL2PRD0710MB349.namprd07.prod.outlook.com ([169.254.2.192]) by BL2PRD0710HT005.namprd07.prod.outlook.com ([10.255.102.40]) with mapi id 14.16.0233.002; Tue, 6 Nov 2012 18:27:55 +0000
From: Stephan Wenger <stewe@stewe.org>
To: IETF <ietf@ietf.org>
Subject: Re: IESG Considering a Revision to NOTE WELL
Thread-Topic: IESG Considering a Revision to NOTE WELL
Thread-Index: AQHNvC+P1gsovbnYEkqDQrp0L72z0JfczKkA
Date: Tue, 6 Nov 2012 18:27:54 +0000
Message-ID: <FDBFA77C7400C74F87BC297393B53E35259B2A4D@BL2PRD0710MB349.namprd07.prod.outlook.com>
In-Reply-To: <55D046F8-5DD2-42E8-9B8C-36C612C4B3F8@ietf.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.255.102.5]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <13F1622D1618194FB2E8517B7DB58B9D@namprd07.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: stewe.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Nov 2012 18:28:00 -0000

Hi,
Russ, can you explain why the IESG considers it necessary to tinker with
the Note Well?
As for the substance, I don't like the text for two reasons that can be
found inline.
Stephan

On 11.6.2012 10:00 , "IETF Chair" <chair@ietf.org> wrote:

>The IESG is considering a revision to the NOTE WELL text.  Please review
>and comment.
>
>Russ
>
>
>
>=3D=3D=3D Proposed Revised NOTE WELL Text =3D=3D=3D
>
>Note Well
>
>This summary is only meant to point you in the right direction, and
>doesn't have all the nuances. The IETF's IPR Policy is set forth in
>BCP 79; please read it carefully.
>
>The brief summary:
>  - By participating with the IETF, you agree to follow IETF processes.
>  - If you are aware that a contribution of yours (something you write,
>    say, or discuss in any IETF context) is covered by patents or patent
>    applications, you need to disclose that fact.

1) I'm not in favor of this formulation because it can be read to impose a
stronger disclosure obligation on a participant than BCP 79.
Specifically, as Lars has already pointed out and according to BCP 79, I'm
not "needed" to disclose a patent I'm reasonably and personally aware of
that reads on a document of mine, if that patent is assigned to someone
else but myself and my sponsor/employer, ... For good reasons, BCP 79 does
not require third party disclosures.  I hope that the (few) added words
can be accommodated.
2) On the other hand, the issue of timeliness is not covered at all (as
others have already pointed out.)

I'm especially worried of point 1, which can be seen as a policy change
through the back door.  If, based on this hypothetical Note Well, we would
end up with an IETF disclosure culture in which third party disclosures
would become the norm rather than an exception, we could well end up with
a brain drain especially from folks not quite as senior in their
respective company hierarchy to have the leeway to ignore company guidance
about patents.=20


>  - You understand that meetings might be recorded, broadcast, and
>   publicly archived.
>
>For further information: Talk to a chair, ask an Area Director, or
>review  BCP 9 (on the Internet Standards Process), BCP 25 (on the
>Working Group processes), BCP 78 (on the IETF Trust), and BCP 79 (on
>Intellectual Property Rights in the IETF).



From dhc@dcrocker.net  Tue Nov  6 10:44:27 2012
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 274ED21F8894; Tue,  6 Nov 2012 10:44:27 -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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RFJYSEw7n44e; Tue,  6 Nov 2012 10:44:26 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 58D1B21F87F2; Tue,  6 Nov 2012 10:44:26 -0800 (PST)
Received: from [130.129.17.128] (dhcp-1180.meeting.ietf.org [130.129.17.128]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id qA6IiM4u015151 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 6 Nov 2012 10:44:24 -0800
Message-ID: <50995A82.6050807@dcrocker.net>
Date: Tue, 06 Nov 2012 13:44:18 -0500
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: Ted Hardie <ted.ietf@gmail.com>
Subject: Re: IESG Considering a Revision to NOTE WELL
References: <55D046F8-5DD2-42E8-9B8C-36C612C4B3F8@ietf.org> <CA+9kkMD6qRuW1xOEv-wj5h8aXkdcMZppGbK4dg=D=OGdwcQUug@mail.gmail.com>
In-Reply-To: <CA+9kkMD6qRuW1xOEv-wj5h8aXkdcMZppGbK4dg=D=OGdwcQUug@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Tue, 06 Nov 2012 10:44:24 -0800 (PST)
Cc: IETF <ietf@ietf.org>, IETF Announce <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Nov 2012 18:44:27 -0000

On 11/6/2012 10:14 AM, Ted Hardie wrote:
> That puts the most important information higher up the text and, to
> my eyes at least, makes it more prominent.

+1



On 11/6/2012 12:38 PM, Ted Hardie wrote:> On Tue, Nov 6, 2012 at 11:25
AM, Dave Crocker <dhc@dcrocker.net> wrote:
>>
>>
>> { the directive here is remarkably soft.  much too soft, IMO.  a
>> sentence structure that's a bit too complicated.  so...}
>>
>> A contribution by you consists of anything you write, say or
>> discuss in any IETF context.  If you are aware that any
>> contribution you make is  covered by
>> a patent or a patent application, you are REQUIRED to disclose
>> that fact IMMEDIATELY.
>>
>
> I note that this is not the same language as is in BCP 79, which
> says: " as  soon as reasonably possible " instead of IMMEDIATELY.  I
> don't believe the NOTE WELL should disagree with the BCP on that
> point.

Thanks for checking the BCP language.  Hadn't occurred to me that it had 
anything close to an 'urgency' tone.  Yes, we should use exactly the 
same text here, IMO.

My main concern is that the summary communicate both an imperative to 
report and a directive that it be done real soon.

d/

d/


-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From brian.e.carpenter@gmail.com  Tue Nov  6 11:01:18 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F38D21F8A2B for <ietf@ietfa.amsl.com>; Tue,  6 Nov 2012 11:01:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.581
X-Spam-Level: 
X-Spam-Status: No, score=-103.581 tagged_above=-999 required=5 tests=[AWL=0.018, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, 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 OKQb0W9MkxJf for <ietf@ietfa.amsl.com>; Tue,  6 Nov 2012 11:01:17 -0800 (PST)
Received: from mail-da0-f44.google.com (mail-da0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id 57DA821F8AAF for <ietf@ietf.org>; Tue,  6 Nov 2012 11:01:17 -0800 (PST)
Received: by mail-da0-f44.google.com with SMTP id h15so331080dan.31 for <ietf@ietf.org>; Tue, 06 Nov 2012 11:01:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=2Wffzy5FVdqWvkp0sR537YxlEHm+0+Wt4MPOesKJruY=; b=Xi9FhPmiVpX1Ur7yCBNIvbyveV5hubn25Das80nFUQzLo6X+540vkncNzMo8ZfttsE ef/C2o7CJNypYNkCgkg470Q78PB0ltKeenf6PtpbWvAM+KjhS73q237DAxXc7VEvwamo GW3eghhM+B9OoZn0P+zC/Y7vXbmS3aTNXau7yyNMgimG5wqaZkr8HBVeatM2ef60p0Un Nwcyw+kgfQ+BySHS1yB4R+0FrvaMcuN2Yp4PczuFxMRtkjOveWies4FOpXfZhxmZai0V sB+uN7FrJ99bZ6nOcEt10FDYm/0vIEEfpMtvnwlysa9pJb8jONDvdTGne3NPWuJTezzB v13g==
Received: by 10.68.191.200 with SMTP id ha8mr6089105pbc.51.1352228477139; Tue, 06 Nov 2012 11:01:17 -0800 (PST)
Received: from [130.129.19.51] (dhcp-1333.meeting.ietf.org. [130.129.19.51]) by mx.google.com with ESMTPS id c7sm12866928pay.10.2012.11.06.11.01.15 (version=SSLv3 cipher=OTHER); Tue, 06 Nov 2012 11:01:16 -0800 (PST)
Message-ID: <50995E81.3020606@gmail.com>
Date: Tue, 06 Nov 2012 19:01:21 +0000
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Russ Housley <housley@vigilsec.com>
Subject: Re: IESG Considering a Revision to NOTE WELL
References: <55D046F8-5DD2-42E8-9B8C-36C612C4B3F8@ietf.org> <50992BEF.9000803@gmail.com> <C66E7DEF-EEE8-4678-91C1-1FD46854312C@vigilsec.com>
In-Reply-To: <C66E7DEF-EEE8-4678-91C1-1FD46854312C@vigilsec.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Nov 2012 19:01:18 -0000

On 06/11/2012 17:43, Russ Housley wrote:
> Brian:
> 
> Jorge has reviewed this text.  He says that the current text and this proposed text are both summaries.  Both say that it is important to read the BCP to get all of the details.

OK, good. On reflection my feeling is that we definitely need the introductory
paragraph stressing the disclosure requirement, but I remain bothered by taking
out all the details. I understand there is a problem of attention span,
but there are not really all that many words in the current version.

   Brian

> Russ
> 
> 
> On Nov 6, 2012, at 10:25 AM, Brian E Carpenter wrote:
> 
>> I don't much like the change in approach. I think it will be too easy
>> to brush off; the current approach has enough substance that people
>> who brush it off put themselves in a very weak position.
>>
>> The old text was written with legal advice. What does counsel say
>> about the new proposal?
>>
>> Regards
>>   Brian Carpenter
>>   Cell phone during IETF85: +1 847 219 0880
>>
>> On 06/11/2012 15:00, IETF Chair wrote:
>>> The IESG is considering a revision to the NOTE WELL text.  Please review and comment.
>>>
>>> Russ
>>>
>>>
>>>
>>> === Proposed Revised NOTE WELL Text ===
>>>
>>> Note Well
>>>
>>> This summary is only meant to point you in the right direction, and
>>> doesn't have all the nuances. The IETF's IPR Policy is set forth in
>>> BCP 79; please read it carefully.
>>>
>>> The brief summary:
>>>  - By participating with the IETF, you agree to follow IETF processes.
>>>  - If you are aware that a contribution of yours (something you write,
>>>    say, or discuss in any IETF context) is covered by patents or patent
>>>    applications, you need to disclose that fact.
>>>  - You understand that meetings might be recorded, broadcast, and
>>>   publicly archived.
>>>
>>> For further information: Talk to a chair, ask an Area Director, or
>>> review  BCP 9 (on the Internet Standards Process), BCP 25 (on the
>>> Working Group processes), BCP 78 (on the IETF Trust), and BCP 79 (on
>>> Intellectual Property Rights in the IETF).
> 
> 

From housley@vigilsec.com  Tue Nov  6 11:01:26 2012
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E6EED21F8AEC for <ietf@ietfa.amsl.com>; Tue,  6 Nov 2012 11:01:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.553
X-Spam-Level: 
X-Spam-Status: No, score=-102.553 tagged_above=-999 required=5 tests=[AWL=0.046, 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 cN646hMrSBJI for <ietf@ietfa.amsl.com>; Tue,  6 Nov 2012 11:01:26 -0800 (PST)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 05DAF21F8AB7 for <ietf@ietf.org>; Tue,  6 Nov 2012 11:01:26 -0800 (PST)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 01CAA9A4005; Tue,  6 Nov 2012 14:01:44 -0500 (EST)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id KIEfKQ-vGCB3; Tue,  6 Nov 2012 14:01:16 -0500 (EST)
Received: from dhcp-5421.meeting.ietf.org (dhcp-5421.meeting.ietf.org [130.129.84.33]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 5BF839A4003; Tue,  6 Nov 2012 14:01:42 -0500 (EST)
Subject: Re: IESG Considering a Revision to NOTE WELL
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <FDBFA77C7400C74F87BC297393B53E35259B2A4D@BL2PRD0710MB349.namprd07.prod.outlook.com>
Date: Tue, 6 Nov 2012 14:01:22 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <94CB8D65-EE75-4D54-B846-44F8CB472A48@vigilsec.com>
References: <FDBFA77C7400C74F87BC297393B53E35259B2A4D@BL2PRD0710MB349.namprd07.prod.outlook.com>
To: Stephan Wenger <stewe@stewe.org>
X-Mailer: Apple Mail (2.1085)
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Nov 2012 19:01:27 -0000

Stephan:

Based on the number of late disclosures that are occurring, it is clear =
to us that we need to use very plain language to explain the =
responsibilities to participants.

Russ


On Nov 6, 2012, at 1:27 PM, Stephan Wenger wrote:

> Hi,
> Russ, can you explain why the IESG considers it necessary to tinker =
with
> the Note Well?
> As for the substance, I don't like the text for two reasons that can =
be
> found inline.
> Stephan
>=20
> On 11.6.2012 10:00 , "IETF Chair" <chair@ietf.org> wrote:
>=20
>> The IESG is considering a revision to the NOTE WELL text.  Please =
review
>> and comment.
>>=20
>> Russ
>>=20
>>=20
>>=20
>> =3D=3D=3D Proposed Revised NOTE WELL Text =3D=3D=3D
>>=20
>> Note Well
>>=20
>> This summary is only meant to point you in the right direction, and
>> doesn't have all the nuances. The IETF's IPR Policy is set forth in
>> BCP 79; please read it carefully.
>>=20
>> The brief summary:
>> - By participating with the IETF, you agree to follow IETF processes.
>> - If you are aware that a contribution of yours (something you write,
>>   say, or discuss in any IETF context) is covered by patents or =
patent
>>   applications, you need to disclose that fact.
>=20
> 1) I'm not in favor of this formulation because it can be read to =
impose a
> stronger disclosure obligation on a participant than BCP 79.
> Specifically, as Lars has already pointed out and according to BCP 79, =
I'm
> not "needed" to disclose a patent I'm reasonably and personally aware =
of
> that reads on a document of mine, if that patent is assigned to =
someone
> else but myself and my sponsor/employer, ... For good reasons, BCP 79 =
does
> not require third party disclosures.  I hope that the (few) added =
words
> can be accommodated.
> 2) On the other hand, the issue of timeliness is not covered at all =
(as
> others have already pointed out.)
>=20
> I'm especially worried of point 1, which can be seen as a policy =
change
> through the back door.  If, based on this hypothetical Note Well, we =
would
> end up with an IETF disclosure culture in which third party =
disclosures
> would become the norm rather than an exception, we could well end up =
with
> a brain drain especially from folks not quite as senior in their
> respective company hierarchy to have the leeway to ignore company =
guidance
> about patents.=20
>=20
>=20
>> - You understand that meetings might be recorded, broadcast, and
>>  publicly archived.
>>=20
>> For further information: Talk to a chair, ask an Area Director, or
>> review  BCP 9 (on the Internet Standards Process), BCP 25 (on the
>> Working Group processes), BCP 78 (on the IETF Trust), and BCP 79 (on
>> Intellectual Property Rights in the IETF).
>=20
>=20


From dhc@dcrocker.net  Tue Nov  6 11:31:08 2012
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 98E6521F8889 for <ietf@ietfa.amsl.com>; Tue,  6 Nov 2012 11:31:08 -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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ENrDuwReLMnT for <ietf@ietfa.amsl.com>; Tue,  6 Nov 2012 11:31:08 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id D66EB21F8772 for <ietf@ietf.org>; Tue,  6 Nov 2012 11:31:04 -0800 (PST)
Received: from [130.129.17.128] (dhcp-1180.meeting.ietf.org [130.129.17.128]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id qA6JV1l0016014 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 6 Nov 2012 11:31:03 -0800
Message-ID: <50996571.2010406@dcrocker.net>
Date: Tue, 06 Nov 2012 14:30:57 -0500
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: IESG Considering a Revision to NOTE WELL
References: <55D046F8-5DD2-42E8-9B8C-36C612C4B3F8@ietf.org> <50992BEF.9000803@gmail.com> <C66E7DEF-EEE8-4678-91C1-1FD46854312C@vigilsec.com> <50995E81.3020606@gmail.com>
In-Reply-To: <50995E81.3020606@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Tue, 06 Nov 2012 11:31:03 -0800 (PST)
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Nov 2012 19:31:08 -0000

On 11/6/2012 2:01 PM, Brian E Carpenter wrote:
>  but I remain bothered by taking
> out all the details. I understand there is a problem of attention span,
> but there are not really all that many words in the current version.


Simple human factors:

    You cannot expect anyone to process a mass of text from a slide and 
develop useful understanding, nevermind take required action.


Making a useful slide requires synthesizing it to show only the 
essential information.  That's what I understand the current excise to 
be and it is exactly the right thing to do.

The slide we show should have a very terse statement of the topic, the 
reader's obligations and where to go to find out more.

d/

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From dwm@xpasc.com  Tue Nov  6 11:42:34 2012
Return-Path: <dwm@xpasc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4DA5921F8A59 for <ietf@ietfa.amsl.com>; Tue,  6 Nov 2012 11:42:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.276
X-Spam-Level: 
X-Spam-Status: No, score=-2.276 tagged_above=-999 required=5 tests=[AWL=0.323,  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 D00xhgtCAcvs for <ietf@ietfa.amsl.com>; Tue,  6 Nov 2012 11:42:28 -0800 (PST)
Received: from c2w3p-2.abacamail.com (c2w3p-2.abacamail.com [209.133.53.32]) by ietfa.amsl.com (Postfix) with ESMTP id 8E3A721F8A2B for <ietf@ietf.org>; Tue,  6 Nov 2012 11:42:28 -0800 (PST)
Received: from xpasc.com (unknown [68.164.244.188]) by c2w3p-2.abacamail.com (Postfix) with ESMTP id F1BB03FDBF for <ietf@ietf.org>; Tue,  6 Nov 2012 19:42:27 +0000 (UTC)
Received: from egate.xpasc.com (egate.xpasc.com [10.1.2.49]) by xpasc.com (8.13.8/8.13.8) with ESMTP id qA6JgRYW012032 for <ietf@ietf.org>; Tue, 6 Nov 2012 11:42:27 -0800
Date: Tue, 6 Nov 2012 11:42:27 -0800 (PST)
From: David Morris <dwm@xpasc.com>
To: ietf@ietf.org
Subject: Re: IESG Considering a Revision to NOTE WELL
In-Reply-To: <50995A82.6050807@dcrocker.net>
Message-ID: <alpine.LRH.2.01.1211061133550.11872@egate.xpasc.com>
References: <55D046F8-5DD2-42E8-9B8C-36C612C4B3F8@ietf.org> <CA+9kkMD6qRuW1xOEv-wj5h8aXkdcMZppGbK4dg=D=OGdwcQUug@mail.gmail.com> <50995A82.6050807@dcrocker.net>
User-Agent: Alpine 2.01 (LRH 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Milter-Version: master.1+13-gbab1945
X-AV-Type: clean
X-AV-Accuracy: exact
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: ietf@ietf.org
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Nov 2012 19:42:34 -0000

On Tue, 6 Nov 2012, Dave Crocker wrote:

> On 11/6/2012 12:38 PM, Ted Hardie wrote:> On Tue, Nov 6, 2012 at 11:25
> AM, Dave Crocker <dhc@dcrocker.net> wrote:
> > > 
> > > 
> > > { the directive here is remarkably soft.  much too soft, IMO.  a
> > > sentence structure that's a bit too complicated.  so...}
> > > 
> > > A contribution by you consists of anything you write, say or
> > > discuss in any IETF context.  If you are aware that any
> > > contribution you make is  covered by
> > > a patent or a patent application, you are REQUIRED to disclose
> > > that fact IMMEDIATELY.
> > > 
> > 
> > I note that this is not the same language as is in BCP 79, which
> > says: " as  soon as reasonably possible " instead of IMMEDIATELY.  I
> > don't believe the NOTE WELL should disagree with the BCP on that
> > point.
> 
> Thanks for checking the BCP language.  Hadn't occurred to me that it had
> anything close to an 'urgency' tone.  Yes, we should use exactly the same text
> here, IMO.
> 
> My main concern is that the summary communicate both an imperative to report
> and a directive that it be done real soon.

I agree with real soon, but I think there may be times when the disclosure
needs to be approved by coporate legal folks, so I think something like:

   as soon as legally permitted

implies immediacy but ackowledges real world constraints.

From brian.e.carpenter@gmail.com  Tue Nov  6 11:43:43 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E57321F8A5D for <ietf@ietfa.amsl.com>; Tue,  6 Nov 2012 11:43:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.582
X-Spam-Level: 
X-Spam-Status: No, score=-103.582 tagged_above=-999 required=5 tests=[AWL=0.017, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, 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 580HTz7LMokN for <ietf@ietfa.amsl.com>; Tue,  6 Nov 2012 11:43:42 -0800 (PST)
Received: from mail-da0-f44.google.com (mail-da0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id 29F8821F8748 for <ietf@ietf.org>; Tue,  6 Nov 2012 11:43:42 -0800 (PST)
Received: by mail-da0-f44.google.com with SMTP id h15so346092dan.31 for <ietf@ietf.org>; Tue, 06 Nov 2012 11:43:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=BAAgyn0d0vPouF7UjGNeDkQU52t9lYxe6FC94+fhEas=; b=RzM9GajIPu1u6cQbdllF+YxAEIH6OdvEI9NvHpL2Tb2/ShY+62YZz/D1wrvQE+lS+s XITYYAMmddU57my0emiBT8cEEcQeKrUrnME2yg2j26yQKUMdCZBM2PK5iu95UFacstJ/ +57zNLmnUGth1MO2npWOQkyKJcLgf8tQGNuWMHj+m/gHdKJolzPSTazUGpFs4YoZzNsy co9VG2gLhYDtD0Ovr0WXczNM7YXaQro3PO8szRX6hHxKJC/yJlMyy3Ey0hynpCR/T89U 9kn6u+B/zwOpdVf2r4iIDg4Oo/sPhsEVI2aV1AStQ0rXdznWNcNc6tDyryxRGXPE7k1h QEQg==
Received: by 10.68.247.196 with SMTP id yg4mr6347390pbc.167.1352231018373; Tue, 06 Nov 2012 11:43:38 -0800 (PST)
Received: from [130.129.19.51] (dhcp-1333.meeting.ietf.org. [130.129.19.51]) by mx.google.com with ESMTPS id gq10sm7188951pbc.54.2012.11.06.11.43.37 (version=SSLv3 cipher=OTHER); Tue, 06 Nov 2012 11:43:37 -0800 (PST)
Message-ID: <5099686E.7070001@gmail.com>
Date: Tue, 06 Nov 2012 19:43:42 +0000
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: dcrocker@bbiw.net
Subject: Re: IESG Considering a Revision to NOTE WELL
References: <55D046F8-5DD2-42E8-9B8C-36C612C4B3F8@ietf.org> <50992BEF.9000803@gmail.com> <C66E7DEF-EEE8-4678-91C1-1FD46854312C@vigilsec.com> <50995E81.3020606@gmail.com> <50996571.2010406@dcrocker.net>
In-Reply-To: <50996571.2010406@dcrocker.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Nov 2012 19:43:43 -0000

On 06/11/2012 19:30, Dave Crocker wrote:
> 
> 
> On 11/6/2012 2:01 PM, Brian E Carpenter wrote:
>>  but I remain bothered by taking
>> out all the details. I understand there is a problem of attention span,
>> but there are not really all that many words in the current version.
> 
> 
> Simple human factors:
> 
>    You cannot expect anyone to process a mass of text from a slide and
> develop useful understanding, nevermind take required action.
> 
> 
> Making a useful slide requires synthesizing it to show only the
> essential information.  That's what I understand the current excise to
> be and it is exactly the right thing to do.
> 
> The slide we show should have a very terse statement of the topic, the
> reader's obligations and where to go to find out more.

The slide, yes. But there is the version you see on line, where I think
the details are appropriate.

    Brian

From wesley.george@twcable.com  Tue Nov  6 11:49:13 2012
Return-Path: <wesley.george@twcable.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D6D821F8A78 for <ietf@ietfa.amsl.com>; Tue,  6 Nov 2012 11:49:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.088
X-Spam-Level: 
X-Spam-Status: No, score=-1.088 tagged_above=-999 required=5 tests=[AWL=0.375,  BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, 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 RYdQG-fQ7aU6 for <ietf@ietfa.amsl.com>; Tue,  6 Nov 2012 11:49:13 -0800 (PST)
Received: from cdpipgw01.twcable.com (cdpipgw01.twcable.com [165.237.59.22]) by ietfa.amsl.com (Postfix) with ESMTP id E80B621F858E for <ietf@ietf.org>; Tue,  6 Nov 2012 11:49:12 -0800 (PST)
X-SENDER-IP: 10.136.163.12
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.80,722,1344225600"; d="scan'208";a="465976708"
Received: from unknown (HELO PRVPEXHUB03.corp.twcable.com) ([10.136.163.12]) by cdpipgw01.twcable.com with ESMTP/TLS/RC4-MD5; 06 Nov 2012 14:48:31 -0500
Received: from PRVPEXVS15.corp.twcable.com ([10.136.163.78]) by PRVPEXHUB03.corp.twcable.com ([10.136.163.12]) with mapi; Tue, 6 Nov 2012 14:49:11 -0500
From: "George, Wes" <wesley.george@twcable.com>
To: IETF <ietf@ietf.org>
Date: Tue, 6 Nov 2012 14:49:14 -0500
Subject: RE: IESG Considering a Revision to NOTE WELL
Thread-Topic: IESG Considering a Revision to NOTE WELL
Thread-Index: Ac28L5NDYNnamL+ySCO0u2sCw4ePeQAJr7xA
Message-ID: <2671C6CDFBB59E47B64C10B3E0BD59230336F7AF63@PRVPEXVS15.corp.twcable.com>
References: <55D046F8-5DD2-42E8-9B8C-36C612C4B3F8@ietf.org>
In-Reply-To: <55D046F8-5DD2-42E8-9B8C-36C612C4B3F8@ietf.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Nov 2012 19:49:13 -0000

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> IETF Chair
>
> =3D=3D=3D Proposed Revised NOTE WELL Text =3D=3D=3D
>
>   - You understand that meetings might be recorded, broadcast, and
>    publicly archived.
>
[WEG] I might suggest a small tweak (in brackets below) to this part of the=
 text given some of the previous discussions around blue sheets/privacy and=
 documenting people's participation in IETF potentially against their will:

- You understand that meetings [and therefore your participation in them] m=
ight be recorded, broadcast, and publicly archived.
I think this makes things a little more explicit in a way that may be helpf=
ul to those who are less familiar with IETF meetings.

Otherwise, consider this a +1 to comments supporting simplification of the =
Note Well text to make it a more effective summary.

Wes George

This E-mail and any of its attachments may contain Time Warner Cable propri=
etary information, which is privileged, confidential, or subject to copyrig=
ht belonging to Time Warner Cable. This E-mail is intended solely for the u=
se of the individual or entity to which it is addressed. If you are not the=
 intended recipient of this E-mail, you are hereby notified that any dissem=
ination, distribution, copying, or action taken in relation to the contents=
 of and attachments to this E-mail is strictly prohibited and may be unlawf=
ul. If you have received this E-mail in error, please notify the sender imm=
ediately and permanently delete the original and any copy of this E-mail an=
d any printout.

From eburger@standardstrack.com  Tue Nov  6 12:46:19 2012
Return-Path: <eburger@standardstrack.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6401021F8ADD for <ietf@ietfa.amsl.com>; Tue,  6 Nov 2012 12:46:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.598
X-Spam-Level: 
X-Spam-Status: No, score=-102.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 iJ88gFyeG7s8 for <ietf@ietfa.amsl.com>; Tue,  6 Nov 2012 12:46:18 -0800 (PST)
Received: from biz104.inmotionhosting.com (biz104.inmotionhosting.com [173.247.254.120]) by ietfa.amsl.com (Postfix) with ESMTP id 9ADF621F8AD9 for <ietf@ietf.org>; Tue,  6 Nov 2012 12:46:18 -0800 (PST)
Received: from 226.sub-174-231-128.myvzw.com ([174.231.128.226]:7101 helo=biz104.inmotionhosting.com) by biz104.inmotionhosting.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from <eburger@standardstrack.com>) id 1TVq29-0001xY-IJ for ietf@ietf.org; Tue, 06 Nov 2012 12:46:06 -0800
Message-ID: <dd516ef6-b1cf-46f4-b613-121ee7751303@blur>
From: "Eric Burger"<eburger@standardstrack.com>
To: IETF<ietf@ietf.org>
Date: Tue, 6 Nov 2012 15:46:33 -0500
X-Mailer: Motorola android mail 1.0
MIME-Version: 1.0
Subject: Re: IESG Considering a Revision to NOTE WELL
X-Priority: 3
References: <55D046F8-5DD2-42E8-9B8C-36C612C4B3F8@ietf.org>
In-Reply-To: <55D046F8-5DD2-42E8-9B8C-36C612C4B3F8@ietf.org>
Content-Type: multipart/alternative; boundary="Motorola-A-Mail-BR1gFPHAHLc2nlhC"
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - biz104.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - standardstrack.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Nov 2012 20:46:19 -0000

--Motorola-A-Mail-BR1gFPHAHLc2nlhC
Content-Type: text/plain; Format="Flowed"; DelSp="Yes"; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

Way too simple, straightforward, and easy to understand. Can't we play  
lawyer-on-the-list and make it a full page again?

--
Sent from my mobile device. Thanks be to lemonade!  
http://www.standardstrack.com/ietf/lemonade/

-----Original message-----
From: IETF Chair <chair@ietf.org>
To: IETF Announce <ietf-announce@ietf.org>
Cc: IETF <ietf@ietf.org>
Sent: Tue, Nov 6, 2012 15:01:59 GMT+00:00
Subject: IESG Considering a Revision to NOTE WELL

The IESG is considering a revision to the NOTE WELL text.  Please review and  
comment.

Russ



=== Proposed Revised NOTE WELL Text ===

Note Well

This summary is only meant to point you in the right direction, and
doesn't have all the nuances. The IETF's IPR Policy is set forth in
BCP 79; please read it carefully.

The brief summary:
  - By participating with the IETF, you agree to follow IETF processes.
  - If you are aware that a contribution of yours (something you write,
    say, or discuss in any IETF context) is covered by patents or patent
    applications, you need to disclose that fact.
  - You understand that meetings might be recorded, broadcast, and
   publicly archived.

For further information: Talk to a chair, ask an Area Director, or
review  BCP 9 (on the Internet Standards Process), BCP 25 (on the
Working Group processes), BCP 78 (on the IETF Trust), and BCP 79 (on
Intellectual Property Rights in the IETF).


--Motorola-A-Mail-BR1gFPHAHLc2nlhC
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: base64

PGh0bWw+PGhlYWQ+PHN0eWxlIHR5cGU9InRleHQvY3NzIj5ib2R5IHt3b3JkLXdyYXA6IGJyZWFr
LXdvcmQ7IGJhY2tncm91bmQtY29sb3I6I2ZmZmZmZjt9PC9zdHlsZT48L2hlYWQ+PGJvZHk+PGRp
diBzdHlsZT0iZm9udC1mYW1pbHk6IHNhbnMtc2VyaWY7IGZvbnQtc2l6ZTogMTZweCI+V2F5IHRv
byBzaW1wbGUsIHN0cmFpZ2h0Zm9yd2FyZCwgYW5kIGVhc3kgdG8gdW5kZXJzdGFuZC4gQ2FuJ3Qg
d2UgcGxheSBsYXd5ZXItb24tdGhlLWxpc3QgYW5kIG1ha2UgaXQgYSBmdWxsIHBhZ2UgYWdhaW4/
PGJyPjxicj4tLTxicj5TZW50IGZyb20gbXkgbW9iaWxlIGRldmljZS4gVGhhbmtzIGJlIHRvIGxl
bW9uYWRlISA8YSBocmVmPSJodHRwOi8vd3d3LnN0YW5kYXJkc3RyYWNrLmNvbS9pZXRmL2xlbW9u
YWRlLyI+aHR0cDovL3d3dy5zdGFuZGFyZHN0cmFjay5jb20vaWV0Zi9sZW1vbmFkZS88L2E+PC9k
aXY+PGJyPjxicj4tLS0tLU9yaWdpbmFsIG1lc3NhZ2UtLS0tLTxicj48YmxvY2txdW90ZSBzdHls
ZT0iOyBib3JkZXItbGVmdDogMnB4IHNvbGlkIHJnYigxNiwgMTYsIDI1NSk7IG1hcmdpbi1sZWZ0
OiA1cHg7IHBhZGRpbmctbGVmdDogNXB4OyI+PGRpdiBzdHlsZT0iZm9udC1mYW1pbHk6IHNhbnMt
c2VyaWY7IGZvbnQtc2l6ZTogMTRweCI+PGI+RnJvbTogPC9iPklFVEYgQ2hhaXIgJmx0O2NoYWly
QGlldGYub3JnJmd0OzxiPjxicj5UbzogPC9iPklFVEYgQW5ub3VuY2UgJmx0O2lldGYtYW5ub3Vu
Y2VAaWV0Zi5vcmcmZ3Q7PGI+PGJyPkNjOiA8L2I+SUVURiAmbHQ7aWV0ZkBpZXRmLm9yZyZndDs8
Yj48YnI+U2VudDogPC9iPlR1ZSwgTm92IDYsIDIwMTIgMTU6MDE6NTkgR01UKzAwOjAwPGI+PGJy
PlN1YmplY3Q6IDwvYj5JRVNHIENvbnNpZGVyaW5nIGEgUmV2aXNpb24gdG8gTk9URSBXRUxMPGJy
Pjxicj48L2Rpdj5UaGUgSUVTRyBpcyBjb25zaWRlcmluZyBhIHJldmlzaW9uIHRvIHRoZSBOT1RF
IFdFTEwgdGV4dC4gIFBsZWFzZSByZXZpZXcgYW5kIGNvbW1lbnQuPGJyPjxicj5SdXNzPGJyPjxi
cj48YnI+PGJyPj09PSBQcm9wb3NlZCBSZXZpc2VkIE5PVEUgV0VMTCBUZXh0ID09PTxicj48YnI+
Tm90ZSBXZWxsPGJyPjxicj5UaGlzIHN1bW1hcnkgaXMgb25seSBtZWFudCB0byBwb2ludCB5b3Ug
aW4gdGhlIHJpZ2h0IGRpcmVjdGlvbiwgYW5kPGJyPmRvZXNuJ3QgaGF2ZSBhbGwgdGhlIG51YW5j
ZXMuIFRoZSBJRVRGJ3MgSVBSIFBvbGljeSBpcyBzZXQgZm9ydGggaW48YnI+QkNQIDc5OyBwbGVh
c2UgcmVhZCBpdCBjYXJlZnVsbHkuPGJyPjxicj5UaGUgYnJpZWYgc3VtbWFyeTo8YnI+ICAtIEJ5
IHBhcnRpY2lwYXRpbmcgd2l0aCB0aGUgSUVURiwgeW91IGFncmVlIHRvIGZvbGxvdyBJRVRGIHBy
b2Nlc3Nlcy48YnI+ICAtIElmIHlvdSBhcmUgYXdhcmUgdGhhdCBhIGNvbnRyaWJ1dGlvbiBvZiB5
b3VycyAoc29tZXRoaW5nIHlvdSB3cml0ZSw8YnI+ICAgIHNheSwgb3IgZGlzY3VzcyBpbiBhbnkg
SUVURiBjb250ZXh0KSBpcyBjb3ZlcmVkIGJ5IHBhdGVudHMgb3IgcGF0ZW50PGJyPiAgICBhcHBs
aWNhdGlvbnMsIHlvdSBuZWVkIHRvIGRpc2Nsb3NlIHRoYXQgZmFjdC48YnI+ICAtIFlvdSB1bmRl
cnN0YW5kIHRoYXQgbWVldGluZ3MgbWlnaHQgYmUgcmVjb3JkZWQsIGJyb2FkY2FzdCwgYW5kPGJy
PiAgIHB1YmxpY2x5IGFyY2hpdmVkLjxicj48YnI+Rm9yIGZ1cnRoZXIgaW5mb3JtYXRpb246IFRh
bGsgdG8gYSBjaGFpciwgYXNrIGFuIEFyZWEgRGlyZWN0b3IsIG9yPGJyPnJldmlldyAgQkNQIDkg
KG9uIHRoZSBJbnRlcm5ldCBTdGFuZGFyZHMgUHJvY2VzcyksIEJDUCAyNSAob24gdGhlPGJyPldv
cmtpbmcgR3JvdXAgcHJvY2Vzc2VzKSwgQkNQIDc4IChvbiB0aGUgSUVURiBUcnVzdCksIGFuZCBC
Q1AgNzkgKG9uPGJyPkludGVsbGVjdHVhbCBQcm9wZXJ0eSBSaWdodHMgaW4gdGhlIElFVEYpLjxi
cj48L2Jsb2NrcXVvdGU+PC9ib2R5PjwvaHRtbD4NCg==


--Motorola-A-Mail-BR1gFPHAHLc2nlhC--

From tglassey@earthlink.net  Tue Nov  6 12:51:16 2012
Return-Path: <tglassey@earthlink.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 34C0D21F8B13; Tue,  6 Nov 2012 12:51:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.49
X-Spam-Level: 
X-Spam-Status: No, score=-2.49 tagged_above=-999 required=5 tests=[AWL=0.108,  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 QnZK6j8DN7va; Tue,  6 Nov 2012 12:51:14 -0800 (PST)
Received: from elasmtp-mealy.atl.sa.earthlink.net (elasmtp-mealy.atl.sa.earthlink.net [209.86.89.69]) by ietfa.amsl.com (Postfix) with ESMTP id F377B21F84FA; Tue,  6 Nov 2012 12:51:10 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=nFS0S+WfyS7VTaxYOuZSLSudtEfyORnPie0cFDdbd8rRMsqpqZjMv/CeF//Tx8Fb; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:X-ELNK-Trace:X-Originating-IP;
Received: from [67.180.133.21] (helo=[192.168.15.2]) by elasmtp-mealy.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <tglassey@earthlink.net>) id 1TVq74-0002Tt-D6; Tue, 06 Nov 2012 15:51:10 -0500
Message-ID: <50997842.5080407@earthlink.net>
Date: Tue, 06 Nov 2012 12:51:14 -0800
From: tglassey <tglassey@earthlink.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: Eric Burger <eburger@standardstrack.com>, IPR@ietf.org,  ietf <ietf@ietf.org>
Subject: Re: IESG Considering a Revision to NOTE WELL
References: <55D046F8-5DD2-42E8-9B8C-36C612C4B3F8@ietf.org> <dd516ef6-b1cf-46f4-b613-121ee7751303@blur>
In-Reply-To: <dd516ef6-b1cf-46f4-b613-121ee7751303@blur>
Content-Type: multipart/alternative; boundary="------------060406050200020308070608"
X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec795dd72dc4441b1ebcf31d41e61f1f5f1c350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 67.180.133.21
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Nov 2012 20:51:16 -0000

This is a multi-part message in MIME format.
--------------060406050200020308070608
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

On 11/6/2012 12:46 PM, Eric Burger wrote:
> Way too simple, straightforward, and easy to understand. Can't we play 
> lawyer-on-the-list and make it a full page again?
>
> --
> Sent from my mobile device. Thanks be to lemonade! 
> http://www.standardstrack.com/ietf/lemonade/
>
>
> -----Original message-----
>
>     *From: *IETF Chair <chair@ietf.org>*
>     To: *IETF Announce <ietf-announce@ietf.org>*
>     Cc: *IETF <ietf@ietf.org>*
>     Sent: *Tue, Nov 6, 2012 15:01:59 GMT+00:00*
>     Subject: *IESG Considering a Revision to NOTE WELL
>
>     The IESG is considering a revision to the NOTE WELL text. Please
>     review and comment.
>
>     Russ
>
>
>
>     === Proposed Revised NOTE WELL Text ===
>
>     Note Well
>
>     This summary is only meant to point you in the right direction, and
>     doesn't have all the nuances. The IETF's IPR Policy is set forth in
>     BCP 79; please read it carefully.
>
>     The brief summary:
>     - By participating with the IETF, you agree to follow IETF processes.
>     - If you are aware that a contribution of yours (something you write,
>     say, or discuss in any IETF context) is covered by patents or patent
>     applications, you need to disclose that fact.
>
There is no penalty for NOT DISCLOSING and that is the issue.
>
>     - You understand that meetings might be recorded, broadcast, and
>     publicly archived.
>
So this is the Privacy Waiver Statement.
>
>
>     For further information: Talk to a chair, ask an Area Director, or
>     review BCP 9 (on the Internet Standards Process), BCP 25 (on the
>     Working Group processes), BCP 78 (on the IETF Trust), and BCP 79 (on
>     Intellectual Property Rights in the IETF).
>


-- 
Regards TSG
"Ex-Cruce-Leo"

//Confidential Mailing - Please destroy this if you are not the intended recipient.


--------------060406050200020308070608
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">On 11/6/2012 12:46 PM, Eric Burger
      wrote:<br>
    </div>
    <blockquote cite="mid:dd516ef6-b1cf-46f4-b613-121ee7751303@blur"
      type="cite">
      <style type="text/css">body {word-wrap: break-word; background-color:#ffffff;}</style>
      <div style="font-family: sans-serif; font-size: 16px">Way too
        simple, straightforward, and easy to understand. Can't we play
        lawyer-on-the-list and make it a full page again?<br>
        <br>
        --<br>
        Sent from my mobile device. Thanks be to lemonade! <a
          moz-do-not-send="true"
          href="http://www.standardstrack.com/ietf/lemonade/">http://www.standardstrack.com/ietf/lemonade/</a></div>
      <br>
      <br>
      -----Original message-----<br>
      <blockquote style="border-left: 2px solid rgb(16, 16, 255);
        margin-left: 5px; padding-left: 5px;">
        <div style="font-family: sans-serif; font-size: 14px"><b>From: </b>IETF
          Chair <a class="moz-txt-link-rfc2396E" href="mailto:chair@ietf.org">&lt;chair@ietf.org&gt;</a><b><br>
            To: </b>IETF Announce <a class="moz-txt-link-rfc2396E" href="mailto:ietf-announce@ietf.org">&lt;ietf-announce@ietf.org&gt;</a><b><br>
            Cc: </b>IETF <a class="moz-txt-link-rfc2396E" href="mailto:ietf@ietf.org">&lt;ietf@ietf.org&gt;</a><b><br>
            Sent: </b>Tue, Nov 6, 2012 15:01:59 GMT+00:00<b><br>
            Subject: </b>IESG Considering a Revision to NOTE WELL<br>
          <br>
        </div>
        The IESG is considering a revision to the NOTE WELL text. Please
        review and comment.<br>
        <br>
        Russ<br>
        <br>
        <br>
        <br>
        === Proposed Revised NOTE WELL Text ===<br>
        <br>
        Note Well<br>
        <br>
        This summary is only meant to point you in the right direction,
        and<br>
        doesn't have all the nuances. The IETF's IPR Policy is set forth
        in<br>
        BCP 79; please read it carefully.<br>
        <br>
        The brief summary:<br>
        - By participating with the IETF, you agree to follow IETF
        processes.<br>
        - If you are aware that a contribution of yours (something you
        write,<br>
        say, or discuss in any IETF context) is covered by patents or
        patent<br>
        applications, you need to disclose that fact.<br>
      </blockquote>
    </blockquote>
    There is no penalty for NOT DISCLOSING and that is the issue. <br>
    <blockquote cite="mid:dd516ef6-b1cf-46f4-b613-121ee7751303@blur"
      type="cite">
      <blockquote style="border-left: 2px solid rgb(16, 16, 255);
        margin-left: 5px; padding-left: 5px;"> - You understand that
        meetings might be recorded, broadcast, and<br>
        publicly archived.<br>
      </blockquote>
    </blockquote>
    So this is the Privacy Waiver Statement.<br>
    <blockquote cite="mid:dd516ef6-b1cf-46f4-b613-121ee7751303@blur"
      type="cite">
      <blockquote style="; border-left: 2px solid rgb(16, 16, 255);
        margin-left: 5px; padding-left: 5px;"><br>
        For further information: Talk to a chair, ask an Area Director,
        or<br>
        review BCP 9 (on the Internet Standards Process), BCP 25 (on the<br>
        Working Group processes), BCP 78 (on the IETF Trust), and BCP 79
        (on<br>
        Intellectual Property Rights in the IETF).<br>
      </blockquote>
    </blockquote>
    <br>
    <br>
    <pre class="moz-signature" cols="72">-- 
Regards TSG
"Ex-Cruce-Leo"

//Confidential Mailing - Please destroy this if you are not the intended recipient. 
</pre>
  </body>
</html>

--------------060406050200020308070608--

From sob@sobco.com  Tue Nov  6 13:17:51 2012
Return-Path: <sob@sobco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9410021F89AD for <ietf@ietfa.amsl.com>; Tue,  6 Nov 2012 13:17:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.495
X-Spam-Level: 
X-Spam-Status: No, score=-0.495 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  RDNS_NONE=0.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 VKV8bPQftOmR for <ietf@ietfa.amsl.com>; Tue,  6 Nov 2012 13:17:51 -0800 (PST)
Received: from sobco.sobco.com (unknown [136.248.127.164]) by ietfa.amsl.com (Postfix) with ESMTP id 2A31021F8997 for <ietf@ietf.org>; Tue,  6 Nov 2012 13:17:51 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by sobco.sobco.com (Postfix) with ESMTP id 7954C3665EF; Tue,  6 Nov 2012 16:17:50 -0500 (EST)
X-Virus-Scanned: amavisd-new at sobco.com
Received: from sobco.sobco.com ([127.0.0.1]) by localhost (sobco.sobco.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7lzmjDHMsne7; Tue,  6 Nov 2012 16:17:49 -0500 (EST)
Received: from dhcp-12fd.meeting.ietf.org (dhcp-12fd.meeting.ietf.org [130.129.18.253]) by sobco.sobco.com (Postfix) with ESMTPSA id 64CAE3665DC; Tue,  6 Nov 2012 16:17:49 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: IESG Considering a Revision to NOTE WELL
From: Scott O Bradner <sob@sobco.com>
In-Reply-To: <8C48B86A895913448548E6D15DA7553B197FCD@xmb-rcd-x09.cisco.com>
Date: Tue, 6 Nov 2012 16:17:48 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <8370F371-6CB2-4BDB-BED9-82D9784E429B@sobco.com>
References: <55D046F8-5DD2-42E8-9B8C-36C612C4B3F8@ietf.org> <8C48B86A895913448548E6D15DA7553B197F04@xmb-rcd-x09.cisco.com> <alpine.LFD.2.02.1211061040400.16141@bofh.nohats.ca> <8C48B86A895913448548E6D15DA7553B197FCD@xmb-rcd-x09.cisco.com>
To: Fred Baker (fred) <fred@cisco.com>
X-Mailer: Apple Mail (2.1499)
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Nov 2012 21:17:51 -0000

On Nov 6, 2012, at 10:54 AM, Fred Baker (fred) <fred@cisco.com> wrote:
>=20
> Not being a lawyer, I can't comment on the legal details of IPR cases. =
What I am looking at is the understandability of a statement. A lawyer =
that I was speaking with recently told me that the IETF IPR policy is =
ambiguous; one must file IPR statements for standards, but not for =
informational documents. We wound up wandering through the details of =
legal statements, in which I felt he was working pretty hard to make =
words stand on their heads.

in case anyone wonders

one might have been able to read that into RFC 2026 but that was very =
carefully fixed
in the current documents - disclosures are required for ALL =
contributions

Scott=

From wjhns1@hardakers.net  Tue Nov  6 13:33:23 2012
Return-Path: <wjhns1@hardakers.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DB98D21F8724 for <ietf@ietfa.amsl.com>; Tue,  6 Nov 2012 13:33:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.222
X-Spam-Level: 
X-Spam-Status: No, score=-2.222 tagged_above=-999 required=5 tests=[AWL=0.222,  BAYES_00=-2.599, NO_RELAYS=-0.001, SUBJECT_FUZZY_TION=0.156]
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 gvDKW4tmkpgf for <ietf@ietfa.amsl.com>; Tue,  6 Nov 2012 13:33:23 -0800 (PST)
Received: from mail.hardakers.net (dawn.hardakers.net [IPv6:2001:470:1f00:187::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7ABED21F8457 for <ietf@ietf.org>; Tue,  6 Nov 2012 13:33:23 -0800 (PST)
Received: from localhost (unknown [IPv6:2001:df8:0:16:62d8:19ff:fed4:c8b6]) by mail.hardakers.net (Postfix) with ESMTPSA id 06F6A3B8; Tue,  6 Nov 2012 13:33:19 -0800 (PST)
From: Wes Hardaker <wjhns1@hardakers.net>
To: Olafur Gudmundsson <ogud@ogud.com>
Subject: Re: Recall petition for Mr. Marshall Eubanks
References: <50919671.6000605@ogud.com>
Date: Tue, 06 Nov 2012 13:33:16 -0800
In-Reply-To: <50919671.6000605@ogud.com> (Olafur Gudmundsson's message of "Wed, 31 Oct 2012 17:21:53 -0400")
Message-ID: <0lk3tyo1r7.fsf@wjh.hardakers.net>
User-Agent: Gnus/5.130006 (Ma Gnus v0.6) Emacs/24.1 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
Cc: 'IETF-Discussion list' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Nov 2012 21:33:24 -0000

Olafur Gudmundsson <ogud@ogud.com> writes:

> If you agree with this petition please either comment on this posting,

With regret, if you still need more signatures, you can add my name to
the list and I am nomcom eligible.
-- 
Wes Hardaker
SPARTA, Inc.

From stewe@stewe.org  Tue Nov  6 13:47:24 2012
Return-Path: <stewe@stewe.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 71AA521F8A5E for <ietf@ietfa.amsl.com>; Tue,  6 Nov 2012 13:47:24 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y1LzF7+Kcnyg for <ietf@ietfa.amsl.com>; Tue,  6 Nov 2012 13:47:23 -0800 (PST)
Received: from db3outboundpool.messaging.microsoft.com (db3ehsobe003.messaging.microsoft.com [213.199.154.141]) by ietfa.amsl.com (Postfix) with ESMTP id DD90621F8A4D for <ietf@ietf.org>; Tue,  6 Nov 2012 13:47:22 -0800 (PST)
Received: from mail49-db3-R.bigfish.com (10.3.81.248) by DB3EHSOBE008.bigfish.com (10.3.84.28) with Microsoft SMTP Server id 14.1.225.23; Tue, 6 Nov 2012 21:47:21 +0000
Received: from mail49-db3 (localhost [127.0.0.1])	by mail49-db3-R.bigfish.com (Postfix) with ESMTP id 12A76300254; Tue,  6 Nov 2012 21:47:21 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.240.133; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0710HT003.namprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -17
X-BigFish: PS-17(zz98dI9371I1432I5a4kzz1de0h1202h1d1ah1d2ah1082kzz1033IL8275bh8275dhz2fh2a8h668h839h944hd25hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh1155h)
Received-SPF: pass (mail49-db3: domain of stewe.org designates 157.56.240.133 as permitted sender) client-ip=157.56.240.133; envelope-from=stewe@stewe.org; helo=BL2PRD0710HT003.namprd07.prod.outlook.com ; .outlook.com ; 
Received: from mail49-db3 (localhost.localdomain [127.0.0.1]) by mail49-db3 (MessageSwitch) id 1352238439145144_18995; Tue,  6 Nov 2012 21:47:19 +0000 (UTC)
Received: from DB3EHSMHS002.bigfish.com (unknown [10.3.81.236])	by mail49-db3.bigfish.com (Postfix) with ESMTP id 17E6034017A; Tue,  6 Nov 2012 21:47:19 +0000 (UTC)
Received: from BL2PRD0710HT003.namprd07.prod.outlook.com (157.56.240.133) by DB3EHSMHS002.bigfish.com (10.3.87.102) with Microsoft SMTP Server (TLS) id 14.1.225.23; Tue, 6 Nov 2012 21:47:17 +0000
Received: from BL2PRD0710MB349.namprd07.prod.outlook.com ([169.254.2.192]) by BL2PRD0710HT003.namprd07.prod.outlook.com ([10.255.102.38]) with mapi id 14.16.0233.002; Tue, 6 Nov 2012 21:47:17 +0000
From: Stephan Wenger <stewe@stewe.org>
To: Russ Housley <housley@vigilsec.com>
Subject: Re: IESG Considering a Revision to NOTE WELL
Thread-Topic: IESG Considering a Revision to NOTE WELL
Thread-Index: AQHNvC+P1gsovbnYEkqDQrp0L72z0JfczKkAgABdMAD//9qGAA==
Date: Tue, 6 Nov 2012 21:47:17 +0000
Message-ID: <FDBFA77C7400C74F87BC297393B53E35259B2E90@BL2PRD0710MB349.namprd07.prod.outlook.com>
In-Reply-To: <94CB8D65-EE75-4D54-B846-44F8CB472A48@vigilsec.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.255.102.4]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <90F516DA72BE9B479847DEE7EDD28A78@namprd07.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: stewe.org
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Nov 2012 21:47:24 -0000

Hi Russ,

On 11.6.2012 14:01 , "Russ Housley" <housley@vigilsec.com> wrote:

>Stephan:
>
>Based on the number of late disclosures that are occurring, it is clear
>to us that we need to use very plain language to explain the
>responsibilities to participants.

That's an interesting statement.  To summarize the (long) message below, I
don't think that empirical data supports that there are any significant
numbers of disclosures of which it is likely that they are "late".

I went through the recent IPR disclosures (July 2012 until present) to
check against what documents they have been made.  In tabular form:
Draft-00: 13
Draft-01:  8
Draft-02:  7
Draft-03:  9
Draft-04 and later drafts: 14
Issued RFCs: 4
3rd party disclosures: 15

The 3rd party disclosures obviously are irrelevant here, as there is no
disclosure obligation for third party patent rights per BCP 79, and where
there is no obligation to disclose there cannot be a late disclosure.

Of the four disclosures made against issued RFCs, only one had a match
between an inventor's name and the RFC's author list.  That one is pledged
as RAND-Z.  It's undoubtedly late, but I guess that the rightholder
attempted to cure that lateness by offering advantageous licensing terms.
The other disclosures are RAND, but there is no indication that the
companies making the disclosure were contributing, at least not based on
matching inventor/author names (or my vague recollection of who said what
in meeting rooms at the time).   It can well be that the disclosures are
completely voluntarily, or that the disclosure requirement was triggered
just recently.  There are many examples on why this may have happened: one
of the authors joint the company in question just recently (which is the
case for one of the disclosures), or that the patent changed hands just
recently (which was the case in one of the Opus-related declarations that
looked, at the first glance, late, but clearly wasn't.)  I will also note
that one company that made a disclosure is not an IETF regular, and the
other has a comparatively small delegation for its size.  In conclusion, I
don't believe that any of the four cases have been shown to be late
disclosures, and my personal feeling is that it is highly likely that none
of them is.

As for the disclosures against older drafts (04+), they may or may not be
late.  A disclosure could be made against subject matter that has just
recently been included into a draft that already has some history.  A
disclosure obligation may have been triggered because a participant from a
given company, for the first time, decided to comment on the draft.  And
so on.  Based on the information I have, I could not conclude that there
is a single late disclosure, although I would consider it likely that
there are a few. =20

As for disclosures against drafts 00 through 03, I would argue that most,
if not all, of these disclosures are probably timely.  A year or so is not
an unreasonable time frame for a company to make a disclosure, considering
the amount of paperwork and coordination required to do so.  It's not only
that a company needs to determine, for itself, whether a disclosure is
required (draw up a claim chart, have it checked by legal, understand the
role of the participant, understand the--rather exotic--IETF patent policy
among the other dozens of policies of bodies the company may be involved
in), but the company has also to settle on the licensing terms they wish
to offer (which can involve standards people, legal, and business folks,
and in many cases requires multi-level approval).  I have run that process
for one of the larger IETF participating companies in the past, and
believe me, a year is not unrealistic, even after the
policy-understanding-and-advocating phase is behind that company.  As our
policy does NOT specify another timeframe, I don't think that an argument
to the contrary is bearing as much weight as the procedural argument made
here.=20

(Yes, when analyzing the drafts I have been sloppy in not distinguishing
between WG and individual drafts.  I don't think that would change the
picture significantly.)

So, to summarize, out of the 60 or so non-third-party disclosures that
have been made over the last 4+ months, only "a few" may or may not be
late; the rest almost certainly is not.

Also, I have not seen a trend going towards late disclosures.  Quite
contrary, I have seen a trend towards early disclosures.

I do not believe that, based on this data, there is a need to change the
Note Well.  If you folks still think a change is needed, then at least do
not make a change in such a way that the new Note Well does not correctly
interpret the policy we have.

The way to fix the "timeliness" of disclosures is to change BCP 79, by
adding a definition of timeliness, preferably a hard one (six months or
something like this).

Stephan





>
>Russ
>
>
>On Nov 6, 2012, at 1:27 PM, Stephan Wenger wrote:
>
>> Hi,
>> Russ, can you explain why the IESG considers it necessary to tinker with
>> the Note Well?
>> As for the substance, I don't like the text for two reasons that can be
>> found inline.
>> Stephan
>>=20
>> On 11.6.2012 10:00 , "IETF Chair" <chair@ietf.org> wrote:
>>=20
>>> The IESG is considering a revision to the NOTE WELL text.  Please
>>>review
>>> and comment.
>>>=20
>>> Russ
>>>=20
>>>=20
>>>=20
>>> =3D=3D=3D Proposed Revised NOTE WELL Text =3D=3D=3D
>>>=20
>>> Note Well
>>>=20
>>> This summary is only meant to point you in the right direction, and
>>> doesn't have all the nuances. The IETF's IPR Policy is set forth in
>>> BCP 79; please read it carefully.
>>>=20
>>> The brief summary:
>>> - By participating with the IETF, you agree to follow IETF processes.
>>> - If you are aware that a contribution of yours (something you write,
>>>   say, or discuss in any IETF context) is covered by patents or patent
>>>   applications, you need to disclose that fact.
>>=20
>> 1) I'm not in favor of this formulation because it can be read to
>>impose a
>> stronger disclosure obligation on a participant than BCP 79.
>> Specifically, as Lars has already pointed out and according to BCP 79,
>>I'm
>> not "needed" to disclose a patent I'm reasonably and personally aware of
>> that reads on a document of mine, if that patent is assigned to someone
>> else but myself and my sponsor/employer, ... For good reasons, BCP 79
>>does
>> not require third party disclosures.  I hope that the (few) added words
>> can be accommodated.
>> 2) On the other hand, the issue of timeliness is not covered at all (as
>> others have already pointed out.)
>>=20
>> I'm especially worried of point 1, which can be seen as a policy change
>> through the back door.  If, based on this hypothetical Note Well, we
>>would
>> end up with an IETF disclosure culture in which third party disclosures
>> would become the norm rather than an exception, we could well end up
>>with
>> a brain drain especially from folks not quite as senior in their
>> respective company hierarchy to have the leeway to ignore company
>>guidance
>> about patents.=20
>>=20
>>=20
>>> - You understand that meetings might be recorded, broadcast, and
>>>  publicly archived.
>>>=20
>>> For further information: Talk to a chair, ask an Area Director, or
>>> review  BCP 9 (on the Internet Standards Process), BCP 25 (on the
>>> Working Group processes), BCP 78 (on the IETF Trust), and BCP 79 (on
>>> Intellectual Property Rights in the IETF).
>>=20
>>=20
>
>



From stewe@stewe.org  Tue Nov  6 13:56:43 2012
Return-Path: <stewe@stewe.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2AA0321F8B55 for <ietf@ietfa.amsl.com>; Tue,  6 Nov 2012 13:56:43 -0800 (PST)
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.000,  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 eApZsmZOdZgp for <ietf@ietfa.amsl.com>; Tue,  6 Nov 2012 13:56:42 -0800 (PST)
Received: from db3outboundpool.messaging.microsoft.com (db3ehsobe003.messaging.microsoft.com [213.199.154.141]) by ietfa.amsl.com (Postfix) with ESMTP id 968A321F8B15 for <ietf@ietf.org>; Tue,  6 Nov 2012 13:56:41 -0800 (PST)
Received: from mail2-db3-R.bigfish.com (10.3.81.248) by DB3EHSOBE008.bigfish.com (10.3.84.28) with Microsoft SMTP Server id 14.1.225.23; Tue, 6 Nov 2012 21:56:40 +0000
Received: from mail2-db3 (localhost [127.0.0.1])	by mail2-db3-R.bigfish.com (Postfix) with ESMTP id B695A440319; Tue,  6 Nov 2012 21:56:40 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.240.133; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0710HT005.namprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: 0
X-BigFish: PS0(zz98dI9371I1432Izz1de0h1202h1d1ah1d2ah1082kzz8275bhz2fh2a8h668h839h944hd25hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh1155h)
Received-SPF: pass (mail2-db3: domain of stewe.org designates 157.56.240.133 as permitted sender) client-ip=157.56.240.133; envelope-from=stewe@stewe.org; helo=BL2PRD0710HT005.namprd07.prod.outlook.com ; .outlook.com ; 
Received: from mail2-db3 (localhost.localdomain [127.0.0.1]) by mail2-db3 (MessageSwitch) id 1352238998270488_10822; Tue,  6 Nov 2012 21:56:38 +0000 (UTC)
Received: from DB3EHSMHS007.bigfish.com (unknown [10.3.81.247])	by mail2-db3.bigfish.com (Postfix) with ESMTP id 3E23A2C0049; Tue,  6 Nov 2012 21:56:38 +0000 (UTC)
Received: from BL2PRD0710HT005.namprd07.prod.outlook.com (157.56.240.133) by DB3EHSMHS007.bigfish.com (10.3.87.107) with Microsoft SMTP Server (TLS) id 14.1.225.23; Tue, 6 Nov 2012 21:56:34 +0000
Received: from BL2PRD0710MB349.namprd07.prod.outlook.com ([169.254.2.192]) by BL2PRD0710HT005.namprd07.prod.outlook.com ([10.255.102.40]) with mapi id 14.16.0233.002; Tue, 6 Nov 2012 21:56:32 +0000
From: Stephan Wenger <stewe@stewe.org>
To: Scott O Bradner <sob@sobco.com>, Fred Baker <fred@cisco.com>
Subject: Re: IESG Considering a Revision to NOTE WELL
Thread-Topic: IESG Considering a Revision to NOTE WELL
Thread-Index: AQHNvC+P1gsovbnYEkqDQrp0L72z0Jfc8AEAgAACZoCAAAM9AIAAWlQA//+2/AA=
Date: Tue, 6 Nov 2012 21:56:31 +0000
Message-ID: <FDBFA77C7400C74F87BC297393B53E35259B2F51@BL2PRD0710MB349.namprd07.prod.outlook.com>
In-Reply-To: <8370F371-6CB2-4BDB-BED9-82D9784E429B@sobco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.255.102.4]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <CC93530E08BECC45923FC0ADF8530BC9@namprd07.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: stewe.org
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Nov 2012 21:56:43 -0000

On 11.6.2012 16:17 , "Scott O Bradner" <sob@sobco.com> wrote:

>
>On Nov 6, 2012, at 10:54 AM, Fred Baker (fred) <fred@cisco.com> wrote:
>>=20
>> Not being a lawyer, I can't comment on the legal details of IPR cases.
>>What I am looking at is the understandability of a statement. A lawyer
>>that I was speaking with recently told me that the IETF IPR policy is
>>ambiguous; one must file IPR statements for standards, but not for
>>informational documents. We wound up wandering through the details of
>>legal statements, in which I felt he was working pretty hard to make
>>words stand on their heads.
>
>in case anyone wonders
>
>one might have been able to read that into RFC 2026 but that was very
>carefully fixed
>in the current documents - disclosures are required for ALL contributions

ALL IETF contributions.  NOT all contributions to the RFC editor, and not
all RFCs.  (Which is of a certain relevance given, for example, the VP8
codec definition RFC)

And, only if the IPR in question is yours or your employer's.

Stephan

>
>Scott



From ogud@ogud.com  Tue Nov  6 13:56:55 2012
Return-Path: <ogud@ogud.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 27A0C21F8B9F for <ietf@ietfa.amsl.com>; Tue,  6 Nov 2012 13:56:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.109
X-Spam-Level: 
X-Spam-Status: No, score=-103.109 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_LOW=-1, SUBJECT_FUZZY_TION=0.156, 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 NtJYpYBBQl9j for <ietf@ietfa.amsl.com>; Tue,  6 Nov 2012 13:56:54 -0800 (PST)
Received: from smtp127.dfw.emailsrvr.com (smtp127.dfw.emailsrvr.com [67.192.241.127]) by ietfa.amsl.com (Postfix) with ESMTP id 6FCE621F8B82 for <ietf@ietf.org>; Tue,  6 Nov 2012 13:56:54 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp2.relay.dfw1a.emailsrvr.com (SMTP Server) with ESMTP id 09811780AB; Tue,  6 Nov 2012 16:56:54 -0500 (EST)
X-Virus-Scanned: OK
Received: by smtp2.relay.dfw1a.emailsrvr.com (Authenticated sender: ogud-AT-ogud.com) with ESMTPSA id C3C2178071;  Tue,  6 Nov 2012 16:56:53 -0500 (EST)
Message-ID: <509987A3.8020609@ogud.com>
Date: Tue, 06 Nov 2012 16:56:51 -0500
From: Olafur Gudmundsson <ogud@ogud.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: Olafur Gudmundsson <ogud@ogud.com>
Subject: Re: Recall Petition Submission
References: <50981E59.3090404@ogud.com>
In-Reply-To: <50981E59.3090404@ogud.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ogud@ogud.com, 'IETF-Discussion list' <ietf@ietf.org>, "Lynn St.Amour" <st.amour@isoc.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Nov 2012 21:56:55 -0000

Lynn,

As one of the original signers has been challenged to be NomCom Eligible 
I put forward two more signers
Wes Hardaker wjhns1@hardakers.net Sparta
Joao Luis Silva Damas,  joao@isc.org ISC

	At this time please do not send me any more signatures
as each person that indicates that they support the recall
decreases the pool of candidates to sit on the recall committee.

thanks
	Olafur


On 05/11/2012 15:15, Olafur Gudmundsson wrote:
>
> Lynn St. Amour ISOC president,
>
>    In accordance with the rules in RFC 3777 Section 7, I request that
> you start recall proceedings  against Mr. Marshall Eubanks as member of
> the IAOC as well as IETF Trustee, due to his total disappearance from
> the IAOC and IETF Trust for over 3 months, and either inability or
> refusal to resign.
>
> Evidence to this effect was presented by Bob Hinden [1], as well as
> further evidence that the IETF Trust ousted Mr. Eubanks as  chair of the
> IETF Trust[2] , due to his prolonged absence in that body as well .
>
> I as an IETF member in good standing (having attended over 50 meetings
> since 1987, including 9 of the last 10 meetings), regrettably request
> that you start the recall procedure. Below are listed statements of
> support for this recall petition from  more than 20 other NomCom
> eligible IETF participants.
> The IETF participants below all meet the NomCom criteria as well as the
> diversity of organizations set forth in RFC3777,
> furthermore none is a current member of IETF/IAB/IRTF/IAOC/ISOC board.
>
> Thanks
>
>        Olafur Gudmundsson
>
> [1]
> https://www.ietf.org/ibin/c5i?mid=6&rid=49&gid=0&k1=934&k2=11277&tid=1351092666
>
> [2]
> https://www.ietf.org/ibin/c5i?mid=6&rid=49&gid=0&k1=933&k2=65510&tid=1351272565
>
>
>
>
> Signatories:
> Olafur Gudmundsson ogud@ogud.com  Shinkuro
> Joel Jaeggeli joelja@bogus.com    Zynga inc.
> Mike StJohns mstjohns@ comcast.net   ninethpermutation
> Warren Kumari <warren@kumari.net>  Google
> Margaret Wasserman margaretw42@gmail.com  Painless Security, LLC
>
> Olaf Kolkman olaf@nlnetlabs.nl NlNetLabs
> Melinda Shore melinda.shore@gmail.com No Mountain Software
> Fred Baker fred@cisco.com   Cisco
> Jaap Akkerhuis jaap@NLnetLabs.nl NlNetLabs
> James Polk jmpolk@cisco.com   Cisco
>
> Sam Hartman hartmans-ietf@mit.edu   Painless Security, LLC.
> Andrew Sullivan ajs@anvilwalrusden.com   Dyn Inc.
> Stephen Hanna <shanna@juniper.net>   Jupiter
> Henk Uijterwaal henk.uijerwaal@gmail.com Netherlands Forensics Institute
> Paul Hoffman <paul.hoffman@vpnc.org>    VPNC
>
> John Klensin john-ietf@jck.com  Self
> Mehmet Ersue mehmet.esue@nsn.com  Nokia Siemens Networks
> Tobias Gondrom tobias.gondrom@gondrom.org  Thames Stanley
> Yiu Lee Yiu_Lee@Cable.Comcast.com  Comcast
> Tero Kivinen kivinen@iki.fi  AuthenTec Oy
>
>
>


From paul@cypherpunks.ca  Tue Nov  6 14:18:19 2012
Return-Path: <paul@cypherpunks.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE23F21F85BF for <ietf@ietfa.amsl.com>; Tue,  6 Nov 2012 14:18:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.134
X-Spam-Level: 
X-Spam-Status: No, score=-2.134 tagged_above=-999 required=5 tests=[AWL=0.465,  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 3iO0SYYnSTGK for <ietf@ietfa.amsl.com>; Tue,  6 Nov 2012 14:18:19 -0800 (PST)
Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) by ietfa.amsl.com (Postfix) with ESMTP id 5DC2721F85B0 for <ietf@ietf.org>; Tue,  6 Nov 2012 14:18:19 -0800 (PST)
Received: by bofh.nohats.ca (Postfix, from userid 500) id D507A82B5C; Tue,  6 Nov 2012 17:17:33 -0500 (EST)
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id C98A182B21; Tue,  6 Nov 2012 17:17:33 -0500 (EST)
Date: Tue, 6 Nov 2012 17:17:33 -0500 (EST)
From: Paul Wouters <paul@cypherpunks.ca>
X-X-Sender: paul@bofh.nohats.ca
To: Stephan Wenger <stewe@stewe.org>
Subject: Re: IESG Considering a Revision to NOTE WELL
In-Reply-To: <FDBFA77C7400C74F87BC297393B53E35259B2E90@BL2PRD0710MB349.namprd07.prod.outlook.com>
Message-ID: <alpine.LFD.2.02.1211061715240.29059@bofh.nohats.ca>
References: <FDBFA77C7400C74F87BC297393B53E35259B2E90@BL2PRD0710MB349.namprd07.prod.outlook.com>
User-Agent: Alpine 2.02 (LFD 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Nov 2012 22:18:19 -0000

On Tue, 6 Nov 2012, Stephan Wenger wrote:

> So, to summarize, out of the 60 or so non-third-party disclosures that
> have been made over the last 4+ months, only "a few" may or may not be
> late; the rest almost certainly is not.

Do we have a list of known IPR for which no disclosure was filed
whatsoever (a.k.a. very very very late or possible never filing on
purpose) ? Without that information, I don't think we can judge how
well the Note Well is working currently.

Paul

From brian.e.carpenter@gmail.com  Tue Nov  6 14:20:08 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3BEC221F8BA8 for <ietf@ietfa.amsl.com>; Tue,  6 Nov 2012 14:20:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.583
X-Spam-Level: 
X-Spam-Status: No, score=-103.583 tagged_above=-999 required=5 tests=[AWL=0.016, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, 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 55Q0G8bzcLIj for <ietf@ietfa.amsl.com>; Tue,  6 Nov 2012 14:20:07 -0800 (PST)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id 9A2C121F8BA1 for <ietf@ietf.org>; Tue,  6 Nov 2012 14:20:07 -0800 (PST)
Received: by mail-pb0-f44.google.com with SMTP id ro8so735799pbb.31 for <ietf@ietf.org>; Tue, 06 Nov 2012 14:20:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to :subject:content-type:content-transfer-encoding; bh=CyVca1b3PTyPkcCntZLvpzR7mnP+xr14kEI0Ds/AafI=; b=Hyo4FTn0FBnocgbjKqmVzf4SO7yE0TXI8BlY2Eeg1FIxGjqg8bMfo4h0ESjZ8e7AM0 iQdie+ihOiHyAmwYLGpmUkhQ8mjXxChERTxMGKAc9FX2srJmwhbFKsy+dL0G/LpUl3+X WQq0GZnOPQPxG7Ajpj5Jfgb2Ay2/KPU/2CmJUfOuQOJbd0jttto2x0wtcl5B4M4dfADl Nm2v8x8e17hQ3YGCx6ZdmCPQsGhdWw6RkQxwlkZ/X4fspeezC05EGjIPdY8ahKe8Eg0r khpAHqs2RYoGKv+afZM+/x224v9+PzDsmSznxn3ubHolaZiEUwPgbnpanil3rcyc72qj hj5g==
Received: by 10.68.137.234 with SMTP id ql10mr979874pbb.158.1352240407173; Tue, 06 Nov 2012 14:20:07 -0800 (PST)
Received: from [130.129.66.184] (dhcp-42b8.meeting.ietf.org. [130.129.66.184]) by mx.google.com with ESMTPS id f2sm13080859paz.25.2012.11.06.14.20.05 (version=SSLv3 cipher=OTHER); Tue, 06 Nov 2012 14:20:05 -0800 (PST)
Message-ID: <50998D1A.9010601@gmail.com>
Date: Tue, 06 Nov 2012 22:20:10 +0000
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: IETF discussion list <ietf@ietf.org>
Subject: To the sergeant-at-arms of this list
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Nov 2012 22:20:08 -0000

I'm not quite sure who is the current sergeant-at-arms for the
ietf@ietf.org list, but I request him/her to take immediate
action in response to the highly offensive message just posted,
allegedly by "Carlos Caliente <verywarmcarl@gmail.com>".
It is obnoxious in too many ways to mention.

If intended to be a joke, it's a bad one. If it's intended to be
deeply sarcastic, I don't think that works in an international
community.

Regards
   Brian Carpenter



From stewe@stewe.org  Tue Nov  6 14:22:59 2012
Return-Path: <stewe@stewe.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C9A3921F8BA6 for <ietf@ietfa.amsl.com>; Tue,  6 Nov 2012 14:22:59 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TolDAYPoO5Uw for <ietf@ietfa.amsl.com>; Tue,  6 Nov 2012 14:22:59 -0800 (PST)
Received: from db3outboundpool.messaging.microsoft.com (db3ehsobe004.messaging.microsoft.com [213.199.154.142]) by ietfa.amsl.com (Postfix) with ESMTP id C9C9021F8BA1 for <ietf@ietf.org>; Tue,  6 Nov 2012 14:22:58 -0800 (PST)
Received: from mail16-db3-R.bigfish.com (10.3.81.247) by DB3EHSOBE004.bigfish.com (10.3.84.24) with Microsoft SMTP Server id 14.1.225.23; Tue, 6 Nov 2012 22:22:57 +0000
Received: from mail16-db3 (localhost [127.0.0.1])	by mail16-db3-R.bigfish.com (Postfix) with ESMTP id B855360121; Tue,  6 Nov 2012 22:22:57 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.240.133; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0710HT001.namprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: 1
X-BigFish: PS1(zz98dI1432Izz1de0h1202h1d1ah1d2ah1082kzzz2fh2a8h668h839h944hd25hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh1155h)
Received-SPF: pass (mail16-db3: domain of stewe.org designates 157.56.240.133 as permitted sender) client-ip=157.56.240.133; envelope-from=stewe@stewe.org; helo=BL2PRD0710HT001.namprd07.prod.outlook.com ; .outlook.com ; 
Received: from mail16-db3 (localhost.localdomain [127.0.0.1]) by mail16-db3 (MessageSwitch) id 1352240574875192_5479; Tue,  6 Nov 2012 22:22:54 +0000 (UTC)
Received: from DB3EHSMHS002.bigfish.com (unknown [10.3.81.233])	by mail16-db3.bigfish.com (Postfix) with ESMTP id D3A094001D; Tue,  6 Nov 2012 22:22:54 +0000 (UTC)
Received: from BL2PRD0710HT001.namprd07.prod.outlook.com (157.56.240.133) by DB3EHSMHS002.bigfish.com (10.3.87.102) with Microsoft SMTP Server (TLS) id 14.1.225.23; Tue, 6 Nov 2012 22:22:50 +0000
Received: from BL2PRD0710MB349.namprd07.prod.outlook.com ([169.254.2.192]) by BL2PRD0710HT001.namprd07.prod.outlook.com ([10.255.102.36]) with mapi id 14.16.0233.002; Tue, 6 Nov 2012 22:22:50 +0000
From: Stephan Wenger <stewe@stewe.org>
To: Paul Wouters <paul@cypherpunks.ca>
Subject: Re: IESG Considering a Revision to NOTE WELL
Thread-Topic: IESG Considering a Revision to NOTE WELL
Thread-Index: AQHNvC+P1gsovbnYEkqDQrp0L72z0JfczKkAgABdMAD//9qGAIAAXEqA//+tpAA=
Date: Tue, 6 Nov 2012 22:22:49 +0000
Message-ID: <FDBFA77C7400C74F87BC297393B53E35259B3130@BL2PRD0710MB349.namprd07.prod.outlook.com>
In-Reply-To: <alpine.LFD.2.02.1211061715240.29059@bofh.nohats.ca>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.255.102.4]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <CB72B5D5CBEB284692A3235733E869EF@namprd07.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: stewe.org
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Nov 2012 22:22:59 -0000

On 11.6.2012 17:17 , "Paul Wouters" <paul@cypherpunks.ca> wrote:

>On Tue, 6 Nov 2012, Stephan Wenger wrote:
>
>> So, to summarize, out of the 60 or so non-third-party disclosures that
>> have been made over the last 4+ months, only "a few" may or may not be
>> late; the rest almost certainly is not.
>
>Do we have a list of known IPR for which no disclosure was filed
>whatsoever (a.k.a. very very very late or possible never filing on
>purpose) ? Without that information, I don't think we can judge how
>well the Note Well is working currently.

Obviously, I do not have such information.  Let me return the favor: do
you know how much better a shorter, albeit badly aligned with policy, Note
Well would work?

Stephan

>
>Paul
>



From ynir@checkpoint.com  Tue Nov  6 14:24:49 2012
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8870F21F8B5E for <ietf@ietfa.amsl.com>; Tue,  6 Nov 2012 14:24:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 LRzJSAqiAJ1w for <ietf@ietfa.amsl.com>; Tue,  6 Nov 2012 14:24:48 -0800 (PST)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 8C59A21F88B4 for <ietf@ietf.org>; Tue,  6 Nov 2012 14:24:47 -0800 (PST)
Received: from il-ex01.ad.checkpoint.com (il-ex01.ad.checkpoint.com [194.29.34.26]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id qA6MOi8L031846; Wed, 7 Nov 2012 00:24:44 +0200
X-CheckPoint: {50998B7D-0-1B221DC2-2FFFF}
Received: from il-ex03.ad.checkpoint.com (194.29.34.71) by il-ex01.ad.checkpoint.com (194.29.34.26) with Microsoft SMTP Server (TLS) id 8.3.213.0; Wed, 7 Nov 2012 00:24:43 +0200
Received: from il-ex01.ad.checkpoint.com ([194.29.34.26]) by il-ex03.ad.checkpoint.com ([194.29.34.71]) with mapi; Wed, 7 Nov 2012 00:24:44 +0200
From: Yoav Nir <ynir@checkpoint.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Date: Wed, 7 Nov 2012 00:24:42 +0200
Subject: Re: To the sergeant-at-arms of this list
Thread-Topic: To the sergeant-at-arms of this list
Thread-Index: Ac28bYTlGzHjz6orTYSNiqA9+iRHDQ==
Message-ID: <6599375D-BC6A-485D-8A52-0891A433D099@checkpoint.com>
References: <50998D1A.9010601@gmail.com>
In-Reply-To: <50998D1A.9010601@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-KSE-AntiSpam-Interceptor-Info: protection disabled
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Nov 2012 22:24:49 -0000

AFAIK it's still Jordi. Anyway, I checked the attendee lists for the last 5=
 meetings, and didn't see any Carlos Caliente, although given the gmail add=
ress, it's probably a pseudoname.

On Nov 6, 2012, at 5:20 PM, Brian E Carpenter wrote:

> I'm not quite sure who is the current sergeant-at-arms for the
> ietf@ietf.org list, but I request him/her to take immediate
> action in response to the highly offensive message just posted,
> allegedly by "Carlos Caliente <verywarmcarl@gmail.com>".
> It is obnoxious in too many ways to mention.
>=20
> If intended to be a joke, it's a bad one. If it's intended to be
> deeply sarcastic, I don't think that works in an international
> community.
>=20
> Regards
>   Brian Carpenter


From sob@sobco.com  Tue Nov  6 14:28:11 2012
Return-Path: <sob@sobco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BBBA921F8458 for <ietf@ietfa.amsl.com>; Tue,  6 Nov 2012 14:28:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.163
X-Spam-Level: 
X-Spam-Status: No, score=-0.163 tagged_above=-999 required=5 tests=[AWL=0.332,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  RDNS_NONE=0.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 HCv9i0wWWnfq for <ietf@ietfa.amsl.com>; Tue,  6 Nov 2012 14:28:08 -0800 (PST)
Received: from sobco.sobco.com (unknown [136.248.127.164]) by ietfa.amsl.com (Postfix) with ESMTP id 7CAE621F8BB9 for <ietf@ietf.org>; Tue,  6 Nov 2012 14:27:52 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by sobco.sobco.com (Postfix) with ESMTP id 1BF643671EF; Tue,  6 Nov 2012 17:27:51 -0500 (EST)
X-Virus-Scanned: amavisd-new at sobco.com
Received: from sobco.sobco.com ([127.0.0.1]) by localhost (sobco.sobco.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NbBAYMrMBb70; Tue,  6 Nov 2012 17:27:50 -0500 (EST)
Received: from dhcp3.sobco.com (unknown [136.248.127.173]) by sobco.sobco.com (Postfix) with ESMTPSA id 4153C3671E1; Tue,  6 Nov 2012 17:27:50 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: IESG Considering a Revision to NOTE WELL
From: Scott O Bradner <sob@sobco.com>
In-Reply-To: <FDBFA77C7400C74F87BC297393B53E35259B2F51@BL2PRD0710MB349.namprd07.prod.outlook.com>
Date: Tue, 6 Nov 2012 17:27:43 -0500
Content-Transfer-Encoding: 7bit
Message-Id: <185F011B-8B88-490E-BC88-520343049916@sobco.com>
References: <FDBFA77C7400C74F87BC297393B53E35259B2F51@BL2PRD0710MB349.namprd07.prod.outlook.com>
To: Stephan Wenger <stewe@stewe.org>
X-Mailer: Apple Mail (2.1499)
Cc: IETF list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Nov 2012 22:28:11 -0000

correct - except that the IRTF has adopted the same disclosure requirements

Scott

On Nov 6, 2012, at 4:56 PM, Stephan Wenger <stewe@stewe.org> wrote:

> 
> 
> On 11.6.2012 16:17 , "Scott O Bradner" <sob@sobco.com> wrote:
> 
>> 
>> On Nov 6, 2012, at 10:54 AM, Fred Baker (fred) <fred@cisco.com> wrote:
>>> 
>>> Not being a lawyer, I can't comment on the legal details of IPR cases.
>>> What I am looking at is the understandability of a statement. A lawyer
>>> that I was speaking with recently told me that the IETF IPR policy is
>>> ambiguous; one must file IPR statements for standards, but not for
>>> informational documents. We wound up wandering through the details of
>>> legal statements, in which I felt he was working pretty hard to make
>>> words stand on their heads.
>> 
>> in case anyone wonders
>> 
>> one might have been able to read that into RFC 2026 but that was very
>> carefully fixed
>> in the current documents - disclosures are required for ALL contributions
> 
> ALL IETF contributions.  NOT all contributions to the RFC editor, and not
> all RFCs.  (Which is of a certain relevance given, for example, the VP8
> codec definition RFC)
> 
> And, only if the IPR in question is yours or your employer's.
> 
> Stephan
> 
>> 
>> Scott
> 
> 


From chair@ietf.org  Tue Nov  6 14:50:17 2012
Return-Path: <chair@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ACE5121F8B67 for <ietf@ietfa.amsl.com>; Tue,  6 Nov 2012 14:50:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.521
X-Spam-Level: 
X-Spam-Status: No, score=-102.521 tagged_above=-999 required=5 tests=[AWL=-0.078, BAYES_00=-2.599, SUBJECT_FUZZY_TION=0.156, 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 tHr4ToU9f200 for <ietf@ietfa.amsl.com>; Tue,  6 Nov 2012 14:50:17 -0800 (PST)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:123a::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id 5173B21F8B59 for <ietf@ietf.org>; Tue,  6 Nov 2012 14:50:17 -0800 (PST)
Received: from localhost (c8a.amsl.com [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 49918124423; Tue,  6 Nov 2012 14:50:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5KzyPP_xaN0v; Tue,  6 Nov 2012 14:50:17 -0800 (PST)
Received: from [IPv6:2001:df8::80:6233:4bff:fe20:eb18] (unknown [IPv6:2001:df8:0:80:6233:4bff:fe20:eb18]) by c8a.amsl.com (Postfix) with ESMTPSA id F093A124422; Tue,  6 Nov 2012 14:50:16 -0800 (PST)
Subject: Re: Recall petition for Mr. Marshall Eubanks
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: IETF Chair <chair@ietf.org>
In-Reply-To: <CALA-TkCdB8p=6UoGdX-4aM9=q+s93v_jn0Lb8G8Dy+YW=KRUEQ@mail.gmail.com>
Date: Tue, 6 Nov 2012 17:50:15 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <FED610A0-D824-486E-9FBD-D2CB273305B9@ietf.org>
References: <CALA-TkCdB8p=6UoGdX-4aM9=q+s93v_jn0Lb8G8Dy+YW=KRUEQ@mail.gmail.com>
To: IETF <ietf@ietf.org>
X-Mailer: Apple Mail (2.1085)
Cc: Carlos Caliente <verywarmcarl@gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Nov 2012 22:50:17 -0000

After a very brief consultation with the IESG, I have asked the =
Secretariat to block the verywarmcarl@gmail.com email address from =
further posting to this mail list, and I have asked the Secretariat to =
delete the message from the mail list archive so that searches will not =
bring it up.

On behalf of the IESG,
Russ Housley

From tglassey@earthlink.net  Tue Nov  6 15:27:01 2012
Return-Path: <tglassey@earthlink.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4CDAB21F859A; Tue,  6 Nov 2012 15:27:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.504
X-Spam-Level: 
X-Spam-Status: No, score=-2.504 tagged_above=-999 required=5 tests=[AWL=0.095,  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 k3fNuU433mS7; Tue,  6 Nov 2012 15:27:00 -0800 (PST)
Received: from elasmtp-junco.atl.sa.earthlink.net (elasmtp-junco.atl.sa.earthlink.net [209.86.89.63]) by ietfa.amsl.com (Postfix) with ESMTP id 479AF21F8582; Tue,  6 Nov 2012 15:27:00 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=VlA4IuvOpq1O2ZH1Utoa9yIGaG4+oIsV+TiAh/n9pkYC712X7gLijKmA5ZHEl3gt; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [67.180.133.21] (helo=[192.168.15.2]) by elasmtp-junco.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <tglassey@earthlink.net>) id 1TVsXr-0004D2-Mg; Tue, 06 Nov 2012 18:26:59 -0500
Message-ID: <50999CC7.2000600@earthlink.net>
Date: Tue, 06 Nov 2012 15:27:03 -0800
From: tglassey <tglassey@earthlink.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: ietf@ietf.org, Jorge Contreras <contreraslegal@att.net>,  IETF Chair <chair@ietf.org>
Subject: Re: IESG Considering a Revision to NOTE WELL
References: <FDBFA77C7400C74F87BC297393B53E35259B2E90@BL2PRD0710MB349.namprd07.prod.outlook.com>
In-Reply-To: <FDBFA77C7400C74F87BC297393B53E35259B2E90@BL2PRD0710MB349.namprd07.prod.outlook.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec797c078cc6b6c67fbd128a508764158b49350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 67.180.133.21
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Nov 2012 23:27:01 -0000

On 11/6/2012 1:47 PM, Stephan Wenger wrote:
> Hi Russ,
>
> On 11.6.2012 14:01 , "Russ Housley" <housley@vigilsec.com> wrote:

This isnt complex - if there is a fraud here lets let the FTC deal with 
it.   That is how to keep our hands clean.

So will the Chair ask the IETF Counsel to formally contact the FTC to 
ask them to review this matter.  Then its in the FTC's lap and there is 
no issue for us to worry about.


Todd
>
>> Stephan:
>>
>> Based on the number of late disclosures that are occurring, it is clear
>> to us that we need to use very plain language to explain the
>> responsibilities to participants.
> That's an interesting statement.  To summarize the (long) message below, I
> don't think that empirical data supports that there are any significant
> numbers of disclosures of which it is likely that they are "late".
>
> I went through the recent IPR disclosures (July 2012 until present) to
> check against what documents they have been made.  In tabular form:
> Draft-00: 13
> Draft-01:  8
> Draft-02:  7
> Draft-03:  9
> Draft-04 and later drafts: 14
> Issued RFCs: 4
> 3rd party disclosures: 15
>
> The 3rd party disclosures obviously are irrelevant here, as there is no
> disclosure obligation for third party patent rights per BCP 79, and where
> there is no obligation to disclose there cannot be a late disclosure.
>
> Of the four disclosures made against issued RFCs, only one had a match
> between an inventor's name and the RFC's author list.  That one is pledged
> as RAND-Z.  It's undoubtedly late, but I guess that the rightholder
> attempted to cure that lateness by offering advantageous licensing terms.
> The other disclosures are RAND, but there is no indication that the
> companies making the disclosure were contributing, at least not based on
> matching inventor/author names (or my vague recollection of who said what
> in meeting rooms at the time).   It can well be that the disclosures are
> completely voluntarily, or that the disclosure requirement was triggered
> just recently.  There are many examples on why this may have happened: one
> of the authors joint the company in question just recently (which is the
> case for one of the disclosures), or that the patent changed hands just
> recently (which was the case in one of the Opus-related declarations that
> looked, at the first glance, late, but clearly wasn't.)  I will also note
> that one company that made a disclosure is not an IETF regular, and the
> other has a comparatively small delegation for its size.  In conclusion, I
> don't believe that any of the four cases have been shown to be late
> disclosures, and my personal feeling is that it is highly likely that none
> of them is.
>
> As for the disclosures against older drafts (04+), they may or may not be
> late.  A disclosure could be made against subject matter that has just
> recently been included into a draft that already has some history.  A
> disclosure obligation may have been triggered because a participant from a
> given company, for the first time, decided to comment on the draft.  And
> so on.  Based on the information I have, I could not conclude that there
> is a single late disclosure, although I would consider it likely that
> there are a few.
>
> As for disclosures against drafts 00 through 03, I would argue that most,
> if not all, of these disclosures are probably timely.  A year or so is not
> an unreasonable time frame for a company to make a disclosure, considering
> the amount of paperwork and coordination required to do so.  It's not only
> that a company needs to determine, for itself, whether a disclosure is
> required (draw up a claim chart, have it checked by legal, understand the
> role of the participant, understand the--rather exotic--IETF patent policy
> among the other dozens of policies of bodies the company may be involved
> in), but the company has also to settle on the licensing terms they wish
> to offer (which can involve standards people, legal, and business folks,
> and in many cases requires multi-level approval).  I have run that process
> for one of the larger IETF participating companies in the past, and
> believe me, a year is not unrealistic, even after the
> policy-understanding-and-advocating phase is behind that company.  As our
> policy does NOT specify another timeframe, I don't think that an argument
> to the contrary is bearing as much weight as the procedural argument made
> here.
>
> (Yes, when analyzing the drafts I have been sloppy in not distinguishing
> between WG and individual drafts.  I don't think that would change the
> picture significantly.)
>
> So, to summarize, out of the 60 or so non-third-party disclosures that
> have been made over the last 4+ months, only "a few" may or may not be
> late; the rest almost certainly is not.
>
> Also, I have not seen a trend going towards late disclosures.  Quite
> contrary, I have seen a trend towards early disclosures.
>
> I do not believe that, based on this data, there is a need to change the
> Note Well.  If you folks still think a change is needed, then at least do
> not make a change in such a way that the new Note Well does not correctly
> interpret the policy we have.
>
> The way to fix the "timeliness" of disclosures is to change BCP 79, by
> adding a definition of timeliness, preferably a hard one (six months or
> something like this).
>
> Stephan
>
>
>
>
>
>> Russ
>>
>>
>> On Nov 6, 2012, at 1:27 PM, Stephan Wenger wrote:
>>
>>> Hi,
>>> Russ, can you explain why the IESG considers it necessary to tinker with
>>> the Note Well?
>>> As for the substance, I don't like the text for two reasons that can be
>>> found inline.
>>> Stephan
>>>
>>> On 11.6.2012 10:00 , "IETF Chair" <chair@ietf.org> wrote:
>>>
>>>> The IESG is considering a revision to the NOTE WELL text.  Please
>>>> review
>>>> and comment.
>>>>
>>>> Russ
>>>>
>>>>
>>>>
>>>> === Proposed Revised NOTE WELL Text ===
>>>>
>>>> Note Well
>>>>
>>>> This summary is only meant to point you in the right direction, and
>>>> doesn't have all the nuances. The IETF's IPR Policy is set forth in
>>>> BCP 79; please read it carefully.
>>>>
>>>> The brief summary:
>>>> - By participating with the IETF, you agree to follow IETF processes.
>>>> - If you are aware that a contribution of yours (something you write,
>>>>    say, or discuss in any IETF context) is covered by patents or patent
>>>>    applications, you need to disclose that fact.
>>> 1) I'm not in favor of this formulation because it can be read to
>>> impose a
>>> stronger disclosure obligation on a participant than BCP 79.
>>> Specifically, as Lars has already pointed out and according to BCP 79,
>>> I'm
>>> not "needed" to disclose a patent I'm reasonably and personally aware of
>>> that reads on a document of mine, if that patent is assigned to someone
>>> else but myself and my sponsor/employer, ... For good reasons, BCP 79
>>> does
>>> not require third party disclosures.  I hope that the (few) added words
>>> can be accommodated.
>>> 2) On the other hand, the issue of timeliness is not covered at all (as
>>> others have already pointed out.)
>>>
>>> I'm especially worried of point 1, which can be seen as a policy change
>>> through the back door.  If, based on this hypothetical Note Well, we
>>> would
>>> end up with an IETF disclosure culture in which third party disclosures
>>> would become the norm rather than an exception, we could well end up
>>> with
>>> a brain drain especially from folks not quite as senior in their
>>> respective company hierarchy to have the leeway to ignore company
>>> guidance
>>> about patents.
>>>
>>>
>>>> - You understand that meetings might be recorded, broadcast, and
>>>>   publicly archived.
>>>>
>>>> For further information: Talk to a chair, ask an Area Director, or
>>>> review  BCP 9 (on the Internet Standards Process), BCP 25 (on the
>>>> Working Group processes), BCP 78 (on the IETF Trust), and BCP 79 (on
>>>> Intellectual Property Rights in the IETF).
>>>
>>
>
>


-- 
Regards TSG
"Ex-Cruce-Leo"

//Confidential Mailing - Please destroy this if you are not the intended recipient.


From housley@vigilsec.com  Tue Nov  6 15:30:28 2012
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5145D21F8B9A for <ietf@ietfa.amsl.com>; Tue,  6 Nov 2012 15:30:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.557
X-Spam-Level: 
X-Spam-Status: No, score=-102.557 tagged_above=-999 required=5 tests=[AWL=0.042, 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 M6aQx7V33kBC for <ietf@ietfa.amsl.com>; Tue,  6 Nov 2012 15:30:28 -0800 (PST)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 7B4AE21F8B79 for <ietf@ietf.org>; Tue,  6 Nov 2012 15:30:27 -0800 (PST)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 532879A4003; Tue,  6 Nov 2012 18:30:30 -0500 (EST)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id g5o8gqvFvAoH; Tue,  6 Nov 2012 18:30:22 -0500 (EST)
Received: from dhcp-5421.meeting.ietf.org (dhcp-5421.meeting.ietf.org [130.129.84.33]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 3CFB59A4001; Tue,  6 Nov 2012 18:30:29 -0500 (EST)
Subject: Re: IESG Considering a Revision to NOTE WELL
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <FDBFA77C7400C74F87BC297393B53E35259B2E90@BL2PRD0710MB349.namprd07.prod.outlook.com>
Date: Tue, 6 Nov 2012 18:30:21 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <B0B80E3B-8BF6-4BD0-A166-1E22AD7608DA@vigilsec.com>
References: <FDBFA77C7400C74F87BC297393B53E35259B2E90@BL2PRD0710MB349.namprd07.prod.outlook.com>
To: Stephan Wenger <stewe@stewe.org>
X-Mailer: Apple Mail (2.1085)
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Nov 2012 23:30:28 -0000

Stephan:

>> Based on the number of late disclosures that are occurring, it is =
clear
>> to us that we need to use very plain language to explain the
>> responsibilities to participants.
>=20
> That's an interesting statement.  To summarize the (long) message =
below, I
> don't think that empirical data supports that there are any =
significant
> numbers of disclosures of which it is likely that they are "late".

If the disclosure is made after the document completes WG Last Call, =
then it is late in the IETF standards process.  When the disclosure =
comes after this point in the process, then we need to loop back and =
redo some steps.

Russ



From gtw@gtwassociates.com  Tue Nov  6 15:55:04 2012
Return-Path: <gtw@gtwassociates.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 14ED121F8B99 for <ietf@ietfa.amsl.com>; Tue,  6 Nov 2012 15:55:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.221
X-Spam-Level: *
X-Spam-Status: No, score=1.221 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, HTML_MESSAGE=0.001, RCVD_IN_BL_SPAMCOP_NET=1.96]
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 6vk3eZ883-w8 for <ietf@ietfa.amsl.com>; Tue,  6 Nov 2012 15:55:03 -0800 (PST)
Received: from mail7.primary.net (mail7.primary.net [216.87.38.207]) by ietfa.amsl.com (Postfix) with ESMTP id 7315421F8AB5 for <ietf@ietf.org>; Tue,  6 Nov 2012 15:55:01 -0800 (PST)
Received: from pool-71-191-174-95.washdc.fios.verizon.net ([71.191.174.95]:2641 helo=gtwassociates) by mail7.primary.net with esmtpa (Exim 4.63) (envelope-from <gtw@gtwassociates.com>) id 1TVsyt-0004rG-JV; Tue, 06 Nov 2012 17:54:58 -0600
Message-ID: <3E70ED28A6F640BC9A6AD0C1275FC501@gtwassociates>
From: "George Willingmyre" <gtw@gtwassociates.com>
To: "Russ Housley" <housley@vigilsec.com>, "Stephan Wenger" <stewe@stewe.org>, "IETF" <ietf@ietf.org>
References: <FDBFA77C7400C74F87BC297393B53E35259B2E90@BL2PRD0710MB349.namprd07.prod.outlook.com> <B0B80E3B-8BF6-4BD0-A166-1E22AD7608DA@vigilsec.com>
Subject: Re: IESG Considering a Revision to NOTE WELL
Date: Tue, 6 Nov 2012 18:57:44 -0500
Organization: GTW Associates
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_012D_01CDBC50.9ACE0150"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
x-mimeole: Produced By Microsoft MimeOLE V6.00.2900.6157
X-ACL-Warn: X-The email account used to send this email was: gtw@gtwassociates.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: George Willingmyre <gtw@gtwassociates.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Nov 2012 23:55:04 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_012D_01CDBC50.9ACE0150
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I  do not argue that sooner is not better w/r to IP disclosures, however =
see practical data  at ETSI  described at =
http://papers.ssrn.com/sol3/papers.cfm?abstract_id=3D1912198  Assessing =
IPR Disclosure Within Standard Setting: An ICT Case Study  November 2011 =
 Anne Layne-Farrar=20


Russ, w/r to timing of disclosures is a "late" disclosure defined =
anywhere  in procedures as stated: "If the disclosure is made after the =
document completes WG Last Call, then it is late in the IETF standards =
process"


 clip from study=20

Specifically, I take an empirical look at the timing of patent =
disclosures within the European Telecommunications Standards Institute, =
the body responsible for some of the world's most prevalent mobile =
telephony standards. I find that most members officially disclose their =
potentially relevant patents after the standard was published, and =
sometimes considerably so. On the other hand, I also find that the delay =
in declaring patents to ETSI standards has been shrinking over time, =
with disclosures occurring closer to (although for the most part still =
after) the standard publication date for more recent standard =
generations as compared to earlier ones.



George T. Willingmyre, P.E.
President, GTW Associates
Spencerville, MD USA 20868
301.421.4138
www.gtwassociates.com


----- Original Message -----=20
From: "Russ Housley" <housley@vigilsec.com>
To: "Stephan Wenger" <stewe@stewe.org>
Cc: "IETF" <ietf@ietf.org>
Sent: Tuesday, November 06, 2012 6:30 PM
Subject: Re: IESG Considering a Revision to NOTE WELL


Stephan:

>> Based on the number of late disclosures that are occurring, it is =
clear
>> to us that we need to use very plain language to explain the
>> responsibilities to participants.
>=20
> That's an interesting statement.  To summarize the (long) message =
below, I
> don't think that empirical data supports that there are any =
significant
> numbers of disclosures of which it is likely that they are "late".

If the disclosure is made after the document completes WG Last Call, =
then it is late in the IETF standards process.  When the disclosure =
comes after this point in the process, then we need to loop back and =
redo some steps.

Russ



------=_NextPart_000_012D_01CDBC50.9ACE0150
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META name=3DGENERATOR content=3D"MSHTML 8.00.6001.19328">
<STYLE></STYLE>
</HEAD>
<BODY>
<DIV><FONT size=3D2 face=3DArial>I&nbsp; do not argue that sooner is not =
better w/r=20
to IP disclosures, however see practical data &nbsp;at ETSI&nbsp; =
described at=20
</FONT><A=20
href=3D"http://papers.ssrn.com/sol3/papers.cfm?abstract_id=3D1912198"><FO=
NT size=3D2=20
face=3DArial>http://papers.ssrn.com/sol3/papers.cfm?abstract_id=3D1912198=
</FONT></A>&nbsp;=20
<FONT size=3D2 face=3DArial>Assessing <SPAN =
class=3Dsearchword>IPR</SPAN> Disclosure=20
Within Standard Setting: An ICT Case Study&nbsp; November 2011&nbsp; <A=20
style=3D"FONT-SIZE: 14px; FONT-WEIGHT: bold" class=3Dtextlink=20
title=3D"View other papers by this author"=20
href=3D"http://papers.ssrn.com/sol3/cf_dev/AbsByAuth.cfm?per_id=3D232826"=
=20
target=3D_blank>
<H2=20
style=3D"MARGIN: 0px; DISPLAY: inline; FONT-SIZE: 14px; FONT-WEIGHT: =
bold">Anne=20
Layne-Farrar </H2></A></FONT></DIV>
<DIV><FONT size=3D2 face=3DArial></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2 face=3DArial></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2 face=3DArial>Russ, w/r to timing&nbsp;of disclosures =
is a "late"=20
disclosure defined anywhere &nbsp;in procedures as stated: "If the =
disclosure is=20
made after the document completes WG Last Call, then it is late in the =
IETF=20
standards process"</DIV>
<DIV><BR></DIV></FONT>
<DIV><FONT size=3D2 face=3DArial> clip from study </FONT></DIV>
<DIV><FONT size=3D2 face=3DArial></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2 face=3DArial>Specifically, I take an empirical look =
at the <SPAN=20
class=3Dsearchword>timing</SPAN> <SPAN class=3Dsearchword>of</SPAN> =
patent <SPAN=20
class=3Dsearchword>disclosures</SPAN> within the European =
Telecommunications=20
Standards Institute, the body responsible for some <SPAN=20
class=3Dsearchword>of</SPAN> the world=92s most prevalent mobile =
telephony=20
standards. I find that most members officially disclose their =
potentially=20
relevant patents after the standard was published, and sometimes =
considerably=20
so. On the other hand, I also find that the delay in declaring patents =
<SPAN=20
class=3Dsearchword>to</SPAN> <SPAN class=3Dsearchword>ETSI</SPAN> =
standards has been=20
shrinking over time, with <SPAN class=3Dsearchword>disclosures</SPAN> =
occurring=20
closer <SPAN class=3Dsearchword>to</SPAN> (although for the most part =
still after)=20
the standard publication date for more recent standard generations as =
compared=20
<SPAN class=3Dsearchword>to</SPAN> earlier ones.</FONT></DIV>
<DIV><FONT size=3D2 face=3DArial></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2 face=3DArial></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2 face=3DArial></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2 face=3DArial>George T. Willingmyre, =
P.E.<BR>President, GTW=20
Associates<BR>Spencerville, MD USA 20868<BR>301.421.4138<BR></FONT><A=20
href=3D"http://www.gtwassociates.com"><FONT size=3D2=20
face=3DArial>www.gtwassociates.com</FONT></A></DIV>
<DIV><FONT size=3D2 face=3DArial></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2 face=3DArial></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2 face=3DArial>----- Original Message ----- </FONT>
<DIV><FONT size=3D2 face=3DArial>From: "Russ Housley" &lt;</FONT><A=20
href=3D"mailto:housley@vigilsec.com"><FONT size=3D2=20
face=3DArial>housley@vigilsec.com</FONT></A><FONT size=3D2=20
face=3DArial>&gt;</FONT></DIV>
<DIV><FONT size=3D2 face=3DArial>To: "Stephan Wenger" &lt;</FONT><A=20
href=3D"mailto:stewe@stewe.org"><FONT size=3D2=20
face=3DArial>stewe@stewe.org</FONT></A><FONT size=3D2 =
face=3DArial>&gt;</FONT></DIV>
<DIV><FONT size=3D2 face=3DArial>Cc: "IETF" &lt;</FONT><A=20
href=3D"mailto:ietf@ietf.org"><FONT size=3D2=20
face=3DArial>ietf@ietf.org</FONT></A><FONT size=3D2 =
face=3DArial>&gt;</FONT></DIV>
<DIV><FONT size=3D2 face=3DArial>Sent: Tuesday, November 06, 2012 6:30=20
PM</FONT></DIV>
<DIV><FONT size=3D2 face=3DArial>Subject: Re: IESG Considering a =
Revision to NOTE=20
WELL</FONT></DIV></DIV>
<DIV><FONT face=3DArial><BR><FONT size=3D2></FONT></FONT></DIV><FONT =
size=3D2=20
face=3DArial>Stephan:<BR><BR>&gt;&gt; Based on the number of late =
disclosures that=20
are occurring, it is clear<BR>&gt;&gt; to us that we need to use very =
plain=20
language to explain the<BR>&gt;&gt; responsibilities to =
participants.<BR>&gt;=20
<BR>&gt; That's an interesting statement.&nbsp; To summarize the (long) =
message=20
below, I<BR>&gt; don't think that empirical data supports that there are =
any=20
significant<BR>&gt; numbers of disclosures of which it is likely that =
they are=20
"late".<BR><BR>If the disclosure is made after the document completes WG =
Last=20
Call, then it is late in the IETF standards process.&nbsp; When the =
disclosure=20
comes after this point in the process, then we need to loop back and =
redo some=20
steps.<BR><BR>Russ<BR><BR><BR></FONT></BODY></HTML>

------=_NextPart_000_012D_01CDBC50.9ACE0150--


From tglassey@earthlink.net  Tue Nov  6 15:57:55 2012
Return-Path: <tglassey@earthlink.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 65D2721F8B4C for <ietf@ietfa.amsl.com>; Tue,  6 Nov 2012 15:57:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.214
X-Spam-Level: 
X-Spam-Status: No, score=-2.214 tagged_above=-999 required=5 tests=[AWL=-0.216, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_71=0.6]
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 J27WRHny2bhB for <ietf@ietfa.amsl.com>; Tue,  6 Nov 2012 15:57:52 -0800 (PST)
Received: from elasmtp-kukur.atl.sa.earthlink.net (elasmtp-kukur.atl.sa.earthlink.net [209.86.89.65]) by ietfa.amsl.com (Postfix) with ESMTP id 448FB21F8B99 for <ietf@ietf.org>; Tue,  6 Nov 2012 15:57:52 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=XeEo7Vm+/M8A++zNRNJkUPtJ+kZV2aXh5JqYABfic4A7+1C77eeNK+82Vy6IwN9F; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:X-ELNK-Trace:X-Originating-IP;
Received: from [67.180.133.21] (helo=[192.168.15.2]) by elasmtp-kukur.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <tglassey@earthlink.net>) id 1TVt1h-0003M3-AM for ietf@ietf.org; Tue, 06 Nov 2012 18:57:49 -0500
Message-ID: <5099A400.7000705@earthlink.net>
Date: Tue, 06 Nov 2012 15:57:52 -0800
From: tglassey <tglassey@earthlink.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IESG Considering a Revision to NOTE WELL/ NEA IPR issues...
References: <FDBFA77C7400C74F87BC297393B53E35259B2E90@BL2PRD0710MB349.namprd07.prod.outlook.com>
In-Reply-To: <FDBFA77C7400C74F87BC297393B53E35259B2E90@BL2PRD0710MB349.namprd07.prod.outlook.com>
Content-Type: multipart/alternative; boundary="------------080505000202000306020908"
X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec7924727c13db32e4784a0970ccd2b4423d350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 67.180.133.21
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Nov 2012 23:57:55 -0000

This is a multi-part message in MIME format.
--------------080505000202000306020908
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 11/6/2012 1:47 PM, Stephan Wenger wrote:
> Hi Russ,
>
> On 11.6.2012 14:01 , "Russ Housley" <housley@vigilsec.com> wrote:

*'Sunlight Is the Best Disinfectant'*

Sunlight is the best disinfectant," a well-known quote from U.S. Supreme 
Court Justice Louis Brandeis, refers to the benefits of openness and 
transparency. I invoke this quote often as executive director of the 
NYSSCPA, to illustrate that _*the most credible and respected 
organizations operate in an atmosphere of avowed openness*_. We should 
not only accept criticism and suggestions, we should embrace them. If 
questions from constituents, the public, or the media make leaders or 
other responsible parties obfuscate, the questions are usually valid and 
the answers are not. _/*People who feel uncomfortable under the bright 
light of scrutiny and criticism often have something to hide.
*/_

http://www.nysscpa.org/cpajournal/2003/1203/nv/nv2.htm

Todd

>
>> Stephan:e
>>
>> Based on the number of late disclosures that are occurring, it is clear
>> to us that we need to use very plain language to explain the
>> responsibilities to participants.
> That's an interesting statement.  To summarize the (long) message below, I
> don't think that empirical data supports that there are any significant
> numbers of disclosures of which it is likely that they are "late".
>
> I went through the recent IPR disclosures (July 2012 until present) to
> check against what documents they have been made.  In tabular form:
> Draft-00: 13
> Draft-01:  8
> Draft-02:  7
> Draft-03:  9
> Draft-04 and later drafts: 14
> Issued RFCs: 4
> 3rd party disclosures: 15
>
> The 3rd party disclosures obviously are irrelevant here, as there is no
> disclosure obligation for third party patent rights per BCP 79, and where
> there is no obligation to disclose there cannot be a late disclosure.
>
> Of the four disclosures made against issued RFCs, only one had a match
> between an inventor's name and the RFC's author list.  That one is pledged
> as RAND-Z.  It's undoubtedly late, but I guess that the rightholder
> attempted to cure that lateness by offering advantageous licensing terms.
> The other disclosures are RAND, but there is no indication that the
> companies making the disclosure were contributing, at least not based on
> matching inventor/author names (or my vague recollection of who said what
> in meeting rooms at the time).   It can well be that the disclosures are
> completely voluntarily, or that the disclosure requirement was triggered
> just recently.  There are many examples on why this may have happened: one
> of the authors joint the company in question just recently (which is the
> case for one of the disclosures), or that the patent changed hands just
> recently (which was the case in one of the Opus-related declarations that
> looked, at the first glance, late, but clearly wasn't.)  I will also note
> that one company that made a disclosure is not an IETF regular, and the
> other has a comparatively small delegation for its size.  In conclusion, I
> don't believe that any of the four cases have been shown to be late
> disclosures, and my personal feeling is that it is highly likely that none
> of them is.
>
> As for the disclosures against older drafts (04+), they may or may not be
> late.  A disclosure could be made against subject matter that has just
> recently been included into a draft that already has some history.  A
> disclosure obligation may have been triggered because a participant from a
> given company, for the first time, decided to comment on the draft.  And
> so on.  Based on the information I have, I could not conclude that there
> is a single late disclosure, although I would consider it likely that
> there are a few.
>
> As for disclosures against drafts 00 through 03, I would argue that most,
> if not all, of these disclosures are probably timely.  A year or so is not
> an unreasonable time frame for a company to make a disclosure, considering
> the amount of paperwork and coordination required to do so.  It's not only
> that a company needs to determine, for itself, whether a disclosure is
> required (draw up a claim chart, have it checked by legal, understand the
> role of the participant, understand the--rather exotic--IETF patent policy
> among the other dozens of policies of bodies the company may be involved
> in), but the company has also to settle on the licensing terms they wish
> to offer (which can involve standards people, legal, and business folks,
> and in many cases requires multi-level approval).  I have run that process
> for one of the larger IETF participating companies in the past, and
> believe me, a year is not unrealistic, even after the
> policy-understanding-and-advocating phase is behind that company.  As our
> policy does NOT specify another timeframe, I don't think that an argument
> to the contrary is bearing as much weight as the procedural argument made
> here.
>
> (Yes, when analyzing the drafts I have been sloppy in not distinguishing
> between WG and individual drafts.  I don't think that would change the
> picture significantly.)
>
> So, to summarize, out of the 60 or so non-third-party disclosures that
> have been made over the last 4+ months, only "a few" may or may not be
> late; the rest almost certainly is not.
>
> Also, I have not seen a trend going towards late disclosures.  Quite
> contrary, I have seen a trend towards early disclosures.
>
> I do not believe that, based on this data, there is a need to change the
> Note Well.  If you folks still think a change is needed, then at least do
> not make a change in such a way that the new Note Well does not correctly
> interpret the policy we have.
>
> The way to fix the "timeliness" of disclosures is to change BCP 79, by
> adding a definition of timeliness, preferably a hard one (six months or
> something like this).
>
> Stephan
>
>
>
>
>
>> Russ
>>
>>
>> On Nov 6, 2012, at 1:27 PM, Stephan Wenger wrote:
>>
>>> Hi,
>>> Russ, can you explain why the IESG considers it necessary to tinker with
>>> the Note Well?
>>> As for the substance, I don't like the text for two reasons that can be
>>> found inline.
>>> Stephan
>>>
>>> On 11.6.2012 10:00 , "IETF Chair" <chair@ietf.org> wrote:
>>>
>>>> The IESG is considering a revision to the NOTE WELL text.  Please
>>>> review
>>>> and comment.
>>>>
>>>> Russ
>>>>
>>>>
>>>>
>>>> === Proposed Revised NOTE WELL Text ===
>>>>
>>>> Note Well
>>>>
>>>> This summary is only meant to point you in the right direction, and
>>>> doesn't have all the nuances. The IETF's IPR Policy is set forth in
>>>> BCP 79; please read it carefully.
>>>>
>>>> The brief summary:
>>>> - By participating with the IETF, you agree to follow IETF processes.
>>>> - If you are aware that a contribution of yours (something you write,
>>>>    say, or discuss in any IETF context) is covered by patents or patent
>>>>    applications, you need to disclose that fact.
>>> 1) I'm not in favor of this formulation because it can be read to
>>> impose a
>>> stronger disclosure obligation on a participant than BCP 79.
>>> Specifically, as Lars has already pointed out and according to BCP 79,
>>> I'm
>>> not "needed" to disclose a patent I'm reasonably and personally aware of
>>> that reads on a document of mine, if that patent is assigned to someone
>>> else but myself and my sponsor/employer, ... For good reasons, BCP 79
>>> does
>>> not require third party disclosures.  I hope that the (few) added words
>>> can be accommodated.
>>> 2) On the other hand, the issue of timeliness is not covered at all (as
>>> others have already pointed out.)
>>>
>>> I'm especially worried of point 1, which can be seen as a policy change
>>> through the back door.  If, based on this hypothetical Note Well, we
>>> would
>>> end up with an IETF disclosure culture in which third party disclosures
>>> would become the norm rather than an exception, we could well end up
>>> with
>>> a brain drain especially from folks not quite as senior in their
>>> respective company hierarchy to have the leeway to ignore company
>>> guidance
>>> about patents.
>>>
>>>
>>>> - You understand that meetings might be recorded, broadcast, and
>>>>   publicly archived.
>>>>
>>>> For further information: Talk to a chair, ask an Area Director, or
>>>> review  BCP 9 (on the Internet Standards Process), BCP 25 (on the
>>>> Working Group processes), BCP 78 (on the IETF Trust), and BCP 79 (on
>>>> Intellectual Property Rights in the IETF).
>>>
>>
>
>


-- 
Regards TSG
"Ex-Cruce-Leo"

//Confidential Mailing - Please destroy this if you are not the intended recipient.


--------------080505000202000306020908
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">On 11/6/2012 1:47 PM, Stephan Wenger
      wrote:<br>
    </div>
    <blockquote
cite="mid:FDBFA77C7400C74F87BC297393B53E35259B2E90@BL2PRD0710MB349.namprd07.prod.outlook.com"
      type="cite">
      <pre wrap="">Hi Russ,

On 11.6.2012 14:01 , "Russ Housley" <a class="moz-txt-link-rfc2396E" href="mailto:housley@vigilsec.com">&lt;housley@vigilsec.com&gt;</a> wrote:</pre>
    </blockquote>
    <br>
    <p align="left"><font face="Arial, Helvetica, sans-serif" size="3"><b>&#8216;Sunlight
          Is the Best Disinfectant&#8217;</b></font> </p>
    <p align="left">Sunlight is the best disinfectant,&#8221; a well-known
      quote from U.S. Supreme Court Justice Louis Brandeis, refers to
      the benefits of openness and transparency. I invoke this quote
      often as executive director of the NYSSCPA, to illustrate that <u><b>the
          most credible and respected organizations operate in an
          atmosphere of avowed openness</b></u>. We should not only
      accept criticism and suggestions, we should embrace them. If
      questions from constituents, the public, or the media make leaders
      or other responsible parties obfuscate, the questions are usually
      valid and the answers are not. <u><i><b>People who feel
            uncomfortable under the bright light of scrutiny and
            criticism often have something to hide.<br>
          </b></i></u></p>
    <a class="moz-txt-link-freetext" href="http://www.nysscpa.org/cpajournal/2003/1203/nv/nv2.htm">http://www.nysscpa.org/cpajournal/2003/1203/nv/nv2.htm</a><br>
    <br>
    Todd<br>
    <br>
    <blockquote
cite="mid:FDBFA77C7400C74F87BC297393B53E35259B2E90@BL2PRD0710MB349.namprd07.prod.outlook.com"
      type="cite">
      <pre wrap="">

</pre>
      <blockquote type="cite">
        <pre wrap="">Stephan:e

Based on the number of late disclosures that are occurring, it is clear
to us that we need to use very plain language to explain the
responsibilities to participants.
</pre>
      </blockquote>
      <pre wrap="">
That's an interesting statement.  To summarize the (long) message below, I
don't think that empirical data supports that there are any significant
numbers of disclosures of which it is likely that they are "late".

I went through the recent IPR disclosures (July 2012 until present) to
check against what documents they have been made.  In tabular form:
Draft-00: 13
Draft-01:  8
Draft-02:  7
Draft-03:  9
Draft-04 and later drafts: 14
Issued RFCs: 4
3rd party disclosures: 15

The 3rd party disclosures obviously are irrelevant here, as there is no
disclosure obligation for third party patent rights per BCP 79, and where
there is no obligation to disclose there cannot be a late disclosure.

Of the four disclosures made against issued RFCs, only one had a match
between an inventor's name and the RFC's author list.  That one is pledged
as RAND-Z.  It's undoubtedly late, but I guess that the rightholder
attempted to cure that lateness by offering advantageous licensing terms.
The other disclosures are RAND, but there is no indication that the
companies making the disclosure were contributing, at least not based on
matching inventor/author names (or my vague recollection of who said what
in meeting rooms at the time).   It can well be that the disclosures are
completely voluntarily, or that the disclosure requirement was triggered
just recently.  There are many examples on why this may have happened: one
of the authors joint the company in question just recently (which is the
case for one of the disclosures), or that the patent changed hands just
recently (which was the case in one of the Opus-related declarations that
looked, at the first glance, late, but clearly wasn't.)  I will also note
that one company that made a disclosure is not an IETF regular, and the
other has a comparatively small delegation for its size.  In conclusion, I
don't believe that any of the four cases have been shown to be late
disclosures, and my personal feeling is that it is highly likely that none
of them is.

As for the disclosures against older drafts (04+), they may or may not be
late.  A disclosure could be made against subject matter that has just
recently been included into a draft that already has some history.  A
disclosure obligation may have been triggered because a participant from a
given company, for the first time, decided to comment on the draft.  And
so on.  Based on the information I have, I could not conclude that there
is a single late disclosure, although I would consider it likely that
there are a few.  

As for disclosures against drafts 00 through 03, I would argue that most,
if not all, of these disclosures are probably timely.  A year or so is not
an unreasonable time frame for a company to make a disclosure, considering
the amount of paperwork and coordination required to do so.  It's not only
that a company needs to determine, for itself, whether a disclosure is
required (draw up a claim chart, have it checked by legal, understand the
role of the participant, understand the--rather exotic--IETF patent policy
among the other dozens of policies of bodies the company may be involved
in), but the company has also to settle on the licensing terms they wish
to offer (which can involve standards people, legal, and business folks,
and in many cases requires multi-level approval).  I have run that process
for one of the larger IETF participating companies in the past, and
believe me, a year is not unrealistic, even after the
policy-understanding-and-advocating phase is behind that company.  As our
policy does NOT specify another timeframe, I don't think that an argument
to the contrary is bearing as much weight as the procedural argument made
here. 

(Yes, when analyzing the drafts I have been sloppy in not distinguishing
between WG and individual drafts.  I don't think that would change the
picture significantly.)

So, to summarize, out of the 60 or so non-third-party disclosures that
have been made over the last 4+ months, only "a few" may or may not be
late; the rest almost certainly is not.

Also, I have not seen a trend going towards late disclosures.  Quite
contrary, I have seen a trend towards early disclosures.

I do not believe that, based on this data, there is a need to change the
Note Well.  If you folks still think a change is needed, then at least do
not make a change in such a way that the new Note Well does not correctly
interpret the policy we have.

The way to fix the "timeliness" of disclosures is to change BCP 79, by
adding a definition of timeliness, preferably a hard one (six months or
something like this).

Stephan





</pre>
      <blockquote type="cite">
        <pre wrap="">
Russ


On Nov 6, 2012, at 1:27 PM, Stephan Wenger wrote:

</pre>
        <blockquote type="cite">
          <pre wrap="">Hi,
Russ, can you explain why the IESG considers it necessary to tinker with
the Note Well?
As for the substance, I don't like the text for two reasons that can be
found inline.
Stephan

On 11.6.2012 10:00 , "IETF Chair" <a class="moz-txt-link-rfc2396E" href="mailto:chair@ietf.org">&lt;chair@ietf.org&gt;</a> wrote:

</pre>
          <blockquote type="cite">
            <pre wrap="">The IESG is considering a revision to the NOTE WELL text.  Please
review
and comment.

Russ



=== Proposed Revised NOTE WELL Text ===

Note Well

This summary is only meant to point you in the right direction, and
doesn't have all the nuances. The IETF's IPR Policy is set forth in
BCP 79; please read it carefully.

The brief summary:
- By participating with the IETF, you agree to follow IETF processes.
- If you are aware that a contribution of yours (something you write,
  say, or discuss in any IETF context) is covered by patents or patent
  applications, you need to disclose that fact.
</pre>
          </blockquote>
          <pre wrap="">
1) I'm not in favor of this formulation because it can be read to
impose a
stronger disclosure obligation on a participant than BCP 79.
Specifically, as Lars has already pointed out and according to BCP 79,
I'm
not "needed" to disclose a patent I'm reasonably and personally aware of
that reads on a document of mine, if that patent is assigned to someone
else but myself and my sponsor/employer, ... For good reasons, BCP 79
does
not require third party disclosures.  I hope that the (few) added words
can be accommodated.
2) On the other hand, the issue of timeliness is not covered at all (as
others have already pointed out.)

I'm especially worried of point 1, which can be seen as a policy change
through the back door.  If, based on this hypothetical Note Well, we
would
end up with an IETF disclosure culture in which third party disclosures
would become the norm rather than an exception, we could well end up
with
a brain drain especially from folks not quite as senior in their
respective company hierarchy to have the leeway to ignore company
guidance
about patents. 


</pre>
          <blockquote type="cite">
            <pre wrap="">- You understand that meetings might be recorded, broadcast, and
 publicly archived.

For further information: Talk to a chair, ask an Area Director, or
review  BCP 9 (on the Internet Standards Process), BCP 25 (on the
Working Group processes), BCP 78 (on the IETF Trust), and BCP 79 (on
Intellectual Property Rights in the IETF).
</pre>
          </blockquote>
          <pre wrap="">

</pre>
        </blockquote>
        <pre wrap="">

</pre>
      </blockquote>
      <pre wrap="">


</pre>
    </blockquote>
    <br>
    <br>
    <pre class="moz-signature" cols="72">-- 
Regards TSG
"Ex-Cruce-Leo"

//Confidential Mailing - Please destroy this if you are not the intended recipient. 
</pre>
  </body>
</html>

--------------080505000202000306020908--

From randy@psg.com  Tue Nov  6 16:30:42 2012
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 305AB21F8B62 for <ietf@ietfa.amsl.com>; Tue,  6 Nov 2012 16:30:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.45
X-Spam-Level: 
X-Spam-Status: No, score=-2.45 tagged_above=-999 required=5 tests=[AWL=0.149,  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 jcAffyyIKeY1 for <ietf@ietfa.amsl.com>; Tue,  6 Nov 2012 16:30:41 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id D611721F8B56 for <ietf@ietf.org>; Tue,  6 Nov 2012 16:30:41 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from <randy@psg.com>) id 1TVtXU-0009bD-Sh; Wed, 07 Nov 2012 00:30:41 +0000
Date: Wed, 07 Nov 2012 09:30:39 +0900
Message-ID: <m2r4o6l0eo.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: George Willingmyre <gtw@gtwassociates.com>
Subject: Re: IESG Considering a Revision to NOTE WELL
In-Reply-To: <3E70ED28A6F640BC9A6AD0C1275FC501@gtwassociates>
References: <FDBFA77C7400C74F87BC297393B53E35259B2E90@BL2PRD0710MB349.namprd07.prod.outlook.com> <B0B80E3B-8BF6-4BD0-A166-1E22AD7608DA@vigilsec.com> <3E70ED28A6F640BC9A6AD0C1275FC501@gtwassociates>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Cc: IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Nov 2012 00:30:42 -0000

let's be simple here.  'late' would seem to be any time after there was
a reasonable expectation that you knew there was a document on which
there was ipr.

randy

From gtw@gtwassociates.com  Tue Nov  6 17:14:04 2012
Return-Path: <gtw@gtwassociates.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B45B721F889E for <ietf@ietfa.amsl.com>; Tue,  6 Nov 2012 17:14:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.036
X-Spam-Level: *
X-Spam-Status: No, score=1.036 tagged_above=-999 required=5 tests=[AWL=0.185,  BAYES_05=-1.11, RCVD_IN_BL_SPAMCOP_NET=1.96, STOX_REPLY_TYPE=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 jKBfwcUvXytC for <ietf@ietfa.amsl.com>; Tue,  6 Nov 2012 17:14:04 -0800 (PST)
Received: from mail6.primary.net (mail6.primary.net [216.87.38.204]) by ietfa.amsl.com (Postfix) with ESMTP id F0E9421F888C for <ietf@ietf.org>; Tue,  6 Nov 2012 17:14:03 -0800 (PST)
Received: from pool-71-191-174-95.washdc.fios.verizon.net ([71.191.174.95]:2982 helo=gtwassociates) by mail6.primary.net with esmtpa (Exim 4.63) (envelope-from <gtw@gtwassociates.com>) id 1TVuDR-0001CS-FL; Tue, 06 Nov 2012 19:14:03 -0600
Message-ID: <083ADBA41E7B48958C26113CA1FA9C9D@gtwassociates>
From: "George Willingmyre" <gtw@gtwassociates.com>
To: "Randy Bush" <randy@psg.com>, "IETF Disgust" <ietf@ietf.org>
References: <FDBFA77C7400C74F87BC297393B53E35259B2E90@BL2PRD0710MB349.namprd07.prod.outlook.com><B0B80E3B-8BF6-4BD0-A166-1E22AD7608DA@vigilsec.com><3E70ED28A6F640BC9A6AD0C1275FC501@gtwassociates> <m2r4o6l0eo.wl%randy@psg.com>
Subject: Re: IESG Considering a Revision to NOTE WELL
Date: Tue, 6 Nov 2012 20:15:58 -0500
Organization: GTW Associates
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
x-mimeole: Produced By Microsoft MimeOLE V6.00.2900.6157
X-ACL-Warn: X-The email account used to send this email was: gtw@gtwassociates.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: George Willingmyre <gtw@gtwassociates.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Nov 2012 01:14:04 -0000

It is not so simple.   BTW, this is not legal opinion,  rather experience

The phrase  "reasonable expectation" is fraught with difficulty both about 
whether a contribute knew about IP or did not know or should reasonably have 
known and  whether he/she believed any such IP would be  "reasonably 
expected"  to be essential

But my objective in the question  what might be "late" was whether IETF may 
have defined "late" somewhere and the rationale for a new "note well" 
statement that it was because of  recent "late disclosures"

I caution against discouraging disclosures even it they are  "late"

George T. Willingmyre, P.E.
President, GTW Associates
Spencerville, MD USA 20868
301.421.4138
www.gtwassociates.com

----- Original Message ----- 
From: "Randy Bush" <randy@psg.com>
To: "George Willingmyre" <gtw@gtwassociates.com>
Cc: "IETF Disgust" <ietf@ietf.org>
Sent: Tuesday, November 06, 2012 7:30 PM
Subject: Re: IESG Considering a Revision to NOTE WELL


> let's be simple here.  'late' would seem to be any time after there was
> a reasonable expectation that you knew there was a document on which
> there was ipr.
>
> randy
> 


From randy@psg.com  Tue Nov  6 17:23:39 2012
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC24F21F8B07 for <ietf@ietfa.amsl.com>; Tue,  6 Nov 2012 17:23:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.483
X-Spam-Level: 
X-Spam-Status: No, score=-2.483 tagged_above=-999 required=5 tests=[AWL=0.116,  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 C5D4LbLoFYzJ for <ietf@ietfa.amsl.com>; Tue,  6 Nov 2012 17:23:39 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 5A79721F8AF9 for <ietf@ietf.org>; Tue,  6 Nov 2012 17:23:39 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from <randy@psg.com>) id 1TVuMj-000Gwb-Rn; Wed, 07 Nov 2012 01:23:38 +0000
Date: Wed, 07 Nov 2012 10:23:36 +0900
Message-ID: <m2objakxyf.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: George Willingmyre <gtw@gtwassociates.com>
Subject: Re: IESG Considering a Revision to NOTE WELL
In-Reply-To: <083ADBA41E7B48958C26113CA1FA9C9D@gtwassociates>
References: <FDBFA77C7400C74F87BC297393B53E35259B2E90@BL2PRD0710MB349.namprd07.prod.outlook.com> <B0B80E3B-8BF6-4BD0-A166-1E22AD7608DA@vigilsec.com> <3E70ED28A6F640BC9A6AD0C1275FC501@gtwassociates> <m2r4o6l0eo.wl%randy@psg.com> <083ADBA41E7B48958C26113CA1FA9C9D@gtwassociates>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Cc: IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Nov 2012 01:23:39 -0000

[ my last post on this ]

> But my objective in the question what might be "late" was whether IETF
> may have defined "late" somewhere

we are [supposed to be] professionals of *integrity*.  discussion of how
far the submarine should be allowed to run before it surfaces are the
primrose path.  as professionals of integrity, we should not participate
in submarine exercises.

randy

From brian.e.carpenter@gmail.com  Wed Nov  7 04:09:58 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B73A21F8800 for <ietf@ietfa.amsl.com>; Wed,  7 Nov 2012 04:09:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.585
X-Spam-Level: 
X-Spam-Status: No, score=-103.585 tagged_above=-999 required=5 tests=[AWL=0.014, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, 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 qpb7yWkDvg6n for <ietf@ietfa.amsl.com>; Wed,  7 Nov 2012 04:09:57 -0800 (PST)
Received: from mail-da0-f44.google.com (mail-da0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id AA95E21F87D6 for <ietf@ietf.org>; Wed,  7 Nov 2012 04:09:57 -0800 (PST)
Received: by mail-da0-f44.google.com with SMTP id h15so701302dan.31 for <ietf@ietf.org>; Wed, 07 Nov 2012 04:09:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=ZLcmwTz8/cCn8ZuB3cyoUareAroe+xxW/AauTYGhesQ=; b=NCpPz4vuk9L7pGFmXN0X///5d1d6lqvxzu4o4DjP9ieFRBXK0m5jWmbq9OO/QmW8sr NEORdHZzrxIdgIUFYFreCPMOj9IHue2h6Xqe1fduHja3tKW+Qa/KUnEXhxQGSpGLLvFM 2ntW7wKqchd1baysawAzPYYXzCaYw5L0OFyuYQW8NrssbX3mhwXQvoClJGfG752nO1LQ /sy5SGMKk0Ww7LEROzd8XWzRMxqdH/KAdsG1sDKvPBPwJbsx+hxdHc9ncT+ScxbYcv6c FzR3ehbyPic4+LI/II9WN+BR69ly9ouixWbecJ/DvDIeqFvPe83lecmKhy9e314CBf+d iQ7Q==
Received: by 10.68.234.100 with SMTP id ud4mr12893296pbc.82.1352290197436; Wed, 07 Nov 2012 04:09:57 -0800 (PST)
Received: from [130.129.66.184] (dhcp-42b8.meeting.ietf.org. [130.129.66.184]) by mx.google.com with ESMTPS id se4sm14055335pbb.13.2012.11.07.04.09.54 (version=SSLv3 cipher=OTHER); Wed, 07 Nov 2012 04:09:56 -0800 (PST)
Message-ID: <509A4F98.6050702@gmail.com>
Date: Wed, 07 Nov 2012 12:10:00 +0000
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: IETF discussion list <ietf@ietf.org>
Subject: Re: IESG Considering a Revision to NOTE WELL
References: <FDBFA77C7400C74F87BC297393B53E35259B2E90@BL2PRD0710MB349.namprd07.prod.outlook.com>	<B0B80E3B-8BF6-4BD0-A166-1E22AD7608DA@vigilsec.com>	<3E70ED28A6F640BC9A6AD0C1275FC501@gtwassociates>	<m2r4o6l0eo.wl%randy@psg.com>	<083ADBA41E7B48958C26113CA1FA9C9D@gtwassociates> <m2objakxyf.wl%randy@psg.com>
In-Reply-To: <m2objakxyf.wl%randy@psg.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Nov 2012 12:09:58 -0000

On 07/11/2012 01:23, Randy Bush wrote:
> [ my last post on this ]
> 
>> But my objective in the question what might be "late" was whether IETF
>> may have defined "late" somewhere
> 
> we are [supposed to be] professionals of *integrity*.  discussion of how
> far the submarine should be allowed to run before it surfaces are the
> primrose path.  as professionals of integrity, we should not participate
> in submarine exercises.

+1

My experience is that, when the disclosure is made by a corporate IPR
department on behalf of the actual contributor, there can be at least
a couple of months delay. If a draft is at an early stage in the IETF
process, that isn't usually catastrophic, but it is a bit uncomfortable.

I wonder whether we should encourage an informal warning that an
IPR disclosure is in the pipeline, when such a corporate delay is likely.

On the other hand, there is sometimes the happy outcome that the
corporate IPR people decide that the contribution does not infringe
the essential claims, so no disclosure is needed.

    Brian

From mach.chen@huawei.com  Wed Nov  7 04:25:03 2012
Return-Path: <mach.chen@huawei.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8196021F89D0 for <ietf@ietfa.amsl.com>; Wed,  7 Nov 2012 04:25:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.373
X-Spam-Level: 
X-Spam-Status: No, score=-6.373 tagged_above=-999 required=5 tests=[AWL=0.226,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 Mw-h9gayqq6x for <ietf@ietfa.amsl.com>; Wed,  7 Nov 2012 04:25:02 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id A1FB821F8850 for <ietf@ietf.org>; Wed,  7 Nov 2012 04:25:01 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id ALH65371; Wed, 07 Nov 2012 12:24:59 +0000 (GMT)
Received: from LHREML406-HUB.china.huawei.com (10.201.5.243) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 7 Nov 2012 12:24:09 +0000
Received: from SZXEML433-HUB.china.huawei.com (10.72.61.61) by lhreml406-hub.china.huawei.com (10.201.5.243) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 7 Nov 2012 12:24:17 +0000
Received: from SZXEML511-MBX.china.huawei.com ([169.254.3.192]) by szxeml433-hub.china.huawei.com ([10.72.61.61]) with mapi id 14.01.0323.003; Wed, 7 Nov 2012 20:24:13 +0800
From: Mach Chen <mach.chen@huawei.com>
To: "t.p." <daedulus@btconnect.com>, "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: [mpls] Last Call: <draft-ietf-mpls-ipv6-pw-lsp-ping-03.txt> (LabelSwitched Path (LSP) Ping for IPv6 Pseudowire FECs)	toProposed Standard
Thread-Topic: [mpls] Last Call: <draft-ietf-mpls-ipv6-pw-lsp-ping-03.txt> (LabelSwitched Path (LSP) Ping for IPv6 Pseudowire FECs)	toProposed Standard
Thread-Index: AQHNuSTu23yioUPmEECSQKSrGiYylpfeUkdw
Date: Wed, 7 Nov 2012 12:24:13 +0000
Message-ID: <F73A3CB31E8BE34FA1BBE3C8F0CB2AE22CAE869D@SZXEML511-MBX.china.huawei.com>
References: <20121024213116.29724.2375.idtracker@ietfa.amsl.com>, <028101cdb924$b77260a0$4001a8c0@gateway.2wire.net>
In-Reply-To: <028101cdb924$b77260a0$4001a8c0@gateway.2wire.net>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.47.128.104]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Nov 2012 12:25:03 -0000

Hi Tom,
Many thanks for your comments!
Please see my reply inline with [Mach]

Best regards,
Mach


________________________________________
From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] on behalf of t.p. [daed=
ulus@btconnect.com]
Sent: Saturday, November 03, 2012 2:05
To: ietf@ietf.org
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-ipv6-pw-lsp-ping-03.txt>   =
     (LabelSwitched Path (LSP) Ping for IPv6 Pseudowire FECs)        toProp=
osed Standard

I worry about the allocation of sub-TLVs in this I-D.

It calls for
"The following Sub-TLV changes, which comprise three updates and two
   additions, are made for two TLV Types in the aforementioned sub-
   registry: TLV Type 1 for "Target FEC Stack", and TLV Type 21 for
   "Reply Path"."
and it is the Type 21 that worries me.

[Mach] Since draft-ietf-mpls-return-path-specified-lsp-ping has already def=
ined the rule and policy on how to inhirent the sub-TLVs from type 1 TLV, I=
MHO, here it may be no need to explicitly mention how to registry the sub-T=
LVs for Type 21. So, how about this:
"The following Sub-TLV changes, which comprise three updates and two additi=
ons, are made for TLV Type 1."


IANA has, for Type 21,

Reply Path (TEMPORARY - expires 2012-01-20)
[draft-ietf-mpls-return-path-specified-lsp-ping]

and I am unclear what the rules are about updates to expired, TEMPORARY,
allocations.


[Mach] As Loa pointed out, the current IANA registry for Type 21 TLV is not=
 reflecting the proposal in [draft-ietf-mpls-return-path-specified-lsp-ping=
].=20


I worry too that
[draft-ietf-mpls-return-path-specified-lsp-ping]
while confirming the reservation of Type 21 takes a different tack for
sub-TLVs, namely
"
According to the guidelines defined in [RFC5226], the sub-TLV range
   of Reply Path TLV are partitioned as following:
   0-31743 - Reserved, and MUST NOT be allocated."
so quite what this I-D will do to that I-D worries me.

[Mach] This is intended for the Type 21 TLV to have a common part code rang=
e shared with Type 1 TLV and a TLV specific code range for its own dedicaed=
 sub-TLV. I think we should have an agreement on this solution :-)


Best regards,
Mach

And I worry yet more that other I-Ds, such as
draft-zjns-mpls-lsp-ping-relay-reply-00
are heading down the track with further updates in this area of the MPLS
namespace (except that this particular one seems to have abandoned
sub-TLVs).

Tom Petch

----- Original Message -----
From: "The IESG" <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
Cc: <mpls@ietf.org>
Sent: Wednesday, October 24, 2012 9:31 PM

>
> The IESG has received a request from the Multiprotocol Label Switching
WG
> (mpls) to consider the following document:
> - 'Label Switched Path (LSP) Ping for IPv6 Pseudowire FECs'
>   <draft-ietf-mpls-ipv6-pw-lsp-ping-03.txt> as Proposed Standard
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2012-11-09. Exceptionally, comments may
be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>
> Abstract
>
>    Multi-Protocol Label Switching (MPLS) Label Switched Path (LSP)
Ping
>    and traceroute mechanisms are commonly used to detect and isolate
>    data plane failures in all MPLS LSPs including Pseudowire (PW)
LSPs.
>    The PW LSP Ping and traceroute elements, however, are not specified
>    for IPv6 address usage.
>
>    This document extends the PW LSP Ping and traceroute mechanisms so
>    they can be used with IPv6 PWs, and updates RFC 4379.
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-mpls-ipv6-pw-lsp-ping/
>
> IESG discussion can be tracked via
>
http://datatracker.ietf.org/doc/draft-ietf-mpls-ipv6-pw-lsp-ping/ballot/
>
>
> No IPR declarations have been submitted directly on this I-D.
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
>=

From john-ietf@jck.com  Wed Nov  7 04:30:12 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C10C21F88D0 for <ietf@ietfa.amsl.com>; Wed,  7 Nov 2012 04:30:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.369
X-Spam-Level: 
X-Spam-Status: No, score=-102.369 tagged_above=-999 required=5 tests=[AWL=0.230, 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 Vecf76SqC3o8 for <ietf@ietfa.amsl.com>; Wed,  7 Nov 2012 04:30:11 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id A074F21F89D0 for <ietf@ietf.org>; Wed,  7 Nov 2012 04:30:11 -0800 (PST)
Received: from localhost ([::1]) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1TW4li-0000oO-PJ; Wed, 07 Nov 2012 07:30:07 -0500
Date: Wed, 07 Nov 2012 07:30:05 -0500
From: John C Klensin <john-ietf@jck.com>
To: Randy Bush <randy@psg.com>, George Willingmyre <gtw@gtwassociates.com>
Subject: Re: IESG Considering a Revision to NOTE WELL
Message-ID: <01E0761AB140CA16067240C3@JCK-EEE10>
In-Reply-To: <m2objakxyf.wl%randy@psg.com>
References: <FDBFA77C7400C74F87BC297393B53E35259B2E90@BL2PRD0710MB349.namprd07.prod.outlook.com> <B0B80E3B-8BF6-4BD0-A166-1E22AD7608DA@vigilsec.com> <3E70ED28A6F640BC9A6AD0C1275FC501@gtwassociates> <m2r4o6l0eo.wl%randy@psg.com> <083ADBA41E7B48958C26113CA1FA9C9D@gtwassociates> <m2objakxyf.wl%randy@psg.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Nov 2012 12:30:12 -0000

--On Wednesday, 07 November, 2012 10:23 +0900 Randy Bush
<randy@psg.com> wrote:

> [ my last post on this ]
> 
>> But my objective in the question what might be "late" was
>> whether IETF may have defined "late" somewhere
> 
> we are [supposed to be] professionals of *integrity*.
> discussion of how far the submarine should be allowed to run
> before it surfaces are the primrose path.  as professionals of
> integrity, we should not participate in submarine exercises.

FWIW, I completely agree with this, while noting three things:

(1) If someone decides to try to evade the rules rather than
behaving professionally and with integrity, no amount of
hair-splitting on our part about how the rules are written will
help much.  Probably we would just create more loopholes.  There
are days that it is too bad we can't recall participants for
non-professional behavior, but that would almost certainly cause
more problems than it would be worth (or would never be used,
convincing those who are inclined to misbehave that the
misbehavior is ok as long as no one moves to kick them out).

(2) The NOTE WELL isn't about the rules -- if someone doesn't
like the rules, they need to convince the IESG to reopen the IPR
WG.  It seems to me that George's question is about the rules,
not the NOTE WELL (as are several other comments in the thread).

(3) We know how to fix these problems.  It involves abandoning
the IETF's entire "individual participants" model and replacing
it with an organizational model, including explicit, signed,
agreements when an organization wants to participate and
probably a patent policy that requires specific categories of
terms, not just disclosure.   I hope we don't go there.

Observation on the text: I think that a change to something that
reinforces the view that the NOTE WELL is a strong suggestion
that there are rules, that they impose requirements, and that
people pay attention to them is a move in the right direction.
The text we've used for the last few years has contained enough
details to leave many people with the impression that it is the
rule set and that actually understanding the BCPs is unnecessary
except as an added reference/clarification.   The final
paragraph should, IMO, probably include some variation of the
stock "consult your own legal counsel" statement as well as
advice to talk with various IETF people.

    best,
     john



From dhc@dcrocker.net  Wed Nov  7 04:46:35 2012
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 55BB921F88CF for <ietf@ietfa.amsl.com>; Wed,  7 Nov 2012 04:46:35 -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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id isx9E9U8ctDO for <ietf@ietfa.amsl.com>; Wed,  7 Nov 2012 04:46:34 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 638E021F8878 for <ietf@ietf.org>; Wed,  7 Nov 2012 04:46:34 -0800 (PST)
Received: from [130.129.17.128] (dhcp-1180.meeting.ietf.org [130.129.17.128]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id qA7CkVVf031016 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 7 Nov 2012 04:46:32 -0800
Message-ID: <509A5822.1090808@dcrocker.net>
Date: Wed, 07 Nov 2012 07:46:26 -0500
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: IESG Considering a Revision to NOTE WELL
References: <FDBFA77C7400C74F87BC297393B53E35259B2E90@BL2PRD0710MB349.namprd07.prod.outlook.com>	<B0B80E3B-8BF6-4BD0-A166-1E22AD7608DA@vigilsec.com>	<3E70ED28A6F640BC9A6AD0C1275FC501@gtwassociates>	<m2r4o6l0eo.wl%randy@psg.com>	<083ADBA41E7B48958C26113CA1FA9C9D@gtwassociates> <m2objakxyf.wl%randy@psg.com> <509A4F98.6050702@gmail.com>
In-Reply-To: <509A4F98.6050702@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Wed, 07 Nov 2012 04:46:33 -0800 (PST)
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Nov 2012 12:46:35 -0000

On 11/7/2012 7:10 AM, Brian E Carpenter wrote:
> On 07/11/2012 01:23, Randy Bush wrote:
>> we are [supposed to be] professionals of *integrity*.  discussion of how
>> far the submarine should be allowed to run before it surfaces are the
>> primrose path.  as professionals of integrity, we should not participate
>> in submarine exercises.
...
> I wonder whether we should encourage an informal warning that an
> IPR disclosure is in the pipeline, when such a corporate delay is likely.


With my non-attorney's understanding of IPR protection, an 'informal' 
disclosure to an outside party is still a disclosure.  For the scenario 
being discussed, the delay is specifically to get authorization for 
/any/ disclosure, with the presumption that none is permitted absent 
that authorization.

As for an assumption of integrity, the motivation for the current effort 
is caused by a lack of IPR holders' being forthcoming.

It doesn't matter whether the problem has been due to lack of 
understanding, lack of integrity, or something else:  the reasonable 
goal here is to make sure that this fundamental IETF requirement is more 
clear to more people, sooner.

d/

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From john@jck.com  Wed Nov  7 05:09:14 2012
Return-Path: <john@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E30321F88D1 for <ietf@ietfa.amsl.com>; Wed,  7 Nov 2012 05:09:14 -0800 (PST)
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=-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 3P3jsOTluA-w for <ietf@ietfa.amsl.com>; Wed,  7 Nov 2012 05:09:13 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id C9AC921F85BA for <ietf@ietf.org>; Wed,  7 Nov 2012 05:09:13 -0800 (PST)
Received: from localhost ([::1]) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john@jck.com>) id 1TW5NY-0000t6-GM; Wed, 07 Nov 2012 08:09:12 -0500
Date: Wed, 07 Nov 2012 08:09:10 -0500
From: John C Klensin <john@jck.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, IETF discussion list <ietf@ietf.org>
Subject: Re: IESG Considering a Revision to NOTE WELL
Message-ID: <53AD44246D6F28CCE3C1C148@JCK-EEE10>
In-Reply-To: <509A4F98.6050702@gmail.com>
References: <FDBFA77C7400C74F87BC297393B53E35259B2E90@BL2PRD0710MB349.namprd07.prod.outlook.com> <B0B80E3B-8BF6-4BD0-A166-1E22AD7608DA@vigilsec.com> <3E70ED28A6F640BC9A6AD0C1275FC501@gtwassociates> <m2r4o6l0eo.wl%randy@psg.com> <083ADBA41E7B48958C26113CA1FA9C9D@gtwassociates> <m2objakxyf.wl%randy@psg.com> <509A4F98.6050702@gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Nov 2012 13:09:14 -0000

--On Wednesday, 07 November, 2012 12:10 +0000 Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:

>...
> My experience is that, when the disclosure is made by a
> corporate IPR department on behalf of the actual contributor,
> there can be at least a couple of months delay. If a draft is
> at an early stage in the IETF process, that isn't usually
> catastrophic, but it is a bit uncomfortable.
> 
> I wonder whether we should encourage an informal warning that
> an IPR disclosure is in the pipeline, when such a corporate
> delay is likely.
> 
> On the other hand, there is sometimes the happy outcome that
> the corporate IPR people decide that the contribution does not
> infringe the essential claims, so no disclosure is needed.

I think it would be hard to write rules here for reasons that
include the contrast above (and again note this is about the
rules, not about the NOTE WELL text).   But it would be
perfectly consistent with today's rules for a participant to
post a disclosure that says "I think there may be an issue here,
clarifying corporate statement will follow".  That wouldn't stop
the "timely" clock because it doesn't contain any substantive
information that could be evaluated.  I guess that, if I were
personally responsible for being sure that a timely disclosure
occurred and expected some months of delay, I'd consider such a
note to be a professional thing to do, especially since the BCPs
are (deliberately) vague and open-ended about exactly what a
disclosure has to contain.  

A WG seeing such a placeholder notice would presumably do
absolutely nothing other than remembering to ping the individual
and company if things got close to a critical decisions point
without any real information being available.

I can agree with "encourage", but I don't think any of this
requires extra text or rules.

best,
   john


From stewe@stewe.org  Wed Nov  7 05:33:51 2012
Return-Path: <stewe@stewe.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 29D2A21F88D2 for <ietf@ietfa.amsl.com>; Wed,  7 Nov 2012 05:33:51 -0800 (PST)
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.000,  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 fjA3jCkl1UNO for <ietf@ietfa.amsl.com>; Wed,  7 Nov 2012 05:33:50 -0800 (PST)
Received: from co1outboundpool.messaging.microsoft.com (co1ehsobe006.messaging.microsoft.com [216.32.180.189]) by ietfa.amsl.com (Postfix) with ESMTP id A743821F8825 for <ietf@ietf.org>; Wed,  7 Nov 2012 05:33:49 -0800 (PST)
Received: from mail126-co1-R.bigfish.com (10.243.78.253) by CO1EHSOBE005.bigfish.com (10.243.66.68) with Microsoft SMTP Server id 14.1.225.23; Wed, 7 Nov 2012 13:33:49 +0000
Received: from mail126-co1 (localhost [127.0.0.1])	by mail126-co1-R.bigfish.com (Postfix) with ESMTP id 3E427B4012F; Wed,  7 Nov 2012 13:33:49 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.240.133; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0710HT001.namprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: 4
X-BigFish: PS4(zzbb2dI98dI1432Izz1de0h1202h1d1ah1d2ah1082kzz8275bhz2fh2a8h668h839h944hd25hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh15d0l1155h)
Received-SPF: pass (mail126-co1: domain of stewe.org designates 157.56.240.133 as permitted sender) client-ip=157.56.240.133; envelope-from=stewe@stewe.org; helo=BL2PRD0710HT001.namprd07.prod.outlook.com ; .outlook.com ; 
Received: from mail126-co1 (localhost.localdomain [127.0.0.1]) by mail126-co1 (MessageSwitch) id 1352295226997203_7073; Wed,  7 Nov 2012 13:33:46 +0000 (UTC)
Received: from CO1EHSMHS020.bigfish.com (unknown [10.243.78.251])	by mail126-co1.bigfish.com (Postfix) with ESMTP id F1ABF98001D; Wed,  7 Nov 2012 13:33:46 +0000 (UTC)
Received: from BL2PRD0710HT001.namprd07.prod.outlook.com (157.56.240.133) by CO1EHSMHS020.bigfish.com (10.243.66.30) with Microsoft SMTP Server (TLS) id 14.1.225.23; Wed, 7 Nov 2012 13:33:47 +0000
Received: from BL2PRD0710MB349.namprd07.prod.outlook.com ([169.254.2.192]) by BL2PRD0710HT001.namprd07.prod.outlook.com ([10.255.102.36]) with mapi id 14.16.0233.002; Wed, 7 Nov 2012 13:33:36 +0000
From: Stephan Wenger <stewe@stewe.org>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, IETF discussion list <ietf@ietf.org>
Subject: Re: IESG Considering a Revision to NOTE WELL
Thread-Topic: IESG Considering a Revision to NOTE WELL
Thread-Index: AQHNvIVx1gsovbnYEkqDQrp0L72z0Jfdk/kAgAC0mgD//8OFAA==
Date: Wed, 7 Nov 2012 13:33:35 +0000
Message-ID: <FDBFA77C7400C74F87BC297393B53E35259B423C@BL2PRD0710MB349.namprd07.prod.outlook.com>
In-Reply-To: <509A4F98.6050702@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.255.102.4]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <B2ADD8B4DCA8324BAD06F7ACB10D38A9@namprd07.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: stewe.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Nov 2012 13:33:51 -0000

On 11.7.2012 07:10 , "Brian E Carpenter" <brian.e.carpenter@gmail.com>
wrote:

>On 07/11/2012 01:23, Randy Bush wrote:
>> [ my last post on this ]
>>=20
>>> But my objective in the question what might be "late" was whether IETF
>>> may have defined "late" somewhere
>>=20
>> we are [supposed to be] professionals of *integrity*.  discussion of how
>> far the submarine should be allowed to run before it surfaces are the
>> primrose path.  as professionals of integrity, we should not participate
>> in submarine exercises.
>
>[...]
>On the other hand, there is sometimes the happy outcome that the
>corporate IPR people decide that the contribution does not infringe
>the essential claims, so no disclosure is needed.

In my experience, it happens very often that a corporate IPR department
finds that a disclosure is not needed.  It is, in most cases, not to the
advantage of a rightholder to disclose a patent unless he is undeniably
obligated to do so, with the result that IPR departments typically do
their homework, claim charts and whatnot.  (That also takes time.)  OTOH,
it is, in many cases, to the advantage of a participant to request a
patent to be disclosed, be it because of IETF-integrity, essential patent
bonuses, or other motivations.

Stephan

>
>    Brian
>



From john@jlc.net  Wed Nov  7 06:57:41 2012
Return-Path: <john@jlc.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AAD0721F87EA for <ietf@ietfa.amsl.com>; Wed,  7 Nov 2012 06:57:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 DiKWqcQmK5Dq for <ietf@ietfa.amsl.com>; Wed,  7 Nov 2012 06:57:41 -0800 (PST)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by ietfa.amsl.com (Postfix) with ESMTP id 2202621F858B for <ietf@ietf.org>; Wed,  7 Nov 2012 06:57:41 -0800 (PST)
Received: by mailhost.jlc.net (Postfix, from userid 104) id C347433D15; Wed,  7 Nov 2012 09:57:40 -0500 (EST)
Date: Wed, 7 Nov 2012 09:57:40 -0500
From: John Leslie <john@jlc.net>
To: Stephan Wenger <stewe@stewe.org>
Subject: Re: IESG Considering a Revision to NOTE WELL
Message-ID: <20121107145740.GA78300@verdi>
References: <509A4F98.6050702@gmail.com> <FDBFA77C7400C74F87BC297393B53E35259B423C@BL2PRD0710MB349.namprd07.prod.outlook.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <FDBFA77C7400C74F87BC297393B53E35259B423C@BL2PRD0710MB349.namprd07.prod.outlook.com>
User-Agent: Mutt/1.4.1i
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Nov 2012 14:57:41 -0000

Stephan Wenger <stewe@stewe.org> wrote:
>... 
> It is, in most cases, not to the advantage of a rightholder to disclose
> a patent unless he is undeniably obligated to do so...

   This is a really strange statement, at first blush.

   So I ask Stephan to clarify what he meant to say (before I react to it).

--
John Leslie <john@jlc.net>

From st.amour@isoc.org  Wed Nov  7 06:58:17 2012
Return-Path: <st.amour@isoc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DB7D221F858B for <ietf@ietfa.amsl.com>; Wed,  7 Nov 2012 06:58:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.443
X-Spam-Level: 
X-Spam-Status: No, score=-103.443 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, SUBJECT_FUZZY_TION=0.156, 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 xYZlR3HxjE5R for <ietf@ietfa.amsl.com>; Wed,  7 Nov 2012 06:58:17 -0800 (PST)
Received: from smtp137.iad.emailsrvr.com (smtp137.iad.emailsrvr.com [207.97.245.137]) by ietfa.amsl.com (Postfix) with ESMTP id 01E3621F8554 for <ietf@ietf.org>; Wed,  7 Nov 2012 06:58:17 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp23.relay.iad1a.emailsrvr.com (SMTP Server) with ESMTP id 73D3F349862; Wed,  7 Nov 2012 09:58:16 -0500 (EST)
X-Virus-Scanned: OK
Received: by smtp23.relay.iad1a.emailsrvr.com (Authenticated sender: st.amour-AT-isoc.org) with ESMTPSA id 7D538349FF4;  Wed,  7 Nov 2012 09:58:15 -0500 (EST)
Subject: Re: Recall Petition Submission
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: "Lynn St.Amour" <st.amour@isoc.org>
In-Reply-To: <509987A3.8020609@ogud.com>
Date: Wed, 7 Nov 2012 09:58:12 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <6E2347D3-57B1-4A1A-B32C-170D403465AB@isoc.org>
References: <50981E59.3090404@ogud.com> <509987A3.8020609@ogud.com>
To: Olafur Gudmundsson <ogud@ogud.com>
X-Mailer: Apple Mail (2.1084)
Cc: 'IETF-Discussion list' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Nov 2012 14:58:18 -0000

Olafur,

this is to acknowledge receipt of your petition.

I also inform the IETF community that I will appoint a Recall Committee =
Chair shortly.

Regards,

Lynn St.Amour
Internet Society President & CEO

On Nov 6, 2012, at 4:56 PM, Olafur Gudmundsson wrote:

>=20
> Lynn,
>=20
> As one of the original signers has been challenged to be NomCom =
Eligible I put forward two more signers
> Wes Hardaker wjhns1@hardakers.net Sparta
> Joao Luis Silva Damas,  joao@isc.org ISC
>=20
> 	At this time please do not send me any more signatures
> as each person that indicates that they support the recall
> decreases the pool of candidates to sit on the recall committee.
>=20
> thanks
> 	Olafur
>=20
>=20
> On 05/11/2012 15:15, Olafur Gudmundsson wrote:
>>=20
>> Lynn St. Amour ISOC president,
>>=20
>>   In accordance with the rules in RFC 3777 Section 7, I request that
>> you start recall proceedings  against Mr. Marshall Eubanks as member =
of
>> the IAOC as well as IETF Trustee, due to his total disappearance from
>> the IAOC and IETF Trust for over 3 months, and either inability or
>> refusal to resign.
>>=20
>> Evidence to this effect was presented by Bob Hinden [1], as well as
>> further evidence that the IETF Trust ousted Mr. Eubanks as  chair of =
the
>> IETF Trust[2] , due to his prolonged absence in that body as well .
>>=20
>> I as an IETF member in good standing (having attended over 50 =
meetings
>> since 1987, including 9 of the last 10 meetings), regrettably request
>> that you start the recall procedure. Below are listed statements of
>> support for this recall petition from  more than 20 other NomCom
>> eligible IETF participants.
>> The IETF participants below all meet the NomCom criteria as well as =
the
>> diversity of organizations set forth in RFC3777,
>> furthermore none is a current member of IETF/IAB/IRTF/IAOC/ISOC =
board.
>>=20
>> Thanks
>>=20
>>       Olafur Gudmundsson
>>=20
>> [1]
>> =
https://www.ietf.org/ibin/c5i?mid=3D6&rid=3D49&gid=3D0&k1=3D934&k2=3D11277=
&tid=3D1351092666
>>=20
>> [2]
>> =
https://www.ietf.org/ibin/c5i?mid=3D6&rid=3D49&gid=3D0&k1=3D933&k2=3D65510=
&tid=3D1351272565
>>=20
>>=20
>>=20
>>=20
>> Signatories:
>> Olafur Gudmundsson ogud@ogud.com  Shinkuro
>> Joel Jaeggeli joelja@bogus.com    Zynga inc.
>> Mike StJohns mstjohns@ comcast.net   ninethpermutation
>> Warren Kumari <warren@kumari.net>  Google
>> Margaret Wasserman margaretw42@gmail.com  Painless Security, LLC
>>=20
>> Olaf Kolkman olaf@nlnetlabs.nl NlNetLabs
>> Melinda Shore melinda.shore@gmail.com No Mountain Software
>> Fred Baker fred@cisco.com   Cisco
>> Jaap Akkerhuis jaap@NLnetLabs.nl NlNetLabs
>> James Polk jmpolk@cisco.com   Cisco
>>=20
>> Sam Hartman hartmans-ietf@mit.edu   Painless Security, LLC.
>> Andrew Sullivan ajs@anvilwalrusden.com   Dyn Inc.
>> Stephen Hanna <shanna@juniper.net>   Jupiter
>> Henk Uijterwaal henk.uijerwaal@gmail.com Netherlands Forensics =
Institute
>> Paul Hoffman <paul.hoffman@vpnc.org>    VPNC
>>=20
>> John Klensin john-ietf@jck.com  Self
>> Mehmet Ersue mehmet.esue@nsn.com  Nokia Siemens Networks
>> Tobias Gondrom tobias.gondrom@gondrom.org  Thames Stanley
>> Yiu Lee Yiu_Lee@Cable.Comcast.com  Comcast
>> Tero Kivinen kivinen@iki.fi  AuthenTec Oy
>>=20
>>=20
>>=20
>=20


From stewe@stewe.org  Wed Nov  7 07:59:55 2012
Return-Path: <stewe@stewe.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D84521F8C0A for <ietf@ietfa.amsl.com>; Wed,  7 Nov 2012 07:59:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.099
X-Spam-Level: 
X-Spam-Status: No, score=-5.099 tagged_above=-999 required=5 tests=[AWL=1.500,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 ytJ1pQYLYQh9 for <ietf@ietfa.amsl.com>; Wed,  7 Nov 2012 07:59:54 -0800 (PST)
Received: from tx2outboundpool.messaging.microsoft.com (tx2ehsobe002.messaging.microsoft.com [65.55.88.12]) by ietfa.amsl.com (Postfix) with ESMTP id 503EB21F8B12 for <ietf@ietf.org>; Wed,  7 Nov 2012 07:59:53 -0800 (PST)
Received: from mail21-tx2-R.bigfish.com (10.9.14.244) by TX2EHSOBE003.bigfish.com (10.9.40.23) with Microsoft SMTP Server id 14.1.225.23; Wed, 7 Nov 2012 15:59:53 +0000
Received: from mail21-tx2 (localhost [127.0.0.1])	by mail21-tx2-R.bigfish.com (Postfix) with ESMTP id E09B81E02E4; Wed,  7 Nov 2012 15:59:52 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.240.133; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0710HT001.namprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: 5
X-BigFish: PS5(zz98dI1432Izz1de0h1202h1d1ah1d2ah1082kzz8275ch8275dhz2fh2a8h668h839h944hd25hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh15d0l1155h)
Received-SPF: pass (mail21-tx2: domain of stewe.org designates 157.56.240.133 as permitted sender) client-ip=157.56.240.133; envelope-from=stewe@stewe.org; helo=BL2PRD0710HT001.namprd07.prod.outlook.com ; .outlook.com ; 
Received: from mail21-tx2 (localhost.localdomain [127.0.0.1]) by mail21-tx2 (MessageSwitch) id 1352303989667876_9599; Wed,  7 Nov 2012 15:59:49 +0000 (UTC)
Received: from TX2EHSMHS027.bigfish.com (unknown [10.9.14.235])	by mail21-tx2.bigfish.com (Postfix) with ESMTP id 95FDE180051; Wed,  7 Nov 2012 15:59:49 +0000 (UTC)
Received: from BL2PRD0710HT001.namprd07.prod.outlook.com (157.56.240.133) by TX2EHSMHS027.bigfish.com (10.9.99.127) with Microsoft SMTP Server (TLS) id 14.1.225.23; Wed, 7 Nov 2012 15:59:47 +0000
Received: from BL2PRD0710MB349.namprd07.prod.outlook.com ([169.254.2.192]) by BL2PRD0710HT001.namprd07.prod.outlook.com ([10.255.102.36]) with mapi id 14.16.0233.002; Wed, 7 Nov 2012 15:59:46 +0000
From: Stephan Wenger <stewe@stewe.org>
To: John Leslie <john@jlc.net>
Subject: Re: IESG Considering a Revision to NOTE WELL
Thread-Topic: IESG Considering a Revision to NOTE WELL
Thread-Index: AQHNvIVx1gsovbnYEkqDQrp0L72z0Jfdk/kAgAC0mgD//8OFAIAAa1QA//+9h4A=
Date: Wed, 7 Nov 2012 15:59:46 +0000
Message-ID: <FDBFA77C7400C74F87BC297393B53E35259B45D1@BL2PRD0710MB349.namprd07.prod.outlook.com>
In-Reply-To: <20121107145740.GA78300@verdi>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.255.102.4]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <274AADBD3FF16B439C8D3B34801670D4@namprd07.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: stewe.org
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Nov 2012 15:59:55 -0000

On 11.7.2012 09:57 , "John Leslie" <john@jlc.net> wrote:

>Stephan Wenger <stewe@stewe.org> wrote:
>>...=20
>> It is, in most cases, not to the advantage of a rightholder to disclose
>> a patent unless he is undeniably obligated to do so...
>
>   This is a really strange statement, at first blush.
>
>   So I ask Stephan to clarify what he meant to say (before I react to
>it).

The vast majority of non-third-party patent disclosures are made by the
rightholder's legal, and not only discloses the patent, but also promises
certain licensing terms (most often RAND, RF, or a non-assert promises
that has many similarities with an RF license).  (This is a shortcut of
the official procedure which would require the IETF brass to ask for
licensing terms after an disclosure without terms has been made.)  Having
made such a statement restricts the freedom of business of the rightholder
with respect to these patents.  Restricting the freedom of business is
usually not a useful thing for a business.

Further, the mere knowledge of the existence of a patent claim against a
specification can derail the inclusion of that technique from the draft.
Assuming the technique was proposed not only for the benefit of getting a
patent in, but for other motives (which, I hope, is still the case of the
vast majority of contributions made to the IETF--I'm not so sure in some
other standards bodies :-), having a patent disclosure against it is not
to the advantage of the proponent.

Of course, the legal folks also have to keep in mind that not disclosing a
patent also can have negative consequences if that patent were asserted
against the standard later.   So they check very carefully whether they
are "undeniably required to" make a disclosure, but if they think they
are, they also make such a disclosure.

Gaming the system by over-declaring (to kill a technology through FUD) or
especially under-declaring (in the hopes to get a patented technology in
the standard without agreeing to encumbrances) is known to have happened,
but it's IMO really not that big an issue any more--mostly, because courts
have brought the hammer down on rightholders who tried.

Clearer?

Stephan


>
>--
>John Leslie <john@jlc.net>
>



From lrosen@rosenlaw.com  Wed Nov  7 09:35:51 2012
Return-Path: <lrosen@rosenlaw.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7913021F8BDC for <ietf@ietfa.amsl.com>; Wed,  7 Nov 2012 09:35:51 -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 2OtcVCssgHiC for <ietf@ietfa.amsl.com>; Wed,  7 Nov 2012 09:35:50 -0800 (PST)
Received: from oproxy11-pub.bluehost.com (oproxy11-pub.bluehost.com [173.254.64.10]) by ietfa.amsl.com (Postfix) with SMTP id A8A1121F8BDA for <ietf@ietf.org>; Wed,  7 Nov 2012 09:35:50 -0800 (PST)
Received: (qmail 32632 invoked by uid 0); 7 Nov 2012 17:35:27 -0000
Received: from unknown (HELO box597.bluehost.com) (66.147.242.197) by oproxy11.bluehost.com with SMTP; 7 Nov 2012 17:35:27 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=rosenlaw.com; s=default;  h=Content-Transfer-Encoding:Content-Type:MIME-Version:Message-ID:Date:Subject:In-Reply-To:References:Cc:To:From:Reply-To; bh=8/OpjcEWLeVjCW3k1szEb6T7LQcvgCduc5Ph6/+IflE=;  b=FkOKt+FMDpZM8+E34TzKDIBvTduDzr9RWM4NEt/Wjo7hGXgWkMU8n54L0UCNksOu6rUyx7nQgta2WymDAH7MmFwwh1pmbMjzSfsC5lJJ8oGoG28FYuDp1pNM+Z4DURgX;
Received: from [70.36.224.178] (port=46106 helo=Lawrencei) by box597.bluehost.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.76) (envelope-from <lrosen@rosenlaw.com>) id 1TW9XA-0003eX-FN; Wed, 07 Nov 2012 10:35:24 -0700
From: "Lawrence Rosen" <lrosen@rosenlaw.com>
To: "'IETF'" <ietf@ietf.org>
References: <55D046F8-5DD2-42E8-9B8C-36C612C4B3F8@ietf.org>
In-Reply-To: <55D046F8-5DD2-42E8-9B8C-36C612C4B3F8@ietf.org>
Subject: RE: IESG Considering a Revision to NOTE WELL
Date: Wed, 7 Nov 2012 09:35:27 -0800
Organization: Rosenlaw & Einschlag
Message-ID: <104f01cdbd0e$476278c0$d6276a40$@rosenlaw.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQDY+wvClJPAlqq2E5BFzs8DMdIGLZnIIawA
Content-Language: en-us
X-Identified-User: {1397:box597.bluehost.com:rosenla1:rosenlaw.com} {sentby:smtp auth 70.36.224.178 authed with lrosen@rosenlaw.com}
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: lrosen@rosenlaw.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Nov 2012 17:35:51 -0000

On 11/6 the IETF Chair proposed the following wording: 
 - If you are aware that a contribution of yours (something you write,
    say, or discuss in any IETF context) is covered by patents or patent
    applications, you need to disclose that fact.

I'm surprised that a standards organization would use the phrase "need to"
instead of one of the REQUIRED words typically used in standards. (See
http://tools.ietf.org/html/bcp14)

So how about:
- If you are aware that a contribution of yours (something you write,
    say, or discuss in any IETF context) is covered by patents or patent
    applications, you MUST disclose that fact.

Meanwhile, I am enjoying the discussion about the expected timeliness of
such REQUIRED disclosures. This is indeed a difficult issue with tradeoffs
for IP owners and those who implement IETF standards. In particular, I want
to see how IETF balances Stephan Wenger's accurate statement that
"[r]estricting the freedom of business [by requiring early disclosures] is
usually not a useful thing for a business [that owns IP]" with the corollary
that "late disclosures may restrict the freedom of business of every other
business." But perhaps, as Stephen also suggests, that hasn't proven to be a
real, measurable problem (yet) at IETF?

/Larry

Lawrence Rosen
Rosenlaw & Einschlag, a technology law firm (www.rosenlaw.com)
3001 King Ranch Rd., Ukiah, CA 95482
Office: 707-485-1242


-----Original Message-----
From: IETF Chair [mailto:chair@ietf.org] 
Sent: Tuesday, November 06, 2012 7:01 AM
To: IETF Announce
Cc: IETF
Subject: IESG Considering a Revision to NOTE WELL

The IESG is considering a revision to the NOTE WELL text.  Please review and
comment.

Russ



=== Proposed Revised NOTE WELL Text ===

Note Well

This summary is only meant to point you in the right direction, and doesn't
have all the nuances. The IETF's IPR Policy is set forth in BCP 79; please
read it carefully.

The brief summary:
  - By participating with the IETF, you agree to follow IETF processes.
  - If you are aware that a contribution of yours (something you write,
    say, or discuss in any IETF context) is covered by patents or patent
    applications, you need to disclose that fact.
  - You understand that meetings might be recorded, broadcast, and
   publicly archived.

For further information: Talk to a chair, ask an Area Director, or review
BCP 9 (on the Internet Standards Process), BCP 25 (on the Working Group
processes), BCP 78 (on the IETF Trust), and BCP 79 (on Intellectual Property
Rights in the IETF).


From tglassey@earthlink.net  Wed Nov  7 11:23:40 2012
Return-Path: <tglassey@earthlink.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2532E21F8B3A for <ietf@ietfa.amsl.com>; Wed,  7 Nov 2012 11:23:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.493
X-Spam-Level: 
X-Spam-Status: No, score=-2.493 tagged_above=-999 required=5 tests=[AWL=0.106,  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 HWIeTNaH+cdR for <ietf@ietfa.amsl.com>; Wed,  7 Nov 2012 11:23:39 -0800 (PST)
Received: from elasmtp-spurfowl.atl.sa.earthlink.net (elasmtp-spurfowl.atl.sa.earthlink.net [209.86.89.66]) by ietfa.amsl.com (Postfix) with ESMTP id 5F58321F89E5 for <ietf@ietf.org>; Wed,  7 Nov 2012 11:23:39 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=i4th8+KyWy5qENduMG7ujp/XAPZQUbV7HXwfpOp/0fsLBcak0rFWen+aHbN7p9QR; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [67.180.133.21] (helo=[192.168.15.2]) by elasmtp-spurfowl.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <tglassey@earthlink.net>) id 1TWBDu-0002i2-JL for ietf@ietf.org; Wed, 07 Nov 2012 14:23:38 -0500
Message-ID: <509AB53D.3010302@earthlink.net>
Date: Wed, 07 Nov 2012 11:23:41 -0800
From: tglassey <tglassey@earthlink.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IESG Considering a Revision to NOTE WELL
References: <FDBFA77C7400C74F87BC297393B53E35259B423C@BL2PRD0710MB349.namprd07.prod.outlook.com>
In-Reply-To: <FDBFA77C7400C74F87BC297393B53E35259B423C@BL2PRD0710MB349.namprd07.prod.outlook.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec793746759d386929f3158fc4ae5a4207b6350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 67.180.133.21
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Nov 2012 19:23:40 -0000

On 11/7/2012 5:33 AM, Stephan Wenger wrote:
> On 11.7.2012 07:10 , "Brian E Carpenter" <brian.e.carpenter@gmail.com>
> wrote:
>
>> On 07/11/2012 01:23, Randy Bush wrote:
>>> [ my last post on this ]
>>>
>>>> But my objective in the question what might be "late" was whether IETF
>>>> may have defined "late" somewhere
>>> we are [supposed to be] professionals of *integrity*.  discussion of how
>>> far the submarine should be allowed to run before it surfaces are the
>>> primrose path.  as professionals of integrity, we should not participate
>>> in submarine exercises.
>> [...]
>> On the other hand, there is sometimes the happy outcome that the
>> corporate IPR people decide that the contribution does not infringe
>> the essential claims, so no disclosure is needed.
> In my experience, it happens very often that a corporate IPR department
> finds that a disclosure is not needed.
Agreed - but most of them are predatory and not interested in 
transparency, something that a GSO must have.
>   It is, in most cases, not to the
> advantage of a rightholder to disclose a patent unless he is undeniably
> obligated to do so, with the result that IPR departments typically do
> their homework, claim charts and whatnot.
Unfortunately in an open and transparent forum which has multiple legal 
parties collaborating on jointly owned and licensed IP this is an issue.
> (That also takes time.)  OTOH,
> it is, in many cases, to the advantage of a participant to request a
> patent to be disclosed, be it because of IETF-integrity, essential patent
> bonuses, or other motivations.
Stephan the hiding of IP protections from the community may in fact be a 
criminal act. It clearly constitutes an intentional fraud if the party 
who has knowledge of the IP is also withholding it because its to their 
financial benefit.

This is what needs to be addressed by a revision to 78/79
>
> Stephan
>
>>     Brian
>>
>
>


-- 
Regards TSG
"Ex-Cruce-Leo"

//Confidential Mailing - Please destroy this if you are not the intended recipient.


From daedulus@btconnect.com  Wed Nov  7 13:12:16 2012
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D15C321F8C59 for <ietf@ietfa.amsl.com>; Wed,  7 Nov 2012 13:12:16 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rRcoP+LS5VlW for <ietf@ietfa.amsl.com>; Wed,  7 Nov 2012 13:12:10 -0800 (PST)
Received: from va3outboundpool.messaging.microsoft.com (va3ehsobe003.messaging.microsoft.com [216.32.180.13]) by ietfa.amsl.com (Postfix) with ESMTP id 6F47C21F8C48 for <ietf@ietf.org>; Wed,  7 Nov 2012 13:12:10 -0800 (PST)
Received: from mail33-va3-R.bigfish.com (10.7.14.241) by VA3EHSOBE009.bigfish.com (10.7.40.29) with Microsoft SMTP Server id 14.1.225.23; Wed, 7 Nov 2012 21:12:09 +0000
Received: from mail33-va3 (localhost [127.0.0.1])	by mail33-va3-R.bigfish.com (Postfix) with ESMTP id 0D32E3A00E7; Wed,  7 Nov 2012 21:12:09 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.253.197; KIP:(null); UIP:(null); IPV:NLI; H:DBXPRD0710HT005.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -25
X-BigFish: PS-25(zzbb2dI98dI9371I542M1432Izz1de0h1202h1d1ah1d2ahzz1033IL8275bh8275dhz2dh2a8h5a9h668h839hd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h304l1155h)
Received: from mail33-va3 (localhost.localdomain [127.0.0.1]) by mail33-va3 (MessageSwitch) id 13523227273801_12692; Wed,  7 Nov 2012 21:12:07 +0000 (UTC)
Received: from VA3EHSMHS009.bigfish.com (unknown [10.7.14.253])	by mail33-va3.bigfish.com (Postfix) with ESMTP id E82FB4A00FB; Wed,  7 Nov 2012 21:12:06 +0000 (UTC)
Received: from DBXPRD0710HT005.eurprd07.prod.outlook.com (157.56.253.197) by VA3EHSMHS009.bigfish.com (10.7.99.19) with Microsoft SMTP Server (TLS) id 14.1.225.23; Wed, 7 Nov 2012 21:12:06 +0000
Received: from CH1PRD0710HT002.namprd07.prod.outlook.com (157.56.245.5) by pod51017.outlook.com (10.255.79.168) with Microsoft SMTP Server (TLS) id 14.16.233.3; Wed, 7 Nov 2012 21:12:05 +0000
Message-ID: <00b301cdbd2c$6ec30e20$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: Russ Housley <housley@vigilsec.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <55D046F8-5DD2-42E8-9B8C-36C612C4B3F8@ietf.org><50992BEF.9000803@gmail.com> <C66E7DEF-EEE8-4678-91C1-1FD46854312C@vigilsec.com>
Subject: Re: IESG Considering a Revision to NOTE WELL
Date: Wed, 7 Nov 2012 21:11:09 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [157.56.245.5]
X-OriginatorOrg: btconnect.com
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Nov 2012 21:12:16 -0000

----- Original Message -----
From: "Russ Housley" <housley@vigilsec.com>
To: "Brian E Carpenter" <brian.e.carpenter@gmail.com>
Cc: "IETF" <ietf@ietf.org>
Sent: Tuesday, November 06, 2012 5:43 PM

Brian:

Jorge has reviewed this text.  He says that the current text and this
proposed text are both summaries.  Both say that it is important to read
the BCP to get all of the details.

<tp>
Even so, I am surprised that Jorge is ok with this.  The new text talks
of something which
"is covered by patents or patent applications"
whereas the RFC talks of
'IPR" or "Intellectual Property Rights": means patent, copyright,
      utility model, invention registration, database and data rights
      that may Cover an Implementing Technology, whether such rights
      arise from a registration or renewal thereof, or an application
      therefore, in each case anywhere in the world'
and the two are different.

Quite often now I see a chair calling explicitly for IPR disclosures and
getting a response that the authors know of no patent application, and
while I have no reason to suspect that anyone is trying to game the
system, it can only be a matter of time before someone spots this
loophole and does.  There have been a number of strangely late
declarations of IPR in the past few years, which have attracted comment,
but most of which have never seem to be satisfactorily explained which
makes me think we need to be more rigorous, more formal, more
challenging, in this matter, not watering down our words.

Tom Petch








Russ


On Nov 6, 2012, at 10:25 AM, Brian E Carpenter wrote:

> I don't much like the change in approach. I think it will be too easy
> to brush off; the current approach has enough substance that people
> who brush it off put themselves in a very weak position.
>
> The old text was written with legal advice. What does counsel say
> about the new proposal?
>
> Regards
>   Brian Carpenter
>   Cell phone during IETF85: +1 847 219 0880
>
> On 06/11/2012 15:00, IETF Chair wrote:
>> The IESG is considering a revision to the NOTE WELL text.  Please
review and comment.
>>
>> Russ
>>
>>
>>
>> === Proposed Revised NOTE WELL Text ===
>>
>> Note Well
>>
>> This summary is only meant to point you in the right direction, and
>> doesn't have all the nuances. The IETF's IPR Policy is set forth in
>> BCP 79; please read it carefully.
>>
>> The brief summary:
>>  - By participating with the IETF, you agree to follow IETF
processes.
>>  - If you are aware that a contribution of yours (something you
write,
>>    say, or discuss in any IETF context) is covered by patents or
patent
>>    applications, you need to disclose that fact.
>>  - You understand that meetings might be recorded, broadcast, and
>>   publicly archived.
>>
>> For further information: Talk to a chair, ask an Area Director, or
>> review  BCP 9 (on the Internet Standards Process), BCP 25 (on the
>> Working Group processes), BCP 78 (on the IETF Trust), and BCP 79 (on
>> Intellectual Property Rights in the IETF).




From joelja@gmail.com  Wed Nov  7 12:34:36 2012
Return-Path: <joelja@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AAEB321F8C30 for <ietf@ietfa.amsl.com>; Wed,  7 Nov 2012 12:34:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.524
X-Spam-Level: 
X-Spam-Status: No, score=-3.524 tagged_above=-999 required=5 tests=[AWL=0.075,  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 kCN9UlLFqB6z for <ietf@ietfa.amsl.com>; Wed,  7 Nov 2012 12:34:36 -0800 (PST)
Received: from mail-da0-f44.google.com (mail-da0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id 00CD621F8C1E for <ietf@ietf.org>; Wed,  7 Nov 2012 12:34:35 -0800 (PST)
Received: by mail-da0-f44.google.com with SMTP id h15so884093dan.31 for <ietf@ietf.org>; Wed, 07 Nov 2012 12:34:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=hf9b/cq1TdDyKsjUrlkG9qzFlx4UVe4NE+RCfHufjrA=; b=GEoFlMA0Fi61Ar3zAL4YUmx+LUbyGA4a29/QFllMfMlMR6n/4bG6Z0tEbz4fsjZU7g npIvAaJ7cQNocD0OmJYOufyFJF4xENfZChVG7P0Hd/kp9BE1UlaiJIxQBpF6JTZyZdD3 etajsfKPQA97dJa85V80WTYeBM9J0RgpU5cDbegiBeexYzX6f9IlodzKthXVv2G8tic/ XHk3vGdTN5DBCFue0X4piPnA2cRU3xuIuJhB/ujSRs6qfEGNCXMhGLlReSD5sSEnYjuE YS598r6N1Cz8HI0PSNHKRnXR9gJ4Is7fETbUUzBj5EF13oXNWGdnQucmbwjA3Ne0r1N8 h3pw==
Received: by 10.68.227.162 with SMTP id sb2mr17553549pbc.4.1352320475685; Wed, 07 Nov 2012 12:34:35 -0800 (PST)
Received: from dhcp-6038.meeting.ietf.org (dhcp-6038.meeting.ietf.org. [130.129.96.56]) by mx.google.com with ESMTPS id az8sm14786304pab.24.2012.11.07.12.34.34 (version=SSLv3 cipher=OTHER); Wed, 07 Nov 2012 12:34:35 -0800 (PST)
Message-ID: <509AC5D9.2060607@gmail.com>
Date: Wed, 07 Nov 2012 15:34:33 -0500
From: joel jaeggli <joelja@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: ietf <ietf@ietf.org>
Subject: IETF Plenary streaming. - Is originating out of ballroom C
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Wed, 07 Nov 2012 13:32:58 -0800
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Nov 2012 20:34:36 -0000

Since we apparently failed to link it in the agenda.

http://ietf85streaming.dnsalias.net/ietf/ietf852.m3u

1600-1945 EST IETF Operations, Administration, and Technical Plenary - 
Grand Ballroom C/D

Sorry
Joel


From tglassey@earthlink.net  Wed Nov  7 13:49:00 2012
Return-Path: <tglassey@earthlink.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5BA9921F8C9B for <ietf@ietfa.amsl.com>; Wed,  7 Nov 2012 13:49:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.503
X-Spam-Level: 
X-Spam-Status: No, score=-2.503 tagged_above=-999 required=5 tests=[AWL=0.096,  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 29vxmyGxO++M for <ietf@ietfa.amsl.com>; Wed,  7 Nov 2012 13:48:59 -0800 (PST)
Received: from elasmtp-mealy.atl.sa.earthlink.net (elasmtp-mealy.atl.sa.earthlink.net [209.86.89.69]) by ietfa.amsl.com (Postfix) with ESMTP id A278521F8C80 for <ietf@ietf.org>; Wed,  7 Nov 2012 13:48:59 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=j2BgTmVQS3LEDmJe2YbDYaWHKw+980XPmqnvHmL+uMmynEcetdSe7iUeSlrP2f08; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [67.180.133.21] (helo=[192.168.15.2]) by elasmtp-mealy.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <tglassey@earthlink.net>) id 1TWDUZ-0005fr-0U for ietf@ietf.org; Wed, 07 Nov 2012 16:48:59 -0500
Message-ID: <509AD74D.2090005@earthlink.net>
Date: Wed, 07 Nov 2012 13:49:01 -0800
From: tglassey <tglassey@earthlink.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IESG Considering a Revision to NOTE WELL
References: <55D046F8-5DD2-42E8-9B8C-36C612C4B3F8@ietf.org><50992BEF.9000803@gmail.com> <C66E7DEF-EEE8-4678-91C1-1FD46854312C@vigilsec.com> <00b301cdbd2c$6ec30e20$4001a8c0@gateway.2wire.net>
In-Reply-To: <00b301cdbd2c$6ec30e20$4001a8c0@gateway.2wire.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec79acc92424e6a9e2b3c643a98ce4ba5cec350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 67.180.133.21
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Nov 2012 21:49:00 -0000

On 11/7/2012 1:11 PM, t.p. wrote:
> ----- Original Message -----
> From: "Russ Housley" <housley@vigilsec.com>
> To: "Brian E Carpenter" <brian.e.carpenter@gmail.com>
> Cc: "IETF" <ietf@ietf.org>
> Sent: Tuesday, November 06, 2012 5:43 PM
>
> Brian:
>
> Jorge has reviewed this text.  He says that the current text and this
> proposed text are both summaries.  Both say that it is important to read
> the BCP to get all of the details.
>
> <tp>
> Even so, I am surprised that Jorge is ok with this.  The new text talks
> of something which
> "is covered by patents or patent applications"
> whereas the RFC talks of
> 'IPR" or "Intellectual Property Rights": means patent, copyright,
>        utility model, invention registration, database and data rights
>        that may Cover an Implementing Technology, whether such rights
>        arise from a registration or renewal thereof, or an application
>        therefore, in each case anywhere in the world'
> and the two are different.
>
> Quite often now I see a chair calling explicitly for IPR disclosures and
> getting a response that the authors know of no patent application, and
> while I have no reason to suspect that anyone is trying to game the
> system, it can only be a matter of time before someone spots this
> loophole and does.  There have been a number of strangely late
> declarations of IPR in the past few years, which have attracted comment,
> but most of which have never seem to be satisfactorily explained which
> makes me think we need to be more rigorous, more formal, more
> challenging, in this matter, not watering down our words.
>
> Tom Petch
>
>   
Tom question for you -  apparently the patent affecting the newly 
proposed NEA standard was filed according to Mssr. Farrel in 2004 - so 
what then is reasonable about the disclosure period?

The issue is simple - the process currently has so much wiggle room in 
it that these types of things happen - so lets eliminate the wiggle room 
completely. This would take new get-tough language on patent disclosure 
and the like as to what happens to an IETF effort when a submarine IP 
event occurs as well.

Todd
>   
>
>
>
>
>
> Russ
>
>
> On Nov 6, 2012, at 10:25 AM, Brian E Carpenter wrote:
>
>> I don't much like the change in approach. I think it will be too easy
>> to brush off; the current approach has enough substance that people
>> who brush it off put themselves in a very weak position.
>>
>> The old text was written with legal advice. What does counsel say
>> about the new proposal?
>>
>> Regards
>>    Brian Carpenter
>>    Cell phone during IETF85: +1 847 219 0880
>>
>> On 06/11/2012 15:00, IETF Chair wrote:
>>> The IESG is considering a revision to the NOTE WELL text.  Please
> review and comment.
>>> Russ
>>>
>>>
>>>
>>> === Proposed Revised NOTE WELL Text ===
>>>
>>> Note Well
>>>
>>> This summary is only meant to point you in the right direction, and
>>> doesn't have all the nuances. The IETF's IPR Policy is set forth in
>>> BCP 79; please read it carefully.
>>>
>>> The brief summary:
>>>   - By participating with the IETF, you agree to follow IETF
> processes.
>>>   - If you are aware that a contribution of yours (something you
> write,
>>>     say, or discuss in any IETF context) is covered by patents or
> patent
>>>     applications, you need to disclose that fact.
>>>   - You understand that meetings might be recorded, broadcast, and
>>>    publicly archived.
>>>
>>> For further information: Talk to a chair, ask an Area Director, or
>>> review  BCP 9 (on the Internet Standards Process), BCP 25 (on the
>>> Working Group processes), BCP 78 (on the IETF Trust), and BCP 79 (on
>>> Intellectual Property Rights in the IETF).
>
>
>


-- 
Regards TSG
"Ex-Cruce-Leo"

//Confidential Mailing - Please destroy this if you are not the intended recipient.


From john@jlc.net  Wed Nov  7 15:19:03 2012
Return-Path: <john@jlc.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A2D1821F8AF9 for <ietf@ietfa.amsl.com>; Wed,  7 Nov 2012 15:19:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 qVkiFwroOwhn for <ietf@ietfa.amsl.com>; Wed,  7 Nov 2012 15:19:03 -0800 (PST)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by ietfa.amsl.com (Postfix) with ESMTP id 72A1C21F8ACA for <ietf@ietf.org>; Wed,  7 Nov 2012 15:19:02 -0800 (PST)
Received: by mailhost.jlc.net (Postfix, from userid 104) id 7B5F633D4D; Wed,  7 Nov 2012 18:19:02 -0500 (EST)
Date: Wed, 7 Nov 2012 18:19:02 -0500
From: John Leslie <john@jlc.net>
To: Stephan Wenger <stewe@stewe.org>
Subject: Re: IESG Considering a Revision to NOTE WELL
Message-ID: <20121107231902.GD78300@verdi>
References: <20121107145740.GA78300@verdi> <FDBFA77C7400C74F87BC297393B53E35259B45D1@BL2PRD0710MB349.namprd07.prod.outlook.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <FDBFA77C7400C74F87BC297393B53E35259B45D1@BL2PRD0710MB349.namprd07.prod.outlook.com>
User-Agent: Mutt/1.4.1i
Cc: John Leslie <john@jlc.net>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Nov 2012 23:19:03 -0000

Stephan Wenger <stewe@stewe.org> wrote:
>...
> 
> Clearer?

   Much clearer. Thank you!

> On 11.7.2012 09:57 , "John Leslie" <john@jlc.net> wrote:
>>Stephan Wenger <stewe@stewe.org> wrote:
>>>... 
>>> It is, in most cases, not to the advantage of a rightholder to disclose
>>> a patent unless he is undeniably obligated to do so...
>>
>> This is a really strange statement, at first blush.
> 
> The vast majority of non-third-party patent disclosures are made by the
> rightholder's legal, and not only discloses the patent, but also promises
> certain licensing terms (most often RAND, RF, or a non-assert promises
> that has many similarities with an RF license).

   Indeed, they mostly do include something about licensing terms --
without these, it would be very difficult to evaluate the impact of
the IPR on deployment. We are always glad to see these.

> (This is a shortcut of the official procedure which would require the
> IETF brass to ask for licensing terms after an disclosure without
> terms has been made.)

   Actually no. There is no "IETF brass" and there is no requirement to
have licensing terms: they merely make things easier (and I do know of
cases where a WGC "suggested" amending an IPR disclosure to include
these).

> Having made such a statement restricts the freedom of business of the
> rightholder with respect to these patents.

   Technically true, certainly...

> Restricting the freedom of business is usually not a useful thing for
> a business.

   Not true. Businesses enter _many_ contracts which restrict their
"freedom" but increase their profitability.

> Further, the mere knowledge of the existence of a patent claim against a
> specification can derail the inclusion of that technique from the draft.

   Good point! In too many cases, the patent system is "damage" that we
feel a need to "route around". :^(

> Assuming the technique was proposed not only for the benefit of getting a
> patent in, but for other motives (which, I hope, is still the case of the
> vast majority of contributions made to the IETF--I'm not so sure in some
> other standards bodies :-), having a patent disclosure against it is not
> to the advantage of the proponent.

   That rather depends upon the _content_ of the disclosure. A disclosure
without even a hint of licensing terms definitely hurts the chances of a
particular technology. But I have seen disclosures which _help_ the chances
of the technology.

> Of course, the legal folks also have to keep in mind that not disclosing a
> patent also can have negative consequences if that patent were asserted
> against the standard later.

   Yes! Fortunately, courts recognize certain patents as "damage" and
help us route around them. ;^)

> So they check very carefully whether they are "undeniably required to"
> make a disclosure, but if they think they are, they also make such a
> disclosure.

   "undeniably required to" is very unfortunate wording. There is no such
thing as a requirement you can't find _some_ lawyer to argue against, for
a price...

   Legal departments _do_ try to balance the risks of losing rights due
to a failure-to-disclose against the risk of losing licensing revenue.
This is _not_ helpful to our process!!!

> Gaming the system by over-declaring (to kill a technology through FUD) or
> especially under-declaring (in the hopes to get a patented technology in
> the standard without agreeing to encumbrances) is known to have happened,
> but it's IMO really not that big an issue any more--mostly, because courts
> have brought the hammer down on rightholders who tried.

   There are many more cases (of both) where courts have not yet "punished"
the over-declaring/under-declaring. :^(

   The "late-declaration" problem, as viewed by the IESG, stems from
declarations received _after_ an IETF-wide LastCall has been issued.
IMHO the individual members are bothered by delays shorter than that,
but don't consider those to be issues for the IESG.

   There (alas!) are cases where the IETF participant doesn't realize
the IPR issue exists until IETF LastCall is issued. But the perceived
"normal" case is one where the IETF participant knows of the IPR before
an I-D is even accepted as a WG draft -- but rather than disclosing
him/herself, asks the legal department of his/her employer to make the
disclosure, and considers that to fully satisfy the obligation.

   IMHO, the IPR-process discussions this week are mainly an attempt
to get across to folks that passing the buck does _not_ satisfy your
obligation: the obligation attaches to the IETF participant, not the
employer; and failure to keep prodding the legal department fails the
"as soon as reasonably possible" test.

--
John Leslie <john@jlc.net>

From sm@resistor.net  Thu Nov  8 06:12:05 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 71D3221F8B3B for <ietf@ietfa.amsl.com>; Thu,  8 Nov 2012 06:12:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.457
X-Spam-Level: 
X-Spam-Status: No, score=-102.457 tagged_above=-999 required=5 tests=[AWL=0.142, 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 yRc1FSJ8SQkM for <ietf@ietfa.amsl.com>; Thu,  8 Nov 2012 06:12:04 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 88A3921F8B7C for <ietf@ietf.org>; Thu,  8 Nov 2012 06:12:04 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id qA8EBxXe012241 for <ietf@ietf.org>; Thu, 8 Nov 2012 06:12:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1352383923; bh=T+Yj/w5NkJTRHj1nmSdTznckmp63obFt5BmQM/i6xDk=; h=Date:To:From:Subject:Cc; b=0K6OhBAqxivkXG5kZ/x0J8+m86dZ8FPzjrauwsL7DS0KEkRw9XVPZUlOblbWT7vJQ qOs73k5tEGZiWT7ktfIL+5V/Jo0TIZLISpivghTKGRkGzl0y+6xhiP0rvcU2Kojsf0 H1t7lqcUKoEPXjPynzkyIOhBuKuzimgVjVWJz+yg=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1352383923; i=@resistor.net; bh=T+Yj/w5NkJTRHj1nmSdTznckmp63obFt5BmQM/i6xDk=; h=Date:To:From:Subject:Cc; b=cpcN73QPTE9s96B+tic/GGZ/Xir5w0K3FQNtvQY5mzICJC+uN4RpaeM4xNSPydIhU SC3sWFWXGtDXaaBOeaA7ziYUBZKFzwy4MZVLlivySmLfLCmvERafpxw9smcQK8F0OI mBT5gOac3EGcEVajOzsYJB5GpUad54f++HwcF8AU=
Message-Id: <6.2.5.6.2.20121108031742.0654a200@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 08 Nov 2012 05:12:16 -0800
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Evolutionizing the IETF
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Nov 2012 14:12:05 -0000

Hello,

I was given the following link at the plenary: 
http://iaoc.ietf.org/documents/IANA-ietf85-nov2012.pdf  and it turned 
out to be a 404.  Could the IAOC please fix the link?

According to the the IAOC report there was one large interim meeting 
where 38 people attended onsite and 23 attended online.  The event 
resulted in a US$ 18,000 loss.  Can someone comment on what WG 
progress was made [1]?

There is a direct contribution of US $2.2 million by the Internet 
Society next year.  Is the plan to rely on Internet Society subsidies 
or to fix the deficit?  One argument made was that the fees have not 
been increased over the last years.  I'll point out that there hasn't 
been significant increase in paid attendance over the years.  Either 
the IETF is only relevant to the usual folks or else the meetings are 
not made relevant enough for (new) people to attend.

I read http://www.rfc-editor.org/rfc/IETFreports/ietf85.pdf  It's the 
usual reporting from the RFC Editor.  I would like to suggest posting 
that report a week before the meeting so that people can read it if 
they have the inclination to do so.  I gather that after the RFCFORM 
side-meeting which started with the usual discussion about what to 
discuss about, the *SE have understood that they should not negotiate 
with terrorists. :-)  It would be refreshing if the *SE could "think 
outside the box" and share their thoughts about the RFC Series with 
the community and comment on how they intend to reach out to the 
audience which do not attend IETF meetings.

The IAB report is the usual fare.  Why can't this be posted one week 
before the meeting?  The report mentions several drafts and the 
number of open issues.  That's not interesting.  How about picking 
one issue, explain the IAB angle and select someone who has provided 
feedback on the draft to comment?

NomCom posted the list of candidates for an area to a public non-IETF 
mailing list.  This is a departure from past practice [2].

Harald Alvestrand mentioned IETF 55 [3].  Some people might find the 
slides interesting.

Regards,
-sm

P.S. The audio quality was bad.

1. http://www.ietf.org/mail-archive/web/ietf/current/msg75244.html
2. http://www.ietf.org/mail-archive/web/ietf-announce/current/msg07929.html
3. http://www.ietf.org/proceedings/55/slides/plenary-2/index.html


From joelja@bogus.com  Thu Nov  8 06:24:41 2012
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 31D2E21F8AD7 for <ietf@ietfa.amsl.com>; Thu,  8 Nov 2012 06:24:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.522
X-Spam-Level: 
X-Spam-Status: No, score=-102.522 tagged_above=-999 required=5 tests=[AWL=0.077, 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 N7b5FxXHlwGb for <ietf@ietfa.amsl.com>; Thu,  8 Nov 2012 06:24:40 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 4D30B21F86AD for <ietf@ietf.org>; Thu,  8 Nov 2012 06:24:40 -0800 (PST)
Received: from dhcp-6038.meeting.ietf.org (dhcp-6038.meeting.ietf.org [130.129.96.56]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id qA8EOce7068888 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Thu, 8 Nov 2012 14:24:39 GMT (envelope-from joelja@bogus.com)
Message-ID: <509BC0A6.4000107@bogus.com>
Date: Thu, 08 Nov 2012 09:24:38 -0500
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: SM <sm@resistor.net>
Subject: Re: Evolutionizing the IETF
References: <6.2.5.6.2.20121108031742.0654a200@elandnews.com>
In-Reply-To: <6.2.5.6.2.20121108031742.0654a200@elandnews.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Thu, 08 Nov 2012 14:24:39 +0000 (UTC)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Nov 2012 14:24:41 -0000

On 11/8/12 8:12 AM, SM wrote:
> Hello,
>
> I was given the following link at the plenary: 
> http://iaoc.ietf.org/documents/IANA-ietf85-nov2012.pdf  and it turned 
> out to be a 404.  Could the IAOC please fix the link?
>
> According to the the IAOC report there was one large interim meeting 
> where 38 people attended onsite and 23 attended online. The event 
> resulted in a US$ 18,000 loss.  Can someone comment on what WG 
> progress was made [1]?
I wrote a draft summarizing my experience of the LIM.

http://tools.ietf.org/html/draft-jaeggli-interim-observations-03

Given an attendance fee of $100, and an expected attendance of ~70-100 
the expenses were essentially cooked into the experiment from the outset 
in my understanding.
> There is a direct contribution of US $2.2 million by the Internet 
> Society next year.  Is the plan to rely on Internet Society subsidies 
> or to fix the deficit?  One argument made was that the fees have not 
> been increased over the last years.  I'll point out that there hasn't 
> been significant increase in paid attendance over the years.  Either 
> the IETF is only relevant to the usual folks or else the meetings are 
> not made relevant enough for (new) people to attend.
>
> I read http://www.rfc-editor.org/rfc/IETFreports/ietf85.pdf  It's the 
> usual reporting from the RFC Editor.  I would like to suggest posting 
> that report a week before the meeting so that people can read it if 
> they have the inclination to do so.  I gather that after the RFCFORM 
> side-meeting which started with the usual discussion about what to 
> discuss about, the *SE have understood that they should not negotiate 
> with terrorists. :-)  It would be refreshing if the *SE could "think 
> outside the box" and share their thoughts about the RFC Series with 
> the community and comment on how they intend to reach out to the 
> audience which do not attend IETF meetings.
>
> The IAB report is the usual fare.  Why can't this be posted one week 
> before the meeting?  The report mentions several drafts and the number 
> of open issues.  That's not interesting.  How about picking one issue, 
> explain the IAB angle and select someone who has provided feedback on 
> the draft to comment?
>
> NomCom posted the list of candidates for an area to a public non-IETF 
> mailing list.  This is a departure from past practice [2].
>
> Harald Alvestrand mentioned IETF 55 [3].  Some people might find the 
> slides interesting.
>
> Regards,
> -sm
>
> P.S. The audio quality was bad.
>
> 1. http://www.ietf.org/mail-archive/web/ietf/current/msg75244.html
> 2. 
> http://www.ietf.org/mail-archive/web/ietf-announce/current/msg07929.html
> 3. http://www.ietf.org/proceedings/55/slides/plenary-2/index.html
>


From brian.e.carpenter@gmail.com  Thu Nov  8 06:41:21 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 23ED321F8AEA for <ietf@ietfa.amsl.com>; Thu,  8 Nov 2012 06:41:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.59
X-Spam-Level: 
X-Spam-Status: No, score=-103.59 tagged_above=-999 required=5 tests=[AWL=0.009, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, 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 dq78vGRqWlaG for <ietf@ietfa.amsl.com>; Thu,  8 Nov 2012 06:41:20 -0800 (PST)
Received: from mail-da0-f44.google.com (mail-da0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id 9267021F8ADD for <ietf@ietf.org>; Thu,  8 Nov 2012 06:41:20 -0800 (PST)
Received: by mail-da0-f44.google.com with SMTP id h15so1295779dan.31 for <ietf@ietf.org>; Thu, 08 Nov 2012 06:41:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=4iT2xUIJWqglDVsPDv3K996tU6pyQAfGAHK9niL1Bmk=; b=WS2U2RoxHGTiMzakRetSW8zihUEvfXPBNsfoBOZGi9A31UUV0lndTQjHlweSmlryAg GRpTIK/bArFoJCCgD4iz718uzxY1AoyZZHoFR8JBbXNJ3p1LqzPRc8JoS5ppfqvss4De wyRjGsL+92i960n7le3KMG0PFShHq7/SS6/1M2QXGGnalhE2yru62FSAOtazq8RPJdhJ +4LU/IAF/8aPGegHflKT1vPDqe/dz3keU/N+NabTkTA9XQaZVRBki3rISHoISPyyRO5O 0FT56EK/S/aTRzdSBddAuQKwCRkzTRNcuA8nMuPMsbBW6/gAa6yPSgNfVFdOSIpGdZZa 05hg==
Received: by 10.69.1.1 with SMTP id bc1mr24576779pbd.102.1352385680322; Thu, 08 Nov 2012 06:41:20 -0800 (PST)
Received: from [130.129.19.51] (dhcp-1333.meeting.ietf.org. [130.129.19.51]) by mx.google.com with ESMTPS id ku7sm14256740pbc.0.2012.11.08.06.41.17 (version=SSLv3 cipher=OTHER); Thu, 08 Nov 2012 06:41:17 -0800 (PST)
Message-ID: <509BC497.7070001@gmail.com>
Date: Thu, 08 Nov 2012 14:41:27 +0000
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: SM <sm@resistor.net>
Subject: Re: Evolutionizing the IETF
References: <6.2.5.6.2.20121108031742.0654a200@elandnews.com>
In-Reply-To: <6.2.5.6.2.20121108031742.0654a200@elandnews.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Nov 2012 14:41:21 -0000

On 08/11/2012 13:12, SM wrote:
...

> There is a direct contribution of US $2.2 million by the Internet
> Society next year.  Is the plan to rely on Internet Society subsidies or
> to fix the deficit?  

I think that calling it a deficit is slightly misleading, since we are
a non-profit organisation. One of the reasons that CNRI gave up control
of the IETF Secretariat was because the IETF needed more income than
can be generated by reasonable meeting fees, to operate the various
services that are not directly related to the meetings. If we had to
cover those expenses out of meeting fees, the latter would have to be
more than doubled. Would you like that?

Personally I am very happy that ISOC sees supporting the IETF and the
RFC Editor as part of its mission, and even more happy that it has the
money to do so. I am also very happy that ICANN takes a similar
attitude to the IETF-IANA function.

   Brian

From adrian@olddog.co.uk  Thu Nov  8 06:53:37 2012
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6072721F880C for <ietf@ietfa.amsl.com>; Thu,  8 Nov 2012 06:53:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.413
X-Spam-Level: 
X-Spam-Status: No, score=-2.413 tagged_above=-999 required=5 tests=[AWL=0.186,  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 T+vRq-JxUf6O for <ietf@ietfa.amsl.com>; Thu,  8 Nov 2012 06:53:36 -0800 (PST)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) by ietfa.amsl.com (Postfix) with ESMTP id 76BD521F8590 for <ietf@ietf.org>; Thu,  8 Nov 2012 06:53:36 -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 qA8ErX5b013282;  Thu, 8 Nov 2012 14:53:34 GMT
Received: from 950129200 (dhcp-4076.meeting.ietf.org [130.129.64.118]) (authenticated bits=0) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id qA8ErVfP013230 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 8 Nov 2012 14:53:33 GMT
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'SM'" <sm@resistor.net>
Subject: Newcomers [Was: Evolutionizing the IETF]
Date: Thu, 8 Nov 2012 14:53:32 -0000
Message-ID: <00f401cdbdc0$d3a1a8d0$7ae4fa70$@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: Ac29wNEadq7E6o7oSCOOOn8+ZNRnaA==
Content-Language: en-gb
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Nov 2012 14:53:37 -0000

Trimming SM's email...

> There is a direct contribution of US $2.2 million by the Internet
> Society next year.  Is the plan to rely on Internet Society subsidies
> or to fix the deficit?  One argument made was that the fees have not
> been increased over the last years.  I'll point out that there hasn't
> been significant increase in paid attendance over the years.  Either
> the IETF is only relevant to the usual folks or else the meetings are
> not made relevant enough for (new) people to attend.

I am repeatedly struck by how many new people *do* attend.

According to Russ's slides [1] 195/1098 are newcomers. And just to labour the
point, a newcomer is not a returnee after 10 years, but someone who has never
attended before.

This number (around 10%) seems consistent over all meetings. So naively, we
should be growing our attendance by around 300 per year.

That we are not reflects our inability to retain, not our inability to attract
(assuming that we are not completely refreshing the IETF attendance every three
or four years). Should not be rocket science to follow up with some newcomers to
find out why they only attend once and never come back.

All other points made by SM may be valid.

Adrian

[1] http://www.ietf.org/proceedings/85/slides/slides-85-iesg-opsandtech-13


From daedulus@btconnect.com  Thu Nov  8 07:05:38 2012
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 32F5B21F8B4C for <ietf@ietfa.amsl.com>; Thu,  8 Nov 2012 07:05:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.099
X-Spam-Level: 
X-Spam-Status: No, score=-5.099 tagged_above=-999 required=5 tests=[AWL=1.500,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 W1nN133r+dC2 for <ietf@ietfa.amsl.com>; Thu,  8 Nov 2012 07:05:37 -0800 (PST)
Received: from tx2outboundpool.messaging.microsoft.com (tx2ehsobe001.messaging.microsoft.com [65.55.88.11]) by ietfa.amsl.com (Postfix) with ESMTP id 2DF6521F8B2F for <ietf@ietf.org>; Thu,  8 Nov 2012 07:05:36 -0800 (PST)
Received: from mail131-tx2-R.bigfish.com (10.9.14.243) by TX2EHSOBE008.bigfish.com (10.9.40.28) with Microsoft SMTP Server id 14.1.225.23; Thu, 8 Nov 2012 15:05:36 +0000
Received: from mail131-tx2 (localhost [127.0.0.1])	by mail131-tx2-R.bigfish.com (Postfix) with ESMTP id 3BE8312036B	for <ietf@ietf.org>; Thu,  8 Nov 2012 15:05:36 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.253.197; KIP:(null); UIP:(null); IPV:NLI; H:DBXPRD0710HT003.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -24
X-BigFish: PS-24(zz9371I119bI542M1432Izz1de0h1202h1d1ah1d2ahzz8275ch1033IL17326ah8275bh8275dhz2dh2a8h5a9h668h839hd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h304l1155h)
Received: from mail131-tx2 (localhost.localdomain [127.0.0.1]) by mail131-tx2 (MessageSwitch) id 135238713483879_4670; Thu,  8 Nov 2012 15:05:34 +0000 (UTC)
Received: from TX2EHSMHS024.bigfish.com (unknown [10.9.14.240])	by mail131-tx2.bigfish.com (Postfix) with ESMTP id 11D35360046; Thu,  8 Nov 2012 15:05:34 +0000 (UTC)
Received: from DBXPRD0710HT003.eurprd07.prod.outlook.com (157.56.253.197) by TX2EHSMHS024.bigfish.com (10.9.99.124) with Microsoft SMTP Server (TLS) id 14.1.225.23; Thu, 8 Nov 2012 15:05:29 +0000
Received: from BL2PRD0610HT001.namprd06.prod.outlook.com (157.56.240.117) by pod51017.outlook.com (10.255.79.166) with Microsoft SMTP Server (TLS) id 14.16.233.3; Thu, 8 Nov 2012 15:05:24 +0000
Message-ID: <000401cdbdc2$5f06d200$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: <afarrel@juniper.net>, <ietf@ietf.org>
References: <20121030154625.13482.31090.idtracker@ietfa.amsl.com> <005801cdb813$894c97c0$4001a8c0@gateway.2wire.net> <00bb01cdbab3$f104fa40$d30eeec0$@juniper.net>
Subject: Re: WG Action: Rechartered Bidirectional Forwarding Detection (bfd)
Date: Thu, 8 Nov 2012 14:55:37 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [157.56.240.117]
X-FOPE-CRA-Verdict: 157.56.253.197$juniper.net%12218%4%btconnect.com%False%False%0$
X-OriginatorOrg: btconnect.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Nov 2012 15:05:38 -0000

----- Original Message -----
From: "Adrian Farrel" <afarrel@juniper.net>
To: "'t.p.'" <daedulus@btconnect.com>; <ietf@ietf.org>
Sent: Sunday, November 04, 2012 5:43 PM
> Hello Tom.
>
> Charter text is distinct from milestones.
> The charter is discussed by IESG and put out for community review.
> Milestones are set by the chairs in discussion with their AD.
> The process for handling the updates is also different.
>
> The BFD chairs agreed with me that they would update the milestones
once the new
> charter text was posted, so I hope we'll see that "soon".

Understood, but be aware of the impact it has, at least on me.  I was
glad to see that one item, which I expect to engage with, was still in
the Charter and then looked below to see when I might want to set aside
time for it, only to see all those dates in the past, reminiscent of all
those failed project plans that I have seen over the years.  If the
dates are not updated, then I would think it a better process to send
out just the updated Charter, without any dates.

Tom Petch

> Cheers,
> Adrian
>
> > -----Original Message-----
> > From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf
Of t.p.
> > Sent: 01 November 2012 09:28
> > To: ietf@ietf.org
> > Subject: Re: WG Action: Rechartered Bidirectional Forwarding
Detection (bfd)
> >
> > I realise that the timekeeping of the IETF is not on a par with its
> > engineering, but it seems a shame to promulgate a new charter for
which
> > every milestone is already several months in arrears.
> >
> > Tom Petch
> >
> >
> > ----- Original Message -----
> > From: "The IESG" <iesg-secretary@ietf.org>
> > To: "IETF-Announce" <ietf-announce@ietf.org>
> > Cc: "bfd WG" <rtg-bfd@ietf.org>
> > Sent: Tuesday, October 30, 2012 3:46 PM
> >
> > > The Bidirectional Forwarding Detection (bfd) working group in the
> > Routing
> > > Area of the IETF has been rechartered. For additional information
> > please
> > > contact the Area Directors or the WG Chairs.
> > >
> > > Bidirectional Forwarding Detection (bfd)
> > > ------------------------------------------------
> > > Current Status: Active Working Group
> > >
> > > Chairs:
> > >   David Ward <dward@cisco.com>
> > >   Jeffrey Haas <jhaas@pfrc.org>
> > >
> > > Technical advisors:
> > >   Dave Katz <dkatz@juniper.net>
> > >
> > > Assigned Area Director:
> > >   Adrian Farrel <adrian@olddog.co.uk>
> > >
> > > Mailing list
> > >   Address: rtg-bfd@ietf.org
> > >   To Subscribe: rtg-bfd-request@ietf.org
> > >   Archive: http://www.ietf.org/mail-archive/web/rtg-bfd/
> > >
> > > Charter of Working Group:
> > >
> > > The BFD Working Group is chartered to standardize and support the
> > > bidirectional forwarding detection protocol (BFD) and its
extensions.
> > A
> > > core goal of the working group is to standardize BFD in the
context of
> > IP
> > > routing, or protocols such as MPLS that are based on IP routing,
in a
> > way
> > > that will encourage multiple, inter-operable vendor
implementations.
> > The
> > > Working Group will also provide advice and guidance on BFD to
other
> > > working groups or standards bodies as requested.
> > >
> > > BFD is a protocol intended to detect faults in the bidirectional
path
> > > between two forwarding engines, including physical interfaces,
> > > subinterfaces, data link(s), and to the extent possible the
forwarding
> > > engines themselves, with potentially very low latency. It operates
> > > independently of media, data protocols, and routing protocols. An
> > > additional goal is to provide a single mechanism that can be used
for
> > > liveness detection over any media, at any protocol layer, with
> > > a wide range of detection times and overhead, to avoid a
proliferation
> > > of different methods.
> > >
> > > Important characteristics of BFD include:
> > >
> > > - Simple, fixed-field encoding to facilitate implementations in
> > hardware.
> > >
> > > - Independence of the data protocol being forwarded between two
> > systems.
> > >   BFD packets are carried as the payload of whatever encapsulating
> > >   protocol is appropriate for the medium and network.
> > >
> > > - Path independence: BFD can provide failure detection on any kind
of
> > >   path between systems, including direct physical links, virtual
> > circuits,
> > >   tunnels, MPLS LSPs, multihop routed paths, and unidirectional
links
> > (so
> > >   long as there is some return path, of course).
> > >
> > > - Ability to be bootstrapped by any other protocol that
automatically
> > >   forms peer, neighbor or adjacency relationships to seed BFD
endpoint
> > >   discovery.
> > >
> > > The working group is chartered to complete the following work
items:
> > >
> > > 1. Develop the MIB module for BFD and submit it to the IESG for
> > > publication as a Proposed Standard.
> > >
> > > 2a. Provide a generic keying-based cryptographic authentication
> > mechanism
> > > for the BFD protocol in discussion with the KARP working group.
This
> > > mechanism will support authentication through a key identifier for
the
> > BFD
> > > session's Security Association rather than specifying new
> > authentication
> > > extensions.
> > >
> > > 2b. Provide extensions to the BFD MIB in support of the generic
> > > keying-based cryptographic authentication mechanism.
> > >
> > > 2c. Specify cryptographic authentication procedures for the BFD
> > protocol
> > > using HMAC-SHA-256 (possibly truncated to a smaller integrity
check
> > > value) using the generic keying-based cryptographic authentication
> > mechanism.
> > >
> > > 3. Provide an extension to the BFD core protocol in support of
> > point-to-
> > > multipoint links and networks.
> > >
> > > 4. Assist the MPLS working group in the standardization of the BFD
> > > protocol for MPLS-TP.  The preferred solution will be
interoperable
> > with the
> > > current BFD specification.
> > >
> > > 5. Provide one or more mechanisms to run BFD over Link Aggregation
> > Group
> > > Interfaces.
> > >
> > > The working group will maintain a relationship with the KARP and
MPLS
> > > working groups, and will communicate with the IEEE with respect to
BFD
> > > over LAGs.
> > >
> > > Milestones:
> > >   Done     - Submit the base protocol specification to the IESG to
be
> > > considered as a Proposed Standard
> > >   Done     - Submit BFD encapsulation and usage profile for
single-hop
> > > IPv4 and IPv6 adjacencies to the IESG to be considered as a
Proposed
> > > Standard
> > >   Done     - Submit BFD encapsulation and usage profile for MPLS
LSPs
> > to
> > > the IESG to be considered as a Proposed Standard
> > >   Done     - Submit BFD encapsulation and usage profile for
multi-hop
> > > IPv4 and IPv6 adjacencies to the IESG to be considered as a
Proposed
> > > Standard
> > >   Sep 2011 - Submit the BFD MIB to the IESG to be considered as a
> > > Proposed Standard
> > >   Dec 2011 - Submit the generic keying based cryptographic
> > authentication
> > > mechanism to the IESG to be considered as a Proposed Standard
> > >   Dec 2011 - Submit a BFD MIB extension in support of the generic
> > keying
> > > document to the IESG to be considered as a Proposed Standard
> > >   Dec 2011 - Submit the cryptographic authentication procedures
for
> > BFD
> > > to the IESG to be considered as a Proposed Standard
> > >   Mar 2012 - Submit the the document on BFD point-to-multipoint
> > support
> > > to the IESG to be considered as a Proposed Standard
> > >   Jun 2012 - Submit the bootstrapping mechanism for BFD using DHCP
to
> > the
> > > IESG to be considered as a Proposed Standard



From framefritti@gmail.com  Thu Nov  8 07:25:12 2012
Return-Path: <framefritti@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 00FA321F894E for <ietf@ietfa.amsl.com>; Thu,  8 Nov 2012 07:25:12 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Unjf4u9XnvgC for <ietf@ietfa.amsl.com>; Thu,  8 Nov 2012 07:25:11 -0800 (PST)
Received: from mail-ie0-f172.google.com (mail-ie0-f172.google.com [209.85.223.172]) by ietfa.amsl.com (Postfix) with ESMTP id 26C5A21F8ACD for <ietf@ietf.org>; Thu,  8 Nov 2012 07:25:11 -0800 (PST)
Received: by mail-ie0-f172.google.com with SMTP id 9so4869642iec.31 for <ietf@ietf.org>; Thu, 08 Nov 2012 07:25:10 -0800 (PST)
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=kq6jnPQORaqmg3YPV+A0vbUFgioYMmQEEHRiL7SP9R4=; b=sEZ8Sf1qVrXdeSzNgaFqsAPpld+O9zHuVlSetbEHBiHyRO4ioJEMEc70VL/t4KduL5 SY6eb8nQfll5f06tHKfINf5h38i0Q66zRsW3AjIdD/AFLfQiUbuj1kukwTLEnK1M0zwZ xF2uvCNRzlRTGrGrujvOIISmg4J/Qw4Bj7ZrI5Cb3CYgF3/g7V1n8bxZ3y2zRctcI6Um 3Jy/jmTlvNg2fkndLtaLJpELP1sNXrYMTGrWLsddnfWNhHrQXksWYUyXHAW7Qcgj67WI jPWS6FSND+pwoz7G5Cp6rwVV/w/ZFigiE6P6IyBEHHx4Yubeau4JepYHeHebdaJ7p6md mjcw==
MIME-Version: 1.0
Received: by 10.50.222.226 with SMTP id qp2mr8325551igc.74.1352388310784; Thu, 08 Nov 2012 07:25:10 -0800 (PST)
Received: by 10.64.98.202 with HTTP; Thu, 8 Nov 2012 07:25:10 -0800 (PST)
In-Reply-To: <00f401cdbdc0$d3a1a8d0$7ae4fa70$@olddog.co.uk>
References: <00f401cdbdc0$d3a1a8d0$7ae4fa70$@olddog.co.uk>
Date: Thu, 8 Nov 2012 16:25:10 +0100
Message-ID: <CABSMSPXxw87rxaxwEKoC5PK41DTdzSQb7q4BmxVyJ-_ucM=gNw@mail.gmail.com>
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
From: Riccardo Bernardini <framefritti@gmail.com>
To: IETF Discussion <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Nov 2012 15:25:12 -0000

>
> That we are not reflects our inability to retain, not our inability to attract
> (assuming that we are not completely refreshing the IETF attendance every three
> or four years). Should not be rocket science to follow up with some newcomers to
> find out why they only attend once and never come back.

Hi,
I am one of those non-returning newcomers, so maybe I can reply with
my own motivations.  I came to Maastricht, few meetings ago because I
had some specific interest (and, I admit, I was a bit curios of seeing
a meeting live, but that was not the main motivation... Just the icing
on the cake).

I did not return (yet, I think I'll do) because I work in the
University, so scientific conferences are more natural an environment
for me.  Also, depending on the location, a 1-week participation is
quite expensive (not more expensive than your average conference, but
expensive nevertheless) and since funding are pretty scarce, coming to
a meeting (with my regret) is something that I'll do when I'll have
some very strong motivation.

Add to this that you can do most of interaction via e-mail and can
remotely participate via streaming + jabber and you can understand
that it is unlikely to have the strict necessity of being "on place."

So, to summarize

Q: Why did you come?
A: Because I had a very specific interest

Q: Why did you not return?
A: Because the necessity of being at meeting does not compensate for
the cost.  Also I work at University, so I participate more to
scientific conference than to engineering meetings. (Also, teaching
duties do not help)

Q: Do you plan to return?
A: Yes, I do, maybe fairly soon, but I have no precise plan yet.

Riccardo

From agmalis@gmail.com  Thu Nov  8 07:32:17 2012
Return-Path: <agmalis@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE10C21F87ED for <ietf@ietfa.amsl.com>; Thu,  8 Nov 2012 07:32:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.431
X-Spam-Level: 
X-Spam-Status: No, score=-3.431 tagged_above=-999 required=5 tests=[AWL=0.167,  BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 eMp0YjsNvKu5 for <ietf@ietfa.amsl.com>; Thu,  8 Nov 2012 07:32:17 -0800 (PST)
Received: from mail-ie0-f172.google.com (mail-ie0-f172.google.com [209.85.223.172]) by ietfa.amsl.com (Postfix) with ESMTP id D8D7E21F8595 for <ietf@ietf.org>; Thu,  8 Nov 2012 07:32:16 -0800 (PST)
Received: by mail-ie0-f172.google.com with SMTP id 9so4883056iec.31 for <ietf@ietf.org>; Thu, 08 Nov 2012 07:32:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=7S0ER91a57iDRlxSKSLCfGN9RpudzSpBPJbu2J8dgpc=; b=hFS5vwL/QFAHHXLQKE1Jd8yFZEQqTZtVBqXoeFWwpgYCkrl81RTBOexa14Iz78FEWr H7+tG5XUbH0Rl+Xq53mAtNmNteD1Gp0gka9PBOd9VZxTwD+uiK+TSB/fKmkuxt2fr7zc ciC0ooF4zxW/cLVGTLJENIx4ZrCb1Kz5H0LU6MbSzGU6n7ylF/z8G0YZlvyV7ciYKWK2 VejWjagks6t2ntfp+wSb8hlknru4qyrsEUcNfzYq6kgeSUolUlnYfV0qrJfApdXUmn52 BlFRw/gSBQ5gPUeOimkpnYk51YtEikhQRuFKdFY8LiHpEkim2Oyw9jCubJ3Hwd0BmRJg gktg==
Received: by 10.50.159.170 with SMTP id xd10mr8271144igb.44.1352388736486; Thu, 08 Nov 2012 07:32:16 -0800 (PST)
MIME-Version: 1.0
Received: by 10.64.35.195 with HTTP; Thu, 8 Nov 2012 07:31:56 -0800 (PST)
In-Reply-To: <00f401cdbdc0$d3a1a8d0$7ae4fa70$@olddog.co.uk>
References: <00f401cdbdc0$d3a1a8d0$7ae4fa70$@olddog.co.uk>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Thu, 8 Nov 2012 10:31:56 -0500
Message-ID: <CAA=duU0OdEETgbRCaQm2bikbZW6+4xJbg9jzZiYSNQzaBHvwBg@mail.gmail.com>
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
To: Adrian Farrel <adrian@olddog.co.uk>
Content-Type: multipart/alternative; boundary=14dae93409713c8e7104cdfd8a5c
Cc: SM <sm@resistor.net>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Nov 2012 15:32:17 -0000

--14dae93409713c8e7104cdfd8a5c
Content-Type: text/plain; charset=ISO-8859-1

There's obviously a subset of the "newcomers" who only attend because a
meeting is local or otherwise convenient to attend, or come with narrowly
focused interests, and never planned to become a regular.

Since attendance is largely flat over last few years, obviously newcomers
that become regulars are offset by existing participants that drop out or
cannot make a particular meeting. Drop outs have to be expected for any
number of reasons, such as change in job function, change in (or loss of)
employer, end of a work item of interest, and so on.

I, for one, think we're actually not in a bad place right now, and would
not welcome a return of the 2600-attendee meetings, where meeting rooms and
hallways were filled to overflowing, with no real commensurate increase in
the set of participants doing the work.

Cheers,
Andy


On Thu, Nov 8, 2012 at 9:53 AM, Adrian Farrel <adrian@olddog.co.uk> wrote:

> Trimming SM's email...
>
> > There is a direct contribution of US $2.2 million by the Internet
> > Society next year.  Is the plan to rely on Internet Society subsidies
> > or to fix the deficit?  One argument made was that the fees have not
> > been increased over the last years.  I'll point out that there hasn't
> > been significant increase in paid attendance over the years.  Either
> > the IETF is only relevant to the usual folks or else the meetings are
> > not made relevant enough for (new) people to attend.
>
> I am repeatedly struck by how many new people *do* attend.
>
> According to Russ's slides [1] 195/1098 are newcomers. And just to labour
> the
> point, a newcomer is not a returnee after 10 years, but someone who has
> never
> attended before.
>
> This number (around 10%) seems consistent over all meetings. So naively, we
> should be growing our attendance by around 300 per year.
>
> That we are not reflects our inability to retain, not our inability to
> attract
> (assuming that we are not completely refreshing the IETF attendance every
> three
> or four years). Should not be rocket science to follow up with some
> newcomers to
> find out why they only attend once and never come back.
>
> All other points made by SM may be valid.
>
> Adrian
>
> [1] http://www.ietf.org/proceedings/85/slides/slides-85-iesg-opsandtech-13
>
>

--14dae93409713c8e7104cdfd8a5c
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

There&#39;s obviously a subset of the &quot;newcomers&quot; who only attend=
 because a meeting is local or otherwise convenient to attend, or come with=
 narrowly focused interests, and never planned to become a regular.<br><br>

Since attendance is largely flat over last few years, obviously newcomers t=
hat become regulars are offset by existing participants that drop out or ca=
nnot make a particular meeting. Drop outs have to be expected for any numbe=
r of reasons, such as change in job function, change in (or loss of) employ=
er, end of a work item of interest, and so on.<br>

<br>I, for one, think we&#39;re actually not in a bad place right now, and =
would not welcome a return of the 2600-attendee meetings, where meeting roo=
ms and hallways were filled to overflowing, with no real commensurate incre=
ase in the set of participants doing the work.<br>

<br>Cheers,<br>Andy<br><div class=3D"gmail_extra"><br><br><div class=3D"gma=
il_quote">On Thu, Nov 8, 2012 at 9:53 AM, Adrian Farrel <span dir=3D"ltr">&=
lt;<a href=3D"mailto:adrian@olddog.co.uk" target=3D"_blank">adrian@olddog.c=
o.uk</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Trimming SM&#39;s email...<br>
<br>
&gt; There is a direct contribution of US $2.2 million by the Internet<br>
&gt; Society next year. =A0Is the plan to rely on Internet Society subsidie=
s<br>
&gt; or to fix the deficit? =A0One argument made was that the fees have not=
<br>
&gt; been increased over the last years. =A0I&#39;ll point out that there h=
asn&#39;t<br>
&gt; been significant increase in paid attendance over the years. =A0Either=
<br>
&gt; the IETF is only relevant to the usual folks or else the meetings are<=
br>
&gt; not made relevant enough for (new) people to attend.<br>
<br>
I am repeatedly struck by how many new people *do* attend.<br>
<br>
According to Russ&#39;s slides [1] 195/1098 are newcomers. And just to labo=
ur the<br>
point, a newcomer is not a returnee after 10 years, but someone who has nev=
er<br>
attended before.<br>
<br>
This number (around 10%) seems consistent over all meetings. So naively, we=
<br>
should be growing our attendance by around 300 per year.<br>
<br>
That we are not reflects our inability to retain, not our inability to attr=
act<br>
(assuming that we are not completely refreshing the IETF attendance every t=
hree<br>
or four years). Should not be rocket science to follow up with some newcome=
rs to<br>
find out why they only attend once and never come back.<br>
<br>
All other points made by SM may be valid.<br>
<br>
Adrian<br>
<br>
[1] <a href=3D"http://www.ietf.org/proceedings/85/slides/slides-85-iesg-ops=
andtech-13" target=3D"_blank">http://www.ietf.org/proceedings/85/slides/sli=
des-85-iesg-opsandtech-13</a><br>
<br>
</blockquote></div><br></div>

--14dae93409713c8e7104cdfd8a5c--

From adrian@olddog.co.uk  Thu Nov  8 07:32:21 2012
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 76BBB21F8B1C for <ietf@ietfa.amsl.com>; Thu,  8 Nov 2012 07:32:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.431
X-Spam-Level: 
X-Spam-Status: No, score=-2.431 tagged_above=-999 required=5 tests=[AWL=0.168,  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 5zyWg+b-EpId for <ietf@ietfa.amsl.com>; Thu,  8 Nov 2012 07:32:20 -0800 (PST)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) by ietfa.amsl.com (Postfix) with ESMTP id C2FAC21F87ED for <ietf@ietf.org>; Thu,  8 Nov 2012 07:32:19 -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 qA8FWEAb000631;  Thu, 8 Nov 2012 15:32:14 GMT
Received: from 950129200 (dhcp-4076.meeting.ietf.org [130.129.64.118]) (authenticated bits=0) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id qA8FW647000582 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 8 Nov 2012 15:32:10 GMT
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'t.p.'" <daedulus@btconnect.com>
References: <20121030154625.13482.31090.idtracker@ietfa.amsl.com>	<005801cdb813$894c97c0$4001a8c0@gateway.2wire.net>	<00bb01cdbab3$f104fa40$d30eeec0$@juniper.net> <000401cdbdc2$5f06d200$4001a8c0@gateway.2wire.net>
In-Reply-To: <000401cdbdc2$5f06d200$4001a8c0@gateway.2wire.net>
Subject: RE: WG Action: Rechartered Bidirectional Forwarding Detection (bfd)
Date: Thu, 8 Nov 2012 15:32:07 -0000
Message-ID: <012801cdbdc6$395b4730$ac11d590$@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: AQHhniOh4evmUXLYFBRFMmjGM5g1JQFaLxJpAaSt+GcBnVIRIZeTbioQ
Content-Language: en-gb
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Nov 2012 15:32:21 -0000

Tom,

I hear you.
The BFD chairs are working with me on this and we expect (well I demand ;-) to
have new milestones out within 7 days.

Adrian

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of t.p.
> Sent: 08 November 2012 14:56
> To: afarrel@juniper.net; ietf@ietf.org
> Subject: Re: WG Action: Rechartered Bidirectional Forwarding Detection (bfd)
> 
> ----- Original Message -----
> From: "Adrian Farrel" <afarrel@juniper.net>
> To: "'t.p.'" <daedulus@btconnect.com>; <ietf@ietf.org>
> Sent: Sunday, November 04, 2012 5:43 PM
> > Hello Tom.
> >
> > Charter text is distinct from milestones.
> > The charter is discussed by IESG and put out for community review.
> > Milestones are set by the chairs in discussion with their AD.
> > The process for handling the updates is also different.
> >
> > The BFD chairs agreed with me that they would update the milestones
> once the new
> > charter text was posted, so I hope we'll see that "soon".
> 
> Understood, but be aware of the impact it has, at least on me.  I was
> glad to see that one item, which I expect to engage with, was still in
> the Charter and then looked below to see when I might want to set aside
> time for it, only to see all those dates in the past, reminiscent of all
> those failed project plans that I have seen over the years.  If the
> dates are not updated, then I would think it a better process to send
> out just the updated Charter, without any dates.
> 
> Tom Petch
> 
> > Cheers,
> > Adrian
> >
> > > -----Original Message-----
> > > From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf
> Of t.p.
> > > Sent: 01 November 2012 09:28
> > > To: ietf@ietf.org
> > > Subject: Re: WG Action: Rechartered Bidirectional Forwarding
> Detection (bfd)
> > >
> > > I realise that the timekeeping of the IETF is not on a par with its
> > > engineering, but it seems a shame to promulgate a new charter for
> which
> > > every milestone is already several months in arrears.
> > >
> > > Tom Petch
> > >
> > >
> > > ----- Original Message -----
> > > From: "The IESG" <iesg-secretary@ietf.org>
> > > To: "IETF-Announce" <ietf-announce@ietf.org>
> > > Cc: "bfd WG" <rtg-bfd@ietf.org>
> > > Sent: Tuesday, October 30, 2012 3:46 PM
> > >
> > > > The Bidirectional Forwarding Detection (bfd) working group in the
> > > Routing
> > > > Area of the IETF has been rechartered. For additional information
> > > please
> > > > contact the Area Directors or the WG Chairs.
> > > >
> > > > Bidirectional Forwarding Detection (bfd)
> > > > ------------------------------------------------
> > > > Current Status: Active Working Group
> > > >
> > > > Chairs:
> > > >   David Ward <dward@cisco.com>
> > > >   Jeffrey Haas <jhaas@pfrc.org>
> > > >
> > > > Technical advisors:
> > > >   Dave Katz <dkatz@juniper.net>
> > > >
> > > > Assigned Area Director:
> > > >   Adrian Farrel <adrian@olddog.co.uk>
> > > >
> > > > Mailing list
> > > >   Address: rtg-bfd@ietf.org
> > > >   To Subscribe: rtg-bfd-request@ietf.org
> > > >   Archive: http://www.ietf.org/mail-archive/web/rtg-bfd/
> > > >
> > > > Charter of Working Group:
> > > >
> > > > The BFD Working Group is chartered to standardize and support the
> > > > bidirectional forwarding detection protocol (BFD) and its
> extensions.
> > > A
> > > > core goal of the working group is to standardize BFD in the
> context of
> > > IP
> > > > routing, or protocols such as MPLS that are based on IP routing,
> in a
> > > way
> > > > that will encourage multiple, inter-operable vendor
> implementations.
> > > The
> > > > Working Group will also provide advice and guidance on BFD to
> other
> > > > working groups or standards bodies as requested.
> > > >
> > > > BFD is a protocol intended to detect faults in the bidirectional
> path
> > > > between two forwarding engines, including physical interfaces,
> > > > subinterfaces, data link(s), and to the extent possible the
> forwarding
> > > > engines themselves, with potentially very low latency. It operates
> > > > independently of media, data protocols, and routing protocols. An
> > > > additional goal is to provide a single mechanism that can be used
> for
> > > > liveness detection over any media, at any protocol layer, with
> > > > a wide range of detection times and overhead, to avoid a
> proliferation
> > > > of different methods.
> > > >
> > > > Important characteristics of BFD include:
> > > >
> > > > - Simple, fixed-field encoding to facilitate implementations in
> > > hardware.
> > > >
> > > > - Independence of the data protocol being forwarded between two
> > > systems.
> > > >   BFD packets are carried as the payload of whatever encapsulating
> > > >   protocol is appropriate for the medium and network.
> > > >
> > > > - Path independence: BFD can provide failure detection on any kind
> of
> > > >   path between systems, including direct physical links, virtual
> > > circuits,
> > > >   tunnels, MPLS LSPs, multihop routed paths, and unidirectional
> links
> > > (so
> > > >   long as there is some return path, of course).
> > > >
> > > > - Ability to be bootstrapped by any other protocol that
> automatically
> > > >   forms peer, neighbor or adjacency relationships to seed BFD
> endpoint
> > > >   discovery.
> > > >
> > > > The working group is chartered to complete the following work
> items:
> > > >
> > > > 1. Develop the MIB module for BFD and submit it to the IESG for
> > > > publication as a Proposed Standard.
> > > >
> > > > 2a. Provide a generic keying-based cryptographic authentication
> > > mechanism
> > > > for the BFD protocol in discussion with the KARP working group.
> This
> > > > mechanism will support authentication through a key identifier for
> the
> > > BFD
> > > > session's Security Association rather than specifying new
> > > authentication
> > > > extensions.
> > > >
> > > > 2b. Provide extensions to the BFD MIB in support of the generic
> > > > keying-based cryptographic authentication mechanism.
> > > >
> > > > 2c. Specify cryptographic authentication procedures for the BFD
> > > protocol
> > > > using HMAC-SHA-256 (possibly truncated to a smaller integrity
> check
> > > > value) using the generic keying-based cryptographic authentication
> > > mechanism.
> > > >
> > > > 3. Provide an extension to the BFD core protocol in support of
> > > point-to-
> > > > multipoint links and networks.
> > > >
> > > > 4. Assist the MPLS working group in the standardization of the BFD
> > > > protocol for MPLS-TP.  The preferred solution will be
> interoperable
> > > with the
> > > > current BFD specification.
> > > >
> > > > 5. Provide one or more mechanisms to run BFD over Link Aggregation
> > > Group
> > > > Interfaces.
> > > >
> > > > The working group will maintain a relationship with the KARP and
> MPLS
> > > > working groups, and will communicate with the IEEE with respect to
> BFD
> > > > over LAGs.
> > > >
> > > > Milestones:
> > > >   Done     - Submit the base protocol specification to the IESG to
> be
> > > > considered as a Proposed Standard
> > > >   Done     - Submit BFD encapsulation and usage profile for
> single-hop
> > > > IPv4 and IPv6 adjacencies to the IESG to be considered as a
> Proposed
> > > > Standard
> > > >   Done     - Submit BFD encapsulation and usage profile for MPLS
> LSPs
> > > to
> > > > the IESG to be considered as a Proposed Standard
> > > >   Done     - Submit BFD encapsulation and usage profile for
> multi-hop
> > > > IPv4 and IPv6 adjacencies to the IESG to be considered as a
> Proposed
> > > > Standard
> > > >   Sep 2011 - Submit the BFD MIB to the IESG to be considered as a
> > > > Proposed Standard
> > > >   Dec 2011 - Submit the generic keying based cryptographic
> > > authentication
> > > > mechanism to the IESG to be considered as a Proposed Standard
> > > >   Dec 2011 - Submit a BFD MIB extension in support of the generic
> > > keying
> > > > document to the IESG to be considered as a Proposed Standard
> > > >   Dec 2011 - Submit the cryptographic authentication procedures
> for
> > > BFD
> > > > to the IESG to be considered as a Proposed Standard
> > > >   Mar 2012 - Submit the the document on BFD point-to-multipoint
> > > support
> > > > to the IESG to be considered as a Proposed Standard
> > > >   Jun 2012 - Submit the bootstrapping mechanism for BFD using DHCP
> to
> > > the
> > > > IESG to be considered as a Proposed Standard



From sm@resistor.net  Thu Nov  8 09:35:21 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E9B1721F84D5 for <ietf@ietfa.amsl.com>; Thu,  8 Nov 2012 09:35:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.464
X-Spam-Level: 
X-Spam-Status: No, score=-102.464 tagged_above=-999 required=5 tests=[AWL=0.136, 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 oo4HPy1ur+oI for <ietf@ietfa.amsl.com>; Thu,  8 Nov 2012 09:35:20 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 22EA321F84D2 for <ietf@ietf.org>; Thu,  8 Nov 2012 09:35:20 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id qA8HZCGH002326; Thu, 8 Nov 2012 09:35:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1352396117; bh=XcxWx2utFwhhblZOBlmhmM+iD52MDGHZYKiq3FGvk7g=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=iTDdEh4TLkH3QradLcH6kaFNsdY1A3a4+w2hWbOjPGWg+Wf2aU2cd1X86GF0PBsBw 4Knl5g5cbmUFE/QB5hfGlgKDVan7MbRr7o0ebsl56292GC8pCsWp++MGWBiZqESUTR N7TTUVM3WWV9DBns5tizWT87VpI9DD3i4xe44A+8=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1352396117; i=@resistor.net; bh=XcxWx2utFwhhblZOBlmhmM+iD52MDGHZYKiq3FGvk7g=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=pRVIL5HcK/fDC6lTlVqOq3TCsejEcRPUIORjGiMKBEnxXiJ4Qi9Da9aR8f0r7/TN1 szeOohT1cHUXZzKJ7PLngfCdPfRU5SMm78mpAYLY+tr9lph6ka02ZKHH+p72briKcM nRBBVgZcE2SJL20QtmaQKStrmDr3luAkTT1txlMI=
Message-Id: <6.2.5.6.2.20121108082215.0bf2d8e8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 08 Nov 2012 08:45:27 -0800
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
From: SM <sm@resistor.net>
Subject: Re: Evolutionizing the IETF
In-Reply-To: <509BC497.7070001@gmail.com>
References: <6.2.5.6.2.20121108031742.0654a200@elandnews.com> <509BC497.7070001@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Nov 2012 17:35:21 -0000

Hi Brian,
At 06:41 08-11-2012, Brian E Carpenter wrote:
>I think that calling it a deficit is slightly misleading, since we are
>a non-profit organisation. One of the reasons that CNRI gave up control
>of the IETF Secretariat was because the IETF needed more income than
>can be generated by reasonable meeting fees, to operate the various
>services that are not directly related to the meetings. If we had to
>cover those expenses out of meeting fees, the latter would have to be
>more than doubled. Would you like that?

The IETF is not registered as a non-profit organization.  I'll skip 
the discussion about non-profit as it might be a distraction.

I'll +0 on the question as I am not paying that fee.  Yesterday, John 
Levine asked about meeting fees and the surplus.  Someone pointed out 
that it is not a surplus; it's a deficit.  My comment was about the 
acceptable (please do not ask me to define acceptable :-)) 
fee.  Where's the balance between the fee being charged and 
revenue?  If one has more revenue, one will always find some strong 
argument to do the community a favor by not increasing the meeting fee.

>Personally I am very happy that ISOC sees supporting the IETF and the
>RFC Editor as part of its mission, and even more happy that it has the
>money to do so. I am also very happy that ICANN takes a similar
>attitude to the IETF-IANA function.

I doubt that ICANN is doing the IETF a favor by not charging for the 
IETF-IANA function.  According to the IANA report IANA did not meet 
the SLA target in April and June.  I don't have a problem with that 
as the IANA person said that she will do X on Y date and that is what happened.

Regards,
-sm

P.S. Thanks to the person who sent me the correct link for the IANA report 


From sm@resistor.net  Thu Nov  8 09:35:25 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E77C621F87CF for <ietf@ietfa.amsl.com>; Thu,  8 Nov 2012 09:35:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.469
X-Spam-Level: 
X-Spam-Status: No, score=-102.469 tagged_above=-999 required=5 tests=[AWL=0.130, 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 gvXYKumm5t6c for <ietf@ietfa.amsl.com>; Thu,  8 Nov 2012 09:35:25 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id A404521F87A3 for <ietf@ietf.org>; Thu,  8 Nov 2012 09:35:23 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id qA8HZCGJ002326; Thu, 8 Nov 2012 09:35:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1352396120; bh=82ks0Tp8G+OdYQV470KXizOw06z5RlcFgpENafURG8g=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=jsFpO9ZzyBPC07O9x33VHsr4oQNoRW4zf8Zn4Vw4ue1f3g4hlJGyVfMHWhWxVozHu VbNKWtfNKxjXHpKzfc6UcbWpIEXV9xd/7f6m0h+1KnAhU4REtagEPPgsBilmPKzH78 Z5Cy0Ck6MWTUv6hire1+OcRITvpR1urWlylmcbDA=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1352396120; i=@resistor.net; bh=82ks0Tp8G+OdYQV470KXizOw06z5RlcFgpENafURG8g=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=W4fohmC6dZDSpX+4opxYyK5ge6DJh26l/FFiPyngqlfKK+yrc/+SCNW6TgLpEHilL 2EcpR47Ihn9pqLvcaAxHmi/Ah9m/hrWNwxW9PPCq3B8IRUTakJFmEaxR/vjF5ms9gX AHQBZB5GOKsuPOpRW+4/AE9ESZLpXyIYqIWB1Gl8=
Message-Id: <6.2.5.6.2.20121108084550.0c066178@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 08 Nov 2012 09:16:46 -0800
To: "Andrew G. Malis" <agmalis@gmail.com>
From: SM <sm@resistor.net>
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
In-Reply-To: <CAA=duU0OdEETgbRCaQm2bikbZW6+4xJbg9jzZiYSNQzaBHvwBg@mail.g mail.com>
References: <00f401cdbdc0$d3a1a8d0$7ae4fa70$@olddog.co.uk> <CAA=duU0OdEETgbRCaQm2bikbZW6+4xJbg9jzZiYSNQzaBHvwBg@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Nov 2012 17:35:26 -0000

Hi Andy,
At 07:31 08-11-2012, Andrew G. Malis wrote:
>There's obviously a subset of the "newcomers" who only attend 
>because a meeting is local or otherwise convenient to attend, or 
>come with narrowly focused interests, and never planned to become a regular.

Yes.

>Since attendance is largely flat over last few years, obviously 
>newcomers that become regulars are offset by existing participants 
>that drop out or cannot make a particular meeting. Drop outs have to 
>be expected for any number of reasons, such as change in job 
>function, change in (or loss of) employer, end of a work item of 
>interest, and so on.

I suggest looking at this differently as it might provide a better 
answer to Adrian's comment.  Is there any data to explain why 
attendance is flat?

>I, for one, think we're actually not in a bad place right now, and 
>would not welcome a return of the 2600-attendee meetings, where 
>meeting rooms and hallways were filled to overflowing, with no real 
>commensurate increase in the set of participants doing the work.

I was following this working group which will likely be shut down 
because there is not enough participation.  There are quite a few 
working group which fit that profile.  I prefer not to view things as 
"actually not in a bad place" as it encourages complacency.

Personally, I like to see messages such as 
http://www.ietf.org/mail-archive/web/ietf/current/msg75744.html as it 
helps to understand the views which often go unheard.

Regards,
-sm 


From ted.ietf@gmail.com  Thu Nov  8 11:46:38 2012
Return-Path: <ted.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C343421F8522 for <ietf@ietfa.amsl.com>; Thu,  8 Nov 2012 11:46:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.432
X-Spam-Level: 
X-Spam-Status: No, score=-3.432 tagged_above=-999 required=5 tests=[AWL=0.167,  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 kY8ucrxnniKF for <ietf@ietfa.amsl.com>; Thu,  8 Nov 2012 11:46:37 -0800 (PST)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id A78D321F8507 for <ietf@ietf.org>; Thu,  8 Nov 2012 11:46:36 -0800 (PST)
Received: by mail-vb0-f44.google.com with SMTP id fc26so3453310vbb.31 for <ietf@ietf.org>; Thu, 08 Nov 2012 11:46:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=UyYctHo8b6nZZ152C0kUCMlXP1EA+FhP8nq5CKdcc1c=; b=qqBwa+L8SvJgdYhRQYf89fFIihScyJiH3CHCslPuScBiOVBZDFq53DSS2Ii2unjAcF 9gZAZkPneQ1/G7h/UNmdObymziiUKw4zTmajpu/KmaFZ8tzvDUY45zzR/LSJOv1yqX4N GHpi/ZOZ8VXn8V/SaYSMHv03Gs0XHhqDZPTTfc3YEolX3POCGuRcozOyI5aBZkla1KWF CZWCu30YYQMR/U8zc1gV7I7BR+E9k3JbHlHWWViHcHPOadfJxG+MthtLGt3k7eXAfsiU J0JCxgOWiAvLYJW5MZzpei7+Ul/0gohlpCi8VRNKV8IwAOHUqqk/W9erG3UwB3hjntW8 rwcg==
MIME-Version: 1.0
Received: by 10.220.39.206 with SMTP id h14mr8243768vce.41.1352403990180; Thu, 08 Nov 2012 11:46:30 -0800 (PST)
Received: by 10.58.164.35 with HTTP; Thu, 8 Nov 2012 11:46:30 -0800 (PST)
Date: Thu, 8 Nov 2012 14:46:30 -0500
Message-ID: <CA+9kkMCMX13q0EAwyDYLjLnPrYusaq=NXrGNiMj2Wo5ecR09bg@mail.gmail.com>
Subject: Common sense, process, and the nature of change
From: Ted Hardie <ted.ietf@gmail.com>
To: IETF <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Nov 2012 19:46:39 -0000

At the plenary last night, Andrew Sullivan set off a series of
conversations at the mic lines by asking what seems at first to be a
fairly simple question:  why is that we seem now to have more process
and less reliance on common sense?  As those at the plenary will have
noticed, the conversation did not stick directly to that question, but
went through some interesting history, called for a bit of data,
entertained a plea for mentoring, and then questioned whether point
solutions or major change would actually work to improve the IETF.

Thinking a bit about the directions that conversation took, I think
there is both a relatively simple answer to Andrew's question and a
much larger piece of context that need to be teased out of the
discussion.  The relatively simple answer is that we don't just use
common sense any more because we don't want to trust individuals as
much as we used to.  That lack of trust isn't directed at the current
IESG, IAOC,  or IAB, but at future incumbents.  We have come to the
idea that allowing a current set of office-holders to make ad hoc
decisions implies that all later incumbents will share that ability.
Since we don't know those later incumbents (how could we?), we don't
trust them; since we don't trust them, we don't want to cede to them a
power that might later get abused.  So we attempt to use structure and
process to restrict those unknown future incumbents.  That's
interesting in part because we believe in precedent enough to worry
that ceding decision making will grant to later officer holders
equivalent power, but we don't believe in it enough to believe it will
guide what the later officer holders will do.  That, again, likely
stems from a lack of trust.

So why don't we trust the future IETF NomCom that picks those folks or
the incumbents when picked?

I think that's where the larger context comes in.  The IETF is not
simply an engineering organization, it is a mission-based
organization.  Our mission is to make the Internet work and grow.
Belief in that mission is something built into the context of the
IETF, and it is part of what helps each of us guide our decisions
here.  Where some SDOs get compromises entirely by horse-trading, many
of the compromises that let the IETF work by rough consensus actually
come about because of that shared mission.  We recognize that
compromise to get interoperability is a key part of what lets the
Internet continue to work and grow.  We both give our technical
insight to that mission and we subordinate our technical desires to
it.

That works in part because we know that others here share that
mission.  We don't recite it at meetings or make it the subject of
ceremonies, but we recognize that spending enough time here will cause
both that mission and the whole-Internet engineering perspective to
seep into the bones of the participants.  We get a direct sense of it
from those with whom we interact (Pete and Murray's exchange last
night was a great precis of that process), we get an indirect sense of
it from broader social networks, and we have institutionalized it in
things like the NomCom eligibility rules.

I suspect that some of the trust issues we have with imagined future
incumbents actually comes from a subconscious fear that we won't be as
successful at passing on a belief in that mission as we have so far
been.  That may be because the current mechanisms are largely ad hoc
(as Joe's comments on mentoring hinted); it may be more free form than
that.  To counter that concern, we may want to extend the methods we
already do have (Edu teams, newcomers socials, and so on) for longer
parts of the initial participation periods.  We may even want to
consider new ways of generating affiliation to our core goals.
However we do it, it seems likely that energy put into making sure
that the IETF's mission is part of each participant's understanding of
their work will return benefits both to the IETF now and when those
unknown future incumbents take office.

The other thing that context suggests is probably equally important.
As a mission-based organization, we have a natural touchstone for
evaluating change.  If a proposed change furthers the mission of the
organization, we can likely manage the transition it implies, whatever
the scale might be.  If it hinders the mission of the organization, it
shouldn't be taken on however cheaply and easily it might be done.

Maintaining the power of the incumbents? Not important.  Maintaining
the current structures? Not important.  Change for change's sake?  Not
valuable.  Making sure the mission gets done?  Pretty much the only
thing that matters.

Since this is all long since baked into the bones of most IETF
participants, this no doubt seems a bit trite or even silly.  But
there are times when it is important to say things out loud, and this
may be one of them. If we are considering why change in the IETF
increasingly looks like ossification and if we are considering how to
fix that, we should keep our mission in mind.

My two cents as an individual,

Ted Hardie

From agmalis@gmail.com  Thu Nov  8 11:51:51 2012
Return-Path: <agmalis@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5284721F8489 for <ietf@ietfa.amsl.com>; Thu,  8 Nov 2012 11:51:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.459
X-Spam-Level: 
X-Spam-Status: No, score=-3.459 tagged_above=-999 required=5 tests=[AWL=0.139,  BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 Pyno5LG5Wac5 for <ietf@ietfa.amsl.com>; Thu,  8 Nov 2012 11:51:50 -0800 (PST)
Received: from mail-ia0-f172.google.com (mail-ia0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id BBCA821F8808 for <ietf@ietf.org>; Thu,  8 Nov 2012 11:51:50 -0800 (PST)
Received: by mail-ia0-f172.google.com with SMTP id x24so2479039iak.31 for <ietf@ietf.org>; Thu, 08 Nov 2012 11:51:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=Uj6U8NVS1PW/UfBPoebv+aGdSugMdSFUJzkHR9ZXWMM=; b=Br9621tjIiRsrtxpq6P6brJyG21yKxfmFGEK2HgMplUsyVFVoD0SMD59j2NRLDN5fw jH6SEuyr9qADqY0fBXv1lMgBAYU2Kg617hJhVo1ofrk3DbruU6eqFXkThpoXo+dZ7M5R 9j65tuy7UaISr7uJwabo3i8B/6XtLCUvmix5nLtT3Nn4A/YgW9w6wYYWJGDHcBO5yydR 5LwAjuHuRJX9vhNoNJQssJkPUqyK85Ia4gn+psToPsl7rDWgAqVaoo8qisr0/CdK2y48 Ndolsy66A0HNintugNOwdCpkJlwEGzYIQdirSlRIAHg2uIitVZyM6zwLGYMlXzYYCF/6 9BWw==
Received: by 10.50.91.169 with SMTP id cf9mr21007706igb.44.1352404297118; Thu, 08 Nov 2012 11:51:37 -0800 (PST)
MIME-Version: 1.0
Received: by 10.64.35.195 with HTTP; Thu, 8 Nov 2012 11:51:16 -0800 (PST)
In-Reply-To: <6.2.5.6.2.20121108084550.0c066178@resistor.net>
References: <00f401cdbdc0$d3a1a8d0$7ae4fa70$@olddog.co.uk> <CAA=duU0OdEETgbRCaQm2bikbZW6+4xJbg9jzZiYSNQzaBHvwBg@mail.gmail.com> <6.2.5.6.2.20121108084550.0c066178@resistor.net>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Thu, 8 Nov 2012 14:51:16 -0500
Message-ID: <CAA=duU0AzEbO2+KnzS7p4e9SxwtagBLDs1YCTWZ4ze=kKu-HNw@mail.gmail.com>
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
To: SM <sm@resistor.net>
Content-Type: multipart/alternative; boundary=e89a8f3b9dadb8f27704ce012968
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Nov 2012 19:51:51 -0000

--e89a8f3b9dadb8f27704ce012968
Content-Type: text/plain; charset=ISO-8859-1

SM,

I was following this working group which will likely be shut down because
> there is not enough participation.  There are quite a few working group
> which fit that profile.  I prefer not to view things as "actually not in a
> bad place" as it encourages complacency.
>

Back in the 90s, I chaired a WG that regularly had less than 10 attendees,
but all of them were interested and contributed, and we got a good set of
RFCs as a result. You don't need a large number of participants, just
committed ones.

I do agree though, that was a good response from Riccardo.

Cheers,
Andy

--e89a8f3b9dadb8f27704ce012968
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div class=3D"gmail_extra">SM,<br><br><div class=3D"gmail_quote"><blockquot=
e class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc sol=
id;padding-left:1ex"><div id=3D":2l9">I was following this working group wh=
ich will likely be shut down because there is not enough participation. =A0=
There are quite a few working group which fit that profile. =A0I prefer not=
 to view things as &quot;actually not in a bad place&quot; as it encourages=
 complacency.<br>


</div></blockquote></div><br>Back in the 90s, I chaired a WG that regularly=
 had less than 10 attendees, but all of them were interested and contribute=
d, and we got a good set of RFCs as a result. You don&#39;t need a large nu=
mber of participants, just committed ones.<br>

<br>I do agree though, that was a good response from Riccardo.<br><br>Cheer=
s,<br>Andy<br><br></div>

--e89a8f3b9dadb8f27704ce012968--

From sm@resistor.net  Thu Nov  8 12:10:50 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BAA0A21F86AF for <ietf@ietfa.amsl.com>; Thu,  8 Nov 2012 12:10:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.475
X-Spam-Level: 
X-Spam-Status: No, score=-102.475 tagged_above=-999 required=5 tests=[AWL=0.124, 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 70MriC-86JLK for <ietf@ietfa.amsl.com>; Thu,  8 Nov 2012 12:10:50 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id A20C921F86AD for <ietf@ietf.org>; Thu,  8 Nov 2012 12:10:49 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id qA8KAcDZ008259; Thu, 8 Nov 2012 12:10:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1352405443; bh=6Oxs+eNNKcvo5S45bjCMEAAwBwI6MS6WdLKf+sXuO70=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=qHWOD9PCuxR63wil/HvDUwscwzqFtPTQlV54GtNET35xdqiUIpUj8RDo1W78e0dQp 3t2GXyMn/vieG3qDZmw/D4bMAtSd8HNsJyVUyL86wTl1cnQBglgEa7p1Y77iklAA8T lZMe6Y3zVjeWY/di2nUeNO7ejybj+BYChPGnULdY=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1352405443; i=@resistor.net; bh=6Oxs+eNNKcvo5S45bjCMEAAwBwI6MS6WdLKf+sXuO70=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=4DPsoLHR6DymX5KLFScSb9WjLfcxVSIJoX/Vt5JUmpRHzJn/a0AwieHPDKwVm3QgS Q0LHWXtx24/1TIqL4KGflWodj9DRDLor5UG895MlLvPlFgbU6HIx0brgRmYkYbSGK/ adSa7QmeB+cKIOZhzfxGIQKrtf3+xYEVftXg12QA=
Message-Id: <6.2.5.6.2.20121108115742.097ddd20@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 08 Nov 2012 12:08:02 -0800
To: "Andrew G. Malis" <agmalis@gmail.com>
From: SM <sm@resistor.net>
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
In-Reply-To: <CAA=duU0AzEbO2+KnzS7p4e9SxwtagBLDs1YCTWZ4ze=kKu-HNw@mail.g mail.com>
References: <00f401cdbdc0$d3a1a8d0$7ae4fa70$@olddog.co.uk> <CAA=duU0OdEETgbRCaQm2bikbZW6+4xJbg9jzZiYSNQzaBHvwBg@mail.gmail.com> <6.2.5.6.2.20121108084550.0c066178@resistor.net> <CAA=duU0AzEbO2+KnzS7p4e9SxwtagBLDs1YCTWZ4ze=kKu-HNw@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Nov 2012 20:10:50 -0000

Hi Andy,
At 11:51 08-11-2012, Andrew G. Malis wrote:
>Back in the 90s, I chaired a WG that regularly had less than 10 
>attendees, but all of them were interested and contributed, and we 
>got a good set of RFCs as a result. You don't need a large number of 
>participants, just committed ones.

Agreed.

The thread that Adrian commented about was Newcomers.  During 
yesterday's plenary someone mentioned mentorship.  These (new) 
participants will be the committed ones of tomorrow or else there is 
no tomorrow.

Regards,
-sm 


From ajs@anvilwalrusden.com  Thu Nov  8 12:43:10 2012
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 175AF21F8685 for <ietf@ietfa.amsl.com>; Thu,  8 Nov 2012 12:43:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.828
X-Spam-Level: 
X-Spam-Status: No, score=-0.828 tagged_above=-999 required=5 tests=[AWL=0.012,  BAYES_00=-2.599, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311]
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 hNlRXuUpzpTK for <ietf@ietfa.amsl.com>; Thu,  8 Nov 2012 12:43:09 -0800 (PST)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id 90EF021F8683 for <ietf@ietf.org>; Thu,  8 Nov 2012 12:43:09 -0800 (PST)
Received: from mx1.yitter.info (dhcp-13cd.meeting.ietf.org [130.129.19.205]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id B47258A031 for <ietf@ietf.org>; Thu,  8 Nov 2012 20:43:07 +0000 (UTC)
Date: Thu, 8 Nov 2012 15:42:58 -0500
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: Common sense, process, and the nature of change
Message-ID: <20121108204257.GA78036@mx1.yitter.info>
References: <CA+9kkMCMX13q0EAwyDYLjLnPrYusaq=NXrGNiMj2Wo5ecR09bg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CA+9kkMCMX13q0EAwyDYLjLnPrYusaq=NXrGNiMj2Wo5ecR09bg@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Nov 2012 20:43:10 -0000

Ted,

Thanks for a thoughtful note.  I think you may well be on to an
explanation here.  But there's something of a bitter irony about it.

On Thu, Nov 08, 2012 at 02:46:30PM -0500, Ted Hardie wrote:

> process to restrict those unknown future incumbents.  That's
> interesting in part because we believe in precedent enough to worry
> that ceding decision making will grant to later officer holders
> equivalent power, but we don't believe in it enough to believe it will
> guide what the later officer holders will do.  That, again, likely
> stems from a lack of trust.

[â€¦]

> evaluating change.  If a proposed change furthers the mission of the
> organization, we can likely manage the transition it implies, whatever
> the scale might be.  If it hinders the mission of the organization, it
> shouldn't be taken on however cheaply and easily it might be done.

Both of these seem right to me, but the irony is that the fear of
unknown future incumbents is all by itself creating the warm, dark
place where we are growing the things that hinder the mission of the
organization.  For one of the things that allowed the mission to get
done was the ability of the organization to look at strange, one-off
cases, decide that they were a one-off case, make a decision, and move
on.  

The increasing weight of the processes simply don't allow that any
more, and it causes people outside the IETF to say things like, "I'm
not taking this work over there to be nibbled to death by ducks."  The
recent process invocation in the unfortunate IAOC situation is not the
only example of this: WG formation is difficult and expensive.  WGs
spend a great deal of time tip-toeing around delicate issues in an
effort to avoid making the appeal mechanism work.  These are changes
too, even if they're just the result of gradual accretion, and they
are bad for the mission.

Best,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From john_brzozowski@cable.comcast.com  Thu Nov  8 12:48:27 2012
Return-Path: <john_brzozowski@cable.comcast.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7089921F85D6 for <ietf@ietfa.amsl.com>; Thu,  8 Nov 2012 12:48:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.407
X-Spam-Level: 
X-Spam-Status: No, score=-102.407 tagged_above=-999 required=5 tests=[AWL=-1.510, BAYES_00=-2.599, HOST_EQ_MODEMCABLE=1.368, IP_NOT_FRIENDLY=0.334, 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 R5+sEPleeQju for <ietf@ietfa.amsl.com>; Thu,  8 Nov 2012 12:48:26 -0800 (PST)
Received: from cable.comcast.com (pacdcavout01.cable.comcast.com [69.241.43.119]) by ietfa.amsl.com (Postfix) with ESMTP id B6AF521F849D for <ietf@ietf.org>; Thu,  8 Nov 2012 12:48:26 -0800 (PST)
Received: from ([24.40.56.114]) by pacdcavout01.cable.comcast.com with ESMTP  id 97wm3m1.33484219; Thu, 08 Nov 2012 15:40:21 -0500
Received: from PACDCEXMB01.cable.comcast.com ([169.254.1.22]) by PACDCEXHUB01.cable.comcast.com ([fe80::84e8:95f3:f13b:169e%12]) with mapi id 14.02.0318.001; Thu, 8 Nov 2012 15:48:13 -0500
From: "Brzozowski, John" <John_Brzozowski@Cable.Comcast.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: IETF 85 Bits-n-Bytes
Thread-Topic: IETF 85 Bits-n-Bytes
Thread-Index: AQHNvfJeL0+1XYhgB0+CMmpRyN4fEA==
Date: Thu, 8 Nov 2012 20:48:12 +0000
Message-ID: <BD87928F6BFAEF4EBEB883E1C4F587723034B7BB@PACDCEXMB01.cable.comcast.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.4.120824
x-originating-ip: [24.40.55.70]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <FFEE206868441F449D57ACC00909C6CA@cable.comcast.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Nov 2012 20:48:27 -0000

Folks,

Please remember to visit Bits-n-Bytes here at IETF 85 in Atlanta, GA.  We
have some nice demonstrations and refreshments for you this evening.

There will also be some t-shirts given away each hour for those that stop
by and check out the demonstrations.

Regards,

John
=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
John Jason Brzozowski
Comcast Cable
m) +1-609-377-6594
e) mailto:john_brzozowski@cable.comcast.com
o) +1-484-962-0060
w) http://www.comcast6.net
=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




From ted.ietf@gmail.com  Thu Nov  8 12:55:13 2012
Return-Path: <ted.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C78421F8738 for <ietf@ietfa.amsl.com>; Thu,  8 Nov 2012 12:55:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.443
X-Spam-Level: 
X-Spam-Status: No, score=-3.443 tagged_above=-999 required=5 tests=[AWL=0.156,  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 PIbhvK3SpEW0 for <ietf@ietfa.amsl.com>; Thu,  8 Nov 2012 12:55:13 -0800 (PST)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id C434721F8686 for <ietf@ietf.org>; Thu,  8 Nov 2012 12:55:12 -0800 (PST)
Received: by mail-vb0-f44.google.com with SMTP id fc26so3526574vbb.31 for <ietf@ietf.org>; Thu, 08 Nov 2012 12:55:12 -0800 (PST)
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 :cc:content-type; bh=ss8aINg/hDXmSzHSdhm0EmpSQYFvDigdekHmd4g855Y=; b=JiQB9zswyK20mM8ZqDrI8/BJc55eQxDn2uJppYVofvTqcjkwRqAnNjJ4apmKgPcPH0 J0mPQxxNhHP3aozFR0HU5mq4TbYRztlOeDH030uRN1rsW67/pQrwVVs14WAynmbAtsWN qSBE5uBe8M87Pk5N8+7SpSyoPLOEdgoMJlrbvBVb/+ccxorX5cedj7SwCh330kHz8Wab nbQ1xpdqxS+jAlcNrPI6XvtpDytO7aKjJwKCehrHkLDBT+OlMzkfzillGBR2lx5xUBC+ ZMs9H8X/XsV+1s8h5Wp3ehG9SnsFHfZfAdWtEpLd74lB4Nb9fC497PuTTuKBwdPThHqo APqA==
MIME-Version: 1.0
Received: by 10.220.220.7 with SMTP id hw7mr8293117vcb.17.1352408111921; Thu, 08 Nov 2012 12:55:11 -0800 (PST)
Received: by 10.58.164.35 with HTTP; Thu, 8 Nov 2012 12:55:11 -0800 (PST)
In-Reply-To: <20121108204257.GA78036@mx1.yitter.info>
References: <CA+9kkMCMX13q0EAwyDYLjLnPrYusaq=NXrGNiMj2Wo5ecR09bg@mail.gmail.com> <20121108204257.GA78036@mx1.yitter.info>
Date: Thu, 8 Nov 2012 15:55:11 -0500
Message-ID: <CA+9kkMBpTRKsiJ_TdcJU5P1MhwmCYpRLP=7CccpL9pTt_Of91w@mail.gmail.com>
Subject: Re: Common sense, process, and the nature of change
From: Ted Hardie <ted.ietf@gmail.com>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Nov 2012 20:55:13 -0000

On Thu, Nov 8, 2012 at 3:42 PM, Andrew Sullivan <ajs@anvilwalrusden.com> wrote:
> Both of these seem right to me, but the irony is that the fear of
> unknown future incumbents is all by itself creating the warm, dark
> place where we are growing the things that hinder the mission of the
> organization.

I agree that this can be the case.  That's part of the reason I
believe putting energy into ensuring we share a common sense of our
mission is worthwhile; it will help us avoid the desire to institute
process changes that derive from a lack of trust.

Those efforts will likely not be sufficient, though, to tackle other
issues.  EDU team-style efforts may help us with both trust issues and
its resultant duck-nibbling, but they are not going to help with the
structural complexity of references (a different issue raised last
night).  I hope, though, that we can use a common touchstone for
evaluating process changes.  That may help us work out what efforts
are worth the time and effort not just for the IETF, but for the
Internet.

regards,

Ted Hardie

From hartmans@mit.edu  Thu Nov  8 13:09:43 2012
Return-Path: <hartmans@mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 08D9A21F867B for <ietf@ietfa.amsl.com>; Thu,  8 Nov 2012 13:09:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[AWL=-1.000, 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 SRMY6BL89xZs for <ietf@ietfa.amsl.com>; Thu,  8 Nov 2012 13:09:42 -0800 (PST)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id 65B2221F8665 for <ietf@ietf.org>; Thu,  8 Nov 2012 13:09:36 -0800 (PST)
Received: from carter-zimmerman.suchdamage.org (dhcp-917d.meeting.ietf.org [130.129.9.125]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.painless-security.com (Postfix) with ESMTPS id A104E2021E; Thu,  8 Nov 2012 16:08:37 -0500 (EST)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 6B15D412A; Thu,  8 Nov 2012 16:09:34 -0500 (EST)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Ted Hardie <ted.ietf@gmail.com>
Subject: Re: Common sense, process, and the nature of change
References: <CA+9kkMCMX13q0EAwyDYLjLnPrYusaq=NXrGNiMj2Wo5ecR09bg@mail.gmail.com>
Date: Thu, 08 Nov 2012 16:09:34 -0500
In-Reply-To: <CA+9kkMCMX13q0EAwyDYLjLnPrYusaq=NXrGNiMj2Wo5ecR09bg@mail.gmail.com> (Ted Hardie's message of "Thu, 8 Nov 2012 14:46:30 -0500")
Message-ID: <tsly5ib4x9t.fsf@mit.edu>
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
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Nov 2012 21:09:43 -0000

>>>>> "Ted" == Ted Hardie <ted.ietf@gmail.com> writes:

    Ted> want to trust individuals as much as we used to.  That lack of
    Ted> trust isn't directed at the current IESG, IAOC, or IAB, but at
    Ted> future incumbents.  We have come to the idea that allowing a
    Ted> current set of office-holders to make ad hoc decisions implies
    Ted> that all later incumbents will share that ability.  Since we
    Ted> don't know those later incumbents (how could we?), we don't
    Ted> trust them; since we don't trust them, we don't want to cede to
    Ted> them a power that might later get abused.  So we attempt to use
    Ted> structure and process to restrict those unknown future
    Ted> incumbents.  

ted, I'm a strong proponent of process over common sense (within limits)
but don't believe the above captures my rationale at all.

I am as worried about the current officers as much as any future
officers.

Especially when people have a lot of power, It's difficult to come
forward and say that you think they've abused that power or made a
decision that negatively impacts fairness.

Also, I believe people--even very good people--are bad at making
decisions that impact fairness, especially when they care significantly
about the outcome of those decisions.

So, for myself, as the importance of the work an organization does, the
maximum I am willing to trust anyone with regard to process issues
decreases significantly.
This is not a negative statement about any office holders, past, current
or future.
This is simply a belief that it is important to use more process as the
importance of things affected by the process increase.

I believe that the IETF's impact has increased and so I believe that the
IETF needs more process than it used to.

--Sam

From dhc@dcrocker.net  Thu Nov  8 13:18:53 2012
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 87B4221F89E5 for <ietf@ietfa.amsl.com>; Thu,  8 Nov 2012 13:18:53 -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=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 Ea5Vtfer53qz for <ietf@ietfa.amsl.com>; Thu,  8 Nov 2012 13:18:52 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 9E6A621F898A for <ietf@ietf.org>; Thu,  8 Nov 2012 13:18:52 -0800 (PST)
Received: from [130.129.17.128] (dhcp-1180.meeting.ietf.org [130.129.17.128]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id qA8LInLk030341 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 8 Nov 2012 13:18:50 -0800
Message-ID: <509C21B2.1000009@dcrocker.net>
Date: Thu, 08 Nov 2012 16:18:42 -0500
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: Ted Hardie <ted.ietf@gmail.com>
Subject: Re: Common sense, process, and the nature of change
References: <CA+9kkMCMX13q0EAwyDYLjLnPrYusaq=NXrGNiMj2Wo5ecR09bg@mail.gmail.com>
In-Reply-To: <CA+9kkMCMX13q0EAwyDYLjLnPrYusaq=NXrGNiMj2Wo5ecR09bg@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Thu, 08 Nov 2012 13:18:51 -0800 (PST)
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Nov 2012 21:18:53 -0000

Ted,

On 11/8/2012 2:46 PM, Ted Hardie wrote:
>       why is that we seem now to have more process
> and less reliance on common sense?
...
>    Thinking a bit about the directions that conversation took, I think
> there is both a relatively simple answer to Andrew's question and a
> much larger piece of context that need to be teased out of the
> discussion.  The relatively simple answer is that we don't just use
> common sense any more because we don't want to trust individuals as
> much as we used to.

And the decisions have dramatically larger effects.

And those making the decisions are held dramatically more accountable.

And the IETF community is dramatically more diverse, which means far 
less shared culture about process.

And...

And...



 >   That lack of trust isn't directed at the current
> IESG, IAOC,  or IAB, but at future incumbents.

This assessment has what empirical basis?

Quite a few appealing alternative theories could be postulated.  I hope 
that selecting among them is subject to more analysis than a popularity 
contest of subjective feel.  ("It's the answer because we all decide it 
feels right.")


>     We have come to the
> idea that allowing a current set of office-holders to make ad hoc
> decisions implies that all later incumbents will share that ability.

This is a rather existential community.  Most of our behaviors here 
pertain to the present, including present actors.

But really, Ted, where does your idea come from, that the issues with 
our current operation hang on some amorphous concern about unspecified, 
future actors, rather than some set of our current actors?


> I think that's where the larger context comes in.  The IETF is not
> simply an engineering organization, it is a mission-based
> organization.  Our mission is to make the Internet work and grow.

We like to utter phrases like that.  They are nice phrases about goals 
that no one could reasonably object to.

However they actually have essentially nothing to do with the concrete 
technical work we do here, except to the extent we pay engineering 
attention to scaling.

In fact, lofty, abstract goals such as you cite almost certainly 
distract us from the pragmatics that we have the skills to attend to.

But feel free to cite specifics that distinguish between what we (would) 
do merely as an engineering organization, versus what we (actually?) do 
as an organization to make the Internet grow.


> Belief in that mission is something built into the context of the
> IETF, and it is part of what helps each of us guide our decisions
> here.  Where some SDOs get compromises entirely by horse-trading, many
> of the compromises that let the IETF work by rough consensus actually
> come about because of that shared mission.

Oh?  It isn't because, for example, we simply worry more about 
engineering quality?  (When we actually do worry about it...)


>  We recognize that
> compromise to get interoperability is a key part of what lets the
> Internet continue to work and grow.

Whereas most of the IETF engineering discussions about compromise that 
I've participated in were in terms of what it will take to make things 
work.  You know, the sort of thing engineers worry about.  There are 
actually rather few marketing discussions about growing the Internet, 
during these engineering compromise discussions.


> The other thing that context suggests is probably equally important.
> As a mission-based organization, we have a natural touchstone for
> evaluating change.  If a proposed change furthers the mission of the
> organization, we can likely manage the transition it implies, whatever
> the scale might be.  If it hinders the mission of the organization, it
> shouldn't be taken on however cheaply and easily it might be done.

I'd be interested to hear some examples of when this has been done, in 
and for the terms you cite, since I don't recall participating in any.


d/
-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From ted.ietf@gmail.com  Thu Nov  8 13:25:28 2012
Return-Path: <ted.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4375621F86A1 for <ietf@ietfa.amsl.com>; Thu,  8 Nov 2012 13:25:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.452
X-Spam-Level: 
X-Spam-Status: No, score=-3.452 tagged_above=-999 required=5 tests=[AWL=0.147,  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 LqeJbxlZffLg for <ietf@ietfa.amsl.com>; Thu,  8 Nov 2012 13:25:26 -0800 (PST)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 373C621F8AEB for <ietf@ietf.org>; Thu,  8 Nov 2012 13:25:26 -0800 (PST)
Received: by mail-vb0-f44.google.com with SMTP id fc26so3555672vbb.31 for <ietf@ietf.org>; Thu, 08 Nov 2012 13:25:20 -0800 (PST)
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 :cc:content-type; bh=L7G1az+9QWZ93A5kkeUJ4Mw07Bk52pyN+Az6lbknrso=; b=tRkqUqfJkxFWt1U9SUfHSwvPbuqPJyIo7FIuQ9uDQ8MVPe8z8ygJNfYiA9OxnL2I90 LvLg6fx8wj7nOEGszHizSJsTAdVfRc2e3bp4FngOx85dRX5lEXv09n8MwK/NtXCBAm7l uLgO0xDF1oFIJUxyaiL4Udsm6rkpMktAYubtSmiiMXn+1+8F84qsp9/28+A8cyukVwXl wTV35s4atKGXnaoHp4ZOZTfRuN8WNvWmVoyVptHLzVRBUFScSmdNbPC7PInaXJsZrdq+ MLBCcEkMSyKnKoLrUAGmWmxlnGPD8Sq8em+vddVc4wuDbkPvIlneFhqLpjQY4rZ1F9GA NQkA==
MIME-Version: 1.0
Received: by 10.52.37.103 with SMTP id x7mr7391448vdj.61.1352409920727; Thu, 08 Nov 2012 13:25:20 -0800 (PST)
Received: by 10.58.164.35 with HTTP; Thu, 8 Nov 2012 13:25:20 -0800 (PST)
In-Reply-To: <tsly5ib4x9t.fsf@mit.edu>
References: <CA+9kkMCMX13q0EAwyDYLjLnPrYusaq=NXrGNiMj2Wo5ecR09bg@mail.gmail.com> <tsly5ib4x9t.fsf@mit.edu>
Date: Thu, 8 Nov 2012 16:25:20 -0500
Message-ID: <CA+9kkMBSMB3Wq8wUXu0AcTfEwwck--L7P70NUiu6FaHeQH0Dkw@mail.gmail.com>
Subject: Re: Common sense, process, and the nature of change
From: Ted Hardie <ted.ietf@gmail.com>
To: Sam Hartman <hartmans-ietf@mit.edu>
Content-Type: text/plain; charset=ISO-8859-1
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Nov 2012 21:25:28 -0000

On Thu, Nov 8, 2012 at 4:09 PM, Sam Hartman <hartmans-ietf@mit.edu> wrote:

> So, for myself, as the importance of the work an organization does, the
> maximum I am willing to trust anyone with regard to process issues
> decreases significantly.
> This is not a negative statement about any office holders, past, current
> or future.
> This is simply a belief that it is important to use more process as the
> importance of things affected by the process increase.
>
I think the old catchphrase for this was "rule of law, not rule of
men", and I agree that there are fundamental benefits of that
approach.  But the starting point of this discussion was questioning
why we seem to need process for everything--even one off situations
that have "special circumstances" all over them.  I think if we could
agree to evaluate the impact of individual decisions according to your
criteria ("what's the impact?"), before deciding on the need for
process, we would be standing on common ground.

But it sounds like we disagree on whether we can trust our current or
future leadership to make that sort of call.  While I think that
increased trust would increase the latitude that the community would
extend to our leadership in ways that would improve our lot, it sounds
like you would believe that this would grant too much power.  Is that
a fair summary of where we disagree?

regards,

Ted

From sm@resistor.net  Thu Nov  8 13:36:41 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7470521F85E8 for <ietf@ietfa.amsl.com>; Thu,  8 Nov 2012 13:36:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.48
X-Spam-Level: 
X-Spam-Status: No, score=-102.48 tagged_above=-999 required=5 tests=[AWL=0.119, 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 JHhbcMzbyQm7 for <ietf@ietfa.amsl.com>; Thu,  8 Nov 2012 13:36:40 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E7AD21F8546 for <ietf@ietf.org>; Thu,  8 Nov 2012 13:36:40 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id qA8LaS7J020235; Thu, 8 Nov 2012 13:36:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1352410593; bh=28DQeAQkv3WffpCejgsaM4M05V0bt0abv4pTb0stDbM=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=345Q7A5Lxg+64uNE1n1hvTLfGPVSU6o3dE8iChywhTFUEMzev5hSpPyIUXpA5xSsz RRUhiOmZuPpLtb4iNJbcT65VR1EIEpG96mT6uzPXFHCwCUHDHUNlB/luasnf59PIuP Wn6ZQHQi90M0A3YFvkswimF00d/MqhSpi0TpVzNI=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1352410593; i=@resistor.net; bh=28DQeAQkv3WffpCejgsaM4M05V0bt0abv4pTb0stDbM=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=vVSWZAG0AadEFQHWgFhAzHv+tq7uYs6zLh1TgkEZkr6YmsRGpOrot9VePn+odJF+S xB9wbURncMQ5QwE1g7/TNzpPnyxr83yNZyVdpDlAeaRqHmVbUsacCohQOOJnPGurt+ Mc7g8Q49EJbMPVugrb+S1pS6EyQcXGRq8M7uZ4II=
Message-Id: <6.2.5.6.2.20121108121305.0bcbb690@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 08 Nov 2012 13:34:42 -0800
To: Ted Hardie <ted.ietf@gmail.com>
From: SM <sm@resistor.net>
Subject: Re: Common sense, process, and the nature of change
In-Reply-To: <CA+9kkMCMX13q0EAwyDYLjLnPrYusaq=NXrGNiMj2Wo5ecR09bg@mail.g mail.com>
References: <CA+9kkMCMX13q0EAwyDYLjLnPrYusaq=NXrGNiMj2Wo5ecR09bg@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Nov 2012 21:36:41 -0000

Hi Ted,
At 11:46 08-11-2012, Ted Hardie wrote:
>Thinking a bit about the directions that conversation took, I think
>there is both a relatively simple answer to Andrew's question and a
>much larger piece of context that need to be teased out of the
>discussion.  The relatively simple answer is that we don't just use
>common sense any more because we don't want to trust individuals as
>much as we used to.  That lack of trust isn't directed at the current
>IESG, IAOC,  or IAB, but at future incumbents.  We have come to the

The five second sound bite is "why don't you trust your leaders"?

>idea that allowing a current set of office-holders to make ad hoc
>decisions implies that all later incumbents will share that ability.

Yes.

>Since we don't know those later incumbents (how could we?), we don't
>trust them; since we don't trust them, we don't want to cede to them a
>power that might later get abused.  So we attempt to use structure and
>process to restrict those unknown future incumbents.  That's
>interesting in part because we believe in precedent enough to worry
>that ceding decision making will grant to later officer holders
>equivalent power, but we don't believe in it enough to believe it will
>guide what the later officer holders will do.  That, again, likely
>stems from a lack of trust.

It's a bit more complicated than that.  If there is a perceived lack 
of transparency, process may be viewed as safeguarding the 
individual's interest.  I once had a chat with an IETF participant 
who asked what to do as the WG Chair took a bad decision.  There were 
two options:

  (i)  The Standards Process

  (ii) Talk to the person

The person did not mention Option (ii).  There is a newcomers' 
tutorial where people are lectured about the marvellous Standards 
Process.  There is very little socialization in the IETF.  The I* 
bodies are lacking when it comes to communication 
skills.  Unfortunately, when the I* bodies communicates the community 
asks "why are you bothering us with this"?

>I think that's where the larger context comes in.  The IETF is not
>simply an engineering organization, it is a mission-based
>organization.  Our mission is to make the Internet work and grow.

Frankly, I don't know what the IETF is.

>Belief in that mission is something built into the context of the
>IETF, and it is part of what helps each of us guide our decisions
>here.  Where some SDOs get compromises entirely by horse-trading, many
>of the compromises that let the IETF work by rough consensus actually
>come about because of that shared mission.  We recognize that
>compromise to get interoperability is a key part of what lets the
>Internet continue to work and grow.  We both give our technical
>insight to that mission and we subordinate our technical desires to
>it.

It is difficult to get people to compromise.

>I suspect that some of the trust issues we have with imagined future
>incumbents actually comes from a subconscious fear that we won't be as
>successful at passing on a belief in that mission as we have so far
>been.  That may be because the current mechanisms are largely ad hoc
>(as Joe's comments on mentoring hinted); it may be more free form than
>that.  To counter that concern, we may want to extend the methods we
>already do have (Edu teams, newcomers socials, and so on) for longer
>parts of the initial participation periods.  We may even want to
>consider new ways of generating affiliation to our core goals.
>However we do it, it seems likely that energy put into making sure
>that the IETF's mission is part of each participant's understanding of
>their work will return benefits both to the IETF now and when those
>unknown future incumbents take office.

I was pleasantly surprised by the level of comments at yesterday's 
plenary.  The Edu team is absent except for a few hours a year.  The 
newcomers' social is IETF-centric.  I like the idea of extending the 
initial participation periods.

I read the last sentence as building trust.  People might share your 
core goals if they "trust" you and they agree with the goals.  That's 
different from convincing them.  People put in energy if it is in 
their interest to do so.

>Maintaining the power of the incumbents? Not important.  Maintaining
>the current structures? Not important.  Change for change's sake?  Not
>valuable.  Making sure the mission gets done?  Pretty much the only
>thing that matters.

Agreed.

Regards,
-sm 


From lear@cisco.com  Thu Nov  8 14:06:24 2012
Return-Path: <lear@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 02DD421F8932 for <ietf@ietfa.amsl.com>; Thu,  8 Nov 2012 14:06:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.592
X-Spam-Level: 
X-Spam-Status: No, score=-110.592 tagged_above=-999 required=5 tests=[AWL=0.007, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, 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 le2B1TyLp6PB for <ietf@ietfa.amsl.com>; Thu,  8 Nov 2012 14:06:23 -0800 (PST)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfa.amsl.com (Postfix) with ESMTP id 13EFA21F88B4 for <ietf@ietf.org>; Thu,  8 Nov 2012 14:06:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=149; q=dns/txt; s=iport; t=1352412383; x=1353621983; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=mqU7MSPrFGvXqESQ8p1jtZb2lF4j77w9qE+ZiMeiKQc=; b=DSAqz1Zrj53IH+giy0fMQEE/FHt8iAtezLP9onFF1zYprA8f50M1Sox8 Yjc7gMm/Xht0uYWflqplsFFE2OgGpVLIVMDfKSuQayagv6o8sl61JphXm LPYf5WZjMssyKgaUXQHXYeBVpymfNKta2yTGUWtR4cNZeb/T363piQ/Ik s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AmUJAPArnFCQ/khR/2dsb2JhbABEhhiIGLQNBAR+gQiCHgEBAQQSARBVARALGAICBRYLAgIJAwIBAgFFBg0BBwEBHodonCSNJZMBgSCQJoETA5V7jliBa4Jw
X-IronPort-AV: E=Sophos;i="4.80,740,1344211200"; d="scan'208";a="78098263"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by ams-iport-2.cisco.com with ESMTP; 08 Nov 2012 22:06:21 +0000
Received: from dhcp-10-55-86-83.cisco.com (dhcp-10-55-86-83.cisco.com [10.55.86.83]) by ams-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id qA8M6L7h004513 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 8 Nov 2012 22:06:21 GMT
Message-ID: <509C2CDD.8040707@cisco.com>
Date: Thu, 08 Nov 2012 23:06:21 +0100
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: SM <sm@resistor.net>
Subject: Re: Common sense, process, and the nature of change
References: <CA+9kkMCMX13q0EAwyDYLjLnPrYusaq=NXrGNiMj2Wo5ecR09bg@mail.gmail.com> <6.2.5.6.2.20121108121305.0bcbb690@resistor.net>
In-Reply-To: <6.2.5.6.2.20121108121305.0bcbb690@resistor.net>
X-Enigmail-Version: 1.4.5
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Ted Hardie <ted.ietf@gmail.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Nov 2012 22:06:24 -0000

On 11/8/12 10:34 PM, SM wrote:
>
> Frankly, I don't know what the IETF is.
>

You are not the only one, and this needs to be fixed.

Eliot


From hartmans@mit.edu  Thu Nov  8 16:08:33 2012
Return-Path: <hartmans@mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4666821F84F8 for <ietf@ietfa.amsl.com>; Thu,  8 Nov 2012 16:08:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.266
X-Spam-Level: 
X-Spam-Status: No, score=-103.266 tagged_above=-999 required=5 tests=[AWL=-0.667, 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 qRK99J8hc5x2 for <ietf@ietfa.amsl.com>; Thu,  8 Nov 2012 16:08:32 -0800 (PST)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id 6FF4921F84DB for <ietf@ietf.org>; Thu,  8 Nov 2012 16:08:32 -0800 (PST)
Received: from carter-zimmerman.suchdamage.org (dhcp-45e6.meeting.ietf.org [130.129.69.230]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.painless-security.com (Postfix) with ESMTPS id 5A17C2036D; Thu,  8 Nov 2012 19:07:33 -0500 (EST)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 84C84412A; Thu,  8 Nov 2012 19:08:30 -0500 (EST)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Ted Hardie <ted.ietf@gmail.com>
Subject: Re: Common sense, process, and the nature of change
References: <CA+9kkMCMX13q0EAwyDYLjLnPrYusaq=NXrGNiMj2Wo5ecR09bg@mail.gmail.com> <tsly5ib4x9t.fsf@mit.edu> <CA+9kkMBSMB3Wq8wUXu0AcTfEwwck--L7P70NUiu6FaHeQH0Dkw@mail.gmail.com>
Date: Thu, 08 Nov 2012 19:08:30 -0500
In-Reply-To: <CA+9kkMBSMB3Wq8wUXu0AcTfEwwck--L7P70NUiu6FaHeQH0Dkw@mail.gmail.com> (Ted Hardie's message of "Thu, 8 Nov 2012 16:25:20 -0500")
Message-ID: <tslpq3n4ozl.fsf@mit.edu>
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
Cc: Sam Hartman <hartmans-ietf@mit.edu>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Nov 2012 00:08:33 -0000

>>>>> "Ted" == Ted Hardie <ted.ietf@gmail.com> writes:

    Ted> I think the old catchphrase for this was "rule of law, not rule
    Ted> of men", and I agree that there are fundamental benefits of
    Ted> that approach.  But the starting point of this discussion was
    Ted> questioning why we seem to need process for everything--even
    Ted> one off situations that have "special circumstances" all over
    Ted> them.  I think if we could agree to evaluate the impact of
    Ted> individual decisions according to your criteria ("what's the
    Ted> impact?"), before deciding on the need for process, we would be
    Ted> standing on common ground.

    Ted> But it sounds like we disagree on whether we can trust our
    Ted> current or future leadership to make that sort of call.  While
    Ted> I think that increased trust would increase the latitude that
    Ted> the community would extend to our leadership in ways that would
    Ted> improve our lot, it sounds like you would believe that this
    Ted> would grant too much power.  Is that a fair summary of where we
    Ted> disagree?


Yes, it sound like a fair summary of where disagreement would be if it
exists.
I don't know if there are cases where we've recently disagreed about how
much latitude to grant our leadership.


As an example, I think we both agreed that it was reasonable for the IAOC to vacate the
position  when the facts were first presented. I can't remember if you
are currently on the iaoc list. I did send them a question wondering if
they were taking the right approach, but that question was based on an
error in my understanding of the facts. Once that was clarified, I
apologized for wasting time.


When additional facts came to light, I favored using the recall
process. However, several of our leaders seem to have agreed with me
that the additional facts changed the situation and made the formal
process desirable to invoke.

Leader: We have a member of our IAOC who is not responsive. We've done a
bunch to try and contact them. We want to declare the position
vacant. Have we missed anything?

Participant 1: I think you always need to use the recall process for
this!

Participant 2: I've looked at the impact page. I can't see any of the
types of impact that are indicators of needing formal process that apply
here. So, I think this is fine.

Participant 3: Well, I've looked at the impact page too, and if our
leaders had the ability  to  remove someone who was participating simply
by claiming they were not, it could have all sorts of impact on
fairness; you could remove people you disagree with etc.
because of these reasons. Have we missed anything?

Participant A) I think  that we really need a real process here.

Participant B) I've looked at the impact page, and this 

Participant 4: Sounds like your concern would be addressed  if the
leaders made it clear that we'd be in a different situation if the
inactive member came forward and objected to their position being
declared vacant; that would remove the potential impact you're concerned
about.

Participant 3: O, yeah, you're right. So if we're clear that complete
silence on the part of the person being removed is a factor here, I
think it's fine to allow a lot more trust.

My point is not for the "impact page" to be a formal part of process; in
fact doing that would go against the entire idea of building trust in
our leaders. My thought here is to find some mechanism to tease apart
the issues where one person thinks trust should be given and another
disagrees. My hope is by having discussion points we can focus our
discussion and better come to agreement on whether there is impact when
someone disagrees. Ultimately, I think you'll need something like this
to have a constructive response to giving leaders more trust when
community members seem to want to give less trust.

From randy@psg.com  Thu Nov  8 16:12:49 2012
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1A27221F8665 for <ietf@ietfa.amsl.com>; Thu,  8 Nov 2012 16:12:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.547
X-Spam-Level: 
X-Spam-Status: No, score=-2.547 tagged_above=-999 required=5 tests=[AWL=0.052,  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 1PSVeNWpqDRb for <ietf@ietfa.amsl.com>; Thu,  8 Nov 2012 16:12:48 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 0765A21F85BB for <ietf@ietf.org>; Thu,  8 Nov 2012 16:12:41 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from <randy@psg.com>) id 1TWcD9-000J8v-Il; Fri, 09 Nov 2012 00:12:40 +0000
Date: Fri, 09 Nov 2012 09:12:38 +0900
Message-ID: <m2haozskg9.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Sam Hartman <hartmans-ietf@mit.edu>
Subject: Re: Common sense, process, and the nature of change
In-Reply-To: <tslpq3n4ozl.fsf@mit.edu>
References: <CA+9kkMCMX13q0EAwyDYLjLnPrYusaq=NXrGNiMj2Wo5ecR09bg@mail.gmail.com> <tsly5ib4x9t.fsf@mit.edu> <CA+9kkMBSMB3Wq8wUXu0AcTfEwwck--L7P70NUiu6FaHeQH0Dkw@mail.gmail.com> <tslpq3n4ozl.fsf@mit.edu>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Cc: IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Nov 2012 00:12:49 -0000

> I don't know if there are cases where we've recently disagreed about how
> much latitude to grant our leadership.

iaoc/marshall

From narten@us.ibm.com  Thu Nov  8 21:53:11 2012
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E67721F8681 for <ietf@ietfa.amsl.com>; Thu,  8 Nov 2012 21:53:11 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XKvU2A3O0cAd for <ietf@ietfa.amsl.com>; Thu,  8 Nov 2012 21:53:10 -0800 (PST)
Received: from e34.co.us.ibm.com (e34.co.us.ibm.com [32.97.110.152]) by ietfa.amsl.com (Postfix) with ESMTP id 5A82A21F8514 for <ietf@ietf.org>; Thu,  8 Nov 2012 21:53:10 -0800 (PST)
Received: from /spool/local by e34.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Thu, 8 Nov 2012 22:53:09 -0700
Received: from d03dlp03.boulder.ibm.com (9.17.202.179) by e34.co.us.ibm.com (192.168.1.134) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Thu, 8 Nov 2012 22:53:06 -0700
Received: from d03relay02.boulder.ibm.com (d03relay02.boulder.ibm.com [9.17.195.227]) by d03dlp03.boulder.ibm.com (Postfix) with ESMTP id 54F5519D803C for <ietf@ietf.org>; Thu,  8 Nov 2012 22:53:06 -0700 (MST)
Received: from d03av03.boulder.ibm.com (d03av03.boulder.ibm.com [9.17.195.169]) by d03relay02.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id qA95r6GC251324 for <ietf@ietf.org>; Thu, 8 Nov 2012 22:53:06 -0700
Received: from d03av03.boulder.ibm.com (loopback [127.0.0.1]) by d03av03.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id qA95r5ja013137 for <ietf@ietf.org>; Thu, 8 Nov 2012 22:53:05 -0700
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.44.115.148]) by d03av03.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id qA95r5p0013115 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 8 Nov 2012 22:53:05 -0700
Received: from rotala.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.5/8.12.5) with ESMTP id qA95r48Q021436 for <ietf@ietf.org>; Fri, 9 Nov 2012 00:53:04 -0500
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.5/8.14.5/Submit) id qA95r3Hl021384 for ietf@ietf.org; Fri, 9 Nov 2012 00:53:03 -0500
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201211090553.qA95r3Hl021384@rotala.raleigh.ibm.com>
Date: Fri, 09 Nov 2012 00:53:03 -0500
To: ietf@ietf.org
Subject: Weekly posting summary for ietf@ietf.org
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 12110905-2876-0000-0000-000001DB95A4
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Nov 2012 05:53:11 -0000

Total of 144 messages in the last 7 days.
 
script run at: Fri Nov  9 00:53:03 EST 2012
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  4.86% |    7 |  7.43% |    77532 | tglassey@earthlink.net
  5.56% |    8 |  4.95% |    51703 | brian.e.carpenter@gmail.com
  4.17% |    6 |  5.03% |    52526 | stewe@stewe.org
  4.86% |    7 |  4.32% |    45115 | dhc@dcrocker.net
  4.17% |    6 |  4.07% |    42507 | sm@resistor.net
  4.17% |    6 |  3.77% |    39303 | housley@vigilsec.com
  3.47% |    5 |  3.39% |    35351 | ted.ietf@gmail.com
  2.78% |    4 |  2.33% |    24271 | paitken@cisco.com
  2.08% |    3 |  2.99% |    31167 | daedulus@btconnect.com
  2.78% |    4 |  2.24% |    23397 | johnl@taugh.com
  2.08% |    3 |  2.29% |    23869 | turchanyi.geza@gmail.com
  2.08% |    3 |  1.84% |    19204 | john-ietf@jck.com
  2.08% |    3 |  1.76% |    18336 | sob@sobco.com
  1.39% |    2 |  2.32% |    24228 | lars@netapp.com
  2.08% |    3 |  1.54% |    16056 | chair@ietf.org
  2.08% |    3 |  1.38% |    14434 | randy@psg.com
  1.39% |    2 |  1.85% |    19287 | adrian@olddog.co.uk
  1.39% |    2 |  1.77% |    18495 | gtw@gtwassociates.com
  1.39% |    2 |  1.67% |    17470 | agmalis@gmail.com
  1.39% |    2 |  1.56% |    16259 | bob.hinden@gmail.com
  1.39% |    2 |  1.51% |    15803 | fred@cisco.com
  1.39% |    2 |  1.47% |    15323 | hartmans-ietf@mit.edu
  1.39% |    2 |  1.43% |    14919 | ynir@checkpoint.com
  1.39% |    2 |  1.37% |    14272 | ogud@ogud.com
  1.39% |    2 |  1.35% |    14123 | jason_livingood@cable.comcast.com
  1.39% |    2 |  1.33% |    13900 | john@jlc.net
  1.39% |    2 |  1.33% |    13874 | joelja@bogus.com
  1.39% |    2 |  1.23% |    12886 | listsebby@me.com
  1.39% |    2 |  1.18% |    12285 | sm+ietf@elandsys.com
  1.39% |    2 |  1.08% |    11249 | carlosm3011@gmail.com
  1.39% |    2 |  0.97% |    10167 | paul@cypherpunks.ca
  0.69% |    1 |  1.10% |    11497 | afarrel@juniper.net
  0.69% |    1 |  1.10% |    11440 | luby@qti.qualcomm.com
  0.69% |    1 |  1.01% |    10488 | vincent.roca@inria.fr
  0.69% |    1 |  0.94% |     9802 | cpignata@cisco.com
  0.69% |    1 |  0.93% |     9693 | mach.chen@huawei.com
  0.69% |    1 |  0.88% |     9215 | eburger@standardstrack.com
  0.69% |    1 |  0.83% |     8634 | narten@us.ibm.com
  0.69% |    1 |  0.80% |     8343 | mstjohns@comcast.net
  0.69% |    1 |  0.76% |     7927 | mehmet.ersue@nsn.com
  0.69% |    1 |  0.76% |     7923 | st.amour@isoc.org
  0.69% |    1 |  0.75% |     7848 | lrosen@rosenlaw.com
  0.69% |    1 |  0.71% |     7386 | arturo.servin@gmail.com
  0.69% |    1 |  0.70% |     7266 | shanna@juniper.net
  0.69% |    1 |  0.69% |     7234 | jordi.palet@consulintel.es
  0.69% |    1 |  0.68% |     7094 | bertietf@bwijnen.net
  0.69% |    1 |  0.68% |     7065 | tobias.gondrom@gondrom.org
  0.69% |    1 |  0.65% |     6829 | touch@isi.edu
  0.69% |    1 |  0.64% |     6706 | framefritti@gmail.com
  0.69% |    1 |  0.63% |     6623 | david.rudin@microsoft.com
  0.69% |    1 |  0.63% |     6557 | wesley.george@twcable.com
  0.69% |    1 |  0.63% |     6529 | john@jck.com
  0.69% |    1 |  0.62% |     6502 | ajs@anvilwalrusden.com
  0.69% |    1 |  0.62% |     6489 | barryleiba@computer.org
  0.69% |    1 |  0.60% |     6305 | henk.uijterwaal@gmail.com
  0.69% |    1 |  0.58% |     6068 | warren@kumari.net
  0.69% |    1 |  0.58% |     6057 | dwm@xpasc.com
  0.69% |    1 |  0.57% |     5997 | verywarmcarl@gmail.com
  0.69% |    1 |  0.57% |     5923 | yiu_lee@cable.comcast.com
  0.69% |    1 |  0.55% |     5789 | vesely@tana.it
  0.69% |    1 |  0.55% |     5710 | jnc@mercury.lcs.mit.edu
  0.69% |    1 |  0.55% |     5701 | lear@cisco.com
  0.69% |    1 |  0.53% |     5568 | smb@cs.columbia.edu
  0.69% |    1 |  0.53% |     5483 | joelja@gmail.com
  0.69% |    1 |  0.51% |     5366 | john_brzozowski@cable.comcast.com
  0.69% |    1 |  0.51% |     5326 | brescia74@verizon.net
  0.69% |    1 |  0.50% |     5166 | finlayson@live555.com
  0.69% |    1 |  0.49% |     5141 | stephen.farrell@cs.tcd.ie
  0.69% |    1 |  0.48% |     4972 | aalain@trstech.net
  0.69% |    1 |  0.47% |     4933 | paul.hoffman@vpnc.org
  0.69% |    1 |  0.47% |     4889 | simon.perreault@viagenie.ca
  0.69% |    1 |  0.45% |     4702 | wjhns1@hardakers.net
--------+------+--------+----------+------------------------
100.00% |  144 |100.00% |  1043497 | Total


From lear@cisco.com  Thu Nov  8 23:26:01 2012
Return-Path: <lear@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B9F7821F8B8D for <ietf@ietfa.amsl.com>; Thu,  8 Nov 2012 23:26:01 -0800 (PST)
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=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, 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 QIoE+-kkJMok for <ietf@ietfa.amsl.com>; Thu,  8 Nov 2012 23:26:00 -0800 (PST)
Received: from mtv-iport-4.cisco.com (mtv-iport-4.cisco.com [173.36.130.15]) by ietfa.amsl.com (Postfix) with ESMTP id E382A21F8B8B for <ietf@ietf.org>; Thu,  8 Nov 2012 23:26:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=298; q=dns/txt; s=iport; t=1352445961; x=1353655561; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=uYWkgBVaXr8HevA/+skbHBrLLbdzKjexUhsnws/QxdU=; b=L1izfEd0BqdlYTMDXnb28OkbzhE3fy8FDVc8zXapv8GbUr7/ZL99zS6w 6AJZKlWbuOie4rR53ScJn2K4lasqe1kRotZuMI4u/yFQjqiBOsI3h979z yBbuYgjUBbWlo8JiDhoSXSXWM5a0CEh+5jAezEgYUyc+zVH5fAOf8Oyim A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAFAD6vnFCrRDoI/2dsb2JhbABEhhm9MYEIgh4BAQEEEgEQVQEQCxgCAgUWCwICCQMCAQIBRQYNAQcBAR6HZ5xUjSWSaoEgkCeBEwOVe45YgWuCcA
X-IronPort-AV: E=Sophos;i="4.80,743,1344211200"; d="scan'208";a="63499940"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-4.cisco.com with ESMTP; 09 Nov 2012 07:26:00 +0000
Received: from sjc-vpn6-1403.cisco.com (sjc-vpn6-1403.cisco.com [10.21.125.123]) by mtv-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id qA97Pxpg017077; Fri, 9 Nov 2012 07:25:59 GMT
Message-ID: <509CB008.5040605@cisco.com>
Date: Fri, 09 Nov 2012 08:26:00 +0100
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: Randy Bush <randy@psg.com>
Subject: Re: Common sense, process, and the nature of change
References: <CA+9kkMCMX13q0EAwyDYLjLnPrYusaq=NXrGNiMj2Wo5ecR09bg@mail.gmail.com> <tsly5ib4x9t.fsf@mit.edu> <CA+9kkMBSMB3Wq8wUXu0AcTfEwwck--L7P70NUiu6FaHeQH0Dkw@mail.gmail.com> <tslpq3n4ozl.fsf@mit.edu> <m2haozskg9.wl%randy@psg.com>
In-Reply-To: <m2haozskg9.wl%randy@psg.com>
X-Enigmail-Version: 1.4.5
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Sam Hartman <hartmans-ietf@mit.edu>, IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Nov 2012 07:26:01 -0000

On 11/9/12 1:12 AM, Randy Bush wrote:
>> I don't know if there are cases where we've recently disagreed about how
>> much latitude to grant our leadership.
> iaoc/marshall
>
>

Not only did we not trust the leadership, but we also didn't trust the
plenary!  THAT has to change.

Eliot

From daedulus@btconnect.com  Fri Nov  9 01:07:22 2012
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C96021F85D0 for <ietf@ietfa.amsl.com>; Fri,  9 Nov 2012 01:07:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.899
X-Spam-Level: 
X-Spam-Status: No, score=-3.899 tagged_above=-999 required=5 tests=[AWL=-0.300, 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 AiK3gN4O511Y for <ietf@ietfa.amsl.com>; Fri,  9 Nov 2012 01:07:21 -0800 (PST)
Received: from va3outboundpool.messaging.microsoft.com (va3ehsobe001.messaging.microsoft.com [216.32.180.11]) by ietfa.amsl.com (Postfix) with ESMTP id 7535521F85CD for <ietf@ietf.org>; Fri,  9 Nov 2012 01:07:21 -0800 (PST)
Received: from mail211-va3-R.bigfish.com (10.7.14.243) by VA3EHSOBE010.bigfish.com (10.7.40.12) with Microsoft SMTP Server id 14.1.225.23; Fri, 9 Nov 2012 09:07:20 +0000
Received: from mail211-va3 (localhost [127.0.0.1])	by mail211-va3-R.bigfish.com (Postfix) with ESMTP id 8BABD520165; Fri,  9 Nov 2012 09:07:20 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.249.85; KIP:(null); UIP:(null); IPV:NLI; H:AMSPRD0710HT005.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -33
X-BigFish: PS-33(zz98dI9371I936eI542M1432I1418I14cbOzz1de0h1202h1d1ah1d2ahzz8275ch1033IL8275bh8275dhz2dh2a8h5a9h668h839hd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h304l1155h)
Received: from mail211-va3 (localhost.localdomain [127.0.0.1]) by mail211-va3 (MessageSwitch) id 1352452039390161_26014; Fri,  9 Nov 2012 09:07:19 +0000 (UTC)
Received: from VA3EHSMHS038.bigfish.com (unknown [10.7.14.254])	by mail211-va3.bigfish.com (Postfix) with ESMTP id 532DD24001D; Fri,  9 Nov 2012 09:07:19 +0000 (UTC)
Received: from AMSPRD0710HT005.eurprd07.prod.outlook.com (157.56.249.85) by VA3EHSMHS038.bigfish.com (10.7.99.48) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 9 Nov 2012 09:07:19 +0000
Received: from AMXPRD0410HT002.eurprd04.prod.outlook.com (157.56.248.165) by pod51017.outlook.com (10.255.160.168) with Microsoft SMTP Server (TLS) id 14.16.233.3; Fri, 9 Nov 2012 09:07:14 +0000
Message-ID: <004301cdbe59$7cdf7b00$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: Ted Hardie <ted.ietf@gmail.com>, SM <sm@resistor.net>
References: <CA+9kkMCMX13q0EAwyDYLjLnPrYusaq=NXrGNiMj2Wo5ecR09bg@mail.gmail.com> <6.2.5.6.2.20121108121305.0bcbb690@resistor.net>
Subject: Re: Common sense, process, and the nature of change
Date: Fri, 9 Nov 2012 09:06:16 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [157.56.248.165]
X-OriginatorOrg: btconnect.com
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Nov 2012 09:07:22 -0000

----- Original Message -----
From: "SM" <sm@resistor.net>
To: "Ted Hardie" <ted.ietf@gmail.com>
Cc: <ietf@ietf.org>
Sent: Thursday, November 08, 2012 9:34 PM

> Hi Ted,
> At 11:46 08-11-2012, Ted Hardie wrote:
> >Thinking a bit about the directions that conversation took, I think
> >there is both a relatively simple answer to Andrew's question and a
> >much larger piece of context that need to be teased out of the
> >discussion.  The relatively simple answer is that we don't just use
> >common sense any more because we don't want to trust individuals as
> >much as we used to.  That lack of trust isn't directed at the current
> >IESG, IAOC,  or IAB, but at future incumbents.  We have come to the
>
> The five second sound bite is "why don't you trust your leaders"?
>
> >idea that allowing a current set of office-holders to make ad hoc
> >decisions implies that all later incumbents will share that ability.
>
> Yes.
>
> >Since we don't know those later incumbents (how could we?), we don't
> >trust them; since we don't trust them, we don't want to cede to them
a
> >power that might later get abused.  So we attempt to use structure
and
> >process to restrict those unknown future incumbents.  That's
> >interesting in part because we believe in precedent enough to worry
> >that ceding decision making will grant to later officer holders
> >equivalent power, but we don't believe in it enough to believe it
will
> >guide what the later officer holders will do.  That, again, likely
> >stems from a lack of trust.
>
> It's a bit more complicated than that.  If there is a perceived lack
> of transparency, process may be viewed as safeguarding the
> individual's interest.  I once had a chat with an IETF participant
> who asked what to do as the WG Chair took a bad decision.  There were
> two options:
>
>   (i)  The Standards Process
>
>   (ii) Talk to the person
>
> The person did not mention Option (ii).  There is a newcomers'
> tutorial where people are lectured about the marvellous Standards
> Process.  There is very little socialization in the IETF.  The I*
> bodies are lacking when it comes to communication
> skills.  Unfortunately, when the I* bodies communicates the community
> asks "why are you bothering us with this"?

I agree that socialization and communication are weak in the IETF but
disagree as to the cause.  Socialization depends on communication and
there is a spectrum in communication from the richest, when I am
standing in front of you, looking you in the eye, to the poorest, a
tweet.

E-mail, the sine qua none of the IETF, is towards the poorer end of the
spectrum, so that as the work of the IETF has become dominated by
e-mail, with little happening face-to-face, so the socialization and
communication - except at the most technical level - has decreased.
Socialization breeds the idea of a common goal, a mission if you will.
If I know you and relate to you, then I am more willing to compromise,
to negotiate, to go the extra mile (such as at the weekend) or to give
up my pet concerns in order to produce a better standard.

Without such socialization, then work becomes dominated by other things
such as the bottom line, legal actions or the fear thereof, a lack of
trust and so on; and yes, we then need more process to ensure progress.
I think that the evolution of the IPR processes in the IETF would be a
good case study for this.

Tom Petch

> >I think that's where the larger context comes in.  The IETF is not
> >simply an engineering organization, it is a mission-based
> >organization.  Our mission is to make the Internet work and grow.
>
> Frankly, I don't know what the IETF is.
>
> >Belief in that mission is something built into the context of the
> >IETF, and it is part of what helps each of us guide our decisions
> >here.  Where some SDOs get compromises entirely by horse-trading,
many
> >of the compromises that let the IETF work by rough consensus actually
> >come about because of that shared mission.  We recognize that
> >compromise to get interoperability is a key part of what lets the
> >Internet continue to work and grow.  We both give our technical
> >insight to that mission and we subordinate our technical desires to
> >it.
>
> It is difficult to get people to compromise.
>
> >I suspect that some of the trust issues we have with imagined future
> >incumbents actually comes from a subconscious fear that we won't be
as
> >successful at passing on a belief in that mission as we have so far
> >been.  That may be because the current mechanisms are largely ad hoc
> >(as Joe's comments on mentoring hinted); it may be more free form
than
> >that.  To counter that concern, we may want to extend the methods we
> >already do have (Edu teams, newcomers socials, and so on) for longer
> >parts of the initial participation periods.  We may even want to
> >consider new ways of generating affiliation to our core goals.
> >However we do it, it seems likely that energy put into making sure
> >that the IETF's mission is part of each participant's understanding
of
> >their work will return benefits both to the IETF now and when those
> >unknown future incumbents take office.
>
> I was pleasantly surprised by the level of comments at yesterday's
> plenary.  The Edu team is absent except for a few hours a year.  The
> newcomers' social is IETF-centric.  I like the idea of extending the
> initial participation periods.
>
> I read the last sentence as building trust.  People might share your
> core goals if they "trust" you and they agree with the goals.  That's
> different from convincing them.  People put in energy if it is in
> their interest to do so.
>
> >Maintaining the power of the incumbents? Not important.  Maintaining
> >the current structures? Not important.  Change for change's sake?
Not
> >valuable.  Making sure the mission gets done?  Pretty much the only
> >thing that matters.
>
> Agreed.
>
> Regards,
> -sm
>
>



From abdussalambaryun@gmail.com  Fri Nov  9 06:32:03 2012
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 62E0A21F868E for <ietf@ietfa.amsl.com>; Fri,  9 Nov 2012 06:32:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.492
X-Spam-Level: 
X-Spam-Status: No, score=-3.492 tagged_above=-999 required=5 tests=[AWL=0.107,  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 rvc-EV7RMldT for <ietf@ietfa.amsl.com>; Fri,  9 Nov 2012 06:32:02 -0800 (PST)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id D94AE21F8542 for <ietf@ietf.org>; Fri,  9 Nov 2012 06:31:55 -0800 (PST)
Received: by mail-vb0-f44.google.com with SMTP id fc26so4346463vbb.31 for <ietf@ietf.org>; Fri, 09 Nov 2012 06:31:55 -0800 (PST)
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=RYlletbGLK4PI1rjPcKqODw3RVEQ/56xGoXlllBtqiU=; b=V5Db9m0opyhwwhd2qwuPSt8eQwSOy0rsLYvyKwtImIVtbFE8EbLOKBsW61fW0KPyrt dD9N/bM2HDOeJN+8btONf0uLjj55L38o4/XoaL1O7pMO7DAuIqyCZ17nNfZKg+lnr1Z2 KkCQNc1EuX3C/r21oEgTK0yWIwlt+VDz6sIAAqkmKUlU2H95HckMdJhEvSr+ZBH89+/I Gf7O7QskQDmCrfUqYNirfyiLhEO8hUy9bdRyMW5prsgrkCEMjyJ/aMysNHmqPrN4+hRz OfDlBEiSWaKpl/sQ2dw03M4G7G5lPfVn3ppxpc45rI5RTRm7dVyfAVtZxSU0vDN7+m9B 4fCg==
MIME-Version: 1.0
Received: by 10.220.8.195 with SMTP id i3mr10224115vci.44.1352471515341; Fri, 09 Nov 2012 06:31:55 -0800 (PST)
Received: by 10.220.204.9 with HTTP; Fri, 9 Nov 2012 06:31:55 -0800 (PST)
In-Reply-To: <CADnDZ8-fjxfgJys8sE10DdZ08tB8HdaTQXbPj2d7-OuQOGi9Pg@mail.gmail.com>
References: <CADnDZ8-fjxfgJys8sE10DdZ08tB8HdaTQXbPj2d7-OuQOGi9Pg@mail.gmail.com>
Date: Fri, 9 Nov 2012 15:31:55 +0100
Message-ID: <CADnDZ8_v3M1fNtkOV4rU1F-iaMC+2qvKhR353vwESiQsfh70MQ@mail.gmail.com>
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Nov 2012 14:32:03 -0000

>> There is a direct contribution of US $2.2 million by the Internet
>> Society next year.  Is the plan to rely on Internet Society subsidies
>> or to fix the deficit?  One argument made was that the fees have not
>> been increased over the last years.  I'll point out that there hasn't
>> been significant increase in paid attendance over the years.  Either
>> the IETF is only relevant to the usual folks or else the meetings are
>> not made relevant enough for (new) people to attend.

I am newcomer and not able to attend because most of meeting in
America instead of Europe.

>
> I am repeatedly struck by how many new people *do* attend.
>

I don't know how long do they remain, for me I am feeling disapointed.

> According to Russ's slides [1] 195/1098 are newcomers. And just to labour
> the
> point, a newcomer is not a returnee after 10 years, but someone who has
> never
> attended before.

hope treated equal with all participants,

>
> This number (around 10%) seems consistent over all meetings. So naively, we
> should be growing our attendance by around 300 per year.
>

agree

> That we are not reflects our inability to retain, not our inability to
> attract
> (assuming that we are not completely refreshing the IETF attendance every
> three
> or four years). Should not be rocket science to follow up with some
> newcomers to
> find out why they only attend once and never come back.
>

For me I still did n't attend but understand that many old
participants are biased and there seems no equal opportunity, people
don't always follow the IETF mission and procedure, they just follow
their ways as long there was no complain.

I call all newcomers to open a new WG and start complaining because we
have to discuss why we were disapointed of the IETF and IESG, and even
the Internet Society.

Please note that I will focus my volunteering work in complaining and
fixing the discourage I found so far.

AB

From ted.ietf@gmail.com  Fri Nov  9 06:50:27 2012
Return-Path: <ted.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA00921F86FC for <ietf@ietfa.amsl.com>; Fri,  9 Nov 2012 06:50:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.467
X-Spam-Level: 
X-Spam-Status: No, score=-3.467 tagged_above=-999 required=5 tests=[AWL=0.132,  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 u1tpbacWRqaL for <ietf@ietfa.amsl.com>; Fri,  9 Nov 2012 06:50:27 -0800 (PST)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 0931921F86FA for <ietf@ietf.org>; Fri,  9 Nov 2012 06:50:26 -0800 (PST)
Received: by mail-vb0-f44.google.com with SMTP id fc26so4369146vbb.31 for <ietf@ietf.org>; Fri, 09 Nov 2012 06:50:20 -0800 (PST)
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 :cc:content-type; bh=C6XWYm50jD4Z4Ko1JaD71GYYHAYqXO1+UZ1v5O3sWVM=; b=YBEFLU+Hg/hUzG86kxAG6kpeQC6DN24MXeM5kApcQGGeDYzo+BmdJkw30n5DK9hXSQ b5NYvv5+cOQ3aI75sTVVvjeQSWXaEFSffCT22AmICNqjwtKsKeAgLbjUgIBjsAuPk0ad ziec6wxuZrH9PVlx+i3gqqUW91a5sri3+gZ0NNg6j7falvnVLl6tNeyL8meMetlMlaaT YMgcKF8TxGWLPuTaJJVyFhcO5OybN1GK/K+l4Uxx7C/lW7QV5o6tli0of1uTZMDARjMw jXs1heyjOVzqTvwKUQOROadscVmQB68nvT+gph2vfZRSwcnTi8FjpRzv8nnFqSlLlP3v MbkA==
MIME-Version: 1.0
Received: by 10.52.37.103 with SMTP id x7mr9085451vdj.61.1352472620760; Fri, 09 Nov 2012 06:50:20 -0800 (PST)
Received: by 10.58.164.35 with HTTP; Fri, 9 Nov 2012 06:50:20 -0800 (PST)
In-Reply-To: <509C21B2.1000009@dcrocker.net>
References: <CA+9kkMCMX13q0EAwyDYLjLnPrYusaq=NXrGNiMj2Wo5ecR09bg@mail.gmail.com> <509C21B2.1000009@dcrocker.net>
Date: Fri, 9 Nov 2012 09:50:20 -0500
Message-ID: <CA+9kkMARwR8BJXffWYi=oXzxwhH+9v3w7Vvr5rQ55SG8x2C_+Q@mail.gmail.com>
Subject: Re: Common sense, process, and the nature of change
From: Ted Hardie <ted.ietf@gmail.com>
To: dcrocker@bbiw.net
Content-Type: text/plain; charset=ISO-8859-1
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Nov 2012 14:50:28 -0000

On Thu, Nov 8, 2012 at 4:18 PM, Dave Crocker <dhc@dcrocker.net> wrote:
> Ted,
>
>
Hi Dave,

Thanks for taking the time to respond.  I think some of the points you
make below echo some of the issues Sam raised, particularly that the
scope of authority makes increased process appropriate.  I'm still
thinking about that, and I don't have much more to say on it right
now.  There were a couple of other questions you asked that I answered
in-line.

> On 11/8/2012 2:46 PM, Ted Hardie wrote:
<snip>

> But really, Ted, where does your idea come from, that the issues with our
> current operation hang on some amorphous concern about unspecified, future
> actors, rather than some set of our current actors?

Both during the recent discussion of the whether a body can declare a
seat vacant and in previous process discussions, I have seen a lot of
postings and heard a fair number of hallways conversations that boiled
down to "this sets a bad precedent".  Some of my thinking about this
is simply trying to understand what people think is happening when
they say "it sets a precedent" in our context.

My experience may, of course, be unusual, and people could also be
using that as a cover for issues that actually pertain to the current
set of leaders.

>
>
>
>> I think that's where the larger context comes in.  The IETF is not
>> simply an engineering organization, it is a mission-based
>> organization.  Our mission is to make the Internet work and grow.
>
>
> We like to utter phrases like that.  They are nice phrases about goals that
> no one could reasonably object to.
>
> However they actually have essentially nothing to do with the concrete
> technical work we do here, except to the extent we pay engineering attention
> to scaling.

I think we simply disagree about this.  I've pointed a lot of new
folks to BCP95/RFC 3935 (our mission statement) and I think it helps
folks understand why we work on what we do and what our goals are.  It
absolutely comes across as trite in some contexts, something I
admitted at the end of my initial mail.

<snip>

>
>> Belief in that mission is something built into the context of the
>> IETF, and it is part of what helps each of us guide our decisions
>> here.  Where some SDOs get compromises entirely by horse-trading, many
>> of the compromises that let the IETF work by rough consensus actually
>> come about because of that shared mission.
>
>
> Oh?  It isn't because, for example, we simply worry more about engineering
> quality?  (When we actually do worry about it...)
>

I think there's more than engineering quality.  A good recent example
of this comes from the RTCWEB working group.  The group decided during
its charter phase to avoid interoperability failure during its
negotiations by making some baseline audio and video codecs mandatory
to implement.  During the audio codec selection decision, there was an
explicit effort to make sure that the codec could be implemented and
deployed by the widest possible set of actors.  That was a compromise
by the folks who had sunk costs in implementations of other codecs, in
order to grow the pie will be RTCWEB.

Did anyone mention our mission statement during that discussion?
Absolutely not.  But I think that class of compromise, where we put
the goal of growing the system above our individual interests, does
happen pretty often in the IETF.

YMMV.

regards,

Ted

From ynir@checkpoint.com  Fri Nov  9 07:08:07 2012
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 188E421F86F9 for <ietf@ietfa.amsl.com>; Fri,  9 Nov 2012 07:08:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.424
X-Spam-Level: 
X-Spam-Status: No, score=-10.424 tagged_above=-999 required=5 tests=[AWL=-0.140, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, SARE_MILLIONSOF=0.315]
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 2NKPcFSnr6oS for <ietf@ietfa.amsl.com>; Fri,  9 Nov 2012 07:08:05 -0800 (PST)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 0160521F8BB4 for <ietf@ietf.org>; Fri,  9 Nov 2012 07:08:04 -0800 (PST)
Received: from il-ex01.ad.checkpoint.com (il-ex01.ad.checkpoint.com [194.29.34.26]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id qA9F7vbK030919; Fri, 9 Nov 2012 17:07:57 +0200
X-CheckPoint: {509D197E-8-1B221DC2-2FFFF}
Received: from il-ex01.ad.checkpoint.com ([194.29.34.26]) by il-ex01.ad.checkpoint.com ([126.0.0.2]) with mapi; Fri, 9 Nov 2012 17:07:56 +0200
From: Yoav Nir <ynir@checkpoint.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Date: Fri, 9 Nov 2012 17:07:55 +0200
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
Thread-Topic: Newcomers [Was: Evolutionizing the IETF]
Thread-Index: Ac2+i/+N97CLg6P7R4ayyk8OJgE0Xw==
Message-ID: <9009A606-ACB8-4F25-992E-DF126822C591@checkpoint.com>
References: <CADnDZ8-fjxfgJys8sE10DdZ08tB8HdaTQXbPj2d7-OuQOGi9Pg@mail.gmail.com> <CADnDZ8_v3M1fNtkOV4rU1F-iaMC+2qvKhR353vwESiQsfh70MQ@mail.gmail.com>
In-Reply-To: <CADnDZ8_v3M1fNtkOV4rU1F-iaMC+2qvKhR353vwESiQsfh70MQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Nov 2012 15:08:07 -0000

On Nov 9, 2012, at 9:31 AM, Abdussalam Baryun wrote:

>>> There is a direct contribution of US $2.2 million by the Internet
>>> Society next year.  Is the plan to rely on Internet Society subsidies
>>> or to fix the deficit?  One argument made was that the fees have not
>>> been increased over the last years.  I'll point out that there hasn't
>>> been significant increase in paid attendance over the years.  Either
>>> the IETF is only relevant to the usual folks or else the meetings are
>>> not made relevant enough for (new) people to attend.
>=20
> I am newcomer and not able to attend because most of meeting in
> America instead of Europe.

Adding US and Canada attendees (I counted last week, might have changed sli=
ghtly) you get to about 51% of the attendees.=20
When meetings are held in other parts of the world (like Taipei, Paris or P=
rague) Americans still make up over 40% of the attendees.
Much as I prefer 4-hour flights to 12-hour flights, it minimizes the genera=
l pain to hold meetings in America.
There's also the issue that finding good venues is considerably easier in A=
merica than in either Europe or Asia

>> I am repeatedly struck by how many new people *do* attend.
>>=20
>=20
> I don't know how long do they remain, for me I am feeling disapointed.

Some come back, and some don't. Could you expand on what you're disappointe=
d about?

>> According to Russ's slides [1] 195/1098 are newcomers. And just to labou=
r
>> the
>> point, a newcomer is not a returnee after 10 years, but someone who has
>> never
>> attended before.
>=20
> hope treated equal with all participants,

The new attendee, same as the old attendee gets to have everyone shut up wh=
en they go to the mike. If you have a draft and a relevant presentation, yo=
u can usually get time at a WG meeting regardless of how many meetings you'=
ve attended. Knowing that you should do these things is the learning curve =
that every one of us must go through.

>> This number (around 10%) seems consistent over all meetings. So naively,=
 we
>> should be growing our attendance by around 300 per year.
>>=20
>=20
> agree

But as both you and Adrian Farrel said, a lot of these don't come back. May=
be a more relevant statistic for the churn would be to count the third-time=
 attendees.

Millions of people go sailing for the first time each year. A huge proporti=
on of those get sea sick or bored, and never do it again. That's not a usef=
ul metric to assess the size of the sailing community.

>> That we are not reflects our inability to retain, not our inability to
>> attract
>> (assuming that we are not completely refreshing the IETF attendance ever=
y
>> three
>> or four years). Should not be rocket science to follow up with some
>> newcomers to
>> find out why they only attend once and never come back.
>>=20
>=20
> For me I still did n't attend but understand that many old
> participants are biased and there seems no equal opportunity, people
> don't always follow the IETF mission and procedure, they just follow
> their ways as long there was no complain.
>=20
> I call all newcomers to open a new WG and start complaining because we
> have to discuss why we were disapointed of the IETF and IESG, and even
> the Internet Society.
>=20
> Please note that I will focus my volunteering work in complaining and
> fixing the discourage I found so far.

OK, but if something or someone discouraged you, speak up. Existing members=
 can't help you if you don't tell us what's wrong.

Yoav



From swb@internet2.edu  Fri Nov  9 08:08:57 2012
Return-Path: <swb@internet2.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 16B4C21F86D5 for <ietf@ietfa.amsl.com>; Fri,  9 Nov 2012 08:08:57 -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 g-ClsyToKkdR for <ietf@ietfa.amsl.com>; Fri,  9 Nov 2012 08:08:56 -0800 (PST)
Received: from int-proxy01.merit.edu (int-proxy01.merit.edu [207.75.116.230]) by ietfa.amsl.com (Postfix) with ESMTP id 344AC21F868F for <ietf@ietf.org>; Fri,  9 Nov 2012 08:08:56 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by int-proxy01.merit.edu (Postfix) with ESMTP id 4292510002B; Fri,  9 Nov 2012 11:08:55 -0500 (EST)
X-Virus-Scanned: amavisd-new at int-proxy01.merit.edu
Received: from int-proxy01.merit.edu ([127.0.0.1]) by localhost (int-proxy01.merit.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D656mSHS0Ajv; Fri,  9 Nov 2012 11:08:51 -0500 (EST)
Received: from swbi2mbp.local (cpe-67-241-75-185.twcny.res.rr.com [67.241.75.185]) by int-proxy01.merit.edu (Postfix) with ESMTPSA id A1F90100002; Fri,  9 Nov 2012 11:08:51 -0500 (EST)
Message-ID: <509D13E3.8010009@internet2.edu>
Date: Fri, 09 Nov 2012 09:32:03 -0500
From: Scott Brim <swb@internet2.edu>
Organization: Internet2
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: Ted Hardie <ted.ietf@gmail.com>
Subject: Re: Common sense, process, and the nature of change
References: <CA+9kkMCMX13q0EAwyDYLjLnPrYusaq=NXrGNiMj2Wo5ecR09bg@mail.gmail.com>
In-Reply-To: <CA+9kkMCMX13q0EAwyDYLjLnPrYusaq=NXrGNiMj2Wo5ecR09bg@mail.gmail.com>
X-Enigmail-Version: 1.4.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Nov 2012 16:08:57 -0000

Ted: Very nice but I would go further.  You believe that everyone in the
IETF has either internalized the mission or will in the course of
participating.  I think the IETF has already lost that unity of mission,
particularly with the influx of corporate participants who were not
around in the idealistic days.  For them the new normal is to use the
IETF as a tool for creating competitive advantage - bleeding the golden
goose while they feed it.  Even back at the IETF@20 celebration, when
long-time participants got up and spoke passionately (and really well)
about the shared mission and values, there were people listening who
reacted with "that's not why I'm here, I think they're out of touch with
the new IETF".  Even having a unified mission is no longer a shared
principle.  So I would guess the main concern, the main anxiety leading
to love of process is not that our future leaders won't be able to
execute on the shared mission we all feel - rather it is that our future
leaders won't have the same mission or even the same principles we do
now, and they cannot be trusted to execute based common sense - there
won't be any "common" sense.

Scott

On 11/08/12 14:46, Ted Hardie allegedly wrote:
> At the plenary last night, Andrew Sullivan set off a series of
> conversations at the mic lines by asking what seems at first to be a
> fairly simple question:  why is that we seem now to have more process
> and less reliance on common sense?  As those at the plenary will have
> noticed, the conversation did not stick directly to that question, but
> went through some interesting history, called for a bit of data,
> entertained a plea for mentoring, and then questioned whether point
> solutions or major change would actually work to improve the IETF.
> 
> Thinking a bit about the directions that conversation took, I think
> there is both a relatively simple answer to Andrew's question and a
> much larger piece of context that need to be teased out of the
> discussion.  The relatively simple answer is that we don't just use
> common sense any more because we don't want to trust individuals as
> much as we used to.  That lack of trust isn't directed at the current
> IESG, IAOC,  or IAB, but at future incumbents.  We have come to the
> idea that allowing a current set of office-holders to make ad hoc
> decisions implies that all later incumbents will share that ability.
> Since we don't know those later incumbents (how could we?), we don't
> trust them; since we don't trust them, we don't want to cede to them a
> power that might later get abused.  So we attempt to use structure and
> process to restrict those unknown future incumbents.  That's
> interesting in part because we believe in precedent enough to worry
> that ceding decision making will grant to later officer holders
> equivalent power, but we don't believe in it enough to believe it will
> guide what the later officer holders will do.  That, again, likely
> stems from a lack of trust.
> 
> So why don't we trust the future IETF NomCom that picks those folks or
> the incumbents when picked?
> 
> I think that's where the larger context comes in.  The IETF is not
> simply an engineering organization, it is a mission-based
> organization.  Our mission is to make the Internet work and grow.
> Belief in that mission is something built into the context of the
> IETF, and it is part of what helps each of us guide our decisions
> here.  Where some SDOs get compromises entirely by horse-trading, many
> of the compromises that let the IETF work by rough consensus actually
> come about because of that shared mission.  We recognize that
> compromise to get interoperability is a key part of what lets the
> Internet continue to work and grow.  We both give our technical
> insight to that mission and we subordinate our technical desires to
> it.
> 
> That works in part because we know that others here share that
> mission.  We don't recite it at meetings or make it the subject of
> ceremonies, but we recognize that spending enough time here will cause
> both that mission and the whole-Internet engineering perspective to
> seep into the bones of the participants.  We get a direct sense of it
> from those with whom we interact (Pete and Murray's exchange last
> night was a great precis of that process), we get an indirect sense of
> it from broader social networks, and we have institutionalized it in
> things like the NomCom eligibility rules.
> 
> I suspect that some of the trust issues we have with imagined future
> incumbents actually comes from a subconscious fear that we won't be as
> successful at passing on a belief in that mission as we have so far
> been.  That may be because the current mechanisms are largely ad hoc
> (as Joe's comments on mentoring hinted); it may be more free form than
> that.  To counter that concern, we may want to extend the methods we
> already do have (Edu teams, newcomers socials, and so on) for longer
> parts of the initial participation periods.  We may even want to
> consider new ways of generating affiliation to our core goals.
> However we do it, it seems likely that energy put into making sure
> that the IETF's mission is part of each participant's understanding of
> their work will return benefits both to the IETF now and when those
> unknown future incumbents take office.
> 
> The other thing that context suggests is probably equally important.
> As a mission-based organization, we have a natural touchstone for
> evaluating change.  If a proposed change furthers the mission of the
> organization, we can likely manage the transition it implies, whatever
> the scale might be.  If it hinders the mission of the organization, it
> shouldn't be taken on however cheaply and easily it might be done.
> 
> Maintaining the power of the incumbents? Not important.  Maintaining
> the current structures? Not important.  Change for change's sake?  Not
> valuable.  Making sure the mission gets done?  Pretty much the only
> thing that matters.
> 
> Since this is all long since baked into the bones of most IETF
> participants, this no doubt seems a bit trite or even silly.  But
> there are times when it is important to say things out loud, and this
> may be one of them. If we are considering why change in the IETF
> increasingly looks like ossification and if we are considering how to
> fix that, we should keep our mission in mind.
> 
> My two cents as an individual,
> 
> Ted Hardie
> 

From ietf@meetecho.com  Fri Nov  9 09:15:55 2012
Return-Path: <ietf@meetecho.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ED62D21F8760 for <ietf@ietfa.amsl.com>; Fri,  9 Nov 2012 09:15:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.699
X-Spam-Level: 
X-Spam-Status: No, score=-1.699 tagged_above=-999 required=5 tests=[AWL=-0.980, BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245]
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 BtiePTkK+rwd for <ietf@ietfa.amsl.com>; Fri,  9 Nov 2012 09:15:55 -0800 (PST)
Received: from smtpdg2.aruba.it (smtpdg2.aruba.it [62.149.158.232]) by ietfa.amsl.com (Postfix) with ESMTP id 8FF7221F875A for <ietf@ietf.org>; Fri,  9 Nov 2012 09:15:54 -0800 (PST)
Received: from [130.129.19.11] ([130.129.19.11]) by smtpcmd01.ad.aruba.it with bizsmtp id MVFq1k00t0ELJoa01VFrzw; Fri, 09 Nov 2012 18:15:52 +0100
Message-ID: <509D3A44.6000409@meetecho.com>
Date: Fri, 09 Nov 2012 18:15:48 +0100
From: Meetecho IETF support <ietf@meetecho.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Meetecho recording of the Plenary session
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Nov 2012 17:15:56 -0000

Dear all,

the full recording (synchronized video, audio, slides and jabber room)
of the Plenary session at IETF-85 is available.

You can watch it by accessing the following URL:
http://www.meetecho.com/ietf85/recordings

In case of problems with the playout, just drop an e-mail to 
ietf-team@meetecho.com.

Cheers,
the Meetecho team

-- 
Meetecho s.r.l.
Web Conferencing and Collaboration Tools
www.meetecho.com

From carlosm3011@gmail.com  Fri Nov  9 09:24:39 2012
Return-Path: <carlosm3011@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A725C21F8743 for <ietf@ietfa.amsl.com>; Fri,  9 Nov 2012 09:24:38 -0800 (PST)
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.000,  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 cBA1HoKgrpQf for <ietf@ietfa.amsl.com>; Fri,  9 Nov 2012 09:24:38 -0800 (PST)
Received: from mail-da0-f44.google.com (mail-da0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id 019CD21F8641 for <ietf@ietf.org>; Fri,  9 Nov 2012 09:24:36 -0800 (PST)
Received: by mail-da0-f44.google.com with SMTP id h15so1870464dan.31 for <ietf@ietf.org>; Fri, 09 Nov 2012 09:24:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=jv73RvmB0MGbkoCXpkA2K405Q7zkOvr6Q/NwAbYPoNE=; b=NpyrALwOwgr24RMJo0dtajJRVIp8HGf5O4TgHNIJkjPigXDGmnnhmdie2kNzC1vqM6 mK2nKxbQFJsnXfmdEKE6kXC8Pmf1jsUhb2QpFkOT7u2JRgBV/kyLqYZJUthGiQe7ViXA oJHkGmj3ZwwbQ87GrEv8GM+ZU/2GsU2b6BU9tQwvqVNrNxzxOcQxWLP9ufwj0WD2UL9K /dmzKAV3HgHqElpglwzukF8/SXtd4wzWSc9fi0DJwKxMcOzuaJ67NzJIpAxvqf8jww27 B6MNDVy1YsYlVOLWdS6eNvpN1SscZoeVy4qiMbblohCcNy2luVYuvRxRNMmBW3vwdO3f e78Q==
Received: by 10.68.241.133 with SMTP id wi5mr35435604pbc.48.1352481876856; Fri, 09 Nov 2012 09:24:36 -0800 (PST)
Received: from ?IPv6:2001:df8:0:16:d50a:342d:e559:209b? ([2001:df8:0:16:d50a:342d:e559:209b]) by mx.google.com with ESMTPS id v9sm18241707paz.6.2012.11.09.09.24.34 (version=SSLv3 cipher=OTHER); Fri, 09 Nov 2012 09:24:35 -0800 (PST)
Message-ID: <509D3C52.1020007@gmail.com>
Date: Fri, 09 Nov 2012 12:24:34 -0500
From: "Carlos M. martinez" <carlosm3011@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Is there ongoing work on SNMP IPv6 mibs ?
References: <50985590.5080507@gmail.com> <50985769.1040704@viagenie.ca>
In-Reply-To: <50985769.1040704@viagenie.ca>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Nov 2012 17:24:39 -0000

I'll take the silence as a NO :-)

So, as a humble kinda newcomer, where should I take some ideas regarding
IPv6 mibs ? Which should be the appropiate WG ?

Cheers!

~Carlos

On 11/5/2012 7:18 PM, Simon Perreault wrote:
> Le 2012-11-05 19:10, Carlos M. martinez a écrit :
>> Other than the CGN-mib we discussed today in sunset4, I wondered whether
>> is there ongoing work on this topic.
> 
> What do you mean exactly? Because there is nothing IPv6-specific in the
> CGN MIB (or NAT MIB), it's all address-family agnostic...
> 
> Simon

From sm@resistor.net  Fri Nov  9 09:46:17 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5486621F875F for <ietf@ietfa.amsl.com>; Fri,  9 Nov 2012 09:46:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.484
X-Spam-Level: 
X-Spam-Status: No, score=-102.484 tagged_above=-999 required=5 tests=[AWL=0.115, 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 yW30XEvAXVq7 for <ietf@ietfa.amsl.com>; Fri,  9 Nov 2012 09:46:16 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4514B21F8501 for <ietf@ietf.org>; Fri,  9 Nov 2012 09:46:16 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id qA9Hk7RM014254; Fri, 9 Nov 2012 09:46:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1352483172; bh=+J2mD6adUQNOnGB610IxpVjvndyFgBAaeVYTqgbF7as=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=B2RyaiWxTR5QvLJ+pixpHmS/mKVk5+akX42ce0+tFBquMpaPK7sO5mARCzgIK2DFW 3fbTAIPYg7SYCSqmk+ugNVbLVtSPR4e8qSGlLythIYYYbJzfjImx+FAAIeudpU1I58 tqgATxzjjW4amGJQFQRJa632A0HHSFYMv/Bj0QVQ=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1352483172; i=@resistor.net; bh=+J2mD6adUQNOnGB610IxpVjvndyFgBAaeVYTqgbF7as=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=bq9g32OmwOYdGwVvArU8FBDYyXXxMs3+q0b5ugpa1f0sKajrEsWcpnmVPBOU2uMe8 1ji1/4+vSd7dJrlFx9XFDA0FF9c3whMRw03AXb395RcCyVsrPoOdkJ8YJfh4hfL0cV 21DBuUYqg3rFEmPURcxhoeowpMTWyjMpIHY+AYns=
Message-Id: <6.2.5.6.2.20121109074113.0b2000f8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 09 Nov 2012 09:28:53 -0800
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
From: SM <sm@resistor.net>
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
In-Reply-To: <CADnDZ8_v3M1fNtkOV4rU1F-iaMC+2qvKhR353vwESiQsfh70MQ@mail.g mail.com>
References: <CADnDZ8-fjxfgJys8sE10DdZ08tB8HdaTQXbPj2d7-OuQOGi9Pg@mail.gmail.com> <CADnDZ8_v3M1fNtkOV4rU1F-iaMC+2qvKhR353vwESiQsfh70MQ@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Nov 2012 17:46:17 -0000

Hi Abdussalam,
At 06:31 09-11-2012, Abdussalam Baryun wrote:
>I am newcomer and not able to attend because most of meeting in
>America instead of Europe.

Most of the money comes from North Americans.  There is some 
historical information in RFC 3717.

>I don't know how long do they remain, for me I am feeling disapointed.

Could you please elaborate on why you are feeling disappointed?

>hope treated equal with all participants,

The problem with treating everyone as equals is that the newcomer has 
the same opportunity as the person who has been attending the IETF 
meetings since a long time.  In practice, newcomers are given a 
slight advantage.  It depends on whom you are dealing with.  The 
suggestion is to be patient with the old people.

>For me I still did n't attend but understand that many old
>participants are biased and there seems no equal opportunity, people
>don't always follow the IETF mission and procedure, they just follow
>their ways as long there was no complain.

The mission says that the IETF will make the Internet work 
better.  That is the public relations explanation.  The better 
explanation could be like this: Let's say I dislike you and we are 
both part of a group writing a specification;  the mission is to get 
that specification written.  The problem is for the people taking 
decisions to see how to get us both to agree so that the group can 
produce a specification.

Now, let's say that you did not win the argument.  If you feel 
strongly about the argument, e.g. you want to prove that you are 
right, you believe that something bad will happen if the protocol is 
designed in such a way, etc., you can complain about it.  If nobody 
complains there is an assumption that everything is ok.

If you want to complain, explain what was wrong and what you would 
like to be done about it.  I suggest reading RFC 4144.  The 
procedures are there in case you feel that you have been ignored and 
you want to do something about it.

>I call all newcomers to open a new WG and start complaining because we
>have to discuss why we were disapointed of the IETF and IESG, and even
>the Internet Society.

You don't need a working group to discussion; you can discuss on this 
mailing list.  It is likely that the IESG will take action on your 
proposal if you can build support for it.

By the way, your message does not explain why you are disappointed 
with the Internet Society.

Regards,
-sm 


From randy_presuhn@mindspring.com  Fri Nov  9 10:26:36 2012
Return-Path: <randy_presuhn@mindspring.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 708E821F8770 for <ietf@ietfa.amsl.com>; Fri,  9 Nov 2012 10:26:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.606
X-Spam-Level: 
X-Spam-Status: No, score=-98.606 tagged_above=-999 required=5 tests=[AWL=-1.804, BAYES_50=0.001, DATE_IN_FUTURE_24_48=3.196, 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 V9nFOVQ0Q-5O for <ietf@ietfa.amsl.com>; Fri,  9 Nov 2012 10:26:36 -0800 (PST)
Received: from elasmtp-scoter.atl.sa.earthlink.net (elasmtp-scoter.atl.sa.earthlink.net [209.86.89.67]) by ietfa.amsl.com (Postfix) with ESMTP id CD0A021F8790 for <ietf@ietf.org>; Fri,  9 Nov 2012 10:26:35 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=cBod/aqHLUsEbyLy+4tF1/UmyoXooGCvVhBmN+P9RxxbBhrQww2TLCcLVCjjxeHv; h=Received:Message-ID:From:To:References:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE:X-ELNK-Trace:X-Originating-IP;
Received: from [99.30.227.99] (helo=oemcomputer) by elasmtp-scoter.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1TWtHm-00020S-D8 for ietf@ietf.org; Fri, 09 Nov 2012 13:26:34 -0500
Message-ID: <002201cdbf70$ecd2e920$6b01a8c0@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: "IETF" <ietf@ietf.org>
References: <CA+9kkMCMX13q0EAwyDYLjLnPrYusaq=NXrGNiMj2Wo5ecR09bg@mail.gmail.com> <509D13E3.8010009@internet2.edu>
Subject: Re: Common sense, process, and the nature of change
Date: Sat, 10 Nov 2012 10:26:37 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
X-ELNK-Trace: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d88868e0cd313c0eb97e64ac12669dbdda97b3c8c996b9e57935350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 99.30.227.99
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Nov 2012 18:26:36 -0000

Hi -

> From: "Scott Brim" <swb@internet2.edu>
> To: "Ted Hardie" <ted.ietf@gmail.com>
> Cc: "IETF" <ietf@ietf.org>
> Sent: Friday, November 09, 2012 6:32 AM
> Subject: Re: Common sense, process, and the nature of change
>
> Ted: Very nice but I would go further.  You believe that everyone in the
> IETF has either internalized the mission or will in the course of
> participating.  I think the IETF has already lost that unity of mission,
> particularly with the influx of corporate participants who were not
> around in the idealistic days.  For them the new normal is to use the
> IETF as a tool for creating competitive advantage -  ....

As I see it, that "new normal" has been the norm as long as I've been
working on IETF-related stuff - over twenty years.

Every organization has some sort of "mission", though the expectation
that all (or even most) participants have fully bought into and internalized
that mission is probably at best a useful fiction.  It is true that behaving as
though one is on board with the mission will help gain the cooperation
of others, and, in the case of the IETF's mission, yield useful work.  But
it's no guarantee, and my experience has been that other considerations
seem to take precedence over the IETF mission for many participants.
Even in those cases, however, behaving as though those participants
were primarily motivated by the IETF mission generally seems the best 
way to sustain the collaboration, or at least the illusion of collaboration,
and hopefully get *something* done.

Cynical? Perhaps, but in other threads we get glimpses of the litigious
hell that is the probable alternative.

Randy


From brian.e.carpenter@gmail.com  Fri Nov  9 10:57:37 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 63F5F21F8447 for <ietf@ietfa.amsl.com>; Fri,  9 Nov 2012 10:57:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.591
X-Spam-Level: 
X-Spam-Status: No, score=-103.591 tagged_above=-999 required=5 tests=[AWL=0.008, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, 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 thSfY3tGrWyg for <ietf@ietfa.amsl.com>; Fri,  9 Nov 2012 10:57:36 -0800 (PST)
Received: from mail-da0-f44.google.com (mail-da0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id D839921F8445 for <ietf@ietf.org>; Fri,  9 Nov 2012 10:57:36 -0800 (PST)
Received: by mail-da0-f44.google.com with SMTP id h15so1900362dan.31 for <ietf@ietf.org>; Fri, 09 Nov 2012 10:57:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=DO892Nscaca8O7o67sek0g082hD+jAYwO9WXAjsnpFk=; b=bXuj0JeZBOBI6bxApCFfU3IIygPFVl3SjycUi13s5BBUh4yMRmLVx/BDB1TyqKj2dn FklNOlCVPwFR/Bu+w3pZAG6IgepktkGUgNE2hX16LFCE7VTyRJlXTjVXbyfaC9pDztN7 EdvEXSYc/2g0qzy+gsTUYi3wlAAKQZfs2/PIfW+JWxhnpedE9SeW0dmwAFwqDdPY7fG8 oPZ9oNsMrTE+1D1VFF/YBTqbImdITl5zWz2eyhIhG8TLuRX6iKoFbwEfv40Li658NClN o7ASZfVoChdz4yCcXrWG7utltA22Uj36UH6GJuD5EUBth2LS89i6KM8pB1uPk03xixrP ciEg==
Received: by 10.68.237.135 with SMTP id vc7mr29529418pbc.2.1352487456591; Fri, 09 Nov 2012 10:57:36 -0800 (PST)
Received: from [130.129.19.51] (dhcp-1333.meeting.ietf.org. [130.129.19.51]) by mx.google.com with ESMTPS id o1sm18338357paz.34.2012.11.09.10.57.35 (version=SSLv3 cipher=OTHER); Fri, 09 Nov 2012 10:57:35 -0800 (PST)
Message-ID: <509D522C.2090006@gmail.com>
Date: Fri, 09 Nov 2012 18:57:48 +0000
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Randy Presuhn <randy_presuhn@mindspring.com>
Subject: Re: Common sense, process, and the nature of change
References: <CA+9kkMCMX13q0EAwyDYLjLnPrYusaq=NXrGNiMj2Wo5ecR09bg@mail.gmail.com>	<509D13E3.8010009@internet2.edu> <002201cdbf70$ecd2e920$6b01a8c0@oemcomputer>
In-Reply-To: <002201cdbf70$ecd2e920$6b01a8c0@oemcomputer>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Nov 2012 18:57:37 -0000

On 10/11/2012 18:26, Randy Presuhn wrote:
> Hi -
> 
>> From: "Scott Brim" <swb@internet2.edu>
>> To: "Ted Hardie" <ted.ietf@gmail.com>
>> Cc: "IETF" <ietf@ietf.org>
>> Sent: Friday, November 09, 2012 6:32 AM
>> Subject: Re: Common sense, process, and the nature of change
>>
>> Ted: Very nice but I would go further.  You believe that everyone in the
>> IETF has either internalized the mission or will in the course of
>> participating.  I think the IETF has already lost that unity of mission,
>> particularly with the influx of corporate participants who were not
>> around in the idealistic days.  For them the new normal is to use the
>> IETF as a tool for creating competitive advantage -  ....
> 
> As I see it, that "new normal" has been the norm as long as I've been
> working on IETF-related stuff - over twenty years.

Which is exactly why Harald wrote the mission statement in the first
place. Inevitably there will be people who come here for the benefit
of their employer's business objectives. It's the job of those who care
about the Internet as a whole to proselytise those people.

I agree with your cynicism, but IMHO the mission statement is the best
tool we have, so we should use it.

I think there is scope for a plenary rant about this, and for a new slide
in the newcomers' presentation, which quotes "reject kings and presidents"
but doesn't currently mention the mission statement afaik.

(http://www.ietf.org/newcomers.html does mention it, but I don't know
how many people start there.)

     Brian

From melinda.shore@gmail.com  Fri Nov  9 11:17:57 2012
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2658521F86D2 for <ietf@ietfa.amsl.com>; Fri,  9 Nov 2012 11:17:57 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FVhlsJ40QUDR for <ietf@ietfa.amsl.com>; Fri,  9 Nov 2012 11:17:34 -0800 (PST)
Received: from mail-ob0-f172.google.com (mail-ob0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id 9785221F86CF for <ietf@ietf.org>; Fri,  9 Nov 2012 11:17:34 -0800 (PST)
Received: by mail-ob0-f172.google.com with SMTP id wo10so966217obc.31 for <ietf@ietf.org>; Fri, 09 Nov 2012 11:17:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=KFr9co0YDToEil1sHeHi9Mm1ZX4/e9UUGwjFbnxor64=; b=vPZt5XVfxXoe0NZ3LcuYFdQU7Id3vx5kjPj6zqYUGt16lfMzzYP+vJOI4fptB5Nurb xswPR0Tr9aEz+W+pL1lzZYi30j4F0e4ZGUo9W5A3cRNx53NeNXhSH87WaDa14Rfr2SHA wSwX1VH/5zAt6CrgJdEXypQAcG4pWjcnEaue2r5KKq/DGG1KUn1+KSGx/cvzsG/CdSSB +1LdIVdq69b3YokCELi5w7c44GiFaRkYoH7+8F408roJ3Gl1Vt8tF3LYNjrgh94DR25D o5Or3tTtQk/10+ttRaoKkVxXxtQI7ssb7uXx+NEuV+yUIMijMuJerdWug5dh9KsWUl4C 8Gzg==
Received: by 10.60.171.200 with SMTP id aw8mr8566012oec.112.1352488654180; Fri, 09 Nov 2012 11:17:34 -0800 (PST)
Received: from [107.17.123.237] (dhcp107-17-123-237.hil-atlahhh.atl.wayport.net. [107.17.123.237]) by mx.google.com with ESMTPS id hz6sm30361875obb.1.2012.11.09.11.17.33 (version=SSLv3 cipher=OTHER); Fri, 09 Nov 2012 11:17:33 -0800 (PST)
Message-ID: <509D56CD.9000508@gmail.com>
Date: Fri, 09 Nov 2012 10:17:33 -0900
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Common sense, process, and the nature of change
References: <CA+9kkMCMX13q0EAwyDYLjLnPrYusaq=NXrGNiMj2Wo5ecR09bg@mail.gmail.com> <509D13E3.8010009@internet2.edu> <002201cdbf70$ecd2e920$6b01a8c0@oemcomputer>
In-Reply-To: <002201cdbf70$ecd2e920$6b01a8c0@oemcomputer>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Nov 2012 19:17:57 -0000

On 11/10/2012 9:26 AM, Randy Presuhn wrote:
> Even in those cases, however, behaving as though those participants
> were primarily motivated by the IETF mission generally seems the best 
> way to sustain the collaboration, or at least the illusion of collaboration,
> and hopefully get *something* done.

This is quite possibly where peer pressure or groupthink or
whatever can possibly have a gating effect, I hope.  In the
best of all possible worlds understanding that cranking out
vast numbers of crappy documents reduces your effectiveness
within the organization because other participants read your
crappy documents and assume that you don't know what you're
doing.  Reputation within the organization matters.

That said, it's also important to think about how we make
decisions.  Consensus-based decision-making does require some
sort of shared commitment to the process and to organizational
happy stuff, because it's otherwise too easy to block progress.
Again, I think it's worthwhile to find some way to communicate
that if you're working within the IETF and you promote things
that are good for your employer and bad for everybody else,
people notice and your overall effectiveness suffers.

Melinda


From nick@inex.ie  Fri Nov  9 11:22:24 2012
Return-Path: <nick@inex.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0BEC521F8705 for <ietf@ietfa.amsl.com>; Fri,  9 Nov 2012 11:22:24 -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 CRpGo1g9yaEd for <ietf@ietfa.amsl.com>; Fri,  9 Nov 2012 11:22:23 -0800 (PST)
Received: from mail.acquirer.com (mail.acquirer.com [IPv6:2a03:8900:0:100::5]) by ietfa.amsl.com (Postfix) with ESMTP id 1036821F86D2 for <ietf@ietf.org>; Fri,  9 Nov 2012 11:22:21 -0800 (PST)
X-Envelope-To: ietf@ietf.org
Received: from cupcake.foobar.org (twinkie.foobar.org [87.192.56.84]) (authenticated bits=0) by mail.acquirer.com (8.14.4/8.14.4) with ESMTP id qA9JLCQ1038659 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Fri, 9 Nov 2012 19:21:18 GMT (envelope-from nick@inex.ie)
Message-ID: <509D57E4.5080906@inex.ie>
Date: Fri, 09 Nov 2012 19:22:12 +0000
From: Nick Hilliard <nick@inex.ie>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: "Carlos M. martinez" <carlosm3011@gmail.com>
Subject: Re: Is there ongoing work on SNMP IPv6 mibs ?
References: <50985590.5080507@gmail.com> <50985769.1040704@viagenie.ca> <509D3C52.1020007@gmail.com>
In-Reply-To: <509D3C52.1020007@gmail.com>
X-Enigmail-Version: 1.4.5
X-Company-Info-1: Internet Neutral Exchange Association Limited. Registered in Ireland No. 253804
X-Company-Info-2: Registered Offices: 1-2, Marino Mart, Fairview, Dublin 3
X-Company-Info-3: Internet Neutral Exchange Association Limited is limited by guarantee
X-Company-Info-4: Offices: 4027 Kingswood Road, Citywest, Dublin 24.
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Nov 2012 19:22:24 -0000

On 09/11/2012 17:24, Carlos M. martinez wrote:
> So, as a humble kinda newcomer, where should I take some ideas regarding
> IPv6 mibs ? Which should be the appropiate WG ?

draft-ietf-idr-bgp4-mibv2 for bgp stuff.  What ideas do you have and maybe
someone could point you in the right direction.

Nick


From fred@cisco.com  Fri Nov  9 13:05:27 2012
Return-Path: <fred@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DDA3621F8661 for <ietf@ietfa.amsl.com>; Fri,  9 Nov 2012 13:05:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.098
X-Spam-Level: 
X-Spam-Status: No, score=-110.098 tagged_above=-999 required=5 tests=[AWL=-0.500, BAYES_00=-2.599, GB_AFFORDABLE=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, 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 vefypxK0AB-n for <ietf@ietfa.amsl.com>; Fri,  9 Nov 2012 13:05:26 -0800 (PST)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id A344A21F8630 for <ietf@ietf.org>; Fri,  9 Nov 2012 13:05:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=82545; q=dns/txt; s=iport; t=1352495125; x=1353704725; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=pL929olDOg10CTZ8S+O717ey9G05cHFVdP+DWOBHp4Y=; b=f4npWWlLg343dhu4yUC2d9ZwEtbbrsEUYO1UYuOHp+xAYild7rppVwlz 0mxIuhcFib87g0xJJ7rVn6aU4RSoILv+8kk1ZVh9pUw3eNIWbOJdfGzTY QzHqeJm8iqmhZS/ViGVA2Q/poZOJrV7G17wF7DPx/vi9W0fcIunMxN6cn U=;
X-Files: ietf-meeting-data.xlsx : 54704
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAB9vnVCtJXHB/2dsb2JhbABEgknAeYEIgh4BAQEDARIBYgQFCwIBCBgKJAIwJQIEAQ0NBgYOh2IGC51zoAgEjBSFaWEDjnuVWIFrgm+CGQ
X-IronPort-AV: E=McAfee;i="5400,1158,6891"; a="140708070"
Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by rcdn-iport-5.cisco.com with ESMTP; 09 Nov 2012 21:05:25 +0000
Received: from xhc-aln-x13.cisco.com (xhc-aln-x13.cisco.com [173.36.12.87]) by rcdn-core2-6.cisco.com (8.14.5/8.14.5) with ESMTP id qA9L5POT000369 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 9 Nov 2012 21:05:25 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.68]) by xhc-aln-x13.cisco.com ([173.36.12.87]) with mapi id 14.02.0318.001; Fri, 9 Nov 2012 15:05:24 -0600
From: "Fred Baker (fred)" <fred@cisco.com>
To: SM <sm@resistor.net>, Abdussalam Baryun <abdussalambaryun@gmail.com>
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
Thread-Topic: Newcomers [Was: Evolutionizing the IETF]
Thread-Index: AQHNvp+wdq7E6o7oSCOOOn8+ZNRnaJfiYzIA
Date: Fri, 9 Nov 2012 21:05:23 +0000
Message-ID: <8C48B86A895913448548E6D15DA7553B19E215@xmb-rcd-x09.cisco.com>
References: <CADnDZ8-fjxfgJys8sE10DdZ08tB8HdaTQXbPj2d7-OuQOGi9Pg@mail.gmail.com> <CADnDZ8_v3M1fNtkOV4rU1F-iaMC+2qvKhR353vwESiQsfh70MQ@mail.gmail.com> <6.2.5.6.2.20121109074113.0b2000f8@resistor.net>
In-Reply-To: <6.2.5.6.2.20121109074113.0b2000f8@resistor.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.82.241.254]
x-tm-as-product-ver: SMEX-10.2.0.1135-7.000.1014-19350.005
x-tm-as-result: No--56.281700-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: multipart/mixed; boundary="_004_8C48B86A895913448548E6D15DA7553B19E215xmbrcdx09ciscocom_"
MIME-Version: 1.0
Cc: IETF list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Nov 2012 21:05:28 -0000

--_004_8C48B86A895913448548E6D15DA7553B19E215xmbrcdx09ciscocom_
Content-Type: multipart/alternative;
	boundary="_000_8C48B86A895913448548E6D15DA7553B19E215xmbrcdx09ciscocom_"

--_000_8C48B86A895913448548E6D15DA7553B19E215xmbrcdx09ciscocom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable


On Nov 9, 2012, at 12:28 PM, SM wrote:

> At 06:31 09-11-2012, Abdussalam Baryun wrote:
>> I am newcomer and not able to attend because most of meeting in
>> America instead of Europe.
>
> Most of the money comes from North Americans.  There is some historical i=
nformation in RFC 3717.

I'd suggest a more thorough analysis.

Data from https://www.ietf.org/meeting/upcoming.html and https://www.ietf.o=
rg/meeting/past.html. Take a look at the attached spreadsheet.

IETF demographics and meeting location policy have changed over time.

Originally, in 1986, not only was the IETF entirely American, it was entire=
ly US Government, and nobody else was invited. That changed pretty quickly,=
 but the community attending remained predominantly US for some time. So me=
etings before 1993 all occurred in North America, and if truth be told, the=
 reason that the meeting in August 1990 was outside the US was that it had =
been intended to be in Seattle, the host had a problem, and UBC came to the=
 rescue.

Starting in 1993, we noted that the demographics had changed; about one in =
six IETF participants came from Europe. So, we tried to place one meeting i=
n six in Europe. We had a small group attending from Australia, and in 2000=
 had a meeting there in recognition of the fact. But by that time, we were =
starting to have a more significant attendance from Asia, notably Japan. So=
 we changed policy to trying to position three meetings in six in North Ame=
rica, two in Europe, and one in Asia+Australia. And starting (IIRC) in 2005=
, we simplified that policy to having one meeting each year in Asia, Europe=
, and North America.

Regarding that last policy, we have unfortunately had some problems; one me=
eting that we intended to have in Asia recently fell through, and we had to=
 move it somewhere, and in another recent case the Asian venues we were loo=
king at essentially priced themselves out of the market. Our Asian friends =
told us that a meeting in Vancouver was an acceptable compromise; getting a=
 visa wasn't as hard for them as a US visa, and it was not too hard to get =
to. So we have had at least two meetings in Vancouver that we fully intende=
d to have in Asia.

Since 2004, we have in fact had about 1/3 of our meetings in Europe. If any=
one has been shortchanged, it has been our Asian friends. "Where the money =
came from" was an issue in the 1990's - we had to assume that a meeting out=
side the US would be financially short due to US participants not attending=
; in 2000, the meeting in San Diego had 2810 people and the meeting in Pitt=
sburg 2344, but the meeting in Adelaide had 1431. By 2004, distribution had=
 become roughly even - meetings that year had right around 1300 attendees r=
egardless of location. The issues are now related to success in finding aff=
ordable venues.






--_000_8C48B86A895913448548E6D15DA7553B19E215xmbrcdx09ciscocom_
Content-Type: text/html; charset="us-ascii"
Content-ID: <11A1A75C972C094AB3221B769F93D201@cisco.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body>
<div class=3D"BodyFragment"><font size=3D"2"><span style=3D"font-size:10pt;=
">
<div class=3D"PlainText"><br>
On Nov 9, 2012, at 12:28 PM, SM wrote:<br>
<br>
&gt; At 06:31 09-11-2012, Abdussalam Baryun wrote:<br>
&gt;&gt; I am newcomer and not able to attend because most of meeting in<br=
>
&gt;&gt; America instead of Europe.<br>
&gt; <br>
&gt; Most of the money comes from North Americans.&nbsp; There is some hist=
orical information in RFC 3717.<br>
<br>
I'd suggest a more thorough analysis.<br>
<br>
Data from <a href=3D"https://www.ietf.org/meeting/upcoming.html">https://ww=
w.ietf.org/meeting/upcoming.html</a> and
<a href=3D"https://www.ietf.org/meeting/past.html">https://www.ietf.org/mee=
ting/past.html</a>. Take a look at the attached spreadsheet.<br>
<br>
IETF demographics and meeting location policy have changed over time. <br>
<br>
Originally, in 1986, not only was the IETF entirely American, it was entire=
ly US Government, and nobody else was invited. That changed pretty quickly,=
 but the community attending remained predominantly US for some time. So me=
etings before 1993 all occurred
 in North America, and if truth be told, the reason that the meeting in Aug=
ust 1990 was outside the US was that it had been intended to be in Seattle,=
 the host had a problem, and UBC came to the rescue.<br>
<br>
Starting in 1993, we noted that the demographics had changed; about one in =
six IETF participants came from Europe. So, we tried to place one meeting i=
n six in Europe. We had a small group attending from Australia, and in 2000=
 had a meeting there in recognition
 of the fact. But by that time, we were starting to have a more significant=
 attendance from Asia, notably Japan. So we changed policy to trying to pos=
ition three meetings in six in North America, two in Europe, and one in Asi=
a&#43;Australia. And starting (IIRC)
 in 2005, we simplified that policy to having one meeting each year in Asia=
, Europe, and North America.<br>
<br>
Regarding that last policy, we have unfortunately had some problems; one me=
eting that we intended to have in Asia recently fell through, and we had to=
 move it somewhere, and in another recent case the Asian venues we were loo=
king at essentially priced themselves
 out of the market. Our Asian friends told us that a meeting in Vancouver w=
as an acceptable compromise; getting a visa wasn't as hard for them as a US=
 visa, and it was not too hard to get to. So we have had at least two meeti=
ngs in Vancouver that we fully intended
 to have in Asia.<br>
<br>
Since 2004, we have in fact had about 1/3 of our meetings in Europe. If any=
one has been shortchanged, it has been our Asian friends. &quot;Where the m=
oney came from&quot; was an issue in the 1990's - we had to assume that a m=
eeting outside the US would be financially
 short due to US participants not attending; in 2000, the meeting in San Di=
ego had 2810 people and the meeting in Pittsburg 2344, but the meeting in A=
delaide had 1431. By 2004, distribution had become roughly even - meetings =
that year had right around 1300
 attendees regardless of location. The issues are now related to success in=
 finding affordable venues.<br>
<br>
<br>
</div>
</span></font></div>
<div class=3D"BodyFragment"><font size=3D"2"><span style=3D"font-size:10pt;=
">
<div class=3D"PlainText"><br>
<br>
<br>
</div>
</span></font></div>
</body>
</html>

--_000_8C48B86A895913448548E6D15DA7553B19E215xmbrcdx09ciscocom_--

--_004_8C48B86A895913448548E6D15DA7553B19E215xmbrcdx09ciscocom_
Content-Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet;
	name="ietf-meeting-data.xlsx"
Content-Description: ietf-meeting-data.xlsx
Content-Disposition: attachment; filename="ietf-meeting-data.xlsx";
	size=54704; creation-date="Fri, 09 Nov 2012 21:05:23 GMT";
	modification-date="Fri, 09 Nov 2012 21:05:23 GMT"
Content-ID: <771BB50E92ED0842A475B256E97D7764@cisco.com>
Content-Transfer-Encoding: base64

UEsDBBQABgAIAAAAIQDF3ldpnwEAAMIGAAATAAgCW0NvbnRlbnRfVHlwZXNdLnhtbCCiBAIooAAC
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAC0
ld9OwyAUxu9NfIeGW9OyeWGMWbeLqZe6xPkACKctjgIB9u/tPaWbmmWuWVZvSimc7/txCofRZFOr
ZAXOS6NzMswGJAHNjZC6zMn7/Dm9J4kPTAumjIacbMGTyfj6ajTfWvAJRmufkyoE+0Cp5xXUzGfG
gsaRwriaBey6klrGF6wEejsY3FFudAAd0tBokPHoEQq2VCF52uDnlgTDSTJt5zVWOWHWKslZQFDa
jNKjcQ6UPxG40uKALt2RZRgZxX0lrb/52+HTQnngIOtmaXEAqV4xnU4KSGbMhRdWIzvdKLo2bvFh
zCI7vbQjhKYoJAdh+LLGrGXeOmDCVwChVllss5pJvWc+4R8nexqbYc8gzfqicAcHrzAt/wnyY9BB
EnC3Ao3Py5MRZToMfdgq8D3nvRXtcsakg3gLDs917wC/tTs4hGPrBoHuXi7P+06ow7fdEzQ2vXni
6YuCXd5M8WmFB7TnH8/3uqf8sWrMnLEea66D8wH2xbGJTi0KgQsSvsvjsVLz7YgF+3zDg1oHzY0g
QBzxpvEGGn8BAAD//wMAUEsDBBQABgAIAAAAIQB9zFSeDQEAAN0CAAALAAgCX3JlbHMvLnJlbHMg
ogQCKKAAAgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAArJJNTsMwEIX3SNzBmn3jtCCEUJ1uEFJ3CIUDTO1pYhL/yHYhvT2GRUOkElWCpT3j5+/N
m/VmMD17pxC1swKWRQmMrHRK20bAa/20uAcWE1qFvbMk4EgRNtX11fqFekz5UWy1jyyr2CigTck/
cB5lSwZj4TzZXNm7YDDlY2i4R9lhQ3xVlnc8/NSAaqLJtkpA2KobYPXR55//os0NJVSYkEsXaOFD
JgtJZy+sxtBQEqCcfM7X8bujyNTAzwPdXg7k9nst6dHJgyGbznjmNCSyitQ8Eno/R7T8T6Ip8zif
oecfLnQ757o5ltXlLL+vwhhXag9mZ1H3I8gpqFOtePPUfMXFJ0tZfQIAAP//AwBQSwMEFAAGAAgA
AAAhAMuC89AOAQAAzgMAABoACAF4bC9fcmVscy93b3JrYm9vay54bWwucmVscyCiBAEooAABAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAKyTz2rDMAzG74O9g9F9cdJtZYw6PWwMet26BzCOEocm
drC1P3n7iRaStJTskqM+oe/7Idmb7W/biG8MsfZOQZakINAZX9SuUvC5f7t7AhFJu0I33qGCHiNs
89ubzTs2mngo2rqLgl1cVGCJumcpo7HY6pj4Dh13Sh9aTVyGSnbaHHSFcpWmaxmmHpCfeYpdoSDs
insQ+77j5P+9fVnWBl+9+WrR0ZUIScyFbKhDhaTgWJ7ELGFQkNcZHpZkiNQ3vMQB4lTPxT8uGm91
wOKDAl94SjGV52DWS8IY3ZgXq2s3rmOQ5iCyJSF+fDhEi0gjxCBFeezMvo7VkjCG70AXNKN2iSPP
fmH+BwAA//8DAFBLAwQUAAYACAAAACEAYfIATe4BAAAzAwAADwAAAHhsL3dvcmtib29rLnhtbIxS
TY+bMBC9V+p/sHwnEAfYNAJWaT7USFW1qtrds9cMwQq2kW0WVlX/ewfYtKl66cnjGfvNe28mux9U
Q17AOml0TpeLiBLQwpRSn3P6/dsxWFPiPNclb4yGnL6Co/fF+3dZb+zl2ZgLQQDtclp7327C0Ika
FHcL04LGSmWs4h6v9hy61gIvXQ3gVROyKEpDxaWmM8LG/g+GqSopYG9Ep0D7GcRCwz3Sd7VsHS2y
SjbwOCsivG2/cIW8h4aShjt/KKWHMqcJXk0PfyVs137sZINVxlIW07D4rfLBkpJ7WH6IYnQJLalN
f9KXrdbGT81zis7xzpudUajTuQcpfIfBWECg0apHCb37gzleyfAkdWn66fvrTdxP6SdZ+hrpJGmE
8HPuE8hz7ZHFXbzGpOfPX0cGKAnfYKfwptVkNracTqInJyT4KlA4BBxxgKL4QriXURGmTqgd1dmN
xMCeyuUIePt5V3PrJ/1vr9nNaza1v/YUvBFo23hMsHEURfhTGC06a3F6O6y8uQOD/+x8keFJOitz
+uMuYatDsl8FLDmugm1yiIJlumJBGh9ZEu8YixP287o6avhnd5QU1jhT+YUwKpzXBtdNhDAImLZv
PW9fkalhs7WiPu3JseFnHNisA7mgmVdm4XXfi18AAAD//wMAUEsDBBQABgAIAAAAIQD8Vr2h4QIA
AAUNAAANAAAAeGwvc3R5bGVzLnhtbOxX3U/bMBB/n7T/wfI7uO2AQZUEbZOq8TCEBJP26jhOatUf
ke1As79+Z6dtAh0URDXtoS9gO/f73YfvztfkcqkkuufWCaNTPD4eYcQ1M4XQVYp/3s2OzjFynuqC
SqN5ilvu8GX28UPifCv57Zxzj4BCuxTPva+nhDg254q6Y1NzDV9KYxX1sLUVcbXltHABpCSZjEZn
RFGhcccwVew1JIraRVMfMaNq6kUupPBt5MJIselVpY2luQRTl+MTytbccbNFrwSzxpnSHwMdMWUp
GN+28oJcEGDKktJo7xAzjfYpPgHqoGG60OZBz8InCOBKKkvcb3RPJZxMMMkSZqSxyENkwLBxONFU
8U7iG5UityIcllQJ2XbHEReDuZJTAlwLUiTY0Vnz7/Q0oPgln0b7dGqXsj1FMAbSQSSFlJt7nYQr
hIMsgfzy3OoZbNBqfdfWcIEaSqG7iCi3Q7qytB1PTgcAEhVmSW5sAaW3zqiQPN1Rlkheeoi4FdU8
/Pemhr+58R7yNEsKQSujqYQlWSNWC3CHcSlvQ3n+KnvuEZAvS6QbNVP+qkgxVHrIo/USPFktO8Ju
AwoegS560BiWfwchWteyDRURtXQ7EO13X6Pj/f6LFJVWfAi4scZz5mNbirn1yI6B8ZMddlw3Kud2
FttQrzFcar/bpz2f/jN7DvGBVH+ax4f8OdSX7ev/Nf2HDNtq12QH/TW8Gs91qJBsz3TKZbmzz+5E
QyMeNNz4NEZbwbrBW/D4Jdj4gsIckuKZkdI88AJ9hwfOSqEXMN1E26Cd5Y2QXuhgKfT/uSgKHmbF
UFSv5zndE8/nPfGAJ2/wayss0FUHcBiSXwzLFhyGx/fAz94HB3PfoP06PJ1ynQ+QjgNs7KxPk+CG
WwZv+RoB+TlAdHPQBgIpWiz7MSXy+TC/xwFmk7SgteAlbaS/23xMcb/+wQvRKLjTldSNuDc+UqS4
X3dSJ3ES63+/ZH8AAAD//wMAUEsDBBQABgAIAAAAIQAORPTfvAAAACUBAAAjAAAAeGwvZHJhd2lu
Z3MvX3JlbHMvZHJhd2luZzEueG1sLnJlbHOEj80KwjAQhO+C7xD2btJ6EJGmvYjQq9QHWNLtD7ZJ
yEaxb2+gFwXB07A77Dc7RfWaJ/GkwKOzGnKZgSBrXDvaXsOtueyOIDiibXFyljQsxFCV201xpQlj
OuJh9CwSxbKGIUZ/UorNQDOydJ5scjoXZoxpDL3yaO7Yk9pn2UGFTwaUX0xRtxpC3eYgmsWn5P9s
13WjobMzj5ls/BGhzIAhJiCGnqIGKdcNr5LL9CyoslBf5co3AAAA//8DAFBLAwQUAAYACAAAACEA
Fa+qPL0AAAArAQAAJAAAAHhsL2NoYXJ0c2hlZXRzL19yZWxzL3NoZWV0MS54bWwucmVsc4SPzQrC
MBCE74LvEPZu0noQkaZeRPAq9QGWZPuDbRKy8advby6CguBtZ5f9ZqbaP6dR3Cny4J2GUhYgyBlv
B9dpuDTH1RYEJ3QWR+9Iw0wM+3q5qM40YspP3A+BRaY41tCnFHZKselpQpY+kMuX1scJU5axUwHN
FTtS66LYqPjJgPqLKU5WQzzZEkQzh+z8n+3bdjB08OY2kUs/LJSN+MjNMhJjR0mDlO8dv4dS5sig
6kp9VaxfAAAA//8DAFBLAwQUAAYACAAAACEASCnKFxMBAACsAQAAGQAAAHhsL2NoYXJ0c2hlZXRz
L3NoZWV0MS54bWyMkE9PwzAMxe9IfIfId5qO/5rW7YIm7YCExOCetW4TrYkrxzDg0+N1A3bk9qw8
/16eZ4uP2Jt35BwoVTApSjCYampC6ip4WS8v7sFkcalxPSWs4BMzLObnZ7PaO5bsEcUoIuUKvMgw
tTbXHqPLBQ2Y9KUljk505M7mgdE141Ls7WVZ3troQoIDYcr/YVDbhhofqH6LmOQAYeydaIHsw5Bh
PhsTntge1WvAXT7R5osoPteu1z6T6yswO+Lthmi7N66aCvQIe8ualkHUAgqyI/NIGlyHj467kLLp
sVVPWdzdgOHQ+d9BaNjvmg2JUByl1/aoLctCzS2R/Awa0LDb6dENT4P+gFfNIfbvzPNvAAAA//8D
AFBLAwQUAAYACAAAACEAMA+IaxEHAADeHQAAEwAAAHhsL3RoZW1lL3RoZW1lMS54bWzsWU9vG0UU
vyPxHUZ7b2MndhpHdarYsVto00axW9TjeD32TjO7s5oZJ/ENtUckJERBXJC4cUBApVbiUj5NoAiK
1K/Am5nd9U48bpwSQEBzaL2zv/fmvd/7M3/26rXjmKFDIiTlSTOoXq4EiCQhH9Jk3Azu9ruXNgIk
FU6GmPGENIMpkcG1rXffuYo3VURigkA+kZu4GURKpZsrKzKEYSwv85Qk8G7ERYwVPIrxylDgI9Ab
s5XVSmV9JcY0CVCCY1B7ZzSiIUF9rTLYypV3GDwmSuqBkImeVk0cCYMdHlQ1Qk5lmwl0iFkzgHmG
/KhPjlWAGJYKXjSDivkLVrauruDNTIipBbIlua75y+QygeHBqplTjAfFpNVurXFlp9BvAEzN4zqd
TrtTLfQZAA5D8NTaUtZZ625UW7nOEsj+nNfdrtQrNRdf0r82Z3Oj1WrVG5ktVqkB2Z+1OfxGZb22
vergDcji63P4Wmu73V538AZk8etz+O6VxnrNxRtQxGhyMIfWAe12M+0FZMTZDS98A+AblQw+Q0E2
FNmlpxjxRC3KtRg/4KILAA1kWNEEqWlKRjiELG7jeCAo1hPgTYJLb+xQKOeG9FxIhoKmqhm8n2Ko
iJm+V8+/ffX8KXr1/MnJw2cnD384efTo5OH3VpcjeAMn47Lgy68/+f3LD9FvT796+fgzP16W8T9/
99FPP37qB0IFzSx68fmTX549efHFx79+89gD3xZ4UIb3aUwkuk2O0D6PwTdDjGs5GYjzSfQjTB0J
HIFuj+qOihzg7SlmPlyLuOTdE9A8fMDrkweOrb1ITBT1zHwzih3gLuesxYWXgJt6rhLD/Uky9k8u
JmXcPsaHvrnbOHFC25mk0DXzpHS4b0fEMXOP4UThMUmIQvodPyDE4919Sh1ed2kouOQjhe5T1MLU
S0mfDpxEmgndoDHEZerzGULtcLN7D7U483m9Qw5dJBQEZh7j+4Q5NF7HE4Vjn8o+jlmZ8FtYRT4j
e1MRlnEdqSDSY8I46gyJlD6ZOwL8LQX9JoZ+5Q37LpvGLlIoeuDTeQtzXkbu8IN2hOPUh+3RJCpj
35MHkKIY7XHlg+9yt0L0M8QBJwvDfY8SJ9xnN4K7dOyYNEsQ/WYiPLG8TriTv70pG2Fiugy0dKdT
xzR5XdtmFPq2neFt224G27CI+YrnxqlmvQj3L2zRO3iS7BGoivkl6m2Hftuhg/98h15Uyxffl2et
GLq03pDYvbbZeccLN94jylhPTRm5Jc3eW8ICNOzCoJYzh05SHMTSCH7qSoYJHNxYYCODBFcfUBX1
IpzCvr0aaCVjmakeS5RyCedFM+zVrfGw91f2tFnX5xDbOSRWu3xoh9f0cH7cKNQYq8bmTJtPtKYV
LDvZ2pVMKfj2JpNVtVFLz1Y1ppmm6MxWuKwpNudyoLxwDQYLNmFng2A/BCyvw7FfTw3nHczIUPNu
Y5SHxUThrwlR5rV1JMJDYkPkDJfYrJrY5Sk05592z+bI+dgsWAPSzjbCpMXi/FmS5FzBjGQQPF1N
LCnXFkvQUTNo1FfrAQpx2gxGcNKFn3EKQZN6L4jZGK6LQiVs1p5Zi6ZIZx43/FlVhcuLBQXjlHEq
pNrBMrIxNK+yULFEz2TtX63XdLJdjAOeZrKcFWsbkCL/mBUQaje0ZDQioSoHuzSiubOPWSfkE0VE
LxoeoQGbiH0M4QdOtT9DKuHCwhS0foDbNc22eeX21qzTlO+0DM6OY5ZGOOuW+nYmrzgLN/2ksME8
lcwD37y2G+fO74qu+ItypZzG/zNX9HIANwhrQx2BEC53BUa6UpoBFyri0IXSiIZdAeu+6R2QLXBD
C6+BfLhiNv8Lcqj/tzVndZiyhoOg2qdjJCgsJyoShOxBWzLZd4ayarb0WJUsU2QyqmSuTK3ZA3JI
WF/3wHXdgwMUQaqbbpK1AYM7nX/uc1ZBg7Heo5TrzelkxdJpa+Dv3rjYYganTu0ldP7m/BcmFqv7
bPWz8kY8XyPLjugXs11SLa8KZ/FrNLKp3tCEZRbg0lprO9acx6v13DiI4rzHMFjsZ1K4B0L6H1j/
qAiZ/V6hF9Q+34feiuDzg+UPQVZf0l0NMkg3SPtrAPseO2iTSauy1GY7H81avlhf8Ea1mPcU2dqy
ZeJ9TrKLTZQ7nVOLF0l2xrDDtR1bSDVE9nSJwtAoP4eYwJgPXeVvUXzwAAK9A7f+E2a/TskUnkwd
pHvCZNeAD6fZTybtgmuzTp9hNJIl+2SE6PA4P38UTNgSsl9I8i2yQWsxnWiF4Jrv0OAKZngtalfL
Qnj1bOFCwswMLbsQNhdqPgXwfSxr3PpoB3jbZK3XurhypljyZyhbwng/Zd6Tz7KU2YPiawP1BpSp
49dTljEF5M0nHnzhFBiOXj3Tf2HRsZluUnbrDwAAAP//AwBQSwMEFAAGAAgAAAAhAD7FMO0XKQAA
AfUAABgAAAB4bC93b3Jrc2hlZXRzL3NoZWV0MS54bWysXdtuI0lyfTfgfxCEfRhjt1vi/YJuLcQi
xYtIe+Hx7j5z1NS0MJLYptiaGRv+d5+orKiKjIrMLErTA+w2I5nnZEacyirGkdif/vrb0+PZ6+7w
8rB//nze+nh5frZ7vtt/eXj++fP53//r5sPw/OzluH3+sn3cP+8+n/++ezn/69W//sunX/eHX16+
7nbHMyA8v3w+/3o8fhtfXLzcfd09bV8+7r/tnjFyvz88bY94efj54uXbYbf9kk96erxoX172L562
D8/nDmF8aIKxv79/uNtN93ffn3bPRwdy2D1uj1j/y9eHby+M9nTXBO5pe/jl+7cPd/unb4D46eHx
4fh7Dnp+9nQ3Xv78vD9sf3rEvn9rdbd3jJ2/qME/Pdwd9i/7++NHwF24hdb3PLoYXQDp6tOXB+yA
0n522N1/Pr9ujTety9b5xdWnPEP/eNj9+iL+fnbc/vTj7nF3d9x9QaHOz6gAP+33v9AblwhdAvPb
9nl39vuP37CNz+e9Pop53H9b7+6P2e7xERx9h5/DEDO9//P5T/vjcf9Ebzs/294dH1537u3TQRfF
/+98efR3LO2iXJv8O6/zJi/23w5nP21fdtn+8Z8PX45fsVis48vufvv98fif+18Xu4efv2J5rR7S
SVkdf/l9unu5QzlpEyC52z8CEf979vQAUY5Qi+1vmNDBphnx47DTvuy02gB5Of5OFcq3duHm5quc
bo/bq0+H/a9nUBYS9oLdQqetMYAAT9FrhMH6gtevV53LTxev2NZdMTiRg+2RP5h5gz1/cCoH+/7Y
TI51/bEbOdZWE+feoJq58AYHPuwSg7Rxt9fjAbu9v5q2Pl3c07b/fX84fj27ftodHu62/sSVMTHP
19ftYffl3Al3RcIFwUMuwRnDzr4fcAT4eLcJPIcBBbxeXb88bP98/f3leNg+PqhlrZvDeJs7e94f
z/6xxfH2HSeev7R8CypHcqvBpf25DngBzZXCa9vCa1MRJIE7BNrja7ouiK11fnXd/8DpbI2GSg8T
gni9whukaDPwlYpWgp6aM+ZmdEnrzhcBrSxvfrj8/OPfNz9M2+Npq/Nvfzk/O/+LeH1Bf/8TBv90
g9F/K4SlVrZixHx9ToW1BKza4w29D/vHskreWXs8k7zFa5OX7iZjXOt3OBNww3nZHV5351dnfppu
E4txCyAlNoJbM5wqagWj65TvMqG3Nh2GyQV4asMRaR1zdOB5anMCy680Q1n09tertp+yDNhBZbkZ
quJzM7qkNdaV1YGyukJZ7nVR4Q4pqxtUFiMKZQntdKAdgTxzr03kRsW+jdLddMa01PISKV6/nW7N
dHRql1fEvDOeS5ritUlT0x4jmvladMYLiVy8NpFT+fK0SQ8Txi24e5o26e24VyttAjuoTTdDa9OM
LmmNdW12oc1eVdKpe11kpEva7AW1yYhmrmddaFMgF69N5FSu8wea2yjdTRfaFHTF67fTrZnO12YX
2hQ0c/fapKlpkxHNfC260KZALl6byKl8edqke66hzV4uNuOEdAPqISwDSlCFBZSv27kZXdJq6irs
KRW618Xee3EVMqKZ1VlPqdC9NpFTWXUqjNLd9JQK3eu3062ZzldhT6nQvTZpaipkRDNfi55SoXtt
Iqfy5amwb6uwHz8h1dP+hN7+eqU+kmTADmrTzdAnpBld0hrr2uxDm31xQrrXRUb6pM1+8IRkRDPX
sz60KZCL1yZyKtdOm1G6mz60KeiK12+nWzOdr80+tClo5u61SVPTJiOa+Vr0oU2BXLw2kVP58rQ5
sLU5OE2b9PbXK/VJJgN2UJtuhtamGV3SGuvaHECbA6FN97rIyIC0OQhqkxHNXM8G0KZALl6byKlc
O21G6W4G0KagK16/nW7NdL42B9CmoJm71yZNTZuMaOZrMYA2BXLx2kRO5cvTJvUojbv38DRt0ttf
r9RpmgE7qE03Q2vTjC5pjXVtDqHNodCme11kZEjaHAa1yYhmrmdDaFMgF69N5FSunTajdDdDaFPQ
Fa/fTrdmOl+bQ2hT0Mzda5Ompk1GNPO1GEKbArl4bSKn8uVpE91LS5ujXGx4slR6m7iBof+cmAEl
qMICyp8xN6NLWk1dhSOlQve62PsorkJGNLM6GykVutcmciqrToVRupuRUqF7/Xa6NdP5KhwpFbrX
Jk1NhYxo5msxUip0r03kVL48FVIL3pIh4thavpaip+t3hpQOJ/n7X69qzXByGriPrruOxRx9TNrh
JcKWRFuX0OhInJRFoEgNXuGsHAXPyhLVTPsM02cSnQM2eirzTqlxyhtQ0oKrPlEReAfluqT05Qrk
uaSaFwGb6uryoyovfCmrJgvALCQuB4K4lQR8cVI/37h/t9ACP0mc9H50xJUAM+BE1FlMUsdnzl3r
ri8JyjhAW63xtH1ZFXNaBDgTLagT46HOeIkaUGdrPJPoM6BTwEZvqE7eiEl5AwZasFCnC7yDcl3u
UqmzNZ5Lqjm4KWBTWerkrXi4C8AsJC4HgrghdVJv31In+SanHJ2Fz1LR5OdE1gJ++Ow0zZk55uRK
90W7JChLnXBt2q2qmNOWC3AmyLfBeFCdjGpKZQawmUTngI3eUJ1RyhtQ0oKFOl3gHZRrO3fINMQo
qDhgU1nq5K0odbahToG7ABEFgriVbPyzk3r5ljoTlo864ie5J47zTps+ZLqH1WkaPHPG0upk28HL
BPxErU4X4EyQ94PEBNXJqAF1wu2ReYaNmAds9IbqjFLCAtXqdIF3UK6pDPUrG5nW6nQBmwrqHKo/
qoO9sXkW4FFqdYEgT0v9KaXgi5ea/ZZ4E55QTbyFmaNdoRbww+I1HSCYavbRyr6EEi+soHa7Oong
YeYBTgyZQxgPipdRA+KFPSTR4WPmARu9oXijlLAuIV6xIQ68g3JNZbDEC1tIUiH1ecCmaiJekwdm
JsQrtsSBII/SbujkJY/AEi95OpHngpp4Cw9IXYoZ/RxIWLymcQTXzRYv2xlKvHCQ2vKnOVouwIkh
TwnjQfEyakC8cJEkOozOPGCjNxRvlBLeJsQrNsSBd1Cu8x/HqbVMkGloVVBxwKZqIl7emlcjuJ0Q
r+DhQJCnoXjJRLDEm3tNV9ftS/mTRzXJFtaQ9phaQA1L1vSTYIPYkmWXw0sHTCZIVhjAHOB0kNWE
8aBkGTUgWZhNEh3OUx6w0RtKNkoJswmSFRviwDso11QG67yFySSpkPo8YFNZj7ImLuwmSFRsgQNB
3NCBSuaBpcnC7BmN1Af7SasY0X4S4hEdmt4RLA9bh+xoKB3CRGoLmw0OUx7gPZOthPGgDhk1oEMY
SxIdLlMesNEb6jBKCWMJOhQb4sA7KNdUBkuHMJQkFVKfB2wqS4cmLqwl6FBsgQNB3JAOySiwdFgY
O4YOixHVy89aQAqfh6ZPBHvD1iG7F0qHMIzknuEmeTokCwnjQR0yakCHMJEkOhwlT4c+ekMdRilh
ImkdugAX8Q2UayqDpUOYR3J3SL2nQ5+qyS3c5IGtpHXpAvaWwNPwFk5OgiVTtpbqx2Uxopr6WQtI
pUzVvR5Nd0uP6CeLOW2FiK6wNWlJk+qFAAU0K7w3DnCCyIHCOIu41p9e2bjo6EOtApcDQdzqQCha
+Lxe8/JA+x5aFfgcsPEbXR5reytIN6QpqDhgU5FWy0/c+VY2Ni4KBW0KXA4EcasUeZ/k2wF/CXEc
WHn65O8M4PlyfN2l7OIHvdFEum53xPNmTbg5CppTSpsZsZbCVQ8H6MdbGkRn2QovCcqQJtY5bQuX
Bqh5oMgPXkGale1Ul6aNi+49pClwORDErfLupFni2tIEPq2r6pAWARu/mTRLSu8WhIRCmoKKAzaV
cTsvcc2toIcPiQp8Dtj4qa34qiXnwDhC26bx1Ml/HB8qHKliTPL34wfmlQQzxCP6tI2nAktRLAnK
0icZTyI56PN7+syNJ6lP1f8bqq7DyuZBC1Xr1QW4CDWe4D2skC9vx6w5+r1avi5g06VqnlOu7Z2h
ua/l6wI2VYOngJLH3BraqFrOLmDzpbbmy5msBkvOplMVkbNzl9pKg1kb+OHj1rSk0OCzj1vTFUEr
dTztCFeEA5wccqowHn4SoCXWLxM0UcczicuBIK7a+m2JaxYVHdMxrUscty5g46eKWujV3AoSOp5L
Kg7YVNZxy7jmVtApHS8kPgds/NRWfH2SiWHp0/SqIvp0tlNbe1Vt4If1aXtVmGM5qQRV1xG6pdCn
aCVzgJNDXhXGI/o0cdEnhT4FLgeCuDV9Mq5ZVDRFoU+BzwEbP1XUQp9MqR4H4EBJKnRJ84BNZemT
cc2toBkKfYqtcMDGT23F1yf5B5Y+TTuq0qfS4aTtLKS2tqMQj+jT9J3mBZaq95KgLH3CfeqIbvG0
7QKcHLKjMB7Rp4k7A8xM4nIgiKvWe1uu1yzqDfBpXeL8dAEbP1XUQp/mVpBQyFFQccCmsvTJuOZW
FsBfSHwO2Piprfj6JIvA0qfpOEX06Vyitnr2y+iX6cPnp2ktoaFsn5+mm4HWPfQpfjmSA5wccpww
XulTfYxd5b/vX3Nj0LSHPgUuB4K46pK9LXHNoqJDD30KfA7Y+KmiFvo0U4SEQp+CigM2FT2Pqk/6
8a2gUw99CnwO2Piprfj6JH/A0mduKuWZFT9kGtGns4Ta2l5qAz+sT9NHQoPP1qdpZaCVCn0KK4MD
nByylzAe0aeJiyYq9ClwORDEremTcQP6hIsk8dHzzQM2fqqohT6ZUt3fYRpJKmQ4D9hUlj4Z19wK
OvjQp0gVB2z81FZ8fZJvYOmTrB+vSeXaUsWvx4/UfXzSdlaR/oKODPGIPk1/aV5gqfvlkqCs+ztc
po74DZpp2wU4OWQ7YVzoszWU/+lHkpXNMwPsTPJwIMgjSejvNf3yfsyi34CP1i3u/y5g86WKXuiX
KZV+YTZJKlQgD9hUpF9/bzqFmzKF5tYWgF9IPg7YfKmt+Xomv8HSM1lIp+jZWU5tbV+1gV+et3rf
6KzbJ6tpgqC/D+WKRjMHOA1ktmD8BOWaPFgVlCt4OBDk8atrKJd5zPKi/w/lCj4O2Hyp8hbKZUql
XNhTkgqGQB6wqZool3nMrcEXgHLF1jhg86W25iuXWv+Wcsk3OkW5zmfS/lPWBn6pXNWVRb/UEi56
2FZ4SVDWSQzPquM1Xl2Ak0OeFcYrPY8u/f/UzyysbB6YBNCz4OFAgGf00adptWcfamcx78gsO2wD
KFowcsBmTJW9UDRTKkXD1ZJUqEEesKmgaD+Fo0uVxE2ZRHNrsBGgaLE1Dth8qa15iu4EDDDEo4pW
n8Em+fthJYz8p/qM8IOKLiaph4i5HV4SlKHoDpytruhhTotAkRy8+tMNxitFDzv+H3X7WNk8MwDN
JA8Hgjytvvrjp+a25DGLfgM+Wnf1bFEEbL5U0Z2eS0pfz0CeSypUIA/YVHRC+xnsqBRuSh5zawvA
LyQfB2y+1NZ8PQessU7CGqvp2blc+rv1MuBUetadXHgA1lmMvrcVXhKWJWhYYTI7QM0DnB3yrDAu
BO0/C+gnnpXNA2NBC9oFgjw+Tf2Ro+Qxqw6jQQvaBWy+VNULQZspRMK1oF3ApmrwyBHfGowHLWgX
sPlSW/MFTbaH8cjRSZhjNUE7Q6ujDtsMOJWg9SNHTlL7bUL0yW09s0PjnS4wHiBf0fnmACeHzDGM
n6BnkwdGBPQseDgQ5EnqmXkCeoZXJvngVOQBmy9V9ELPTOmlEAmHnsXWOGBTNdEz85hbg1EBPQs+
Dth8qa35eiabxNJzwkxTTbVJxxlgHfWUmCEe0bPpmqGvbuuZHR2vGDAqoGfRiecAJ4fMNIyfoGeT
B8YF9Cx4OBDkSeqZecyiw8iAfAUfB2y+VNELPTOll0IkHHoWVBywqZromXnMrcHYgJ4FHwdsvtTW
fD2TrWLpOWG+1fTsfLSOatplHeCXD9AtNQvmga1c9nq8tMPCgHJFD50DnAay2TB+gnJNHqwKyhU8
HAjyJJXLPGZ5YXFAuYKPAzZfqryFcpnSSyEsDihXUHHApmqiXOYxtwbLA8oVfByw+VJb85UbsOU6
CVtOaXCSvx9fbameODLEK+XWnixM/w0delvPpucEywN6Fj13DnByyJbDeKXnxOfwFS25/kQOCwR6
FjwcCPA0aWaUTGbZYYpA0YKRAzZjquyFos3NIeVQtKDigE0FRSeSuIlvDSYJFC34OGDzpbbmK5os
GussThh5qh0z6TjzraOUniEeUbTp2M0LLPXYvSSoutKmHRh5XfG7IBzg5JCRh/FK0Yku/8rmmYFn
Jnk4EORJntC8n4Ce4etJvhssgAI2X6rohZ6ZUp3Q8PUkFSqQB2yqJic085hbWwB+Ifk4YPOltubr
mawgS88J46+mZ+fhdVQ86wC/fLbQPzYJw846i2FCWeElYVmChtHXFQ4ZUPMAZ4ecP4yfIGiTB64f
BC14OBDkSQqaecyqw/WDfgUfB2y+VNULQTOlEjSMPkmFCuQBm6qJoJnH3BpcPwhabI0DNl9qa76g
ybmxBJ1w/pRwJx3n4em+Y4Z4JejaI4dp/MGasvXMJpNXDHiBkK8wlzjAySE/EOOVngdt/7+R3wVe
0ZLr1w28QOhZ8HAgyJPUs8kDDxA6FjwcCPA0eLRZ2ztCnqFawcSBANPlRz9vA20tbGweWH+Qr+Dh
QIAnviNfveQGWepNuH+qOz7pOMeuo34CKkM8ol7T5oMNZavXNK7g/Gn1ugDnhtw/5E6oV6vVxIXT
p9XqAkFc1bW5pa3XrwL4eVqdLhDEVY9ZaxsXWdNadIEgrirhxsaFSae15wJB3Gq9ntK6AVcOcRxH
uUjMn0hTy5zk78dHM3XoZIRf3virNeS3oVkxSYWXNKdeommX7DfhTXKg2DKGISlpKKs1rmxcrAKS
ErgcCOJqSdm4N8Cl9VS2WhEI4qo8rG3cOWDmEpcDQVyVh42NuwDuQuJyIIhbrdeXVMAY6yaMMbXM
Sf7+16uuurtmiFeSUoOws6xTCp6jFV4SlKU02GA98d1+QM0DnAnyxTBeHV7qfF3ZuDB1xzOJy4Eg
bpXh/IK5tXHh0Y1pPUJpLtAUd23jImvjucTlQBBX5WFj48KRHS8kLgeCuFUefKWRt2DcJrsJx0ot
c5K/H0qraPJ0Z4hHlGZaUzBPbKWxDeI/5HXhWPWE/QH7Kg9wJsixwniltMSjyoqWXFc03CooT/Bw
IMiTesizeeBSQYmChwMBnvgjkfusYjMhz9CmYOJAgCn9kGfzwJyCVgUPBwI88R356iUnwVJvwp+q
qdd5Sl11W8q6wC9vvbVz0jSiYJXY6mXTQ6kX/lRPmB0wq/IA54b8KYyfoF6TB94U1Ct4OBDkSarX
5IEnBfUKHg4EeOK1LtRrMiHPUK9g4kCAqYF6TR5YUVCv4OFAgCe+I1+95CZY6k24UTX1Ol+pq92o
LvDD6jXNKNgltnrZ+FDqhUfVE4YHDKs8wLkhjwrjJ6jX5IE/BfUKHg4EeZLqNXngS0G9gocDAZ54
rQv1mkzIM9QrmDgQYGqgXpMHdhTUK3g4EOCJ78hXLzkUlnoTjtTI/5Q66ToXqasdKcQj6jWtJ1gj
tnpNMwVuFMQqzA0OcG7IkcJ4pd5+x/9PWQ4rWrL15ABHSvLAnsoDQZ6kek0eeFBQr9gPB97Ks7b3
gyxDu4KHA0EeP2t9bdVsbB4YT9Cu4OFAkCecN1+55BFYyk04TzXlOhOpq2SQdYFfnrv6+zrg5Nga
ZeNCnbDwmHrSY+q6AOeAPCaMn6BRkwergiQFDweCPOFc5+feLSWhfi3ARoJGBQ8H3sqztnlgKkGj
gocDQZ6kRs39wEyCRgUPB4I84bz5GqW2v6XRhJtU06gzgLqqKZ91gV9qtPZka7pG8DVs5bJDoZQL
76gnnAk4S3mAM0NmEsYr5SY/l5k8MJKgXMHDgQBP/A5XaNdkgoUE7QomDgSY8B1r2vD1b31rKkL9
GkGeoV3Bw4EgTyJzG5sHvhG0K3g4EOQJ78fXLrkXlnZjxlH78lLJcNJ1Zk9XdbUyxCvt6u/rQkvc
UilcBiu8JKx6CeAaQavCl+AAp4acI4xX4k0cHyubB64RxCt4OBDkCZegkK65HyQF0hU8HHgrz9re
DzwjSFfwcCDIk8jbxuZBNSFdwcOBIE84b750ydqwpBtzjSzpOqenqz6qZfR1dOFj17SH0Ki2lWu6
MGjvj6d90cjkAGeGXCOMC+WqX3xRnyJX+Tfo1b8NATwzyYP+fx4I8qR+w8bmQft/TOsVjVkXeCvP
2uZBlsdzycOBII9KW1/lbWPzwB4YLyQPB4I84bx5yu0FXCjEcV/ORed9OWIPX444pMMCX46Iz/zX
verLEQ095yho76rHi4xYg3ouJqmWMNrhpp4JyjiJsc5pX/xmFVyFPFDkC6+gZ/kLNom6rGwemAqQ
r+DhQJAnXBd3Ets8MBmgZ8HDgbfyrG0eZBl6FjwcCPIk8raxeWBCQM+ChwNBnnDefD0HLLCeaYF1
3dcmQrlKbZP8/fiXitXDRYZ4RLmm1zUvsBTFkqAs5cLx6ou297TnApwZssAw3vwktnlmgJ1JHg4E
ecIVKJRr7ucGPLTe6iQuAm/lWdv7QZahXMHDgSBPUrnmfhbgWUgeDgR5wnnzlRuw1HqmpRZRrrPB
ekpuGXAq5aq7Dhwq+3A1PS34ZpCo6G1zgFNA3hnGT5CoyYNVQaKChwNBnnCqC4maPPDNIFHBw4G3
8qwp1/VLG64ZJCp4OBDkSUrU5IFrBokKHg4EecJ58yVKVofxmNszfbOIRJ3X1dO+GXAqiaqTF3aX
JVF4OVZ4SVD1CgAEyhV9bQ5wZsg3w/gJyjV54JlBuYKHA0GecAUK5Zo88MygXMHDgbfyrO28IctQ
ruDhQJAnqVxzP3DMoFzBw4EgTzhvvnLJ5rCUS76V95jrHmzzr1fCY4FS6KTnfK6eOj8zxCPKNc0x
+Di2ck1HBn4ZlCu62hzgzJBnhvETlGvywC+DcgUPB4I84QoUyjV54JdBuYKHA2/lWVMJ6lc8sgzl
Ch4OBHl66osPVBtpY/PALYNyBQ8HgjziK+R8qZJLY0nVNMiqQ7YmVWdq9bRB1gN++dlLeRDwgSxN
wk6xwkuCqqcc5hikKprbHOBUkEGG8ROkavLAHINUBQ8HgjxJqZo8SAqkKng48FaetZ03mGOQquDh
QJAnKVVzP6gmpCp4OBDkCUqVzA1LqqYjFpGq87Z6So1ZD/ilVGvPA6YhBvfGlqrpw8Ajg1RFL5sD
nAryyTBeSXWg1riiNdavAZhi0KYA5kAQOKlNkwemGLQpeDgQ4Bl+9L/VpT2qfQfT2t4REgt1CiYO
BJguPyYfAcwdwRaDOgUPB4I84cz55yq5JpZYTWusEqu61U96zs7qaWsM8YhYTQ8Mdo0tVtPggS0G
sYruNQc4M2SNYTwmVhMYPhjEKoA5EAQOp7y455s8cMEgVsHDgQBPI7GaTEgsxCqYOBBgaiBWkwc+
GMQqeDgQ5AlnzhcrtVgtsZpeWESszr7qqYeYrAf88mRtKbsB1pItS9MkguEFWYqftucA54BML4xX
skwcDCtanHWkwvSSPFhmHgjyiNtWIUsTGA4XZCk2wIEAcCNZmkzwuCBLwcSBANPlx+Qd3uSBxwVZ
Ch4OBHmayjLgc/VMnysiS+dN9ZTwMuBUsqzd8E1Da55z176/aElQdRFNe/C5BsIX4gBnhnwujFdi
rd/wTeAZgGcSmANB4HDKC7GaPDfgoQWKdqoLBHgaidVkQmLHc8nEgQBTgzPU5FmAZyF5OBDkCWfO
O0P7AWsL8ehnfvWBaZK/H1bAyP8xjIzwqzNUnbAwH60zFB6eFV4SFqs1B5WmG0bHy9YltaPhuuGj
2PLmh8vPP/598wMsW8hZ2CgcKHKHYchZ2lw1OUeZVwBYlcx4si6ZYeJC74KZA0HmcNWc3qMLuQXd
bbkQPDWVC0GicUGIhXAgsJAmF0R0KWsQrsul4E5ZLgVGMK4YsRQOBJaSPt6jC9mAblMuBIdjuRCo
DJeUWAgHggsRt0r/GiLRGc8h/YSdVruGnDPWV2d6BpzqGlKD8G+tawX2pBVeEpR1CblrJm/oJb/U
chUD6TuzED+fpR9g/IPhtgTJt3Y8YLm1FuMgB0v9Yn1+ZaxLPANnyIvSa1IfWzYxkBGDhHfmq4Js
B0sVCauqpgrnOvW1VdUHfnmy1lRhWlWw/mxVCIdEHqyeKuqHYmRWKQNxzRQnGM/6o+rOeLG6p54Q
KZehy+LkulPT3qp7wv9RPZNJ33k2fdWyzBCP1N00euCn2XUX/sIJdY/MitSdZ/1RdWe8d9U9AnJy
3am1btU94Z7U6u4cD/0zT1kf+OX13lIXPHw0u8Ki339ChSOzIhXmWX9UhRnvXRWOgJxcYeoUWxWm
xn/t5lV9sKtV2BkFfXXSZ33glxVWD9KwtawCw7URc/TX6MNrsSYtaVLouOvxba5+3kdmRVTBs/4o
VTCekfLyPp887yMgJ6uCOrSWKqjHHlGFao1O+q4n31dqyRCvVKEuezhIVoFhkFjhJUEl6554RlrF
QCIyiFC7x7yrRh86IjDNqx8BObn61PK0qk9N61Oq75rcfaWKrA/88kxQjwIwZawyw4CwwkuCen/1
IyCR6kdmnVL9CEzz6kdATq4+dRat6ic60KrKk77rJfdVfyRDvKp+7do3G9Do6NvVF03QHFN8b055
5ifOzRWtJyShsvq+edbRX7R+GwM5RQyRtVRi8D91bmLcJxefOnVW8RN9XlXkSd+1bPu6z4t4VfyW
uvbR5LfLLNqH4TL7WVkR0/vLGgEpyprsCqxjKymL2lWfwNWj0iYGUhZZfDD1PrYPAg1RxKMHuq5q
/v7Xq75aXEb45YGuL+likvqojwazWWuCCpWtuqRVrWOTGl/CMZDGtY6BNK51DCRd60DjbpBo3NVq
7ZptA1XODDhVrZUQ0JG2iorWqJhTe6C3Jy1p0ulKiExqroQISHMlRECaKyECklYCNYCMs3yQaNap
M3uSv//1aqCu4AzxSglKJtNikpozt8NLgkrWOnFErmIgzWsfWUlZe3HOukZtjLp5sSPU6WJT18cq
dqJDVyu266oN1K05GwC/POJb6llvhlHrH6ynScmyJh6tVjGQsqwJbdzGQCJljay/LGti/ZsYdbqs
1OqxyppowNXK6lppA2UOZAPgl2WtXcNm/22OOWaxI12p8s6dqNOK1hNSTFnsRMZvYyCRYkeomxc7
AlIWO7x+/6mNGjpW7ROtOXVTngxcw2ygW3OIR2pvdtnmBZY61pcEFSpb89pHQJrXPgISqX1kVvPa
R0BOrj21c6zaJxpwtdq7ppnue2YD4JfXfe0fnsGoeYVHekzNqxwBaV7lCEikypFZzascATm5ytS2
saqcaLTVquyaYwN1W84GwC+rrHqwNxg0iryww0uCev8VHgFpXvsISKT2kVnNax8BObn21Oqxah9v
s2mTbDJwrbGB+vyWIV7VvnZnN/tp8wKrdrpHulLlda/ktSL+kGCa1zoCUtZadU50u3kdW0lZ+sSD
ySYGUpZefC7w7+TURrJqHe+q1Wvt+mMD9XSXDYBfXuctdZ+fYdS40Jc0KVSgsqqJtKxiIGWVEyC3
MZDmVY5sp6xy+Mkr/xy3ia0kWeVhoMuGeKzLVqty/n583lanfEb4VZXVk/xNMUtduws7vCSsZPH1
JR2bVBY7keLbGEjjYsdAymInZLeJgaSLTZ0Z45IexttsLVWfSf7+16uhOqEzxEWx1afxWTFLgS1p
Urqq8V9zXMVAmlc5spKiyk2s0dhayjormW5ik8q6hm8a3sk9pJ6MVeZ4D61eZvdDakNVsYzwy2ta
VXmKQePgntvhZb7U4nuXckzLDEsZ4TGQsvjiNud+/i0265RqRxpgVbXj8t3E1nJy9QNNtWG8qVav
vmuPDVWBM+BU1dezbnKW2u83LOzwkrDef+1HQMryJ0/4CMgpaojAVGrwnaBNLAsnV596Oda1H++9
aVdzMnT9sqG6Y2eIi+qrG8CsmKUOjCVNen+ZIyDNyxwBOaXMEZhwmSOTTi4ztW2sMsfbbPUyu47Z
UD1+Z0Pgl0e8eqabYtA84uWcmmFmT1oS0fulEQFpLo0IyCnSiMCEpRGZdLI0qNdjSSPehatLw/XT
hupJJRsCv5SGOgCmGDSlYYaXBPX+4kdAmhc/AnJK8SMwVfFTDwMRkEIM8cdQ/2GQ2j+WHOLtupY6
+CdD13kb6nYd4hE5mO26eYFVu01EOlXlh3slxxXxhzTUvPwRkKL86R+Zia2kKr6+90eYT77yqfFk
lTrRnauV2jXahro7R9+kWV75qngzDBpX/jL/9s3UA3635/+nFrSKgVQ1Vt+yq4RyGwOpapz4MusY
SFljfzNd/fVLmxhIVfPgSvzLO9ClG9a6dIfd/efz6+FofD0izeF3M1vo8VyP2h9QynuqXfuyftW7
NtxQN+8AX0lBfUKY5ty1zwBzO7wkqNAFHL7qI5MqRfjX2m2MqVSA2sw6NqmsuNLaJjaprHDF5FV0
FOjIIW505FDD4tu/dAt1kk9Al0Y9vmVEUF7G6lKbFZPU1b2kOckiddWfaoP5J+5VDKQqmvqkplZy
GwOpitj2/yiQdQykLKrajf53szYxkKrI/kLEP2ntFz3QmRuZnblY0d0Ps43Ug1kGoKroqjDTnKV+
wdrhJUEltaCuiFVsUln7Wo8mNqsqtuJax2aV1VWTNrFJVTWrWX75Ah23kdlxi5XPdc9GSrAZgKry
qdpOcxajfGYnbklQyfJ128PeoFX9b7Xv4lKOgFTl9DHU48RtbCFVcaMY6xhGWepqG25LajObGEhV
+tBCfCFQ/8d4BBuZzTchBLWmST7h9WqkLtUM8YgQzJ9omxdYSlNLgkoKQZ3G+ncIVjGQUggJkNsY
SKmEBMg6BlJKIQGyiYGUUgiD+Fqgfo+lBbMVF9OC68WN1L06G4GgvJGrDs4Mg9bzOM1JFl2JbhWb
VBZZLeA2Nqksqpq0jk0qi6iWt4lNKotWMflFos6LVSSzkRYrkmuKjSqe/KTMRiAoi6Su8hsMGkVa
2OElQaVrpzhWsVll8ep33ghXWT1FtY5RVdVTszaxWWX5qkl++ahXYpXPbHaJ8qk2xmTkOlSjiqco
HwjK8qnazopJtYM10sApP9GED5HiDhsBKcuWALnFAoOKKauYAFnHQMqqJkA2MZCyyGEQv+j0+dUq
utnSihXdtadGSgwZfUAui64Gpxg0rtm5HV7mn7VT/Q8lulU5KV+F/ZUsTgONvpLltsQzPkCWMlCL
WMcmlWVXkzaxSWWZq0l+WQPtq1Hevrq6xpcHyVaFqsskfxuemNRjZoZ4VUw1eFNMUlfwwg4vCSo/
gCN1cRd4o7qsmuCdVGdeX7jOaqfrJktw1W60pU2JZyyhEEC1BL/8gU7WyLWg0JxSxZsUIyPdnEK8
qrgaXNLgH1rDBngn1bABnrtmGxVk3WS/JxW4wfpcoVPr86rfugy0vWigaE7q+vPQSHe4crDyANcK
cFR0Jv9Bl3EjwFM00AjwFBE0AjxFBY0A3ySDQCOMvjkuKAM3hDX5Dd8s/7q5iA64kfWH6aAB4Gk6
aAB4mg4aAJ6mgwaAp+jg4uXrbnecbo/bq08v+8Pxx+P2uDvLvYtJa5y1WlRrGsj2z18ejg/753Jw
QoNohl+U864+fdv+vNtsDz8/PL+cPe7uoQX8I+P4aHN4+Plr+eK4/5afBj/tj8f9U/7Xr7vtl92B
3o033+/3R34BfML8cXf8/u1sf3jYPWOBWMXn829Y1GH7cDw/+4r4/+wx8Dj9Rv/wXHvUHfUHbWoz
ve4Ox4e7+gBgd78d1y/H/P/Pvh8w73/7XfyTHoNO68N1f3L5oUf/0+4PLj8MBu3WZJBdjvqXl/93
Tsfs88v46bfP51+Px2/ji4uXu6+7p+3Lx6eHu8P+ZX9//Hi3f7rY398/3O0unrZ3F7vf7naPF/gH
Q4Z4+fCMjD79Nv7b+h9nm/2XHTZ9fvYfz7u/YZv53//5Ixac/5WSi2W6/80Xe/Hr/vBLXrKr/xcA
AAD//wMAUEsDBBQABgAIAAAAIQDRFuMocwEAAK4DAAAUAAAAeGwvc2hhcmVkU3RyaW5ncy54bWx8
k19PwjAUxd9N/A5NfSRSwMQYMkbmAIMmPMgw8fG6XWmTrZ39A+qnt4MXacXH/m53du65vcn0s6nJ
DrURSk7osD+gBGWpKiG3E7opFtd3lBgLsoJaSZzQLzR0ml5eJMZY4r+VZkK5te2YMVNybMD0VYvS
V96VbsD6o94y02qEynBE29RsNBjcsgaEpKRUTlr/3+GIEifFh8P8SG6GNE2MSBObbtZZwmyasO54
RA/oteVXiHOQUEFI53Jb+wYi7LR3GtJHaEGGcKW05SRrUIsyks+MiFhxPws1XsDH6nzSYWGhfSXy
UYDYx0bybyw5ecbWvdWiDJVyLmRkZYWWo+4CMOH99R4rjJpdavwrrrVyPoMn5QcZ6mTOWB2HcMBQ
xwUf5x7i4WWrbJb1Q/H8gENacCT/dHYyMCKVJWfjP7w3Hbnppto728FptXdOvFuQsWmh9IvjN8Cg
3iFNSdjMcl4syFVIXxF+vRXm9y39AQAA//8DAFBLAwQUAAYACAAAACEAe7ee3YABAAB1AwAAGAAA
AHhsL2RyYXdpbmdzL2RyYXdpbmcxLnhtbJxTwW7CMAy9T9o/RLmPlmowVFHQtAo0aZo4bB/gpYFG
a5LKCVD+fm6bTgxxmLhUiR0/+73nzpeNrthBolPWZHw8ijmTRthCmV3GPz9WDzPOnAdTQGWNzPhJ
Or5c3N/NmwLTo8uREYBxKV0zXnpfp1HkRCk1uJGtpaHs1qIGT1fcRQXCkaB1FSVxPI1cjRIKV0rp
8z7DAx7cgKZBGb7oJoMvZ6u9l89GlBb7WG0dazJODE/tN+qjsvFMUHg2eYqTGSUFZSezZBqPH4c3
O4S6VGKFoCXTINBmPDQyh/VZchNaiffDBpkqMp5wZqgq4y8loGfjAZJeXBZCet7nzYpvx4xdY02+
tGVRK/mVui5+fY5mi3oxh9RutxfUIR2IB8qdIB3UUBSmaevDMQcPbI/qBm9ES580E2l3Ci6Lm5EC
wL+WjtgrIXMr9loa328eygo87bwrVe04w7Q1C1+LXuk/jEn533tw4dyofo1EpQi7FWhw6nIFO23b
P2bxAwAA//8DAFBLAwQKAAAAAAAAACEAKfLq9yhwAAAocAAAFwAAAGRvY1Byb3BzL3RodW1ibmFp
bC5qcGVn/9j/4AAQSkZJRgABAQEASABIAAD/4ge4SUNDX1BST0ZJTEUAAQEAAAeoYXBwbAIgAABt
bnRyUkdCIFhZWiAH2QACABkACwAaAAthY3NwQVBQTAAAAABhcHBsAAAAAAAAAAAAAAAAAAAAAAAA
9tYAAQAAAADTLWFwcGwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAtkZXNjAAABCAAAAG9kc2NtAAABeAAABWxjcHJ0AAAG5AAAADh3dHB0AAAHHAAAABRyWFla
AAAHMAAAABRnWFlaAAAHRAAAABRiWFlaAAAHWAAAABRyVFJDAAAHbAAAAA5jaGFkAAAHfAAAACxi
VFJDAAAHbAAAAA5nVFJDAAAHbAAAAA5kZXNjAAAAAAAAABRHZW5lcmljIFJHQiBQcm9maWxlAAAA
AAAAAAAAAAAUR2VuZXJpYyBSR0IgUHJvZmlsZQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAbWx1YwAAAAAAAAAeAAAADHNrU0sAAAAoAAABeGhySFIAAAAo
AAABoGNhRVMAAAAkAAAByHB0QlIAAAAmAAAB7HVrVUEAAAAqAAACEmZyRlUAAAAoAAACPHpoVFcA
AAAWAAACZGl0SVQAAAAoAAACem5iTk8AAAAmAAAComtvS1IAAAAWAAACyGNzQ1oAAAAiAAAC3mhl
SUwAAAAeAAADAGRlREUAAAAsAAADHmh1SFUAAAAoAAADSnN2U0UAAAAmAAAConpoQ04AAAAWAAAD
cmphSlAAAAAaAAADiHJvUk8AAAAkAAADomVsR1IAAAAiAAADxnB0UE8AAAAmAAAD6G5sTkwAAAAo
AAAEDmVzRVMAAAAmAAAD6HRoVEgAAAAkAAAENnRyVFIAAAAiAAAEWmZpRkkAAAAoAAAEfHBsUEwA
AAAsAAAEpHJ1UlUAAAAiAAAE0GFyRUcAAAAmAAAE8mVuVVMAAAAmAAAFGGRhREsAAAAuAAAFPgBW
AWEAZQBvAGIAZQBjAG4A/QAgAFIARwBCACAAcAByAG8AZgBpAGwARwBlAG4AZQByAGkBDQBrAGkA
IABSAEcAQgAgAHAAcgBvAGYAaQBsAFAAZQByAGYAaQBsACAAUgBHAEIAIABnAGUAbgDoAHIAaQBj
AFAAZQByAGYAaQBsACAAUgBHAEIAIABHAGUAbgDpAHIAaQBjAG8EFwQwBDMEMAQ7BEwEPQQ4BDkA
IAQ/BEAEPgREBDAEOQQ7ACAAUgBHAEIAUAByAG8AZgBpAGwAIABnAOkAbgDpAHIAaQBxAHUAZQAg
AFIAVgBCkBp1KAAgAFIARwBCACCCcl9pY8+P8ABQAHIAbwBmAGkAbABvACAAUgBHAEIAIABnAGUA
bgBlAHIAaQBjAG8ARwBlAG4AZQByAGkAcwBrACAAUgBHAEIALQBwAHIAbwBmAGkAbMd8vBgAIABS
AEcAQgAg1QS4XNMMx3wATwBiAGUAYwBuAP0AIABSAEcAQgAgAHAAcgBvAGYAaQBsBeQF6AXVBeQF
2QXcACAAUgBHAEIAIAXbBdwF3AXZAEEAbABsAGcAZQBtAGUAaQBuAGUAcwAgAFIARwBCAC0AUABy
AG8AZgBpAGwAwQBsAHQAYQBsAOEAbgBvAHMAIABSAEcAQgAgAHAAcgBvAGYAaQBsZm6QGgAgAFIA
RwBCACBjz4/wZYdO9k4AgiwAIABSAEcAQgAgMNcw7TDVMKEwpDDrAFAAcgBvAGYAaQBsACAAUgBH
AEIAIABnAGUAbgBlAHIAaQBjA5MDtQO9A7kDugPMACADwAPBA78DxgOvA7sAIABSAEcAQgBQAGUA
cgBmAGkAbAAgAFIARwBCACAAZwBlAG4A6QByAGkAYwBvAEEAbABnAGUAbQBlAGUAbgAgAFIARwBC
AC0AcAByAG8AZgBpAGUAbA5CDhsOIw5EDh8OJQ5MACAAUgBHAEIAIA4XDjEOSA4nDkQOGwBHAGUA
bgBlAGwAIABSAEcAQgAgAFAAcgBvAGYAaQBsAGkAWQBsAGUAaQBuAGUAbgAgAFIARwBCAC0AcABy
AG8AZgBpAGkAbABpAFUAbgBpAHcAZQByAHMAYQBsAG4AeQAgAHAAcgBvAGYAaQBsACAAUgBHAEIE
HgQxBEkEOAQ5ACAEPwRABD4ERAQ4BDsETAAgAFIARwBCBkUGRAZBACAGKgY5BjEGSgZBACAAUgBH
AEIAIAYnBkQGOQYnBkUARwBlAG4AZQByAGkAYwAgAFIARwBCACAAUAByAG8AZgBpAGwAZQBHAGUA
bgBlAHIAZQBsACAAUgBHAEIALQBiAGUAcwBrAHIAaQB2AGUAbABzAGV0ZXh0AAAAAENvcHlyaWdo
dCAyMDA3IEFwcGxlIEluYy4sIGFsbCByaWdodHMgcmVzZXJ2ZWQuAFhZWiAAAAAAAADzUgABAAAA
ARbPWFlaIAAAAAAAAHRNAAA97gAAA9BYWVogAAAAAAAAWnUAAKxzAAAXNFhZWiAAAAAAAAAoGgAA
FZ8AALg2Y3VydgAAAAAAAAABAc0AAHNmMzIAAAAAAAEMQgAABd7///MmAAAHkgAA/ZH///ui///9
owAAA9wAAMBs/+EAdEV4aWYAAE1NACoAAAAIAAQBGgAFAAAAAQAAAD4BGwAFAAAAAQAAAEYBKAAD
AAAAAQACAACHaQAEAAAAAQAAAE4AAAAAAAAASAAAAAEAAABIAAAAAQACoAIABAAAAAEAAAEAoAMA
BAAAAAEAAACXAAAAAP/bAEMAAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEB
AQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAf/bAEMBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEB
AQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAf/AABEIAJcBAAMBEQACEQEDEQH/
xAAfAAABBQEBAQEBAQAAAAAAAAAAAQIDBAUGBwgJCgv/xAC1EAACAQMDAgQDBQUEBAAAAX0BAgMA
BBEFEiExQQYTUWEHInEUMoGRoQgjQrHBFVLR8CQzYnKCCQoWFxgZGiUmJygpKjQ1Njc4OTpDREVG
R0hJSlNUVVZXWFlaY2RlZmdoaWpzdHV2d3h5eoOEhYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0
tba3uLm6wsPExcbHyMnK0tPU1dbX2Nna4eLj5OXm5+jp6vHy8/T19vf4+fr/xAAfAQADAQEBAQEB
AQEBAAAAAAAAAQIDBAUGBwgJCgv/xAC1EQACAQIEBAMEBwUEBAABAncAAQIDEQQFITEGEkFRB2Fx
EyIygQgUQpGhscEJIzNS8BVictEKFiQ04SXxFxgZGiYnKCkqNTY3ODk6Q0RFRkdISUpTVFVWV1hZ
WmNkZWZnaGlqc3R1dnd4eXqCg4SFhoeIiYqSk5SVlpeYmZqio6Slpqeoqaqys7S1tre4ubrCw8TF
xsfIycrS09TV1tfY2dri4+Tl5ufo6ery8/T19vf4+fr/2gAMAwEAAhEDEQA/AP6lPD//AAiv9haP
9q0HRZ7n+zrPz5pbC3eWWXyU3ySuyFmdmyWdjknkmr0stvP4f1V/636t/r6fj2+fqdTpOkaDrt/B
pmj+DdL1K/uX2Q2trpFvJK3dnbEYEcMYy8s8rJDEgLyuqgmnp/XI/wAk/wCr9hFvXvB1l4S/aR/Z
x+GmqeHPClxpfjey8ceJfEMUWnq5kufD/hzV7e20SUMi2l7pavqNvqMxlid31SxtZI1jitkeaW77
bX3tZv8ADp6632A+6f8AhT/wq/6J14M/8J3S/wD5GqQD/hT/AMKv+ideDP8AwndL/wDkagD8zP2n
fif/AMKq/aM+HOn+DfhBpF78BPhvq/gew/ag1i0+E+j61o0Nv8adQn8NaFLd+LpIBfeFZvhNHN4Z
+Iusw6Nb3g1vQvFMMGpyW1vZkOAfpn/wp/4Vf9E68Gf+E7pf/wAjUAH/AAp/4Vf9E68Gf+E7pf8A
8jUAeW3/AMMvh0nxr8KaOngfwsulXXwt+IOp3OnLomniyn1Gw8W/DO1sr2W2EHlPdWltqN/Bbzsh
kiivbmNGCzOCAepf8Kf+FX/ROvBn/hO6X/8AI1AB/wAKf+FX/ROvBn/hO6X/API1AH5NH4hapbf8
FN779n250zwQvwgOu6ToNl4Jh+Hfw91a/mtdR/Zvj+I41Jo7Lw7b/EXR9Pj8awXkt58Sr3xFqHge
ydLb4f3WhRatrum6nZgH6y/8Kf8AhV/0TrwZ/wCE7pf/AMjUAH/Cn/hV/wBE68Gf+E7pf/yNQB5R
4U+GXw7uvit8W9MufBHhefTtLs/h0+m2MuiafJa2DahpOsy3zWkDQGOBruWGKS4MaqZnjRnyVBoA
9X/4U/8ACr/onXgz/wAJ3S//AJGoAhufhF8L4re4lg+Gngy4njhlkht/7A0qMzyojNHD5jW21PNc
BN7cLu3HgUAfnx+wpd+BPjR4a0nxN8R/HvgzxJ8ata8Na1f/ABM/ZqHgX4V+GY/gd4gsvFCWGoaA
vhWy8H2XxU0h/Bkxj8JPfeN/EusReJzMdfRZDeWEsAB+hv8Awp/4Vf8AROvBn/hO6X/8jUAH/Cn/
AIVf9E68Gf8AhO6X/wDI1AHlPwj+Gfw71XS/GcmpeCPC1/JZ/Fb4n6Xavd6JYXD2+nab4x1S10+x
haWBjHa2VrHHb2sCYjhhRI41VQBQB6t/wp/4Vf8AROvBn/hO6X/8jUAfP37WHhjwv8Mf2YP2hviP
4C8CeC7Lxv4E+C/xK8XeEbxvBuhauLTxJ4e8Iavqui3J0u80+6tNREOoWtvIbK5tp4Lrb5M0MiOy
EA+ef2OL7R/id8RvjB4Xnu/BHx9+EnhPwb8Hdc8MfGFfhv4C0RrX4i+MLLxVL8RfhWdb8C+HPD3g
3xmPCdrpPhXX/tuk6THqHh0+Lf7B167vLqO3MIB+g/8Awp/4Vf8AROvBn/hO6X/8jUAMl+EHwqEc
hHw78GAhHIP/AAjumZyFJzkW2f60Aeb/AAY+GHw51j4QfC3VtV8DeFdR1PU/h54Nv9R1C80PT7m8
vr678PafPdXd1cSwNLPcXE8jzTTSMzySOzsSSTQB6X/wp/4Vf9E68Gf+E7pf/wAjUAfJP7dun6N8
F/2TPjN8Tvhl4N8E6L458J6Jo13oOrSeDvC+ppYS3vi3w/pV7ctZ63pGpaOwj02/vSZ9TsLyys/+
Py4gkjt2FAHpv7PXgv4WeNvhH4U8RzWXgP4h3l6mprf+J7V/hb4viuL2DV76Gex/4SL4YeFPCfgj
U20rYumtNovh/Tgv2by7xJr9Lm4mAPaf+FP/AAq/6J14M/8ACd0v/wCRqAPBf2pfh14C8Nfs3fHX
xD4e8HeG9E13RfhT451PSNY0vR7Gy1LTNRs/D1/PaX1jeW8KT213bTIk0E8TrJFIqurAjNAHnPgr
9kmHxT4Q8M+JD8W/HWlnXdD0zVjplnpng2SzsDf2kVybS2ku/D891JBAZDHG9zNNOyKDLI75Yu7/
AKSb+8DyTw5+z34V+LHxV+MfwWv/AB98ctD1f4FS/DnVr3U7uX4f6bYeI4PiFYeI7/w9q+gXHhAP
qa20CeG78S22vDT7tJZIJTpyHa4Lv+kl/X9MD1rRf2ONB+EHjbwj8TNH8dfEzxn4o0W41600az1W
/wBG1K/kNx4P8T3D6fpU2ux/ZIbnUmt/scMN3d2mmPdXEFxfSx/Zobm3QHJ/Df8A4KL/ALN/xE0n
R9el+MfjHwHo3iTxNpngjw7fePfDHhnSRqvjT+y/As/jfw68FhpmqT6I3wj8WfEjwl8K/inrfiNN
I8NeFfizfT+ApdZn1q0lioA9b039rr4Aat4r0jwJY/tD6pL43174mS/CHSvCEngu4tvE9347i0W1
8SPYDQrnwNFqcek/8I5eReIU8VTW0fhaTQVudYTWW060urmEA+qv+Ee1w5B8b62d33v+Jb4Y54xz
/wASTnjjntxQAv8Awj+vf9Dxrn/gu8M//KSgA/4R/Xv+h41z/wAF3hn/AOUlAHzn8e/GGlfAXTPE
fx58Z+JPGeo6V8MfhJ451nVF0DSvCtzrUmhrr3gm4v7LTbG7srDTrm5ubi1sZFa6uIGT7PtS4RJZ
VcA+Zbn/AIKC2txoXj/xP4P+Hvxv+IGh/Dz9om1/Zl1mTwv4p/ZM/thfiDqXx2vf2cdHub/wvq3x
P03xL4X0XWfiha29rpreL9L0LVZvD2o23idtMTSIb24tQD0TwF+2j4U8a+E/2nfHN7dfEnwn4a/Z
Pn+JNp8S3v7v4GeJ/ELXvwi1Txro3j21s/Bfw/8AEPi7xfpjWGo+AtcTRpvFWjeH4PFVn9l1Pw5J
qOnyvcRgHr/7M3xx8PftWfDM/Fn4b+JviVpvhv8A4Szxf4L8nxt4J0bwrrZ1bwRrdz4e13/iWaho
S3H2SHVrO7tI5j1mtriGRY7iCaKMA+g/+Ef17/oeNc/8F3hn/wCUlAB/wj+vf9Dxrn/gu8M//KSg
D5T+LnxHs/2f9bvtenuPiP438a/Fjx38MvhP4E8EeCNN8DS+JvH/AI51XQvFOq6XpFnN4n/sDwno
Vno3hjw/4q8T67rmua1o2lab4e0DVb66upriG2trgApW/wC2D8EbTXn8E+N/jhqXw1+JOn2mi/8A
CTfD7xhp/hJtX8LeIdam8FW58Dahr3h3TNf8Dar420mb4i+CX1vw94Y8Va9e6bp/iXR9buVTRL+2
1GQAg8V/tqfs2+Ddafw3rH7Slw/iIWHi2/j0bS/DEWr3kx8F6/8AFPwnrGnq2neDri2j1i48W/BT
4peFtA0i4uIdQ8T+IvBuraP4fg1K9SKGQAxPAX7dX7Lnj+TwwNG/aOvdJ1Xxp4O8JeOIbDxR4MXw
readpHjHwDrPxL8L23iq61rwXZ6f4f1rVPAfh3X/ABHpmiaxf2+pX2kaRfXmnW91axCVgD6/8MSP
4z8NeHvGHhr4j6xqvhzxXoek+JPD+qRaV4eji1LRNdsLfVNKv4o7jQIp447ywuoLhEnijmVZAska
OGUAG5/wj+vf9Dxrn/gu8M//ACkoA+C/il+1H8Nf2SvFfw+8BeP/ABB8SrST46+Lf2h9Z0PxBonh
/wAH6j4X0rV/h7d6Tq+o2vi7VNRS0m0O98f694w0Hwl4FVLa403U/Gmt6V4cluNLl1LTRcAGlpv7
ff7Ll54au/EupftKXXhyPSvBnhfxtrmm6z4csPt+lWfim5+H2mR6LFJp3hXUNN8ReKdC8Q/FT4fe
FvFfh3wlqGv6n4a8SeLdC0jV4LW61OyScA4a1/4KWfs2XHjTw94Uuvix8RtB0zXfFPxr8B3HjHxb
8NbnwroOh+Nfgh4y+EXgnXdH1VNa8D215Bperaj8YdGntPF80UHhXSYdL1CHxFqmlXk1pbyAHtfx
O/ap+G/we+OvhP4B+OPH3jrSta8TfDbxh8T7vxkvhrwo/wAPfB2keFdG8WeJ7XSPF+u/2cs+leIP
GHhT4bfFzxR4RsYtPuotR0f4S+OZrm5s5rTT4dRAOT8Oft9/sk+K7bxDd6N+1hbyQeFvDOqeLdae
+8NHRzBo+kT+EYLoW6av4IsZNR1eVfiD4AvdN8Pact3r+saV488E6zpWm3mleLNAvNQAHT/t0/s4
XGoeGNH0H9ohvEd74nXwld3At7Lw5o9l4X0Hxl4n8Q+DbHWfF+qeI9A0jS/D09r4i8JeLdLu/C+p
3lt4xN74V8T2sGgy3Hh7WI7MA5Wx/a8+F3wt8Z+H/gHqHjDxDpGleCP2YfA3x58R+P7rXvgvZeEf
DPwp1Lw98QptM1Ky0jXNatvif42i0+w+E2vT65feDfBniW00SzvNGvtZvoIryeSAA9U8Vfth/s4+
CvE2ueD/ABL+07Bp/iPwzZ+NNQ8R6aui2V5JoNr8PtQi0bxTJq81j4RubbTmtNeubLw5YxXc0Uuu
eJdR0vw7oaajrWp2FjcAGTa/tvfstXmr+GtBP7VVjaal4qspb2zh1bRbTR4NJWHWfH3huSz8ZXmr
eD7Oz8Bav/wknwt+IfhtdE8bT6Bq8niHwjrWiJZNqlo1qQD2r4MfFLwL+0B4TuPGnwe+M974w8N2
OsTaBf3Vpoek6dcabrMWn6ZrP2DUdK1bwxp+qafcXOia3omvWIvLKEajoWtaRrVi1xpmqWV3OAeu
f8I/r3/Q8a5/4LvDP/ykoA8t+OHgq51z4OfFDRtc8V65qOj6p4E8UWGp2BtdBtReWN1pF3Dc2xub
TSIbqATROyGa3ljnj3bopEcBgAc58NPH/j2x+Hvgmysfgj401mztfC+iW9rq1p4i+HFva6lBFp8C
RX1vBqPjKzv4YblAJo47y1t7hEcLNEjgqADyD4Z3+j2Hx1+NfxK8EeDviL4s+JHjCDw5oXxT8Kxf
GT4G+IbHw6PCb6jbeFrO48Mad41+3+GbjRFutc0+yS9lSV1vNRhuxczxo1uAfQlx448b6prng6DU
vg74t8Pwx+Ipp47zUfEPw+uIZ508NeIkWzRdL8W6hOs0kckkyvLClvtt5EaZZXhSQA+c/EH7DPwV
8Q618OfEVx8LfFkGs/DH4hfGb4iaBePq/wAN9cS6vfj98Xofjl8UtC1Sx8W2niLTn0LXviNaWGr2
s2m2emeJdChsIbLQvEenwT34vADO+A37A/wU/Z08eQ/EnwD4B+J9z4vttc1rXYdT8TfEHw3q7tc6
34TXwRPHfGO6spNaeLw7HHbHV9dk1PxJql6raz4h1vWdZmuL+YA+7v7e8Q/9CPq//g28M/8Ay5oA
5TWPizpPh601y/1630/RbHwzPY23iO81bxp4F0+10G41Rbd9Ng1m4u/EcUWmTagt3atZR3jQvdLc
wGEOJULABL8WtJgvtc0ya30+LUvDGkR+IPElhJ408Cpe6BoU0Rni1nWbZvEYm03S5YAZo7+8SG1e
IeYspXmgDyr4neHfDX7R3hXUPAfiDwxqfiL4c/FL4XeJdIvp/DXi7wyv9seHNX1PwrMb7Rtd07WZ
4BC6pEYbu3mfzBMjwiRBIygHCaB+yZ4P0DRfGvhX+yfi9rHg7xl8cNF/aDTwjrPjrwRNo3hP4i6L
8fpv2lxP4TlsorDWbbSNS+K8x1TVNM1nVtbWbTEj0e2mtLNSGAOouP2avhldfCX42/Ba4+EGsS+C
P2hdS+MWq/FNG13wr/bGv3Xxy8SeKfFXjndrA1EXaRDVfGOtHQEdpv7CtpLa3smVLaM0Adr8DfhR
4T/Zy+Htp8LfhF8JdQ8LeCrHxB4y8TW2kW+r+GGSLVfHfi3WvGviCUMNXT91JrWvXwtIdu20sVtb
KL9zbR0Aevf294h/6EfV/wDwbeGf/lzQBn6p4zvdD0+61bWvDNzpOl2UfnXmo6l4h8I2NjaxZCmW
5u7nXY4IY9zAb5JFXJAzk0AfN/xp+GPhv44PN4f8c6P408MaloPjn4d+Nvh14u8G+OvDnhLxz4J+
JGg6br1tomteE9Yk1O4s5dVvNG1PxDol3pN5p+s6ZrPhzV9c0jVtKvLG+nhoA+aNQ/Ye/Zk8UeI9
V0XV9R+K/iPxT4tsta8Uado978fPCl9renfEO3tfBvhDxV8fvC9iup/b0+J5n+Gfh201rX5U1Dwz
YavY6wkPhqwm1vxBFqAB6L4L/Yn+A8fhzTJNL8J/Ebxxpl/qng3xe/iXVfitoXiG48W6p4T+LHx0
+Numa5qOs2erxRam2q+Pf2jPifqWrS2hhgv7PU9OsIFtrbSrUAA4vxx/wTi+GXij9nfxZ+ztp+jf
Ey10XxxqX7O3/CReLfEPi3w54h8Wnw7+zzd+CNI0XS9J1Cy1rw+NJ1PVvhf4Pf4bXGt2yh207Vrq
91a01sSX9lqIB+kMGr61awQ21t4B1K2treKOC3t4NS8LQwQQQoI4oYYo9YWOKKKNVSONFVERQqgA
AUAS/wBveIf+hH1f/wAG3hn/AOXNAHyB8V/2Z/hn+1BoniXSPi/8MPEniXTb7wx8e/hHNb2PivR9
IFt4Z+MHibwRq/iea1lt9XiubLxVo2ufDDwZrPhPxNYyxX/hnXNHj1XSJ1ufLmQA888Pf8E8PgT4
b1CxubLwJ8W7nTNBv9E1fwb4Y1H4oaNd+HPAmt6f8RPhN8VvEOteErNtQS6sdQ+IPj34KeAfEHjd
ry+1C3u57TV4dDt9AtfEWtw3wB1WufsQ/CTxHe/Eu51nwR8Ury1+KL/GJtZ0dviLoCaVo6fHvxB8
J/F3xTg8NRRXyXWnQeJPFnwb8JeI/KubzUF07UZ9dTTfslhqQsrYAh+Mv7B/7P3x58X+NPiJ8R/g
t4q1P4jeNb/wldS/EC08baRY+LvDOneDfDE3hDT/AAv4M1WLWmPh3wnqOg6r4utNf0G2ie01r/hP
vHL3gZvEE/lgGV43/wCCfnwA+Iela3o/in4U+PtQtNc/tSaff4+0J2tdR1Hwb8BPBVvq1pHcalPb
G+0aw/Zp+EupaQt5b3ljHrOi31ze2V9a6vf2UoBC/wCw/wDs7R6Z/wAK+134deItWHiS1+H97f6D
eeL/AIf+H38WWfwYvvHV3ptzJ4b8IP4X0dLJrn4v+JE8XDw9oml2V8dYsjcR20/lSygF67/Y6+Hf
xBgk1/UtA+K1npPj/wDZk8K/s3ePPB3h/wAd+ErDwb42+F2heFfiBoXh231KC8W58S2WraFafFXx
Xc6Xq+i69ol6t7JptxqCXb6dGhAM/Sf+Cfnwa0/Q/iHpd/4X+NXiXV/ijp9zD4v8ceIvito1z41u
9dl+Jlp8YrLxpZatY3unWuleK9D+JGnaX4l0G70/TrfTdLm0uwsYNK/sqD7CwB50n/BMP4S3/j3X
9f8AF2n/ABh8aeAvE/hnwvaeL/hhrXj3w/Ho3xN8faV8QP2g/iTrvxO+LV9p2rWVx4s8Qat4q+P+
qavo9josXhLR/DN/odkLazvNLXTNK0YA+yP2dPgpoX7MPw6i+GPw48E+KJPD0OpSaoJ9XvfhjBqk
07abpejwi9m8K2nhez1GW20vRtNshqeo2N1rd5HbJJquqahcfvqAPeP7e8Q/9CPq/wD4NvDP/wAu
aAOB+Kus65N8NPHkU3g/VLSGTwnryS3Ump+HpI7dG064DTPHBq0szrGMsyxRvIwGERmIBAMv4WfE
z4dab8NvAen6h468JWV9Z+EtBt7u0uvEGlw3NtcRabbpLBPDJcrJFNE4KSRuodHBVgGBFAHzT8Gb
ePS/2k/i/wDG34rar8CbK517Rr3wD8Mtd8DfE+1kGl/Cyz8XSeItL0HV/B8vhTRRJ4p8Sajc3Hi3
xr4tvvFOuu+ri00LRNP0/SrSS61AA+t9U+IvgHV9X8G2+leNPC+ozw+JpLmWGy1zTbmSO3Twz4ki
aZ0iuGZYlkmijLkBQ8iLnc6ggHoP/CUeHP8AoPaR/wCDC1/+O0AH/CUeHP8AoPaR/wCDC1/+O0AH
/CUeHP8AoPaR/wCDC1/+O0Afip8Y/wBjXxl4/wDiF+1h4m0bwf8AB3S7L4m/GH4S/Fv4UTaf8TPB
cNvq3jLwV8LfHPwj8Q+KPi54S8afAz4i+ENattb0rxtfavfaVqOg+K9RMosr7StTsfEfh3Q72IA+
Tof+CUPxw0TUvEdtafFP4YeIdItvBnwj8My30/jiDTbv4n6P8MNb/Yvvr/RrO31T4feJbvwL4i+J
Wj/suavp3xM1TxrqnxW8A6pe6l4PHhfwH4W06TxgLwA/bz9m3TfFPw6+H/we8G/F3xz4Q8S+P/Df
w28SaZ4k1nw82i2Oj+a/ijRbnSNNhGkaN4W0u7uNI0N7HR7zWLHwz4btvEN/pl7rsOgaOl+dPtgD
6g/4Sjw5/wBB7SP/AAYWv/x2gA/4Sjw5/wBB7SP/AAYWv/x2gA/4Sjw5/wBB7SP/AAYWv/x2gA/4
Sjw5/wBB7SP/AAYWv/x2gD4+/b3+G4/aP/ZK+NPwU8Iad8MvGXi34heEb/w94Ys/iD4ktNI8NaJr
9/E8GleMJ746J4neO98I3kkWv6YLfSZLs39jA1nc2V0sN1EAcn+0N4O8Y/FvTvh/4k8IS/D+D4lf
CH4yfAf47HwP4g8aNZeGvEF74R0jxFYeKvBFt45s9Ev5bOZbLxPqn9ieIZPDEtrdajp9gl/YafZ3
89xZAH5/237DH7SXhG/vNc+EfjL4HfDv4lfET4d/GvQPiv8AEy68df8ACXaVbXXxs8a/H3xjoVv4
A8N3/wANLPxn4X8ZfAbXvj1Pf6N478MfEPwnoXxR8P8Ahm+0Xxh4Ki1LXtI1DwqAfo9+wr8GdS/Z
M+Dur/ATxD49+HHiLwR4N+I3i+9+CVx4NsbjwpY6N8KvF8tn4ytvBtx4X1TxD4quNDTwV4017xp4
a8O2q+K/EUbeCtP8MSm9t52n02yAPs//AISjw5/0HtI/8GFr/wDHaAD/AISjw5/0HtI/8GFr/wDH
aAD/AISjw5/0HtI/8GFr/wDHaAOR8HeI/D8dprYk1vSkL+LvFUihr+1BaOTWrtkcZl+66ncp7ggj
g0Add/wlHhz/AKD2kf8Agwtf/jtAB/wlHhz/AKD2kf8Agwtf/jtAB/wlHhz/AKD2kf8Agwtf/jtA
B/wlHhz/AKD2kf8Agwtf/jtAHxJ8T/h1q+vftvfs3/H/AMM6H8K7jwt8OfhX8Zvh54+8c33jS10v
4gPafEq48JXuh6Ppekp4avm1jQfDt94Pnv5LW58T6XBJe+KZriG2EunyvdAH1n4I8R+H4fBvhSKX
W9KSSPw5oqSI1/bBkddOtwysDLlWU5DKcFSCCAQaAOo/4Sjw5/0HtI/8GFr/APHaAD/hKPDn/Qe0
j/wYWv8A8doAP+Eo8Of9B7SP/Bha/wDx2gA/4Sjw5/0HtI/8GFr/APHaAPPvix4i0G4+GXj+CDWt
Lmmm8I6/HFFHfWzySSPptwqIiCQszuxAVQCWJAAJNAGZ8KfAvgi++GXgG8vfB3hW7u7nwjoE9zdX
Xh7SJ7i4mk023aSaeeWzeWWWRiWeSRmd2JZiSSaAPlD4erHa/t0/Ej4S6vceFfFHgHWPgncfE3wl
4bh0fwN4jt/DOqaP8SrbwprsepahYeB/COo+DrqNdZsdK0bwhNcfEBNTstN1LWr/AMU6XqNmdO1E
A+0NX8G+D9M1bwXPpvhTw1p88nieSB5rLQtLtZXhfwv4ldomkgtUdo2eNHZCSpZEYjKggA77+xtI
/wCgVpv/AIA2v/xqgA/sbSP+gVpv/gDa/wDxqgA/sbSP+gVpv/gDa/8AxqgD8dfiD8SfjzqnxP8A
20fAHhb9oP4WeCfDvwY+KHwa1+XxFq2geDPD+s/Dv4P+KPgj4x8SeIvC3he51Pw1470bVvE8Hj7T
fCN1qeq+ONLa2m8Np44jtJPD962ipZAH53+Gv+Chv7YXiLUtFOo674E8P3fxh0/4cfDXRtPvvDPh
7RdD+FXxAv8AXv8Agnf4X+JnivXIrzwZrOr+CbTw/dftIfFV/C+v69qnxSsPE+oiL+2Phv4Hg+H8
1h4yAP3i/ZS8f6b8a/hj8HfiJLY3dzNrXgPx3YX974hj8N31/rGqeEPH1l4M1HX11Dw54f8ADOh6
rpeu32g3WseH9Y0/w14di1XQNQ07UToOiyXcmm2wB9cf2NpH/QK03/wBtf8A41QAf2NpH/QK03/w
Btf/AI1QAf2NpH/QK03/AMAbX/41QAf2NpH/AECtN/8AAG1/+NUAfF3/AAUC8eRfBj9lj4iePvD/
AIvv/hx4usRpWl+BL/wl4f8AAWseJvEnxA8R38WgeB/BWj6Z480zU9EvpPEfijUdLg1C2h02/wBa
k0aLUhodrLqf2cUAecfFr4k+O/hBoP7NWr67rngD+1vFvxv/AGXPh38c/F+i6NZ/8IFqWmeNfB3i
az8XX2gT6xFv0Pw94i8bR6Onh2/uJIb2OO/0yx803N2I5AD8/b79vj4p/CLRLj9oP4keLPDvxM+H
firSP2svD/wX+FHw60nwTFrGo+OPhD4k/a28WeAdS+JGl3fhmPVLnwZ8Rvh58MPhn4c+FvjDwX4+
guda8S6hpGl3vgLW18UnxXaAH6Hf8EyPjj4q/aM/Zn/tD4xaVeS/GP4V/Ejx38HPiVqPibwJovgH
WvEOq+Fr621jwz4tvfBGm3Wo2/heXxZ8O/EvgzxBLpaTm3W41CebTWudIm0+9uQD9DP7G0j/AKBW
m/8AgDa//GqAD+xtI/6BWm/+ANr/APGqAD+xtI/6BWm/+ANr/wDGqAOQ8G6TpT2muF9M09ivi/xW
gLWVsSFTWrtVUZiPyqAAo6ADA4oA6/8AsbSP+gVpv/gDa/8AxqgA/sbSP+gVpv8A4A2v/wAaoAP7
G0j/AKBWm/8AgDa//GqAD+xtI/6BWm/+ANr/APGqAPib4neO/EHhP9uX9mP4ZWvi3wtafDr4qfB7
9oe+1z4bTeGtAXU7/wAV/D+6+GV54a8Tx+ILiSTVmX7J4i1rTrbR7O1s7N1ttRubqbUZRAmnAH1h
4H0nSpPBnhN30zTnd/DeiMzNZWxZmOm22WYmLJYnkk5JOSSSTQB1P9jaR/0CtN/8AbX/AONUAH9j
aR/0CtN/8AbX/wCNUAH9jaR/0CtN/wDAG1/+NUAH9jaR/wBArTf/AABtf/jVAHnvxa0rS4vhh8QJ
YtNsI5E8IeIHSRLO3V0YabcEMjLGGVgeQwIIPIOaAPL/AIaeH/jVP8PfBM+j/EnwTp+lS+F9Ek06
wvPhrqGo3dnZvp8DW9tc38fj2xS8mhiKpJcrZWqzOC4gjB20AeRfD3xYmpfHn4o/CT4c+PvhPb/F
DQtB0zxn8Sdd8Pfs9y6bp2ryalrWpaW9lqHi6y8fQL4l8TaTqUMza7aPPez6RNqEUd7NHfTXEEYB
9B3GhfF221zwe/iL4heENVs28RTJBBpvw8vtKmivD4a8RNHcSTzeONRWaFYlnje2EUTO8qSCdREY
5QD1L+zvGX/Q06P/AOEpN/8ANJQAf2d4y/6GnR//AAlJv/mkoAP7O8Zf9DTo/wD4Sk3/AM0lAH5r
fEn42/smeGPEHxqsPEvw98L+JPHfhr4s+Cfh7460O3/ZIl1XxV8SPiTr/hDxD8UvDdxpIvoEm+IC
WHhXwx4u8TxeK1uL7TbYaBqzWOqSXoijnAOOu/24f2GfEOtfFG+mvfAviW41f4ceEdY8V+J3/Ztl
1MfFvw34vHwUg8IeDjfXDSah4xutXuPjj8F9P0Xw/raPa31z4itYdPWceHdcOkAH3x8Orq88Q2fw
21jwpcaZ4Y0DUfhld3Hh/QW8DQ6MmgaILvwpHa6J/Ylh4haysPsUQgt4oLKYWlpFb+Rbo8TI6AHs
X9neMv8AoadH/wDCUm/+aSgA/s7xl/0NOj/+EpN/80lAB/Z3jL/oadH/APCUm/8AmkoAP7O8Zf8A
Q06P/wCEpN/80lAHzt+1Pr3hT4f/AAZ8SeOPjjoejfE74deE2g13WvD7fBWH4kJaR2CTzSeIJPD9
/q99aRRaNaC7uZNSmSM26EwwStdXUME4Bxmp+NvhZ/wjHgjT/EF34O1X4V/H2/8Agv8ADn4d+G7/
AOETaj4U1xfG3hTUvEfgDR7vwbe3f2TRNHj0XRPMS21WwhtNLe2tIJYLKaJIwAeT+Cv2gP2VPHHx
O1fw/wCG9K8Cf2/8OPh74jbxR48vf2drTSNE+HngL4SePPH/AIT/ALF1Txbf3VsdJ8O6V4n+Cvi+
98P2NtMdEs18N2F9D9jmutHFwAfU37PXxN8PftCfC/Q/jr8IvE2lN4X+JrXWpz3eofDDUPCviafW
fD9xJ4L1Oy8Y6Nqmr2GuWPibw9ceGz4Zv7LXbdNS05dGh051SC0gRQD27+zvGX/Q06P/AOEpN/8A
NJQAf2d4y/6GnR//AAlJv/mkoAP7O8Zf9DTo/wD4Sk3/AM0lAHJ+ENP8WNa60YfEulRgeLPFCyB/
DMsu6ZdZuhLIpHiCPYkjgusWGMYO0ySY3kA6z+zvGX/Q06P/AOEpN/8ANJQAf2d4y/6GnR//AAlJ
v/mkoAP7O8Zf9DTo/wD4Sk3/AM0lAB/Z3jL/AKGnR/8AwlJv/mkoA+a/GGu/DWL9pb4W/DzxXY+F
dS+PPiDwB438ZfDjxnf/AAJn1GbSfDHge80uz8R2Gk/FG5uZbTRdTSTxdHcL4csddh1KS0vbu+ks
ltrkS3AB7b4K0/xa3g7wq0HiXSooW8O6M0cT+GJZnjQ6dblUaX/hIY/MKjgv5absZ2LnAAOn/s7x
l/0NOj/+EpN/80lAB/Z3jL/oadH/APCUm/8AmkoAP7O8Zf8AQ06P/wCEpN/80lAB/Z3jL/oadH/8
JSb/AOaSgDgPirYeK0+Gnj17rxHpdxbL4S15p4IvDUtvJNENOuC8aTnX5xCzrlRKYZdhO7Y2MEA4
L4bfFfUdL+H3grTovhX8TNTjsfC+iWqajp+grNYXyw6fAgurOb7QPNtp8eZBJgF42ViBnFAHiHw3
8E/Br4cfHDxV8Xfhz8FPitpHjjW/CWoeFfEeh2LXmoaai6v42v8Ax3rutS6Jea1etY6tq/iPVJJ7
+RFgtt53RW0Nxc3Mk4B9Kz/E3UNb1zwfay/DP4iaMIfEE92LnVtES2t5mj8NeIY/s0chuCDcOJjK
qnGY4ZWzlcEA9R/4Su8/6FLxL/4CQ/8Ax+gA/wCErvP+hS8S/wDgJD/8foAP+ErvP+hS8S/+AkP/
AMfoA/Or4lfsieEPH2u/tHeIfFvjvx61t8ePEHw81TxVp2seF/hfq2neBJfAWjX3h7w1D4XPiHR7
5dH1UeHNWksbLWNQF1qUEjRXluXEs8FwAeM3X/BLr9mGLWfElzpU/wASdFjttA8ExeHdHYeBtTXw
Vb/D3U/gprvgV9bk1fTLq78a+EPCF58B/AQ8JeE/HT6l4a8Oabd+KLPSIbdfEc00AB94fAbwP4Z+
A3hH4XfCvwFovi7U/CvgzwF4nsdKvb9dOubzU/7V8UaPr2o6mG077LpcNtcapqF5NBYaXa2mlaXb
XFrp2l2tvp9tbwxgH0X/AMJXef8AQpeJf/ASH/4/QAf8JXef9Cl4l/8AASH/AOP0AH/CV3n/AEKX
iX/wEh/+P0AH/CV3n/QpeJf/AAEh/wDj9AHhX7R/gS2+Pvwl8SfDHX4PE/hfw7rqRnxDev4V8F+J
rK60e3WV7yx1LSfG1hrOgyWpVlvI7ua0WfTr+zstQhmU2zRygHkXiT4B+EvE/wAOvBvwfsLn4o+G
YvgvcfAnUvhF47t7/TdY8caF4k+EWgy6T4Q1rUb/AF2O8s/FF/qekR3dlrw1C1kbXrXUtUlDW11N
HdQAHz74j/4J0/BTxpD4T8J674s+Mt9pfh/wh8SPD/8AZljP4G0vxZ4l/wCFu6r43m+Od3rXi7SN
GtPFt7oXxLn+IXj/AP4SPwhb3kHhjTNd1iPWtIs9O1PQdJNmAfan7Pfwo8Cfs86L460f4U+HfHx8
G/EP4i6v8VItH1PWLrxVY6FrnifR9As/EqeH9Y1jUtS1ebTfEOt6NeeMb5dR1TUZW8SeI9euorhL
e6it4AD6A/4Su8/6FLxL/wCAkP8A8foAP+ErvP8AoUvEv/gJD/8AH6AD/hK7z/oUvEv/AICQ/wDx
+gDlPCPiW6htdZA8L+IZd/ivxRMTHaxEIZdZunMTZmH7yPOyQdnBGT1oA6v/AISu8/6FLxL/AOAk
P/x+gA/4Su8/6FLxL/4CQ/8Ax+gA/wCErvP+hS8S/wDgJD/8foAP+ErvP+hS8S/+AkP/AMfoA+bv
Hnwy/wCE0/aL+DPx0m134j6Lq3wh8K/EHw9onw+sdP8ADb6F4i074g/2NH4uvdU+1xSa48kn9g+F
kSTT7y3itDpcSnJvptwB7Z4M8TXUHhDwtCPC3iKYR+HdGQSx2sJjkA063w6Ez8o4+ZG43KQcDOKA
Ol/4Su8/6FLxL/4CQ/8Ax+gA/wCErvP+hS8S/wDgJD/8foAP+ErvP+hS8S/+AkP/AMfoAP8AhK7z
/oUvEv8A4CQ//H6AOC+KfiS6ufhr48t28M+ILZZvCevRtcT2sQhhDabcAyysJiVjT7zsASqgnBxQ
BrfCPWNJi+Fvw9il1TTo5Y/B3h5JI5L62SRHXTLYMro0oZWU5DKwBB4IzQB8s/BD4W6z8O/2qvjl
44stI8PaJ8KfH+nazrNxrniHUPAeoeOdc+J2t+Nhq95ceG9Y8OzNr0Pw3n0Eea2h+Mj9v0/V49Pi
03/RobiOIA+w/EGraXPqfgpYdSsJmHip3KxXlvIwUeFvE4LEJISFBYAk8ZIGcmgDsvttn/z923/f
+L/4qgA+22f/AD923/f+L/4qgA+22f8Az923/f8Ai/8AiqAPw4+On7JXxh8feOv2x7/Q/hjri+Hf
H3xi+DXxU+F9nP4++H/ifwr8TNe8IfCnxl8M/FieO/CPiT4naNLYeDb2+8R2XiS00ue80ibSdQ0X
wvr2l6PPd+HI9KcA+TIf+Ccn7cOk6/4xF74gm8UWt34C+D3g3xX4isfiF4WOofEvw94B1z9ikeNr
XwvqPiDX4NZ1PXPih4Z+BXxNt9Y8N/Faz0nwV4bn1Oay0LU5rLx54ie+AP3M/Ze0T4g+DPhr8EvC
3xhXwnp3xE0H4WeINN8Q6f4Sj0mx0LThD4m0MaLp8Vto0j6HDf2egf2Zba0NCc6E+tw6lJoh/spr
SgD6u+22f/P3bf8Af+L/AOKoAPttn/z923/f+L/4qgA+22f/AD923/f+L/4qgA+22f8Az923/f8A
i/8AiqAPif8A4KC/B74t/tFfsxeOfg98EvFXhTQ9b8ZW19p3ii18Ra3qugR+K/B7eHtf+0eDLHxF
oMc99oU/iPxEfDdpqd8Vjhn8NDXtMe7sG1CO+tgDyLxp8LPjZP8ACD9nGDSbPTfE/wAWP2e/Gf7K
Pj34heDtD8Y2elReNl8BeDNU8LfELQfD3iTXrrStLupf+J3e6zpo8QXdlY6s+kpbXE8U11C4APiy
x/ZM/bW8Da1L43+Fnh3RrP4veP8A4bfHfQfF3inx38QPBniDwl8Nbn4x+Ovjz47+Hb/DTVItfk8a
aF41+Eet/GPRrbx/aWOj6j4A+Ifh3wvdPo94muab4ffUAD9LP2Bfg/8AE39mz4Iah8B/ifqXhvUt
J+G3xB8V2Pwd1zQ/EV/rkF/8HvELWPjLw3pV3c69M/iGO78Dax4j8R/DyEa0Fu7vSPCelalGZba9
glcA+3Pttn/z923/AH/i/wDiqAD7bZ/8/dt/3/i/+KoAPttn/wA/dt/3/i/+KoA4/wAGXdoLTXc3
VuM+MPFhGZ4xkHW7sg8tyCOQe9AHYfbbP/n7tv8Av/F/8VQAfbbP/n7tv+/8X/xVAB9ts/8An7tv
+/8AF/8AFUAH22z/AOfu2/7/AMX/AMVQB8M/FT4feNdR/bp/Zm+MfhjwTd6n4I8G/CX45eBPiT48
j8d6FZafpq+PrnwVf+ENPHgvUPE1vf6l/Z1/4S1a61LU9J8O3FxjW9JjN3cpZyxWIB9eeBby0Hgr
wkDdW4I8N6KCDPGCCNOtwQQWyCDwQec9aAOq+22f/P3bf9/4v/iqAD7bZ/8AP3bf9/4v/iqAD7bZ
/wDP3bf9/wCL/wCKoAPttn/z923/AH/i/wDiqAPO/i5d2rfC74hKtzbszeD/ABAAomjJJOm3GAAG
yST0A5NAHnPww+DPwp1j4c+BtV1T4feFb/UtQ8K6HeX17c6Ray3N3dXGnwSz3E8rJukllkZnd2JL
MSSaAPg39k7X7T4nfHj4j+Avij8KdBszHffHO60Hw9ZeFPD0WjeB9C+F/wAZ4fh14dsfEUkWnRa5
ba74r8OXGmeJ9DudQvbm18R6fcaxf2caW9jbtQB+i178Jfhl4f1rwbeaJ4F8M6ZdT+JJbSae00m1
ikltZPDPiOV4HIT5o2khhkKnI3xo3VQaAPTP+EQ8K/8AQu6N/wCC+1/+N0AH/CIeFf8AoXdG/wDB
fa//ABugA/4RDwr/ANC7o3/gvtf/AI3QB+Jfxw/aY+LnhXxn+2D4W8IeI/ho+l/BD4w/B+O3vtP8
E+Gv+Em8I/Cjxl8J/GWteItM0e016FtM8beK9O+JGleFNPvxdMbmPRr7xHDp8ZvbOwjcA8P+FH7b
vx+8ZeLfinafF60sPhH4e8Ifsyat8Vb+Hw78GtF1/wAQeGfHvgL4bfsw+NvF/hOy0bVLX+0W1abx
D4++J/hKz/t/fpfiuW80NfB37/w1qe8A/ZL9nzwp45/4QH4If8L+0/wxqHxlvvg0dV+J7aV4e03S
NMh8aX1z4UvdU0+302yVrOL+w5r2XRvNgJjuHtJbpMC4IoA+kv8AhEPCv/Qu6N/4L7X/AON0AH/C
IeFf+hd0b/wX2v8A8boAP+EQ8K/9C7o3/gvtf/jdAB/wiHhX/oXdG/8ABfa//G6APjf9ujVvFPws
+CEfjD4S3HgLwjrlh428M/29qfiOw8Nhp/BcY1C98T6b4ePiO1n0X/hKL2zs1TSFv42SV1miizcS
QggHlfxA+N3/AAi3w5/Z2+NOleHLXQvB/wAT/iD+y2vxUufGngy3t9S8IfDL4r+DNYvNYu/EmlRW
7jwlqtt4gvfDOnavOEWLQ7+4lgmaOBXdQD4hsP29fiR4M1y68b/ETQdD8XeA/Efw7/aB1v4Q/D/w
B8OdOm8SeJfEvgvx78f5fhSnje0exXxNoeh/E/wB4V+E1v8ADvxLpoGi6zretjT9VWLUtfgZAD9I
v2BvH/iT41/Au4Pxy8HWOn/HH4XePfFvwq+KhufASeB4dZ1nQri11rwz4t0zw1MJRpmmeMvh34j8
GeKILaGeeK1n1W6svM821lRAD7Y/4RDwr/0Lujf+C+1/+N0AH/CIeFf+hd0b/wAF9r/8boAP+EQ8
K/8AQu6N/wCC+1/+N0Acl4P8K+GpbXWzLoOkyFPFvimJC9hbMVji1m6SNBmPhUQBVUcADAoA63/h
EPCv/Qu6N/4L7X/43QAf8Ih4V/6F3Rv/AAX2v/xugA/4RDwr/wBC7o3/AIL7X/43QAf8Ih4V/wCh
d0b/AMF9r/8AG6APiX4m/EJ/Bn7cP7N3wVivfAkHw/8Ai58JPjfqus+D5/C1nJ4hfxh4Ju/BM/hL
V4dfaJntLPUbPVfEtjb6SNqX8mk39wzM1oqgA+svBHhTwzN4N8KSy6BpEksvh3RpJJHsLZnd3063
ZndjHlmZiWZjksSSSSaAOo/4RDwr/wBC7o3/AIL7X/43QAf8Ih4V/wChd0b/AMF9r/8AG6AD/hEP
Cv8A0Lujf+C+1/8AjdAB/wAIh4V/6F3Rv/Bfa/8AxugDz/4r+F/Ddt8M/H1xb6FpUE8HhLXpYZor
G3SSKRNOuGSRHWMMrqwDKwIIIyDQB5t8NvAvxFvfh94KvNP+LfijS7K68MaLPaabb2Pgp7ewt5LC
BobSB7vwZd3bRQRlY0a5urmchcyTyMSxAPNfDXii91T43eIvg7YeO/i3ofxEi0TVPEmpavqPw78A
6Xo2vaF4d1Sx0FtVg8SR+CGOpWs1/qMdvo0l2EN6kN8bQMLO5EYB7m3gvxzp2v8Ag6bW/il4p1qz
l8QTwLbS2ng2HybhvDXiGSO6jez8H2bmRFikh2yPJCY55CYTIIpIwD1z/hHtQ/6HHxP/AN8+Gf8A
5m6AD/hHtQ/6HHxP/wB8+Gf/AJm6AD/hHtQ/6HHxP/3z4Z/+ZugD4V8dftH/ALK3hHVPivYa9ruv
6r4n8AfE3wr8N/GWiaf8NfC+qeI/EHxE8Q+E9Y+I2iWWj2kngyOfxTc23hbw/wCJfEUmoRvJHa2+
gaxcQzu9tmQAztI/bG/ZZ8X+KPF+n+B/FvjP4jeJ7bwRo3jLU5fBfgDwvr2oeLfClzY/CzV4JNPu
E8MR3WtxaRpPxd+HGsXMV4Yre30/WYrmze4+w3QgAPoX4RePfDnx30X4ZfF34feNPGd34L+Inw41
jxP4X1HVNM0TStTuNHutZ8OR20slhceHgYIbwKLmMyRuZoRbzwTeRLmQA92/4R7UP+hx8T/98+Gf
/mboAP8AhHtQ/wChx8T/APfPhn/5m6AD/hHtQ/6HHxP/AN8+Gf8A5m6AD/hHtQ/6HHxP/wB8+Gf/
AJm6APEvj/4y+Gnwh8BJ4p+M3jHV5/DN34k8PeHNJ0q90jwdrdzr/i7Xb4Wvh7RtG0q98NGC81i5
uBLNbBmiEEFvc3bzRRQSSKAYOt+MvAmlXGijxv4p8QW2kfGTxF8MfAPhbTNZ0bwzdtrHiPxroGs6
3oOhaxps3hy6s4H+yaTeeYrx+TbywMkjSMEYAHm/gv8AaO/Zl8e/EXV/BvhXxlq9/wCI/BnhLxDq
HinXj4O8H2uk+CfC/wAP/GnjzwhdWmva9P4WjbStPtfE3wn8YHSYAraf/wASBbmN4JTApAPd/gZ4
/wDAv7QPww8MfGv4TfEDxLq3gr4iWs2q6dqkml+HdK1C6m066n8P3sGsWNz4XivbXVtJvNIn0a9t
b5ftVnLp5tHCiBVAB65/wj2of9Dj4n/758M//M3QAf8ACPah/wBDj4n/AO+fDP8A8zdAB/wj2of9
Dj4n/wC+fDP/AMzdAHJeD9CvpLXWiPFniOLb4t8UxkRr4dw5TWroNK3meH5D5kpy8m0rHuJ8tEXC
gA63/hHtQ/6HHxP/AN8+Gf8A5m6AD/hHtQ/6HHxP/wB8+Gf/AJm6AD/hHtQ/6HHxP/3z4Z/+ZugA
/wCEe1D/AKHHxP8A98+Gf/mboA8M8R+Lfhfp/wAePAfwg1zxRrUvxl8V+BfF/jrwXJceGfDFzOnh
fwXe6VY6+1t4mk8IsljPDceJbZk06G7E8sM91OY0jO6UA9M8E6Ffy+DvCsg8W+I4Q/h3RWEUSeHP
LiB063Ijj8zw9JJsQfKvmSO+ANzs2SQDp/8AhHtQ/wChx8T/APfPhn/5m6AD/hHtQ/6HHxP/AN8+
Gf8A5m6AD/hHtQ/6HHxP/wB8+Gf/AJm6AD/hHtQ/6HHxP/3z4Z/+ZugDgPitod9B8M/Hsz+KvEVy
kfhLXna3uF8P+ROq6bcExSmDQIJ/LcfK/lTRSbSdsinmgDz/AOGvxeGk/D7wVph+GvxS1H7B4X0S
0+36Z4e0m40688jT4I/tNjPL4hgkmtZiu+GR4YmeMqzRoSQADlPAPiXQvCfxC+L/AI1bwh8ZfFPj
L4ja7oV/qYvvD/hp7vwb4W0bw/ZaV4W8EadaQeK3nsNAtZ4tb8RwG4jhk1HV/Emr3riTchUA9Qn+
Kf8Ab2ueD7Rfh58StKMPiKa68/WdD0q0t5fL8NeIozbxSRa/clrlhN5qRsqK0UUzeYGVVcA9T/4S
yT/oVvFX/gFp3/y1oAP+Esk/6FbxV/4Bad/8taAD/hLJP+hW8Vf+AWnf/LWgD85fid+xq3xI8Tft
FeJ/EPjbxRs+PHiL4beIYLbUPht4PnPwyufhr4Z1jwToV74V1QeKLK9TWj4a1y9sl1ieaGfzpZ9y
SwXlzbuAeW+Cf+CZ/wAO/hZ4h+Jms/D/AMefF3wWnjL4E618A9PmsNL8LxeJPCngfxB4M+GHw800
TeJJNcS71VvB3h74T6dB8PnvILZ9Fv8AUtSuBPeSW9sqAH6Q+GBoPgm78B+EvCPgnW9H8K+EPhtc
eFPDWiWNlp4t9O0DRJvCOm6RZ2SrqjR/Y7Cwsre1X95uUeSAG3MwAPS/+Esk/wChW8Vf+AWnf/LW
gA/4SyT/AKFbxV/4Bad/8taAD/hLJP8AoVvFX/gFp3/y1oAP+Esk/wChW8Vf+AWnf/LWgD5f/av+
C/h/9p3wJ4S8L6/beJvDF54D+Jnhn4p+FdYuvD3h7XdMh8TeHLHXNIjt9Y0HVdbt7DWdM1DRfEmt
2E9lcTJte5ivIiZrWMEA811L9nHTNU+Ffwz+Deg678StG1b9nW6/Z9174Y/ES9sdG8TeII/Enwa0
CbRNI1fxRZ6prH2TxCviTR5NUsdaguLhjdR6rdXCSieKJyAeAeI/+Ca3hbxNp2g+HLr4j/FfTbG0
8H/Fbw14j1Hw94W8I6H448dw/HHU/Hd/8aYfEPiew11Lu98LeKdQ+KXjDUtN8My21zY+DNev9M1P
Q54LjTo1nAPt39mz4MeGv2YPDvjrwb4Gtvidq/g/xd8S/EHxN0rSfEp0zVJfCd/4w0/RJPFelaZq
I1NJLnTNa8X2Wu+Nykscf2bVfFeqwQr9nSE0AfRn/CWSf9Ct4q/8AtO/+WtAB/wlkn/QreKv/ALT
v/lrQAf8JZJ/0K3ir/wC07/5a0Acn4Q8TvFa60B4b8Sy7/FniiXMVpYMEMms3TmJ92pqRLGTtkAy
AwOGYc0AdZ/wlkn/AEK3ir/wC07/AOWtAB/wlkn/AEK3ir/wC07/AOWtAB/wlkn/AEK3ir/wC07/
AOWtAB/wlkn/AEK3ir/wC07/AOWtAHzb4++GOs+NP2i/gl8eodc8aaLafBnwt8SvDNv4Cj8I+Gby
z8TRfFFPD6eI7u81y41pdTspYk8J+GxZJaRukH2O7Jyb+TYAe2eC/E8kPg/wrF/wjXiaXy/DujJ5
sVnYGKTbp1uN8ZbU1Yo33lLKpKkEqDxQB03/AAlkn/QreKv/AAC07/5a0AH/AAlkn/QreKv/AAC0
7/5a0AH/AAlkn/QreKv/AAC07/5a0AH/AAlkn/QreKv/AAC07/5a0AcD8VfEr3Hw08eQHw54ktxN
4T16Mz3FpYrBDv064XzJmj1KR1jTO5ysbsFBIUnigDY+EWpafH8Lfh5HJf2SSJ4N8PK6PdQK6sNL
tsqymQFWB4IIBB4PNAHwF+zD8E/i14B/bD+N/wAV/GsWnW3g7xx/wuFY7ifxHpl9Zwv4i+K+jeI/
Ax8GtbTDWLyx1fwjYtd+LbTxeJm8J+ILRdK8Gyw6Df3NuoB+jXiHULCbU/BSxX1nIw8VOxEdzC5C
jwt4nBYhXJAyQMnjJA6kUAdh9qtv+fiD/v8AR/8AxVAB9qtv+fiD/v8AR/8AxVAB9qtv+fiD/v8A
R/8AxVAH4SfHX9mX4zeN/Hf7Z9xoHwu8Ynw74x+NPwY+KPw0sbrxL4L8QeEPitq/hj4VeM/hx4ut
PF3hzxBrZWy8Fz6p4g0/xLbQMsV3pWo6D4V16xsZ7rQY9MnAPHvhN+xT+1/4A8d/GDVPiL4N8K/H
SY/svan4A0hPHPibTtT8E/EH4r6J8Nf2WtC+H3iC4vbuRvEmt2msePvhL4j8T+KND8YWzaR8P1jv
Zvh8EufF2vC8AP2o/Z9+Eeh/s9eBPgf8E9H1d9Xsvhl8GJPCcmt3txvu9d1LTrvwiNZ1668yWQx3
Ou6u19q8sCuYoHvGggCwxIqgH0p9qtv+fiD/AL/R/wDxVAB9qtv+fiD/AL/R/wDxVAB9qtv+fiD/
AL/R/wDxVAB9qtv+fiD/AL/R/wDxVAHy1+2h8OtV+MP7OPxE+H3g/wAMeEfGPjjxJZ2Oi+C08YNa
S6J4T8QeIdQtvDK/EmeG5EiXM3w10zW9T8b29gqGXVJdDGlxFXvQ6gHg/wAYvg14p8IeAvgn4a+A
unX/AIptf2XPib+zLr0Xg3/hKItP8ReNPhp8MvC+t+CNT0O31vUpks7/AF5dE1SDW/K1m4htNZu9
Ke3uru3lu0uYwD4E079mv9t/wF4kk8efDDwZaH4veP8A4XfHbSte17x/4z8O+IPCPwnvPi98QPj1
44+F1x8ONbSNPGGj+Ofhjqvxh8NWHxL0izT/AIQbxr4Y8L39zYLFr1ho0rAH6c/sA/Cr4q/s9fA/
UPgR8V7rQr6y+FvxC8V6P8JNf0fWdU1WDWfg9rhsPGfhS0uZ/EOo6pr63fgq+8Ta58OV/tfUb27u
tP8AB9hqBuHS8VUAPt/7Vbf8/EH/AH+j/wDiqAD7Vbf8/EH/AH+j/wDiqAD7Vbf8/EH/AH+j/wDi
qAOP8GXFuLTXMzwjPjDxYRmVOQdbuyD97oeoPcc0Adh9qtv+fiD/AL/R/wDxVAB9qtv+fiD/AL/R
/wDxVAB9qtv+fiD/AL/R/wDxVAB9qtv+fiD/AL/R/wDxVAHwd8VvBfje6/b2/Zi+KfhnwLrWqeCP
Dnwg+OPgT4lePLbxTpdtoek/8Jtd+DdR8GWFx4butSjutQeyv/CmtXF9eWli0kf9s6SFlmWKZIAD
7H8C3NuPBXhEG4gBHhrRMgyx5H/EttuvzdfUdQevNAHVfarb/n4g/wC/0f8A8VQAfarb/n4g/wC/
0f8A8VQAfarb/n4g/wC/0f8A8VQAfarb/n4g/wC/0f8A8VQB538XLi3b4XfEJVnhZj4P8QAASoSS
dMuOAN2ST2A5JoA8z+GPwV+FOsfDrwPqup+AvDl7qOo+FtEvb68uLCOSe6u7nT4JZ7iZzy8ksrM7
serMTQB8LfArWLzxT+114u+Bvj/4U+AbrQoNA+NviSaPQtF8KXOmeA7DwJ8WfD/hH4VrB4h0HVb7
Vb+X4heCdbuNV17T/Glnpesaf4o0XVLPSbUWFheqgB+ht58Ifhl4f1vwbeaL4J8P6bdTeI5rOWa2
sIkeS1l8M+I5ZIGPOY2lghkI/vxI3VRQB6b/AMIZ4U/6AGl/+Asf+FAB/wAIZ4U/6AGl/wDgLH/h
QAf8IZ4U/wCgBpf/AICx/wCFAH4wfHH9rH4leDvF37XHg7wtcfAprX4G/Fz4QaX/AG9pll4XvNf+
Hvwl8bfCTxh4v1rUtX8N+L/iL4e03xZ4tsPHPh3w/wCG9Ut31fRvsmleItcvNN0ee/0K2s5QDwX4
W/8ABQz4nfE3xX8UbPx5afDf4D+GPC/7M+ofGm41BvAUXifUvBuv/D/4d/szfEL4i+Fh4ev9bj8R
z+INLm+Kvj/wtqdh4t03S9J1G9t/BKfD/VdfvRr6gA/YP9nfRPG+s/Dz4Hap8e/DXhex+MGvfBk+
IPiRpOiaOum6ZpPirVLnwpf3ejx2RnuRHcaEt9/ZF48czQy31tdzwCOGZI0APpb/AIQzwp/0ANL/
APAWP/CgA/4Qzwp/0ANL/wDAWP8AwoAP+EM8Kf8AQA0v/wABY/8ACgA/4Qzwp/0ANL/8BY/8KAPh
D/goh8V9Z/Zp+BWieMPhX4a8JXXjfxT8VPBfw+0u01a00QXF1BrkWtanqqaDL4n1TQfBsOuw6VoV
5eW7+Mdd0nQ3s7a/gjupdbm0eyuwDz2+/aHj0P4O/spfHG+0r4eWuj/HbxX+yXp/xT8QXWnX2meC
/C/hn4z+ANU1TXNb0641yW0uvDmmv4rn0TTNHvfEkiG3GpWdrqGbu4XIB8k2H/BRfVPCWvXXjn4r
6R8OJPhNqPgL9ojWvhT4e+H+j6Xr/iX4meI/hf45/aHHg/TNatotdm8YeF18ffD/AOGnw8vfhb4h
0vw3rHg74hXfie4tV1O01XV/DMF4Afon+wT8VZf2jfgMNb+KXhLw9pPxo+Hnjfxd8KfjDpeneEtf
8I6bH4w8L3sV5petaT4c8W29t4j0rRPGvgLWvBvjvRrfVYI5103xNbqC6KHYA+1P+EM8Kf8AQA0v
/wABY/8ACgA/4Qzwp/0ANL/8BY/8KAD/AIQzwp/0ANL/APAWP/CgDkvB/hLwzNa62ZdD01yni3xT
Epa1jJWOLWbpI0HH3UQBVHYACgDrf+EM8Kf9ADS//AWP/CgA/wCEM8Kf9ADS/wDwFj/woAP+EM8K
f9ADS/8AwFj/AMKAD/hDPCn/AEANL/8AAWP/AAoA+NPiR8SofBX7af7OvwG3fCmDwR8Y/hR8cPEN
5oN7DDD8RW8XfDy78ByaDd2Ek+rpHJoWoWPiDWbaCwt9Ee6u7zTdTuPt8kVi0FuAfUngnwj4Yn8H
eFZptD02SWXw7o0kkj2sZZ3fTrdmdjjJZiSSTySSTzQB0/8AwhnhT/oAaX/4Cx/4UAH/AAhnhT/o
AaX/AOAsf+FAB/whnhT/AKAGl/8AgLH/AIUAH/CGeFP+gBpf/gLH/hQB5/8AFbwn4atfhn49ubfR
NOhng8Ja9LDNHbIskcqadcMkiMBlWVgGVhyCM0AeKabH8V/CXwP07x3afEm/m0LQPh9Z+IYvC2gf
Drwrq2uLpVho8V2dO0+XVtU0q3v7uC0jYLLfX1mJzGzyzKzHIB83zftRad4W/wCEB1+y+Iut2tn8
XPhz8IvjX4m8Rab8Fvh/bR+BvBHx08U6X4I+GviP4lzf8JBBePPrni3V10maDQY/Et3p8Vhq+q3i
x6ZZC5nAPt6bwt8U7HXPCEuvfFWDXLSTxDNFDax+CNE01obpvDfiF0uvPgldnCRJPEYWUo3n7+Hj
U0Aeqf2P4r/6HA/+CLTP/iaAD+x/Ff8A0OB/8EWmf/E0AH9j+K/+hwP/AIItM/8AiaAPzs+IX7Uf
wJ8H+Jfi34f1fwt4w1/x14L+Lvgn4X6x4dsvgr4Ni174jePfEngTxL8W9AvfCVx4o1TQNN1/TLHw
l4N8Ya6viHW9U0e2ml8PXsWhSapdXmkJqYB52f8AgpF+yZd6p451LTdX17W2s/Anw/8AF2reKLf4
Y+ALK18TeHPG8/wNj8HJqF74g8Q6PfeHNKmb9oH4a3Fr4m+KNv4J+H8tmfE2paZ4rvLDwP4nudJA
PuT4R/EEfHLQfhZ8XPBfifWYvDPxH+GF94u8PHxB4SsNI1qHSNT1DwxLFDf6cXnhSR96Os9tc3tj
cxxpd6ZfXun3UF3OAe5/2P4r/wChwP8A4ItM/wDiaAD+x/Ff/Q4H/wAEWmf/ABNAB/Y/iv8A6HA/
+CLTP/iaAD+x/Ff/AEOB/wDBFpn/AMTQB87/ALS/xM0D4NeB9DvPiXJrPj+28deNNK8A+FPAXh/w
N4R1/WfGHi+70vXPFFtpdhZ+J9T0Lw5HJZ6F4T8Qa9JcazrWmW6waPLDazT6pPYWN2AcPH8a/hvr
Xhb4Y+L5fFL+Ifhx+1DffBPwx8MnHgTSrzT9eT4seC9V8XeCG1fSL9YV0vS5dC0+WS4863eSykaG
CW23g7ADzrwL+1p+z/8AEH4k+KfCmgT30GofDHwB4t8Q+O/GutfDn4e6LoPgTwN8M/iL8TfA94+o
S3+uReKbnw/B4s+DPi2fT9R8N+Hda8M6a1rpCaxqei6xqNrp1AH0r+zp8VdG/aR+Evhn45fDHxJr
Nh4b+IH9o3Etl4n8C6b4Z8YabrXh3U7zwhrmieMtDkaW50vxN4e1TQLrQdTsbqaaa0k04QLK8KRE
gHuH9j+K/wDocD/4ItM/+JoAP7H8V/8AQ4H/AMEWmf8AxNAB/Y/iv/ocD/4ItM/+JoA5PwjpXid7
XWvK8VmIL4s8UIw/sTTW3yLrN0JJSSuR5j5fb0UEKOBQB1n9j+K/+hwP/gi0z/4mgA/sfxX/ANDg
f/BFpn/xNAB/Y/iv/ocD/wCCLTP/AImgA/sfxX/0OB/8EWmf/E0AfPHirxz4U0z9o74Z/BvX31W6
+KvjT4feOvHXgjxfL8MdIudAs9D8A3uiWXiLSI/GtyqG213Pi22u4dE08XLixmuLnUHskurIXwB7
F4L0rxPJ4Q8LPD4sMUTeHdGaOL+w9Nby0OnW5WPcwLNsHy72JZsbmO4mgDpf7H8V/wDQ4H/wRaZ/
8TQAf2P4r/6HA/8Agi0z/wCJoAP7H8V/9Dgf/BFpn/xNAB/Y/iv/AKHA/wDgi0z/AOJoA4H4qaX4
li+GvjyS48Um5gTwnrrTW/8AY2nxefENOuC8Xmou+PzFyvmJ86Z3L8wFAHjVp8SNA1j4C2vw9sLj
xxo2vap8N4fCqa3B8H/iD4q06xub3RF0y4u7eOw0WOx1qFEklNu9rqP2ac7JUmePhgD43k/Zl8AX
+g/C3w5rHxF+LF1pfg/4QfBD4FfEmK1/Z38f2bfEP4ffs6/Euy+JXwwggkbRLh/CWuJqdpLpPijU
oDqMWt6VqN9Ha2WlXn2O6tAD9HLj4v8AhPxFrng+z06x8cJPB4imvH/tL4c+O9JiaKPw14ihZYp9
T8P2sM0+6dCttHI07xiWVYzHFKygHqX/AAmWl/8APl4k/wDCV8Rf/K2gA/4TLS/+fLxJ/wCEr4i/
+VtAB/wmWl/8+XiT/wAJXxF/8raAPzX+JX7IWpfE3xH+1Xqfibxh4F8WeHv2ldY+FmoW3hD4k/sm
y/EjQvAifCnRbvQPD17DpnifVrrRvEPiWytZrTVNL1rUtJS303xDYQ340u4tHl05wD5m/wCHRfw7
0vWLy58MfFDxJBollpng7RdC0rxN8Dp/E1z4r8K+C9W/Zc1HRPhh8d9Qf7Avxd+D2j2n7LXhjRfD
3gGS08Nw6PpXifxXarqNyurXfngH6P8A7NHw70L9mr4cfBj4H2Gr+MPFen/DD4Ya54Xs9Z1Lwlrl
pcTWw8RaJe2tlp+lx2Ux03w9okEy6J4c0xJrtdF8P2GkaVJe3UkC3EwB9Rf8Jlpf/Pl4k/8ACV8R
f/K2gA/4TLS/+fLxJ/4SviL/AOVtAB/wmWl/8+XiT/wlfEX/AMraAD/hMtL/AOfLxJ/4SviL/wCV
tAHz5+094A0X9or4R6z8LLnS/DFxa61faXdTr8WP2f5fjN4UhOmXBvLW/j8EeJbe10WfX9Kv0tNV
8P6nfi7g0vVLK3uZdPvog9u4B4Xrf7Nvhm4+E3wp+Cnw38UeLvBN3+y9efs5av8ABnxXqfgLU/FY
tdQ+BnhqXwtosXjLw6tnpCa3puu+GH1LS9Zt7S60G4d9RfUNIvtPurSB4gD5t8e/8E1LD4jeFPAn
gXX/AI2+LrXQ/B+i/HKK88S6D8DpdG+KOt63+1KnxKtf2irL/hOLVR/Zvw68b2/xb8YX2i+BbXSM
eF/Edj4K1yPWr+TwnawXAB92fsu/Bnwt+y5oPxN8J+H/ABX8V/G3h3x78XvE3xc04+P9N8X+JvEu
gah420jw4fFumXPinU7W51XxDDqvjPTfEHjCO81ORru2m8T3GmiSS2srdqAPp3/hMtL/AOfLxJ/4
SviL/wCVtAB/wmWl/wDPl4k/8JXxF/8AK2gA/wCEy0v/AJ8vEn/hK+Iv/lbQByfhDxbpsNrrQa08
QMX8WeKJR5fhnX5QFl1m6dQxj05gkgBxJExEkbZR1VgRQB1n/CZaX/z5eJP/AAlfEX/ytoAP+Ey0
v/ny8Sf+Er4i/wDlbQAf8Jlpf/Pl4k/8JXxF/wDK2gA/4TLS/wDny8Sf+Er4i/8AlbQB8vfET4da
54z/AGmvgP8AHnTvG1/ovhv4L+EPil4XuvAM/wAI/Eep3/ik/FZPDaa3er4sN7aHRjZL4N8Nf2dD
Hol6FMeq/aHnF/CLIA968FeLdNg8HeFYXs/EJeLw7oyMY/DHiCWMldOtwSksenMkiHGVdGZHGGVi
CCQDp/8AhMtL/wCfLxJ/4SviL/5W0AH/AAmWl/8APl4k/wDCV8Rf/K2gA/4TLS/+fLxJ/wCEr4i/
+VtAB/wmWl/8+XiT/wAJXxF/8raAOA+KvivTrr4aePbaO019ZJ/CWvRI0/hvXbeFWfTrhQZZ59PS
GGME5eSV1RBlmYAE0AcjfabPq37JkumWuj+INevdR+DMdnY6P4VumsfEWoX114bSKwg0m8XVNEa3
uXungZZf7WsQIw5M6qSGAPkTRPC/xnt/DP8AwS9vdR+G3xjfxZ8K00bRPj4BqukyLo+n2XwF8VfD
fXJfGNv/AMJyNP8AEgvfibeeGPEFpe28WvXz6RaT66jW88D2U4B+lHiRf+Jl4JwP+Zsc8D/qVfFG
aAOsoAKACgD8JPj38Nv2kfFPjb9s+y8L+Hf2n5PCF/8AGf4LeOPh9o13fat4h8JfFuz0v4XeMPBn
jLwL4bk0f9oD4a+JvA3w/HjvUPDHjGwfS/Efg7StO1fwr4a1XUdJ1DRH16GQA+S7v4Cf8FQLPWfi
HB4qg+NfifVNS+Gnwk8IeL/E+leME1nQmvfDmo/sax+LvGmnWcPxW8NP8bPDnieHwR8etSk+DejW
Pwa8Y6Doms/Efw7efFXxBqPxS0e+0sA/b79i/Q/ij4Z+Bf7N/h340WXiKw+KGhfBG/0jxjD4s8RJ
4p8RSanp+t+HLWO+1bV0utQAutTsYrTUjpEmq61ceHI7uPw9da7rlzpcur3oB9o0AFABQAUAfhh8
ZPBf7Qmp/Hj9omFPhl+1l4v/AGeNW/aC+APi7xZoeg+Oltb3x98M9D+FHxV8M+PdC+DTS/FPRtS0
vw/afF/Ufg54m1Hwpp914KtdU8L+HtXu4re/dL2y1AA9xufDH7VHhT9nP9lK+1a18eeO/jL8GNc/
ZI8TftK+H/CPiTTr7x3440jw/wCA9V8PfFjTUvr3XdJ0fx5qdrqusRa5rdnPrixeLG0O/utObUNS
m061uwD5FsfB3/BQfwH4rX4heCfhp8YPHvxR8bfC749W9joHxR8W6VB4G+Bl98R/iJ8f/FnwO1fQ
vFemfFu90LU9a0ST4hfCXwx8bfhnrXw48YHT9I8KDxF8P/G0Vl4HttK8RgH6efsC+D/j58LvgjqH
wb/aFt9QvPEXwj+IHirwl4H8cal8Qb74p3fxF+E9+bDxj4B1298dazpHhvxDr+r+G9N8USfDPXr/
AMQeGPD+o32s+BL3UVsZbG9s7+8APtygAoAKAOP8Fgi013IPPjHxaRnuP7cu+ffnNAHYUAFABQAU
AfCPxWsviTB+3l+zH4g8OeG/jPqvw2T4RfHHwx8S9Y0XWFf4NaNqniG68F3vw9n8QeGbjxXZQv4l
W48O+KUn1+y8KarqNpZ3eh2TXyWt20cIB9ieBQR4K8Iggg/8I1ofB4POm2xoA6qgAoAKACgDzr4u
/wDJLfiH/wBid4h/9NlyTQB8xS/B/wAGW37PD+O9J0Kyk8ZWnwuPim1uPEPiHxwfD8urWmgf2mza
lp+i+KdHlFnM8Tq1vp91YbdwWJ4lAAAPla11yx8Q+HP2JtY8IaD8P9W8aftF+Dfg7448cfCEaz8S
jrFh4L8X2Ogal8U/iLpvi5/irDaeDvCfgKz1r7P4eg13w94jvPFfihtP8JWlxc6jqBNmAfoRP8Ev
hr4a1zwfe6PoV3b3Fx4hmsZmm8R+Jr5HtpfDXiGd08m+1i5iVvNt4WEioJF2lQwV3DAHqX/CA+E/
+gWf/A7Uf/kugA/4QHwn/wBAs/8AgdqP/wAl0AH/AAgPhP8A6BZ/8DtR/wDkugD8oPjJ+018YvA3
ib9qDwp4X+DfgLUv+FIfFX4S6FaeK9Ph+LHxJtPCPwj+Inwh8VfEW6+I/wAS/BfhG60jxZrFxaa/
4a0zwpfWPgwwWPhS38aWviTVb/VdF8J63dXoB8c2P/BV7xpr02rXOmfADwxpdlrngH4X6v8ADTSZ
ovHviPXPEHjnxrefsiWviXwJ4OntfFegWnxo+Jvg1/2jfFlpr/wW0i3+Gmv6Jrvg3whos/jLUG8c
3t74WAP1z/ZR8YaX+0P8IvgP8Ydc8O6JpGtfET4Sal4g8R6L4d1XX59L0bxLb65oOl63oyDVZ11T
T73RtVt9Q0zV9EvnuLvQtXt77Rbq+1KbTjfzgH1l/wAID4T/AOgWf/A7Uf8A5LoAP+EB8J/9As/+
B2o//JdAB/wgPhP/AKBZ/wDA7Uf/AJLoAP8AhAfCf/QLP/gdqP8A8l0Aflv8af2lPiV8NdH/AOCi
d3o/wx+D19qP7HXh34eePvA0Wq+M/iCtn4l8CeKPBWr+MNYbxjJa20U6+LUt/D2oR6To+jJYaQk9
/Y2d34guFtbi/uQD6P8Ajn430n4MeLPholl4Z0nU9P8Ail+0L8Fvgvqtzq+r6taQaFpXxB0nxe7a
xZ3EF7HHJqZ1TSdL03TYLxzbXV1qUdqivczW8bgHwlYf8FCo/DWo6v48+NHgHwd4E/Z/g8J/tLah
4D8U6QPGfie4+MnjL9nvxv8AtDWmp+BfD3i+x8VPongbxjN8O/g5oXi/RPDPi3wxdW/xNtde1q88
CeKTcaN/wjjgH27+wh8YtB/a0/Z80z4jeJvDnhfRPiX4e8WeMvhn8W/DfgvXPE2o+FtB+IXgfWpr
G9Tw9fa49pq914e8Q6DP4e8a+GrjUIEubjw54o0meTcZN7AH2T/wgPhP/oFn/wADtR/+S6AD/hAf
Cf8A0Cz/AOB2o/8AyXQAf8ID4T/6BZ/8DtR/+S6AOU8I+CPDFxa600umljH4r8UQJ/puoDbFDrN1
HGvy3QztUDk5ZjkkknNAHV/8ID4T/wCgWf8AwO1H/wCS6AD/AIQHwn/0Cz/4Haj/APJdAB/wgPhP
/oFn/wADtR/+S6AD/hAfCf8A0Cz/AOB2o/8AyXQB8seOvFt94S/a0+BHwOj8G+EJ/hz8X/hb8bvF
Vz4hm8QeKG8c2Xi74U3Xw9eCwtdKV4dEh8OXOl+NC093LeX+pXd+Fjit9MgsHl1MA+gfBfgfwvc+
D/C1xNphaWbw9o0sjC91Bd0j6fbs7YF3gbmJOAAATwAOKAOm/wCEB8J/9As/+B2o/wDyXQAf8ID4
T/6BZ/8AA7Uf/kugA/4QHwn/ANAs/wDgdqP/AMl0AH/CA+E/+gWf/A7Uf/kugDgvip4K8NWXw18e
XdtpxjuLbwnr00Mn2y/fZLHp1wyNte6ZG2sAdrqynowIyCAeIN/wsez/AGfIdQ8TyfCTXfhfafDi
0vdW8Oar8JvHvxB1K+8L22kxXEllqHh3RfFVwfEtyLRAbq2sdDMVw6PItpHCp2AHz9cal8NdIsP2
ZfG4+HH7Ny+HviLB8OLb4AePLH9k/wAUS6N4Sb4kara658N9Ii1KHxV9u8AXeta/rsGpWVlbWsKa
Tqt7NqmqtpiedfAA+4Li1+Na654OPibXfhdcWJ8RTCBdD8JeLLO6S9/4RrxEYpJnv/G1/FJaiEXC
yRJHFKZGhdZ1WN45AD1L7P46/wCgt4T/APCe1j/5p6AD7P46/wCgt4T/APCe1j/5p6AD7P46/wCg
t4T/APCe1j/5p6APzS8feMv2ErXxF8c4fFfw++C/ivx1bfFTwp4B+MmiaV+x9468b+O/iD8VLvwt
4g+I/huxTRtJ8P6lr3xgvtN8H+H/ABf4qfXNAh8U6ZomleH/ABTNdananStVihAOS1n9oH/gnH4m
8ReMru8034DeOfEHjzRPCtvq+s6X+yf428YT/GUatd/A2fwx4O8Ma1p+h36fFXxZFffFX9nuZfB+
i3Wr63pU/iXwPcXVpajRp5dEAPtv4K674a8XeGfhT4i+Beo/DuH4Uar8MtUn+H8HhvwHrPhTQtO8
ORav4cthpMPhKbU9JvPDd3pl1E2n3ug3mn6XfaDf2d9pWpaZbX8E0MAB7/8AZ/HX/QW8J/8AhPax
/wDNPQAfZ/HX/QW8J/8AhPax/wDNPQAfZ/HX/QW8J/8AhPax/wDNPQAfZ/HX/QW8J/8AhPax/wDN
PQB+cfjzXf2J5Z/2rbrxP8LPhN471fwTrHhbSf2rrPRv2MPiF8RfEGv3l7Z3Xi7QLvxZp+jeGdY1
H4oaJpNnpN/rVz4kso/E3h3w/Npd7Fd6paalaTWyAHrOra98EPEHgfwfoHimX4NeJ/gl8c5Pgl4J
+FHh/UPhjqXiT4e+MB4m8NXXij4V6XpXhv7Vdafpulto2hxapotxqVra6bposbFll0+aO3UgHlng
jxV+xD8Q/iLd6B4J8GfAjXfFnwu8E3ema54ntf2WfEcXhn4VeCfhr4x8a+GLLw94n+IlzpkPhXwD
p2m+KPhH40PhDQ9V1vTIb2Lwg+q6DBJaTaPcXwB9VfAD4geDfjf8OdM+PfwE8QfDvWvA3xoK+LV8
Xab8OvEvhfUPF1/pVtb+B5L/AMS6drGpaN4iTxBo1r4TtPCN3B4ksINZ0uDw5baJPFBFpkNvEAe2
fZ/HX/QW8J/+E9rH/wA09AB9n8df9Bbwn/4T2sf/ADT0AH2fx1/0FvCf/hPax/8ANPQByfhCDxmb
XW/J1TwwgHizxQJPN0LVZC0w1m6850KeI49sTSZMcbBnRcK0khG8gHWfZ/HX/QW8J/8AhPax/wDN
PQAfZ/HX/QW8J/8AhPax/wDNPQAfZ/HX/QW8J/8AhPax/wDNPQAfZ/HX/QW8J/8AhPax/wDNPQB8
w+M7j4L3X7T/AMLvC/jTSfhDqn7Ub/D3xh4v+E/iLVvglr+reKdF8DeGr610/wAVf8I98UJnudO8
MtHd+JozJ4cj8Uafq2pQ3t3ewaXc2kV1cIAe7+CYPGp8HeFTBqnhdIT4d0YxLLoOrSSrGdPt9iyS
J4kiR3C4Duscas2WCIDtAB0/2fx1/wBBbwn/AOE9rH/zT0AH2fx1/wBBbwn/AOE9rH/zT0AH2fx1
/wBBbwn/AOE9rH/zT0AH2fx1/wBBbwn/AOE9rH/zT0AcB8VYPGI+Gnj03ep+GZLUeE9eNxHb6Hqk
Nw8P9nXHmLDNL4huI45SuQjvBKqtgtGwyCAfCmo/t5/srWXwhu/g3q/xh1PwX4xt/BDeAdY1CL4Z
+MfEg0DVV0oaPqjwwLobaVqptmNxHEy3b2krbZVeRMBgD5cb40/sV3fg79lrwNqv7U2s3el/stj4
fjw14jtP2eNa034k36/DS/0ttDt9I8eR6BNf+CbLxF4f0PSfCPxGtNCtHTxr4fTUbOdtOTVJ1QA/
QHRP2/v2Wfif4m8M6L4M8f6hqmo6Xqd14gvYZfBXjPT1i0u20PWNOmuBLqOhWsUjLd6rZR+TG7zM
JWdYykcjKAe8f8NP/Bj/AKGe6/8ACe8Qf/K2gA/4af8Agx/0M91/4T3iD/5W0AH/AA0/8GP+hnuv
/Ce8Qf8AytoA/NT4p/Bb4TfFjxP+0fr/AIk/aJsL62+Pvif4Z+JNM07Wf2dI9cm+E118L/DeseDd
D1LwTq0+o294fFi+GNavLOHxNdgeVcTXi3elajoWqat4fvgDxvRf2Ev2R/B/iLxjrPg742X32LW/
h34U+Gnh7SfHnwZ/4Th7Hw54Hh+Cln4C0/xvq8beHNT+IGn/AAktPgjo03wOiWXwtqnws1nX9e1v
TtZ1O7niVAD9Bf2fNc/Zy/Zq+Hvwm+DvgHxTrV14K+F3w71Xwna6nq+iaq+ranqN/reka1fatqKW
ej2lsL7XtUOtaxeJp9ja6baz3DW9pb2tsLeBQD6K/wCGn/gx/wBDPdf+E94g/wDlbQAf8NP/AAY/
6Ge6/wDCe8Qf/K2gA/4af+DH/Qz3X/hPeIP/AJW0AH/DT/wY/wChnuv/AAnvEH/ytoA/Nj4t/Cvw
z8UNa/amv7T9srxJ4O0n9qef4V6f4q0HSPgb5qWPgH4ZW+o6VdfDi41f7faazqvh34g+G9UvPDXj
i6tbzQdbvNIur230rUdKW9nDAHsnxNHwm+Jngrwj4Zi+Lt14D8W/CvxN8GPiB8NfiB4Y+GGNG07x
38KNNutNWeX4azWb6MPCOrafqGr6Nd+EIL6wFhpOreVoWs2F7p1hqUAB8l+JP2Nv2dfFNroGl337
Unj/AEuzsvAPxV8E+KvEfhT4U6T4T+Kfj+3+P+tePdc+O2j+KPiToeh2t/dfDLxrqfxR8c+IPDvw
wOltpvw38aXXh7xd4T1e3vvDdtBdAH3V+zbe/s6fsw6F8QfCHgv4o+P/ABB4Q8Z/FLxJ8U9I0nxy
vjHxZqPg7UfGthok/jHR7DxNrdvfa9q+m6944s/EfxAkfWbu5u7XWvGes2sM50+KyihAPo3/AIaf
+DH/AEM91/4T3iD/AOVtAB/w0/8ABj/oZ7r/AMJ7xB/8raAD/hp/4Mf9DPdf+E94g/8AlbQBzfhn
9o/4Radb6rHd+JLmNrrxJ4h1CEDQddfda3+qXFzbSEppzBS8MisUbDoTtdQwIoA6T/hp/wCDH/Qz
3X/hPeIP/lbQAf8ADT/wY/6Ge6/8J7xB/wDK2gA/4af+DH/Qz3X/AIT3iD/5W0AH/DT/AMGP+hnu
v/Ce8Qf/ACtoA+ZfiB4h+HXjb9pT4G/H60+O15oOkfBfwp8SvC3/AArgfCq91SHxWnxTXQU8R311
4suGg1LSJok8JeF102KxsJUtzY6iZ2uRqu2zAPe/Cn7SPwg0vwx4d0288SXMd3YaHpVndRjQddkE
dxbWMEUyCSPTmRwkiModGZWxuUkEGgDf/wCGn/gx/wBDPdf+E94g/wDlbQAf8NP/AAY/6Ge6/wDC
e8Qf/K2gA/4af+DH/Qz3X/hPeIP/AJW0AH/DT/wY/wChnuv/AAnvEH/ytoA434iftEfCbX/AfjHR
NL8RXNxqWreG9Y0+xgbQ9bhWa7u7GaGCNpptPjijDyOql5HVFzlmABNAH//Z//9QSwMEFAAGAAgA
AAAhAHeZREJMEAAAj6gAABQAAAB4bC9jaGFydHMvY2hhcnQxLnhtbOxdbW/bRhL+fsD9B5+Qoh+K
2CIpUpRRs3Dca5EmaYsm7Yf7RktrWxeKVElKte/X31Lk7AztzHTUXNAesDaQyNLMvjzP7orzwuGX
X91vipO9qZt1VV5MgtPp5MSUy2q1Lm8vJj+/++Z5Ojlp2rxc5UVVmovJg2kmX2V//9uXy/PlXV63
b7f50pzYRsrmfHkxuWvb7fnZWbO8M5u8Oa22prSf3VT1Jm/tn/Xt2arOf7ONb4qzcDpNzg6NTIYG
8j/QwCZfl6Bfa/Srm5v10nxdLXcbU7b9KGpT5K1FoLlbb5tJZie3ylsTLKazk31eWFwmZ92bRV7e
9m+Y8vnPb/s362pXrszqqqpLC2P/8bT7aLM8vyxaU5e2qauqbG1vwzw3KqQ2ef1+t32+rDZbO7jr
dbFuHw7DtQO0bV/dVXYeJz+ZX3fr2jQXk2UwAyDsyydQbNbLumqqm/bUtnjWowBsdM3Oz9KzcODD
TjaYnTftQ2EGAIK0m9KZ6/cwhG/yorjOl+87bKiwk0WBTvMxGp3agf/uRb5rq3frtjBfm8K0ZkWA
XJ5vi6q9rE3eCRb5Q7Vrez7WpbnqVmH3/q0lYmtXVq/Yr9l61XO0z+uHq6qoRvzYMZu601yv7nul
pJeu6pWpR/23951c09Y/mZvu1U32+dq0N883xrS2y+d2teSny2b/+T+evXwWfHnWSfQKV7ndCt3r
bXtlF0rbNzusp217Yvu+mEwPS26ffV/V7d3J5cbU62XetbK3kHeqh/9s90Nr9j0Yi33ZD65bLf10
mofNdWU3dbdwS7tpD8Qtz1FgmR8AK3eb35/Oi2fh+bMXzxaJm5RVc5PqN/ZVtTLZt8Yu/7w4iB22
++HdxxNfxD3Ej2duD57xfLtZ9+AEAzghLxIOIhEvEg0iM15kNojEvEg8iCS8SDKIzHmR+SCS8iLp
ILLgRRaDSDDlZQJYWYEEMCAcCBAHgHEggBwAyoEAsz2luv2wzwIB6ACQDgSoA8A6EMAOAO1AgNue
bsOYBMADQDwUEA8B8VBAPATEQwHxEBAPBcRDQDwUEA8B8VBAPATEQwHxEBAPBcRDQDwUEA8B8VBA
PATEIwHxCBCPBMQjQDwSEI8A8UhAPALEIwHxCBCPBMQjQDwSEI8A8UhAPALEIwHxCBCPBMQjQHwm
ID4DxGcC4jNAfCYgPgPEZwLiM0B8JiA+A8RnAuIzQHwmID4DxGcC4jNAfCYgPgPEZwLiM0A8FhCP
AfFYQDwGxGMB8RgQjwXEY0A8FhCPAfFYQDwGxGMB8RgQjwXEY0A8FhCPAfFYQDwGxBMB8QQQTwTE
E0A8ERBPAPFEQDwBxBMB8QQQTwTEE0A8ERBPAPFEQDwBxBMB8QQQTwTEE0B8LiA+B8TnAuJzQHwu
ID4HxOcC4nNAfC4gPgfE5wLic0B8LiA+B8TnAuJzQHwuID4HxOcC4nNAPBUQTwHxVEA8BcRTAfEU
EE8FxFNAPBUQTwHxVEA8BcRTAfEUEE8FxFNAPBUQTwHxVEA8BcQXAuILQHwhIL4AxBcC4gtAfCEg
vgDEFwLiC0B88QRxa1yitdf/cbAY7cvBhrRGZnfhrDIlX3am5EuFKTn97NNZkQLugKggAngKIoCm
IAKrVxCBtSuIwMoVRGDdCiKwagURNCIFQxPWrNSOAmC0IIW+FBCj/Si0owDZWY/T0wXroACYJRnA
eXqajn7YVp0hKbTq7EhJBlCXZGBd29Fxs3RGpCQDK9vKBKNftlXgQK8B697OZzr6ZftAftJo9MNq
ELZ083BGqHoeziLVayCTI2wDljNnq6qxcoarflRHc+5M2unpPBz9cnw4+9ZqsDLIMi9DeOXaccat
enTO0tVrIJOj+YfsyJ0NPD1NotEvOw84JfUayKR2VLh7R2OKDt5idF6jM9fZzXZUox9+5sjrSCHh
NZBlpYYzr9Wjcra2XgM5144KT2WtBnI+j7mF4Uxyu1x5IcLsqHMWdWefi80imULfyJ/yvHbGutS3
M9ZFIWSJH6Az1sWWkIsRgPy6dZa7ek05M356Go+h4sh3Nr3VYGWQJF4GOWJlnEE/PZ0FFAN2DTnr
fno6+p6OIm6sztTX94G7SjsqZFKrgSepVgP3G48nXvloW1Uw6TwF6jXk3Abqdep8CPo+cB8qV7bz
Luj7QF61fSCvLEvO7WBXZDz65daw80EIe9K5IGyr4x+2VcUOde4I22qYxvMA/mWtEuebUO9Q56iY
nobcWJ2fwsqwwDo/xe90LTgtBm9Fs6kqG2c/BMgPmRpWZUgFeJwRMH+SETCE7o/ICPjuIzIC/rmr
bQ7NGLdutD4VwKLwoQtMODcErxh8AQg+MTgZnnjE8EoWjgLBAwlnuuB/hCNd8j76VIAhNi9A7VMB
Jj4VYOK8MD4VIPOpAJlPBch8KkDmUwEynwqQ+VSAzKcCZD4VIPtLpAJ816UCfPcpUwGEJAwIVQsi
YEUKImBFCiJgRQoiYEUKImBFCiJgRQoi6AlkE+3RYcSKuFQAoadAga/LJpfaUSDscsmldhQYO/NR
agdRPtzh8SHvg8sjn57yMohzMP4Zu3nQ1UBSAdhWSSoAL4PLmpdB1Fl3HUkF4GUQ9XEEndfAha7V
QEbGmQBT1n/p0s4tQTQkwUdlXA661RiF3dmJOCtUr4FbRtsHoVI5KiRWCxZJBtAO62jWSTKAtg9k
nacAjztehuxDbueRZADl6EgygFbjaCpJMoC2D/wq0mogk9rl4hLn1eueZAMod6NLqVfvX5dfr9Yg
2QDKUZFsAK0GIV13DrmcfP08COnKPpB07Tzw0OYjNyQ1QNss7l+tBtnNusmSpAF+6CRpQBBCMgUh
PH8FIaRMEEKWBCEkRhlKJ6kBWg1kSauBLCk1SBKBVgO/TLVhcuRP2weSqdVAZrUaSLNW42jO3Q0H
+vSJozknCQbKeZAEA36Bk5wCbbNH00xyCrR9HE2zu5fhd8LaaA6QDINxKuCMu4whGQZsJg3JMNDO
FTczTxNJMRhlGKRsiuBHpRiwEPx1UwwOxRKW56ToQNgnHRyRYvDqI1IMLpt1/sXlzqYU5MU6Hy8h
n2og3IIDx4lPNThUqMADynmJfNWBzFcdyHzVgcxXHch81YHMVx3IfNWBzFcdyHzVgcxXHch81YHM
Vx3IPnXVgVddqsErn2owQXciG95H/yErgsE3VgQ9hKwIeo5YEWdESiF5dPXy7YCZLrWD7ly+HfTs
8TIKjI9MNeD7UsDsKtYJcyfJBWxfJLmAl1Hg7FLUpfEocHa16qR2FIvZVaqT2lHgTHIEWHxIVgAv
o1jPrkidMGZy3z/flwJnV6FO6ovgPCrHwCdhkNv52TwUV63OhjvHPkn0M7lidYIMieCr49iEBeWM
XB07C5RWBc8cbUgeGdNq4Hmk1UA2tRr4jaAM1foYfvZHYvjT8R3ebCCH3N+vVkHW1SpIu1qFnKTa
uSguFEgcnz3sSBifl1F8gZE7//l2cJtqkSF3/qtVjqeMBPiVO9UV91OvV1fpT61BAvx8FJEUBhCE
kEBBCI9dQQgpFITwcBWEkCYl5iQkr9XAfaXVINtKuRNJTF67REmEXq2CFKpVkFC1CtKrVkGylRiT
KL3ym5RE6dmkRRKlD8c/3EWSq0so3lsPdQmtEK0D8CdG6f9adQAWT+oAREcH6V9/RJB+9GSAk7Jq
T37J7WM6dvbJHWPifcTeR+y750WglQRnvX9OQOafE5D55wRkvjiALw6w98UB9r44gIVAqOjtnxMw
cQUGfcTeR+z3PmJvIZAqdYEjxj8noH+ynDVG/8BzAl53EfvXnzJiLxWphweB8XXjwUcltAI+KUEE
fFCCCPicBBFwLwoi4KgXRGDdCiXiwYoUREjEnr3/mhQHGJXBT3kNgNtWJB/98BqAvl4DyJBmB2xI
MkCHvmdgx2qMHTlowJOiAvyckZ8RSDyuJO7Ptkri/rwM8sPLEEa4WZKiAiwSJO4/uumdr4DvHlhn
8R27YdlxICPKSC6pKaB0ppN8AeWoSPaAVgOj2FoNZFKrgbwqsSIlBbR94L7TauAuVNaxJwkJbG1q
kpDAy5BdyK0vkpCgHB0pKaDVQCa1GsiktpI/nplaDWRSOypkUtsH7t7RXeB8fQ+SjaDVQJaVGqSi
gFYDd69WAzlXVrMmFQW0GoTz0bDYHUGSEUYKPB/uYYDqOt6kvIC2D7zg0c78aM5JWoKyD5KkoNU4
mnOSwKDtAznXauA+12rgPmfDfiR7QXlbP8le0Gogy0oNkr2g1cCdrbzPmjzjQKuBp7lWA1nWaiDL
Wg1kWYsVnubaPnBna/tAztm1R5IflCua5D7wrZLdy10tkAoEfDvInXZ0yB3fKmHLP8fgYvL//RwD
a5ufdUFhUmVgdnQCw5uPSGAYVxn4wmcvPL5nfvA7+ewFn70wRsDdMOKzF3z2wt5nL1gIhBiMc9P4
egO+3oCN7wvFeZz/IxaeBBTDxXUsPQsIrqdj4RE1zrERC88Dcr6MWFjjMRg5PnvBP9pg7x9tYKPy
wg2Kznj39QZ89sL+k9cbeNNlL7z5lNkLwlpH3yJ7exo6nVgR9B6yIvCtKIwFvhMFEXQxsR2hB5AV
gW9D4S5g9PGxNxOT7AVeBvEdV+7nNRBurQair9VAMvhxIBu8DNKh7RnZ4VtFelgGfZ0C+yxLYZ/4
OgUyPr5OgTL9wtcp6PaZ8g5Okhmg1SDfM6NQNB8fxxsvlX181LMG+BuVnTEs3SbqjGE1hiT+r50f
+RZSYki+hZQa+J0kIHI0mSTkr5wsCflrNcgFhW6yJOSv7YNcUCj7IJcXSo2jaSYJADxpJOYvCCGz
vBCJ7AtCeEEoCCFl2ig2XgNqNZAyrQZSptVAyoTJ4mYUhDT7jzw3QLlunaWvPp5ImF7bB5Kp1UAy
tRpIpq9PsF7d2+A7fk36+gRdHH/1+rpouhfNXfXba3NrytUr83Cyz4uLyRDq7z75JS+evHeVt9/n
G/Pk/bem/uD7P5p6acr2ifyL3fV1Yd6u/0Obsnd8uKFt8vq9qXu9oE82aDZV1d6NmsrvX676N8Lp
PJnGUWwfDnjIVXj8SZJMD1OzfRTr0lzd5fXhRnd7i8nlfYfFYwVsqlnaZxuUt30GxNrOJm/XVdl3
u1mXb/L7rsuudgIKrkxhWjq3roMfq6bXuu7HWO4232zak5uq3uTtVbUyF5NvTWnsoxQmJ021s8i9
XpfvzepiMiCwyf9d1e/Wy/dvLDp9U9Wu7RuzI3n8WVmVpv+wtTqWdDeA0ty376r+s2VdNc3lPYUR
wLJ34HQfmmHY+a6t/mXqQa/7q1caRldcF5fF7QDMsq375u27P9zcNGZYA0FPw/K8rN7sinb9el/Y
gfXtAEGOE7siP0wODpBgXtX/E3KKAc8O62/r9apbLs1hTX2Ar+lnfzJVuEwFqg4fvTDtb8YM9Fz3
f3RTtQt3wNm+2hZVe1mbvFvsxeFkwFdu9QzLt8gf7Oo7IFPZUiL2zzGNqN+1+su6+aEsBpFhxazW
zfZFkZfvm8thid3m2x7+7gD62q6M5gfbtN1i46aX/fa1Az68ervNlyb7rwAAAAD//wMAUEsDBBQA
BgAIAAAAIQB0sIjRtQEAAK8DAAAQAAgBZG9jUHJvcHMvYXBwLnhtbCCiBAEooAABAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAKxTTW/bMAy9D9h/MHRP5HTBMASyiiLd0MOKBUjanVWZjoXKkiGy
RrxfP9pGGncFdhh248fD4+MTpa5Pjc86SOhiKMRqmYsMgo2lC8dCPBy+Lb6IDMmE0vgYoBA9oLjW
Hz+oXYotJHKAGVMELERN1G6kRFtDY3DJ7cCdKqbGEKfpKGNVOQu30b40EEhe5flnCSeCUEK5aF8J
xcS46ehfSctoB334eOhbFqzVTdt6Zw3xlvre2RQxVpTdG+sCRayzrycLXsk5TLHOPdiX5KjXuZLz
VO2t8bDlEboyHkHJS0HdgRns2xmXUKuONh1YiilD94sNXIvsySAMwgrRmeRMIBY4wKZkjH2LlPTP
mJ6xBiBUkgFTcQzn2Hns1no1Ajj4K3Di2tYm/Q/yQd20JU99u//BkQf8Ue2GSe/tuJrbMYqazJj0
OaBq0bAB7OeiNGSWFru5F6+ujJtMq89tGp1nTX+o2MamNaHXW4c2ZvseCRr2+FxW3114xof2EG8N
wfmJ3xbVnr2Dkq/i3L8U1B2/bvIDCesKRyjPmPeN4TQfp/+nV+tl/innW5vVlLz8NP0bAAD//wMA
UEsDBBQABgAIAAAAIQCvfNaXPAEAAGUCAAARAAgBZG9jUHJvcHMvY29yZS54bWwgogQBKKAAAQAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACcklFPwyAUhd9N/A8N7y2lVaOk7ZJp9uQSE2c0vhG4
68gKJYB2+/fSdqtb5pOP3HP4OOeGYrZTTfQN1slWl4gkKYpA81ZIXZfobbWI71HkPNOCNa2GEu3B
oVl1fVVwQ3lr4cW2BqyX4KJA0o5yU6KN94Zi7PgGFHNJcOggrlurmA9HW2PD+JbVgLM0vcMKPBPM
M9wDYzMR0QEp+IQ0X7YZAIJjaECB9g6ThOBfrwer3J8XBuXEqaTfm9DpEPeULfgoTu6dk5Ox67qk
y4cYIT/BH8vn16FqLHW/Kw6oKgSn3ALzra0WFkQ0Z1uwBT4Z9ytsmPPLsO21BDHfnzkv1cAcKozg
wAyh6FjhqLznj0+rBaqylGQxIXH6sMpSepPT2/yzf/zsfh9yHKhDhH8Tj4CqwBcfo/oBAAD//wMA
UEsDBBQABgAIAAAAIQBmSzFLAwUAAGkqAAAQAAAAeGwvY2FsY0NoYWluLnhtbGTa3YpbyRUG0PtA
3qHRfaatfynYHkIgsP/uMg/QtDtjQ7tt3CYkbx8lMCZT68bg1Tp1vjqSUNXe9fbnf31+vvvn07fX
T19e3m22P73Z3D29PH758Onl13ebX/7+tz9dNnev3x9ePjw8f3l5erf599Pr5uf3f/zD28eH58e/
fnz49HJ3G+Hl9d3m4/fvX/98f//6+PHp88PrT1++Pr3c/vKPL98+P3y//ffbr/evX789PXx4/fj0
9P3z8/3uzZvT/efbAJv3bx/vvr3b/GV72Nx9uoXY3D3/99/7H34L9T//IacVditsj8ht3N+Pcl5h
v8L1NvvfX3Nl3Cv3vlzXqy4EvnCvC7M8E/D82xP68STOzOpE5hOZT2Q+kvlI5iOZj2Q+kPlA5gOZ
92Tek3lP5h2Zd2TekXlH5i1XbbkXAZnVljtdGffqa0hz4QleuNeFJ3gm4JkneGZWJ57gicwnMp/I
fCTzkcxHMh/IfCDzgcx7Mu/JvCfznsw7Mu/IvCPzlauuXHXlqgszvTDTCzM9M9MzMz0z0zMzPZH5
ROYTmY9kPpL5SOYDmQ9kPpD5QOY9mfdk3pN5R+YdmXdr5ljj5Aq1Qq8wK8SaNleoFXqFWSHWyeQK
tUKvMCvE+v7kCrVCrzArxPr25Qq1Qq8wK8T67uYKtUKvMCvE+oHNFWqFXmFWiO36gU6kkEYGie36
oU+kkEYGCX70EimkkUGCn8ZECmlkkPixZPxtQZRIIY0MEiwgEymkkUGC5UYihTQySGzXb0wihTQy
SGzXr00ihTQySGzX704ihTQySLDQS6SQRgYJlgWJFNLIIMGPUyKFNDJIsBBOpJBGBgmWTYkU0sgg
wY93IoU0MkiwUUikkEYGCZaViRTSyCDB4iaRQhoZJNhIJVJII4MEy+5ECmlkkGDxl0ghjQwSbDQT
KaSRQYJtSSKFNDJIsDhOpJBGBgk24okU0sggwbYtkUIaGSTYPCRSSCODBIWKRAppZJBgW5tIIY0M
EmyuEimkkUGCQk4ihTQySLDtT6SQRgYJNp+JFNLIIEGhK5FCGhkkKIskUkgjgwSb80QKaWSQoBCY
SCGNDBKUjRIppJFBguJFIoU0MkhQKE2kkEYGCcpqiRTSyCBBcSeRQhoZJCgkJ1JII4MEZcdECmlk
kKD4lUghjQwSFNoTKaSRQYKybCKFNDJIUBxMpJBGBgkaEYkU0sggQdk6kUIaGSQoniZSSCODBI2a
RAppZJCgrJ9IIY0MEhSXEymkkUGCRlYihTQySND2SKSQRgYJiu+JFNLIIEGjL5FCGhkkaAslUkgj
gwTNiUQKaWSQoBGaSCGNDBK0zRIppJFBguZNIoU0MkjQKE6kkEYGCdqKiRTSyCBBcyuRQhoZJGik
J1JII4MEbddECmlkkKD5l0ghjQwSHDRIpJBGBgna0okU0sggQXM0kUIaGSQ4iJFIIY0MErTtEymk
kUGC5nEihTQySHBQJZFCGhkkONaQSCGNDBI01xMppJFBgoM8iRTSyCBxpT+IFNLIIMHhg0QKaWSQ
4KBTIoU0MkhwLCaRQhoZJDickUghjQwSHARLpJBGBgmODSVSSCODBIdXEimkkUGCg3KJFNLIIHGl
P4gU0sggtx49X0Lp1qVfX3Vr069069OvdBveTj10G3591W34lW7Dr5TrKZZaoVeYFWKFXO9SK/QK
s0L8H9z/OCT6/j8AAAD//wMAUEsBAi0AFAAGAAgAAAAhAMXeV2mfAQAAwgYAABMAAAAAAAAAAAAA
AAAAAAAAAFtDb250ZW50X1R5cGVzXS54bWxQSwECLQAUAAYACAAAACEAfcxUng0BAADdAgAACwAA
AAAAAAAAAAAAAADYAwAAX3JlbHMvLnJlbHNQSwECLQAUAAYACAAAACEAy4Lz0A4BAADOAwAAGgAA
AAAAAAAAAAAAAAAWBwAAeGwvX3JlbHMvd29ya2Jvb2sueG1sLnJlbHNQSwECLQAUAAYACAAAACEA
YfIATe4BAAAzAwAADwAAAAAAAAAAAAAAAABkCQAAeGwvd29ya2Jvb2sueG1sUEsBAi0AFAAGAAgA
AAAhAPxWvaHhAgAABQ0AAA0AAAAAAAAAAAAAAAAAfwsAAHhsL3N0eWxlcy54bWxQSwECLQAUAAYA
CAAAACEADkT037wAAAAlAQAAIwAAAAAAAAAAAAAAAACLDgAAeGwvZHJhd2luZ3MvX3JlbHMvZHJh
d2luZzEueG1sLnJlbHNQSwECLQAUAAYACAAAACEAFa+qPL0AAAArAQAAJAAAAAAAAAAAAAAAAACI
DwAAeGwvY2hhcnRzaGVldHMvX3JlbHMvc2hlZXQxLnhtbC5yZWxzUEsBAi0AFAAGAAgAAAAhAEgp
yhcTAQAArAEAABkAAAAAAAAAAAAAAAAAhxAAAHhsL2NoYXJ0c2hlZXRzL3NoZWV0MS54bWxQSwEC
LQAUAAYACAAAACEAMA+IaxEHAADeHQAAEwAAAAAAAAAAAAAAAADREQAAeGwvdGhlbWUvdGhlbWUx
LnhtbFBLAQItABQABgAIAAAAIQA+xTDtFykAAAH1AAAYAAAAAAAAAAAAAAAAABMZAAB4bC93b3Jr
c2hlZXRzL3NoZWV0MS54bWxQSwECLQAUAAYACAAAACEA0RbjKHMBAACuAwAAFAAAAAAAAAAAAAAA
AABgQgAAeGwvc2hhcmVkU3RyaW5ncy54bWxQSwECLQAUAAYACAAAACEAe7ee3YABAAB1AwAAGAAA
AAAAAAAAAAAAAAAFRAAAeGwvZHJhd2luZ3MvZHJhd2luZzEueG1sUEsBAi0ACgAAAAAAAAAhACny
6vcocAAAKHAAABcAAAAAAAAAAAAAAAAAu0UAAGRvY1Byb3BzL3RodW1ibmFpbC5qcGVnUEsBAi0A
FAAGAAgAAAAhAHeZREJMEAAAj6gAABQAAAAAAAAAAAAAAAAAGLYAAHhsL2NoYXJ0cy9jaGFydDEu
eG1sUEsBAi0AFAAGAAgAAAAhAHSwiNG1AQAArwMAABAAAAAAAAAAAAAAAAAAlsYAAGRvY1Byb3Bz
L2FwcC54bWxQSwECLQAUAAYACAAAACEAr3zWlzwBAABlAgAAEQAAAAAAAAAAAAAAAACByQAAZG9j
UHJvcHMvY29yZS54bWxQSwECLQAUAAYACAAAACEAZksxSwMFAABpKgAAEAAAAAAAAAAAAAAAAAD0
ywAAeGwvY2FsY0NoYWluLnhtbFBLBQYAAAAAEQARAHUEAAAl0QAAAAA=

--_004_8C48B86A895913448548E6D15DA7553B19E215xmbrcdx09ciscocom_--

From arturo.servin@gmail.com  Fri Nov  9 15:26:10 2012
Return-Path: <arturo.servin@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 72F0021F8604 for <ietf@ietfa.amsl.com>; Fri,  9 Nov 2012 15:26:10 -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, GB_AFFORDABLE=1, 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 rem8kBl-XH8r for <ietf@ietfa.amsl.com>; Fri,  9 Nov 2012 15:26:09 -0800 (PST)
Received: from mail-ye0-f172.google.com (mail-ye0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id C91E621F85EE for <ietf@ietf.org>; Fri,  9 Nov 2012 15:26:09 -0800 (PST)
Received: by mail-ye0-f172.google.com with SMTP id l13so916803yen.31 for <ietf@ietf.org>; Fri, 09 Nov 2012 15:26:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=SLqZyX0HJ9m0C5rE+6+7xZQhGakZ+swzqZaz4ogRv5M=; b=Y0oBC9Xrqs5HS9tDhTpoO9P5gjA29iENKxxrboTrD9DFotPYTAupJtJiqU4CLiIARa 4PDMDCCg2JST52Sar/Pf+zKMUV9dMfXmxAK4ETynH8hUb33rKD2DfFpvWLuLBLKb+tQj c9DwQAYp8k0Y6E39z7ZKonXa6y/g+Ov1gAiWYY/KYf1edJG8QX3VDxf8/hRRAce4xDe5 FeIHs3RQQ3T2RtHtu9W8s8iZqRfx475+mxAHlWbPLiPyD+1ymc+w7JK0aycYqmsGUdne QqV/6fHaX/L4SertXtBwH0MH5WsjvaTLcNDknwycdX7kcO0NBrq1tp1gsjp4IFqNV+pO DVog==
Received: by 10.236.117.33 with SMTP id i21mr13426820yhh.81.1352503569417; Fri, 09 Nov 2012 15:26:09 -0800 (PST)
Received: from MiniR2D2.local (ip-64-134-245-158.public.wayport.net. [64.134.245.158]) by mx.google.com with ESMTPS id z28sm31353171yhh.7.2012.11.09.15.26.07 (version=SSLv3 cipher=OTHER); Fri, 09 Nov 2012 15:26:08 -0800 (PST)
Message-ID: <509D910D.7060503@gmail.com>
Date: Fri, 09 Nov 2012 18:26:05 -0500
From: Arturo Servin <arturo.servin@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
References: <CADnDZ8-fjxfgJys8sE10DdZ08tB8HdaTQXbPj2d7-OuQOGi9Pg@mail.gmail.com> <CADnDZ8_v3M1fNtkOV4rU1F-iaMC+2qvKhR353vwESiQsfh70MQ@mail.gmail.com> <6.2.5.6.2.20121109074113.0b2000f8@resistor.net> <8C48B86A895913448548E6D15DA7553B19E215@xmb-rcd-x09.cisco.com>
In-Reply-To: <8C48B86A895913448548E6D15DA7553B19E215@xmb-rcd-x09.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Nov 2012 23:26:10 -0000

	So basically the IETF is roaming most of the time in  North America,
sometimes in Europe and once in a while in Asia. Is that how the IETF
thinks about the global development of Internet standards?

	No wonder why some countries in Africa and Latin America are
approaching ITU.

	If the IETF really wants to make a change we need to stop thinking that
North-America/Europe = Global.

Regards,
as

On 09/11/2012 16:05, Fred Baker (fred) wrote:
> 
> On Nov 9, 2012, at 12:28 PM, SM wrote:
> 
>> At 06:31 09-11-2012, Abdussalam Baryun wrote:
>>> I am newcomer and not able to attend because most of meeting in
>>> America instead of Europe.
>> 
>> Most of the money comes from North Americans.  There is some historical information in RFC 3717.
> 
> I'd suggest a more thorough analysis.
> 
> Data from https://www.ietf.org/meeting/upcoming.html and
> https://www.ietf.org/meeting/past.html. Take a look at the attached
> spreadsheet.
> 
> IETF demographics and meeting location policy have changed over time.
> 
> Originally, in 1986, not only was the IETF entirely American, it was
> entirely US Government, and nobody else was invited. That changed pretty
> quickly, but the community attending remained predominantly US for some
> time. So meetings before 1993 all occurred in North America, and if
> truth be told, the reason that the meeting in August 1990 was outside
> the US was that it had been intended to be in Seattle, the host had a
> problem, and UBC came to the rescue.
> 
> Starting in 1993, we noted that the demographics had changed; about one
> in six IETF participants came from Europe. So, we tried to place one
> meeting in six in Europe. We had a small group attending from Australia,
> and in 2000 had a meeting there in recognition of the fact. But by that
> time, we were starting to have a more significant attendance from Asia,
> notably Japan. So we changed policy to trying to position three meetings
> in six in North America, two in Europe, and one in Asia+Australia. And
> starting (IIRC) in 2005, we simplified that policy to having one meeting
> each year in Asia, Europe, and North America.
> 
> Regarding that last policy, we have unfortunately had some problems; one
> meeting that we intended to have in Asia recently fell through, and we
> had to move it somewhere, and in another recent case the Asian venues we
> were looking at essentially priced themselves out of the market. Our
> Asian friends told us that a meeting in Vancouver was an acceptable
> compromise; getting a visa wasn't as hard for them as a US visa, and it
> was not too hard to get to. So we have had at least two meetings in
> Vancouver that we fully intended to have in Asia.
> 
> Since 2004, we have in fact had about 1/3 of our meetings in Europe. If
> anyone has been shortchanged, it has been our Asian friends. "Where the
> money came from" was an issue in the 1990's - we had to assume that a
> meeting outside the US would be financially short due to US participants
> not attending; in 2000, the meeting in San Diego had 2810 people and the
> meeting in Pittsburg 2344, but the meeting in Adelaide had 1431. By
> 2004, distribution had become roughly even - meetings that year had
> right around 1300 attendees regardless of location. The issues are now
> related to success in finding affordable venues.
> 
> 
> 
> 
> 

From sm@resistor.net  Fri Nov  9 16:47:52 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B40A421F8514 for <ietf@ietfa.amsl.com>; Fri,  9 Nov 2012 16:47:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.989
X-Spam-Level: 
X-Spam-Status: No, score=-101.989 tagged_above=-999 required=5 tests=[AWL=-0.390, BAYES_00=-2.599, GB_AFFORDABLE=1, 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 cPmG0KolJSCb for <ietf@ietfa.amsl.com>; Fri,  9 Nov 2012 16:47:52 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0FA9F21F8476 for <ietf@ietf.org>; Fri,  9 Nov 2012 16:47:51 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id qAA0lhLU009291; Fri, 9 Nov 2012 16:47:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1352508467; bh=jCH1q1iE1sLkra5vSJjVr8ebKSJOom5Zw2ubKRB1brE=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=QZz6mQRhBpz4xCyiqCa+jYXmKUg/dh+udspnWj1WfE1BttSdyV4NbDL/6Q3p+eliC sWv/cmfks71vNBnfUvbttmi4VvS5mPENdVUdO/5trtnC0Ue6jMxiPBD764KXe33qsm X1mGZMcDWkG1O49Ues5mJEi79ZSEL+EQV+XsUDJs=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1352508467; i=@resistor.net; bh=jCH1q1iE1sLkra5vSJjVr8ebKSJOom5Zw2ubKRB1brE=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=S59JCNuxsFZwIlB3g/M7QJJ3m1qekJXsDnTKZrNDoZognWXwMNG1hNZM/QVhn5Wl7 TtgeMx04A8Lx4fD0FUIjLuDmJLosgzpIwcodTKqbBdzEbiLzXzxBAooFhBrQ/TuP5j /+87r1CaiUj9UUzHwEKVp+ONu3rxidrlqf3SepWA=
Message-Id: <6.2.5.6.2.20121109160400.0aedba00@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 09 Nov 2012 16:42:12 -0800
To: Arturo Servin <arturo.servin@gmail.com>
From: SM <sm@resistor.net>
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
In-Reply-To: <509D910D.7060503@gmail.com>
References: <CADnDZ8-fjxfgJys8sE10DdZ08tB8HdaTQXbPj2d7-OuQOGi9Pg@mail.gmail.com> <CADnDZ8_v3M1fNtkOV4rU1F-iaMC+2qvKhR353vwESiQsfh70MQ@mail.gmail.com> <6.2.5.6.2.20121109074113.0b2000f8@resistor.net> <8C48B86A895913448548E6D15DA7553B19E215@xmb-rcd-x09.cisco.com> <509D910D.7060503@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 10 Nov 2012 00:47:52 -0000

Hi Arturo,
At 15:26 09-11-2012, Arturo Servin wrote:
>         So basically the IETF is roaming most of the time in  North America,
>sometimes in Europe and once in a while in Asia. Is that how the IETF
>thinks about the global development of Internet standards?
>
>         No wonder why some countries in Africa and Latin America are
>approaching ITU.
>
>         If the IETF really wants to make a change we need to stop 
> thinking that
>North-America/Europe = Global.

Fred Baker mentioned that:

   "The issues are now related to success in finding affordable venues."

The IAOC Chair commented about meetings in Latin America a few months 
ago [1].  It might be possible (non-IETF effort) to reduce the cost 
to participants to offset an expensive venue in Latin America.

Regards,
-sm

1. http://www.ietf.org/mail-archive/web/ietf/current/msg74666.html  


From arturo.servin@gmail.com  Fri Nov  9 16:50:57 2012
Return-Path: <arturo.servin@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A2AD221F8979 for <ietf@ietfa.amsl.com>; Fri,  9 Nov 2012 16:50:57 -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, GB_AFFORDABLE=1, 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 zQjzV9qdKIbL for <ietf@ietfa.amsl.com>; Fri,  9 Nov 2012 16:50:56 -0800 (PST)
Received: from mail-ob0-f172.google.com (mail-ob0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id 10A9B21F8961 for <ietf@ietf.org>; Fri,  9 Nov 2012 16:50:55 -0800 (PST)
Received: by mail-ob0-f172.google.com with SMTP id wo10so1210388obc.31 for <ietf@ietf.org>; Fri, 09 Nov 2012 16:50:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=OhFyVV+DHHWODEyakROhLby7YY3I90YlL9zwvWys4JM=; b=iwpEi9zrAXDiupj3bHZ6psdX9jLjcsAUEAN5eAZnolCRAuTLhrSlDG2UJxVhz/hsHG pVp/0GLx3/4+ZNNNuFcdwDeTVLiNCw0zK72GOL7YEEZIRb+rR85rI5qIwSClWuKXZY5G pCjE7NyZ0ebHOWDy6n6stpHeZpbZ8/9aWyMRYahaPZWBMoAfBec89ohurdEPd65MZNUT PpGP03rHVM7CNepvxZVbVGyjb62318wVETNDDdnjLOvQXF/OaH+X1bcvQHQk1K6W0rn6 9mCAUp27gVDdwoQhZPD0yxmKQT7PtF4UQt27UIHrw6s+XYJWnh64W2Kuh2cMP0cUoldm OCZg==
Received: by 10.182.122.9 with SMTP id lo9mr5088695obb.39.1352508652084; Fri, 09 Nov 2012 16:50:52 -0800 (PST)
Received: from MiniR2D2.local (ip-64-134-245-158.public.wayport.net. [64.134.245.158]) by mx.google.com with ESMTPS id bd5sm115042obb.5.2012.11.09.16.50.46 (version=SSLv3 cipher=OTHER); Fri, 09 Nov 2012 16:50:51 -0800 (PST)
Message-ID: <509DA4DD.2090008@gmail.com>
Date: Fri, 09 Nov 2012 19:50:37 -0500
From: Arturo Servin <arturo.servin@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: SM <sm@resistor.net>
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
References: <CADnDZ8-fjxfgJys8sE10DdZ08tB8HdaTQXbPj2d7-OuQOGi9Pg@mail.gmail.com> <CADnDZ8_v3M1fNtkOV4rU1F-iaMC+2qvKhR353vwESiQsfh70MQ@mail.gmail.com> <6.2.5.6.2.20121109074113.0b2000f8@resistor.net> <8C48B86A895913448548E6D15DA7553B19E215@xmb-rcd-x09.cisco.com> <509D910D.7060503@gmail.com> <6.2.5.6.2.20121109160400.0aedba00@resistor.net>
In-Reply-To: <6.2.5.6.2.20121109160400.0aedba00@resistor.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 10 Nov 2012 00:50:57 -0000

SM

On 09/11/2012 19:42, SM wrote:
> Hi Arturo,
> At 15:26 09-11-2012, Arturo Servin wrote:
>>         So basically the IETF is roaming most of the time in  North
>> America,
>> sometimes in Europe and once in a while in Asia. Is that how the IETF
>> thinks about the global development of Internet standards?
>>
>>         No wonder why some countries in Africa and Latin America are
>> approaching ITU.
>>
>>         If the IETF really wants to make a change we need to stop
>> thinking that
>> North-America/Europe = Global.
>
> Fred Baker mentioned that:
>
>   "The issues are now related to success in finding affordable venues."
    ICANN finds them, the IGF does it, the RIRs do it. Why not the IETF?
 
> The IAOC Chair commented about meetings in Latin America a few months
> ago [1].  It might be possible (non-IETF effort) to reduce the cost to
> participants to offset an expensive venue in Latin America.
>
> Regards,
> -sm
>
> 1. http://www.ietf.org/mail-archive/web/ietf/current/msg74666.html 

    I am sure they would find support, it is just a matter to look and ask.

Regards,
as


From brian.e.carpenter@gmail.com  Fri Nov  9 16:50:58 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ED4F221F89EA for <ietf@ietfa.amsl.com>; Fri,  9 Nov 2012 16:50:57 -0800 (PST)
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=-2.599, GB_AFFORDABLE=1, RCVD_IN_DNSWL_LOW=-1, 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 sZTedFSzC9zC for <ietf@ietfa.amsl.com>; Fri,  9 Nov 2012 16:50:56 -0800 (PST)
Received: from mail-yh0-f44.google.com (mail-yh0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id E4FAD21F895C for <ietf@ietf.org>; Fri,  9 Nov 2012 16:50:54 -0800 (PST)
Received: by mail-yh0-f44.google.com with SMTP id 56so966540yhq.31 for <ietf@ietf.org>; Fri, 09 Nov 2012 16:50:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=Bq+20tqguv2UIINJxjPdojXJeXqE23+J91jmulHPRk8=; b=lWzrzwpHauXQS/PB96q4oUZMwmWqYqpwUSqUtWHHGpeMqdvff88JhBWsFEkX+cBjYl ZVbTvoIWDMzq8OIesiLoGgQUgMTxwoEaJfywqwfHb73oqDEwyyHyDwxO9zTSXjaQ5Uw2 vVG5Y07K50F7ljc1WFXRY3Rs5pb2MYRdiDz0kvjtrcfolFsSdrrjeJbjxwW8uUH6IUUH 5fZLL/IWqpkpwJBXAhQ+3lGUUXXSXR77H48GqAklCkelCby+J+dyn3tte6QrpJXTU/Zu CzXDXqTfljKaBp4HBVJIol8bP3s8l9LJ+ILf1SboX7bZXR9tZCMUfMdXGq1RZS0qhc2A pPsw==
Received: by 10.236.119.37 with SMTP id m25mr13203728yhh.95.1352508642264; Fri, 09 Nov 2012 16:50:42 -0800 (PST)
Received: from [10.241.77.38] (m5e5f36d0.tmodns.net. [208.54.95.94]) by mx.google.com with ESMTPS id z6sm115505yhl.8.2012.11.09.16.50.40 (version=SSLv3 cipher=OTHER); Fri, 09 Nov 2012 16:50:41 -0800 (PST)
Message-ID: <509DA4E7.1090504@gmail.com>
Date: Sat, 10 Nov 2012 00:50:47 +0000
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Arturo Servin <arturo.servin@gmail.com>
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
References: <CADnDZ8-fjxfgJys8sE10DdZ08tB8HdaTQXbPj2d7-OuQOGi9Pg@mail.gmail.com>	<CADnDZ8_v3M1fNtkOV4rU1F-iaMC+2qvKhR353vwESiQsfh70MQ@mail.gmail.com>	<6.2.5.6.2.20121109074113.0b2000f8@resistor.net>	<8C48B86A895913448548E6D15DA7553B19E215@xmb-rcd-x09.cisco.com> <509D910D.7060503@gmail.com>
In-Reply-To: <509D910D.7060503@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 10 Nov 2012 00:50:58 -0000

Arturo,

On 09/11/2012 23:26, Arturo Servin wrote:
> 	So basically the IETF is roaming most of the time in  North America,
> sometimes in Europe and once in a while in Asia. Is that how the IETF
> thinks about the global development of Internet standards?

No. The criterion has always been to hold meetings where they can be
most effective in making the Internet work better - as far as a
standards organisation can do that. That means choosing places where
a meeting can be run effectively and a reasonably high proportion
of those actively participating can afford to attend. As participation
in the IETF has evolved, so has the geographical part of site selection
policy evolved, as Fred described. For example, the attendance data will
tell you why the policy has recently led to two meetings in China.

I think you'll find the policy is different for more operational
meetings, which as far as I can tell have been taking place in Asia,
Africa and Latin America for years. Those meetings have different
criteria for their part in making the Internet work better.

> 
> 	No wonder why some countries in Africa and Latin America are
> approaching ITU.

ITU-T does a great deal of its standards-making in Geneva. The meetings
in other areas tend have a different purpose, as do many ISOC activities.

> 	If the IETF really wants to make a change we need to stop thinking that
> North-America/Europe = Global.

I think nobody has thought that for at least 10 years (IETF 54).

    Brian
> 
> Regards,
> as
> 
> On 09/11/2012 16:05, Fred Baker (fred) wrote:
>> On Nov 9, 2012, at 12:28 PM, SM wrote:
>>
>>> At 06:31 09-11-2012, Abdussalam Baryun wrote:
>>>> I am newcomer and not able to attend because most of meeting in
>>>> America instead of Europe.
>>> Most of the money comes from North Americans.  There is some historical information in RFC 3717.
>> I'd suggest a more thorough analysis.
>>
>> Data from https://www.ietf.org/meeting/upcoming.html and
>> https://www.ietf.org/meeting/past.html. Take a look at the attached
>> spreadsheet.
>>
>> IETF demographics and meeting location policy have changed over time.
>>
>> Originally, in 1986, not only was the IETF entirely American, it was
>> entirely US Government, and nobody else was invited. That changed pretty
>> quickly, but the community attending remained predominantly US for some
>> time. So meetings before 1993 all occurred in North America, and if
>> truth be told, the reason that the meeting in August 1990 was outside
>> the US was that it had been intended to be in Seattle, the host had a
>> problem, and UBC came to the rescue.
>>
>> Starting in 1993, we noted that the demographics had changed; about one
>> in six IETF participants came from Europe. So, we tried to place one
>> meeting in six in Europe. We had a small group attending from Australia,
>> and in 2000 had a meeting there in recognition of the fact. But by that
>> time, we were starting to have a more significant attendance from Asia,
>> notably Japan. So we changed policy to trying to position three meetings
>> in six in North America, two in Europe, and one in Asia+Australia. And
>> starting (IIRC) in 2005, we simplified that policy to having one meeting
>> each year in Asia, Europe, and North America.
>>
>> Regarding that last policy, we have unfortunately had some problems; one
>> meeting that we intended to have in Asia recently fell through, and we
>> had to move it somewhere, and in another recent case the Asian venues we
>> were looking at essentially priced themselves out of the market. Our
>> Asian friends told us that a meeting in Vancouver was an acceptable
>> compromise; getting a visa wasn't as hard for them as a US visa, and it
>> was not too hard to get to. So we have had at least two meetings in
>> Vancouver that we fully intended to have in Asia.
>>
>> Since 2004, we have in fact had about 1/3 of our meetings in Europe. If
>> anyone has been shortchanged, it has been our Asian friends. "Where the
>> money came from" was an issue in the 1990's - we had to assume that a
>> meeting outside the US would be financially short due to US participants
>> not attending; in 2000, the meeting in San Diego had 2810 people and the
>> meeting in Pittsburg 2344, but the meeting in Adelaide had 1431. By
>> 2004, distribution had become roughly even - meetings that year had
>> right around 1300 attendees regardless of location. The issues are now
>> related to success in finding affordable venues.
>>
>>
>>
>>
>>
> 

From arturo.servin@gmail.com  Fri Nov  9 17:00:43 2012
Return-Path: <arturo.servin@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3534221F88B1 for <ietf@ietfa.amsl.com>; Fri,  9 Nov 2012 17:00:43 -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, GB_AFFORDABLE=1, 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 gH8t6b9SeN0F for <ietf@ietfa.amsl.com>; Fri,  9 Nov 2012 17:00:42 -0800 (PST)
Received: from mail-ob0-f172.google.com (mail-ob0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id 7ED1121F8A26 for <ietf@ietf.org>; Fri,  9 Nov 2012 17:00:37 -0800 (PST)
Received: by mail-ob0-f172.google.com with SMTP id wo10so1215499obc.31 for <ietf@ietf.org>; Fri, 09 Nov 2012 17:00:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=WjyOJThexxCEABQcDyoImcJKX14VNYQkjdGGsn58Ia4=; b=vMl566OIqZpDf6gxyc3DAND7V09zXpTtJ/KH3cHf6SUOy49FR8k5n1Z9thfJT2uJ0h jlLQdhWtAlmS74a/IcszJtD1aetgkUT3Zrb+6H2HUkTtbL9VjrOZnZyYY+zjtvz3o893 3hJVe2eUZ0y8JICAN25i/HJxMFzmwi2TQKPMrzQCw60cLKh9KrZ2w47dZLwWpAwiQtsy 7+BXVOm1p4+22VIppfyE5Vvu90KKYOFTJENEzRceJek+IrWvcE80ZBe45I+rxBmuAzU8 +qFH7LiR1Aepm4az+fDAWKlpclX2N+h6SkkrPqhHYLXpz2gYmNk/xSJwK/ROCeEorMdj HK2A==
Received: by 10.60.171.200 with SMTP id aw8mr9254464oec.112.1352509237176; Fri, 09 Nov 2012 17:00:37 -0800 (PST)
Received: from MiniR2D2.local (ip-64-134-245-158.public.wayport.net. [64.134.245.158]) by mx.google.com with ESMTPS id jd1sm124996obb.8.2012.11.09.17.00.29 (version=SSLv3 cipher=OTHER); Fri, 09 Nov 2012 17:00:36 -0800 (PST)
Message-ID: <509DA723.7030703@gmail.com>
Date: Fri, 09 Nov 2012 20:00:19 -0500
From: Arturo Servin <arturo.servin@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
References: <CADnDZ8-fjxfgJys8sE10DdZ08tB8HdaTQXbPj2d7-OuQOGi9Pg@mail.gmail.com>	<CADnDZ8_v3M1fNtkOV4rU1F-iaMC+2qvKhR353vwESiQsfh70MQ@mail.gmail.com>	<6.2.5.6.2.20121109074113.0b2000f8@resistor.net>	<8C48B86A895913448548E6D15DA7553B19E215@xmb-rcd-x09.cisco.com> <509D910D.7060503@gmail.com> <509DA4E7.1090504@gmail.com>
In-Reply-To: <509DA4E7.1090504@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 10 Nov 2012 01:00:43 -0000

Brian,

    Your comment just reinforce my perception that the IETF is not
interested in being an global organization of standards.

    People is asking how to evolve the IETF, well, one possibility is to
start thinking global and to reach more people outside the common
venues. It is more expensive, more complex, yes. But in my opinion is
worthy if we really want to show that we care about the multistakeholder
model that we preach.

    Hard times may come, some people will ask why the Internet standards
are just developed in some places and will challenge us. Frankly, what I
see is that we do not care.

Regards,
as

On 09/11/2012 19:50, Brian E Carpenter wrote:
> Arturo,
>
> On 09/11/2012 23:26, Arturo Servin wrote:
>> 	So basically the IETF is roaming most of the time in  North America,
>> sometimes in Europe and once in a while in Asia. Is that how the IETF
>> thinks about the global development of Internet standards?
> No. The criterion has always been to hold meetings where they can be
> most effective in making the Internet work better - as far as a
> standards organisation can do that. That means choosing places where
> a meeting can be run effectively and a reasonably high proportion
> of those actively participating can afford to attend. As participation
> in the IETF has evolved, so has the geographical part of site selection
> policy evolved, as Fred described. For example, the attendance data will
> tell you why the policy has recently led to two meetings in China.
>
> I think you'll find the policy is different for more operational
> meetings, which as far as I can tell have been taking place in Asia,
> Africa and Latin America for years. Those meetings have different
> criteria for their part in making the Internet work better.
>
>> 	No wonder why some countries in Africa and Latin America are
>> approaching ITU.
> ITU-T does a great deal of its standards-making in Geneva. The meetings
> in other areas tend have a different purpose, as do many ISOC activities.
>
>> 	If the IETF really wants to make a change we need to stop thinking that
>> North-America/Europe = Global.
> I think nobody has thought that for at least 10 years (IETF 54).
>
>     Brian
>> Regards,
>> as
>>
>> On 09/11/2012 16:05, Fred Baker (fred) wrote:
>>> On Nov 9, 2012, at 12:28 PM, SM wrote:
>>>
>>>> At 06:31 09-11-2012, Abdussalam Baryun wrote:
>>>>> I am newcomer and not able to attend because most of meeting in
>>>>> America instead of Europe.
>>>> Most of the money comes from North Americans.  There is some historical information in RFC 3717.
>>> I'd suggest a more thorough analysis.
>>>
>>> Data from https://www.ietf.org/meeting/upcoming.html and
>>> https://www.ietf.org/meeting/past.html. Take a look at the attached
>>> spreadsheet.
>>>
>>> IETF demographics and meeting location policy have changed over time.
>>>
>>> Originally, in 1986, not only was the IETF entirely American, it was
>>> entirely US Government, and nobody else was invited. That changed pretty
>>> quickly, but the community attending remained predominantly US for some
>>> time. So meetings before 1993 all occurred in North America, and if
>>> truth be told, the reason that the meeting in August 1990 was outside
>>> the US was that it had been intended to be in Seattle, the host had a
>>> problem, and UBC came to the rescue.
>>>
>>> Starting in 1993, we noted that the demographics had changed; about one
>>> in six IETF participants came from Europe. So, we tried to place one
>>> meeting in six in Europe. We had a small group attending from Australia,
>>> and in 2000 had a meeting there in recognition of the fact. But by that
>>> time, we were starting to have a more significant attendance from Asia,
>>> notably Japan. So we changed policy to trying to position three meetings
>>> in six in North America, two in Europe, and one in Asia+Australia. And
>>> starting (IIRC) in 2005, we simplified that policy to having one meeting
>>> each year in Asia, Europe, and North America.
>>>
>>> Regarding that last policy, we have unfortunately had some problems; one
>>> meeting that we intended to have in Asia recently fell through, and we
>>> had to move it somewhere, and in another recent case the Asian venues we
>>> were looking at essentially priced themselves out of the market. Our
>>> Asian friends told us that a meeting in Vancouver was an acceptable
>>> compromise; getting a visa wasn't as hard for them as a US visa, and it
>>> was not too hard to get to. So we have had at least two meetings in
>>> Vancouver that we fully intended to have in Asia.
>>>
>>> Since 2004, we have in fact had about 1/3 of our meetings in Europe. If
>>> anyone has been shortchanged, it has been our Asian friends. "Where the
>>> money came from" was an issue in the 1990's - we had to assume that a
>>> meeting outside the US would be financially short due to US participants
>>> not attending; in 2000, the meeting in San Diego had 2810 people and the
>>> meeting in Pittsburg 2344, but the meeting in Adelaide had 1431. By
>>> 2004, distribution had become roughly even - meetings that year had
>>> right around 1300 attendees regardless of location. The issues are now
>>> related to success in finding affordable venues.
>>>
>>>
>>>
>>>
>>>


From dwm@xpasc.com  Fri Nov  9 17:52:36 2012
Return-Path: <dwm@xpasc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 755D921F8841 for <ietf@ietfa.amsl.com>; Fri,  9 Nov 2012 17:52:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.238
X-Spam-Level: 
X-Spam-Status: No, score=-1.238 tagged_above=-999 required=5 tests=[AWL=-0.931, BAYES_00=-2.599, GB_AFFORDABLE=1, MISSING_HEADERS=1.292]
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 dJAe7dpRfKig for <ietf@ietfa.amsl.com>; Fri,  9 Nov 2012 17:52:36 -0800 (PST)
Received: from c2w3p-2.abacamail.com (c2w3p-2.abacamail.com [209.133.53.32]) by ietfa.amsl.com (Postfix) with ESMTP id 1CD2121F8819 for <ietf@ietf.org>; Fri,  9 Nov 2012 17:52:35 -0800 (PST)
Received: from xpasc.com (unknown [68.164.244.188]) by c2w3p-2.abacamail.com (Postfix) with ESMTP id D33653FDE3 for <ietf@ietf.org>; Sat, 10 Nov 2012 01:52:34 +0000 (UTC)
Received: from egate.xpasc.com (egate.xpasc.com [10.1.2.49]) by xpasc.com (8.13.8/8.13.8) with ESMTP id qAA1qYY7016482 for <ietf@ietf.org>; Fri, 9 Nov 2012 17:52:34 -0800
Date: Fri, 9 Nov 2012 17:52:34 -0800 (PST)
From: David Morris <dwm@xpasc.com>
cc: ietf@ietf.org
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
In-Reply-To: <509DA4DD.2090008@gmail.com>
Message-ID: <alpine.LRH.2.01.1211091748160.16248@egate.xpasc.com>
References: <CADnDZ8-fjxfgJys8sE10DdZ08tB8HdaTQXbPj2d7-OuQOGi9Pg@mail.gmail.com> <CADnDZ8_v3M1fNtkOV4rU1F-iaMC+2qvKhR353vwESiQsfh70MQ@mail.gmail.com> <6.2.5.6.2.20121109074113.0b2000f8@resistor.net> <8C48B86A895913448548E6D15DA7553B19E215@xmb-rcd-x09.cisco.com> <509D910D.7060503@gmail.com> <6.2.5.6.2.20121109160400.0aedba00@resistor.net> <509DA4DD.2090008@gmail.com>
User-Agent: Alpine 2.01 (LRH 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Milter-Version: master.1+13-gbab1945
X-AV-Type: clean
X-AV-Accuracy: exact
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: ietf@ietf.org
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 10 Nov 2012 01:52:36 -0000

On Fri, 9 Nov 2012, Arturo Servin wrote:

> SM
> 
> On 09/11/2012 19:42, SM wrote:
> >
> > Fred Baker mentioned that:
> >
> >   "The issues are now related to success in finding affordable venues."
>     ICANN finds them, the IGF does it, the RIRs do it. Why not the IETF?
>  
> > The IAOC Chair commented about meetings in Latin America a few months
> > ago [1].  It might be possible (non-IETF effort) to reduce the cost to
> > participants to offset an expensive venue in Latin America.
> >
> > Regards,
> > -sm
> >
> > 1. http://www.ietf.org/mail-archive/web/ietf/current/msg74666.html 
> 
>     I am sure they would find support, it is just a matter to look and ask.

Sometimes it is up to the folks who want to make the change to do the 
looking and asking. 

ICANN has an entirely different funding model than
the IETF as well as significantly different stakeholders. ICANN has
participants willing to spend hundreds of thousands of dollars to
join the quest for TLDs for example. Many IETF participants must
pay their own expenses or compete for their employer's very scarse
travel funds.

From joelja@bogus.com  Fri Nov  9 22:25:20 2012
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF16B21F8553 for <ietf@ietfa.amsl.com>; Fri,  9 Nov 2012 22:25:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.599
X-Spam-Level: 
X-Spam-Status: No, score=-101.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_AFFORDABLE=1, 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 m1n-tSBqCp1i for <ietf@ietfa.amsl.com>; Fri,  9 Nov 2012 22:25:20 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 2189521F8543 for <ietf@ietf.org>; Fri,  9 Nov 2012 22:25:19 -0800 (PST)
Received: from joels-MacBook-Air.local (c-98-234-216-143.hsd1.ca.comcast.net [98.234.216.143]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id qAA6PE9j094056 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Sat, 10 Nov 2012 06:25:14 GMT (envelope-from joelja@bogus.com)
Message-ID: <509DD3E0.6050408@bogus.com>
Date: Fri, 09 Nov 2012 23:11:12 -0500
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Arturo Servin <arturo.servin@gmail.com>
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
References: <CADnDZ8-fjxfgJys8sE10DdZ08tB8HdaTQXbPj2d7-OuQOGi9Pg@mail.gmail.com>	<CADnDZ8_v3M1fNtkOV4rU1F-iaMC+2qvKhR353vwESiQsfh70MQ@mail.gmail.com>	<6.2.5.6.2.20121109074113.0b2000f8@resistor.net>	<8C48B86A895913448548E6D15DA7553B19E215@xmb-rcd-x09.cisco.com> <509D910D.7060503@gmail.com> <509DA4E7.1090504@gmail.com> <509DA723.7030703@gmail.com>
In-Reply-To: <509DA723.7030703@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Sat, 10 Nov 2012 06:25:15 +0000 (UTC)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 10 Nov 2012 06:25:20 -0000

On 11/9/12 8:00 PM, Arturo Servin wrote:
> Brian,
>
>      Your comment just reinforce my perception that the IETF is not
> interested in being an global organization of standards.
>
>      People is asking how to evolve the IETF, well, one possibility is to
> start thinking global and to reach more people outside the common
> venues. It is more expensive, more complex, yes. But in my opinion is
> worthy if we really want to show that we care about the multistakeholder
> model that we preach.
Multistakeholder is a loaded term from other contexts. IETF participants 
whether they attend the meeting or not are self-selected.

I have some thoughts about interim meetings as an outreach tool in draft 
form and I would appreciate some feeback on those sections.

http://www.ietf.org/id/draft-jaeggli-interim-observations-03.txt
>      Hard times may come, some people will ask why the Internet standards
> are just developed in some places and will challenge us. Frankly, what I
> see is that we do not care.
Why shouldn't standards be developed elsewhere (oddly enough, they are)? 
IETF participants have never had a monopoly on either need or good ideas.

  Regards, as On 09/11/2012 19:50, Brian E Carpenter wrote:
>> Arturo,
>>
>> On 09/11/2012 23:26, Arturo Servin wrote:
>>> 	So basically the IETF is roaming most of the time in  North America,
>>> sometimes in Europe and once in a while in Asia. Is that how the IETF
>>> thinks about the global development of Internet standards?
>> No. The criterion has always been to hold meetings where they can be
>> most effective in making the Internet work better - as far as a
>> standards organisation can do that. That means choosing places where
>> a meeting can be run effectively and a reasonably high proportion
>> of those actively participating can afford to attend. As participation
>> in the IETF has evolved, so has the geographical part of site selection
>> policy evolved, as Fred described. For example, the attendance data will
>> tell you why the policy has recently led to two meetings in China.
>>
>> I think you'll find the policy is different for more operational
>> meetings, which as far as I can tell have been taking place in Asia,
>> Africa and Latin America for years. Those meetings have different
>> criteria for their part in making the Internet work better.
>>
>>> 	No wonder why some countries in Africa and Latin America are
>>> approaching ITU.
>> ITU-T does a great deal of its standards-making in Geneva. The meetings
>> in other areas tend have a different purpose, as do many ISOC activities.
>>
>>> 	If the IETF really wants to make a change we need to stop thinking that
>>> North-America/Europe = Global.
>> I think nobody has thought that for at least 10 years (IETF 54).
>>
>>      Brian
>>> Regards,
>>> as
>>>
>>> On 09/11/2012 16:05, Fred Baker (fred) wrote:
>>>> On Nov 9, 2012, at 12:28 PM, SM wrote:
>>>>
>>>>> At 06:31 09-11-2012, Abdussalam Baryun wrote:
>>>>>> I am newcomer and not able to attend because most of meeting in
>>>>>> America instead of Europe.
>>>>> Most of the money comes from North Americans.  There is some historical information in RFC 3717.
>>>> I'd suggest a more thorough analysis.
>>>>
>>>> Data from https://www.ietf.org/meeting/upcoming.html and
>>>> https://www.ietf.org/meeting/past.html. Take a look at the attached
>>>> spreadsheet.
>>>>
>>>> IETF demographics and meeting location policy have changed over time.
>>>>
>>>> Originally, in 1986, not only was the IETF entirely American, it was
>>>> entirely US Government, and nobody else was invited. That changed pretty
>>>> quickly, but the community attending remained predominantly US for some
>>>> time. So meetings before 1993 all occurred in North America, and if
>>>> truth be told, the reason that the meeting in August 1990 was outside
>>>> the US was that it had been intended to be in Seattle, the host had a
>>>> problem, and UBC came to the rescue.
>>>>
>>>> Starting in 1993, we noted that the demographics had changed; about one
>>>> in six IETF participants came from Europe. So, we tried to place one
>>>> meeting in six in Europe. We had a small group attending from Australia,
>>>> and in 2000 had a meeting there in recognition of the fact. But by that
>>>> time, we were starting to have a more significant attendance from Asia,
>>>> notably Japan. So we changed policy to trying to position three meetings
>>>> in six in North America, two in Europe, and one in Asia+Australia. And
>>>> starting (IIRC) in 2005, we simplified that policy to having one meeting
>>>> each year in Asia, Europe, and North America.
>>>>
>>>> Regarding that last policy, we have unfortunately had some problems; one
>>>> meeting that we intended to have in Asia recently fell through, and we
>>>> had to move it somewhere, and in another recent case the Asian venues we
>>>> were looking at essentially priced themselves out of the market. Our
>>>> Asian friends told us that a meeting in Vancouver was an acceptable
>>>> compromise; getting a visa wasn't as hard for them as a US visa, and it
>>>> was not too hard to get to. So we have had at least two meetings in
>>>> Vancouver that we fully intended to have in Asia.
>>>>
>>>> Since 2004, we have in fact had about 1/3 of our meetings in Europe. If
>>>> anyone has been shortchanged, it has been our Asian friends. "Where the
>>>> money came from" was an issue in the 1990's - we had to assume that a
>>>> meeting outside the US would be financially short due to US participants
>>>> not attending; in 2000, the meeting in San Diego had 2810 people and the
>>>> meeting in Pittsburg 2344, but the meeting in Adelaide had 1431. By
>>>> 2004, distribution had become roughly even - meetings that year had
>>>> right around 1300 attendees regardless of location. The issues are now
>>>> related to success in finding affordable venues.
>>>>
>>>>
>>>>
>>>>
>>>>


From randy@psg.com  Sat Nov 10 00:15:02 2012
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2206421F8B18 for <ietf@ietfa.amsl.com>; Sat, 10 Nov 2012 00:15:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.541
X-Spam-Level: 
X-Spam-Status: No, score=-2.541 tagged_above=-999 required=5 tests=[AWL=0.058,  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 D1Ce4fOGSD6j for <ietf@ietfa.amsl.com>; Sat, 10 Nov 2012 00:15:01 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id A594021F88B8 for <ietf@ietf.org>; Sat, 10 Nov 2012 00:15:01 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from <randy@psg.com>) id 1TX6DS-000OnB-TH; Sat, 10 Nov 2012 08:14:59 +0000
Date: Sat, 10 Nov 2012 17:14:57 +0900
Message-ID: <m2390hq3ge.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Arturo Servin <arturo.servin@gmail.com>
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
In-Reply-To: <509DA723.7030703@gmail.com>
References: <CADnDZ8-fjxfgJys8sE10DdZ08tB8HdaTQXbPj2d7-OuQOGi9Pg@mail.gmail.com> <CADnDZ8_v3M1fNtkOV4rU1F-iaMC+2qvKhR353vwESiQsfh70MQ@mail.gmail.com> <6.2.5.6.2.20121109074113.0b2000f8@resistor.net> <8C48B86A895913448548E6D15DA7553B19E215@xmb-rcd-x09.cisco.com> <509D910D.7060503@gmail.com> <509DA4E7.1090504@gmail.com> <509DA723.7030703@gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 10 Nov 2012 08:15:02 -0000

arturo,

many of us have the message that you think the ietf should meet in alyc.
so qui bitching, find a locale/hotel, a host, and the connectivity in
somewhere not too hard to reach (i.e. not a puddle-jumper for the last
hour).  then propose it for one or more of dates which are open.

i'll leave my biases out of it, but there are many lovely cities in
south america which i would love to see again.  of course, all i will
see is the inside of a frelling hotel, but that's life i guess.

randy

From sm@resistor.net  Sat Nov 10 03:36:25 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F3C321F857E for <ietf@ietfa.amsl.com>; Sat, 10 Nov 2012 03:36:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.475
X-Spam-Level: 
X-Spam-Status: No, score=-102.475 tagged_above=-999 required=5 tests=[AWL=0.124, 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 zApOy0qwO3ya for <ietf@ietfa.amsl.com>; Sat, 10 Nov 2012 03:36:24 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 641BB21F857C for <ietf@ietf.org>; Sat, 10 Nov 2012 03:36:24 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id qAABaD0a024692; Sat, 10 Nov 2012 03:36:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1352547378; bh=YTZTJW+uz09SeKhuRR0Ul+q4kqfSGyPoG5KPvhnXFUk=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=W0rSIGbIwPpIfV5Fr73l0UA2C469t7aQtmJVu8bwGY2DQbFNUB2AIXGPgjad96Gxf M1+zcHqRNHulUs2FrtO3085sLMDCyUumk/kdRyBAj4kTn7RbQuSllcqqdoB8mUOQ6I q9Dpwaqi5ZlWgCAxIioUwVDLw/C/EYm+sDDOX+e4=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1352547378; i=@resistor.net; bh=YTZTJW+uz09SeKhuRR0Ul+q4kqfSGyPoG5KPvhnXFUk=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=1JkISjMNOV8ckPmgUozkMPK/atqITbCXnNqzC4GkNsrngHCpVbaDc7bE2Nq6mZjMc b1XWNbF3CkrfQ+ikbcHVX4Dkoro+FjijHH5cAbmfL+Tld9w0UrXRLbTDnU9jIBe2DG k6DaMgHfdhQo0bbP8upu8TDbb49eoWMVV5ONlZcs=
Message-Id: <6.2.5.6.2.20121110002306.095ae248@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 10 Nov 2012 03:34:42 -0800
To: Arturo Servin <arturo.servin@gmail.com>
From: SM <sm@resistor.net>
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
In-Reply-To: <509DA723.7030703@gmail.com>
References: <CADnDZ8-fjxfgJys8sE10DdZ08tB8HdaTQXbPj2d7-OuQOGi9Pg@mail.gmail.com> <CADnDZ8_v3M1fNtkOV4rU1F-iaMC+2qvKhR353vwESiQsfh70MQ@mail.gmail.com> <6.2.5.6.2.20121109074113.0b2000f8@resistor.net> <8C48B86A895913448548E6D15DA7553B19E215@xmb-rcd-x09.cisco.com> <509D910D.7060503@gmail.com> <509DA4E7.1090504@gmail.com> <509DA723.7030703@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 10 Nov 2012 11:36:25 -0000

Hi Arturo,
At 17:00 09-11-2012, Arturo Servin wrote:
>     Your comment just reinforce my perception that the IETF is not
>interested in being an global organization of standards.

There are some interesting observations in 
draft-jaeggli-interim-observations-03.  For example:

   "Some entities related to the IETF clearly have outreach and advocacy
    as part of the mission, Internet Society, IETF chair, Liaisons, edu-
    team and so forth.  It is not clear to me, that beyond the scope of
    chartered working group documents that end up as part of the RFC
    series, that working group activities including meetings are well
    suited for use as an outreach mechanism."

A working group I participate in booked a slot during the last 
meeting.  That slot, in my individual opinion, is not to be used for 
presentations.  It is not to discuss matters which have not been 
discussion previously on the mailing list.  If someone who has been 
reviewing drafts comes up and says: "I need some help as management 
is asking for travel justification", the person might get a few 
minutes of agenda time.  If there is no justification for the slot 
except for that the WG session would be cancelled.

There was disagreement in the WG and it was not possible to resolve 
that through mailing list discussions.  That led to the WG doing 
nothing for a month.  The meeting provided an opportunity to resolve 
the problem.  It would be a problem if the meeting was held in, for 
example, Canada, and most of the people doing the work [1] cannot attend.

I suggest that you ask Andy Newton why "IETF executives are 
considering selling URNBIS to a pharmaceutical outfit wishing to 
market sedative hypnotics" [2]. :-)

>     People is asking how to evolve the IETF, well, one possibility is to
>start thinking global and to reach more people outside the common
>venues. It is more expensive, more complex, yes. But in my opinion is
>worthy if we really want to show that we care about the multistakeholder
>model that we preach.

The IETF is different from ICANN or the IGF.  David Morris commented 
about ICANN meetings [3].

Riccardo Bernardini mentioned that [4]:

   "Q: Why did you not return?

   A: Because the necessity of being at meeting does not compensate for
   the cost.  Also I work at University, so I participate more to
   scientific conference than to engineering meetings. (Also, teaching
   duties do not help)"

Scott Brim commented that [5]:

   'Even back at the IETF at 20 celebration, when long-time participants got
    up and spoke passionately (and really well) about the shared mission and
    values, there were people listening who reacted with "that's not why I'm
    here, I think they're out of touch with the new IETF".'

>     Hard times may come, some people will ask why the Internet standards
>are just developed in some places and will challenge us. Frankly, what I

Yes.

There has been nine recent RFCs from South America, two from Africa 
and 312 from Asia, excluding Australia.  There aren't any remote 
participants from Africa.  There are some remote participants from 
Latin America.  There is potential, in my humble opinion, from Latin 
America which can be turned into visible participation in the 
IETF.  I'll mention an off-list comment:  encourage people to 
participate in person, on the mailing lists and file drafts.  I 
suggest talking to the IAOC to find out why the venues they looked 
into were not ok.  Try and get CGI.br to help and find ways to make 
it ok.  I doubt that IETF participants would say no if there is an 
opportunity to go to "cidade maravilhosa".

Regards,
-sm

1. http://www.ietf.org/mail-archive/web/ietf/current/msg75140.html
2. http://www.ietf.org/mail-archive/web/apps-discuss/current/msg06346.html
3. http://www.ietf.org/mail-archive/web/ietf/current/msg75782.html
4. http://www.ietf.org/mail-archive/web/ietf/current/msg75744.html
5. http://www.ietf.org/mail-archive/web/ietf/current/msg75768.html 


From daedulus@btconnect.com  Sat Nov 10 04:18:01 2012
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3FC4B21F85CE for <ietf@ietfa.amsl.com>; Sat, 10 Nov 2012 04:18:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.849
X-Spam-Level: 
X-Spam-Status: No, score=-3.849 tagged_above=-999 required=5 tests=[AWL=-0.250, 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 uQEZw490FOA9 for <ietf@ietfa.amsl.com>; Sat, 10 Nov 2012 04:18:00 -0800 (PST)
Received: from db3outboundpool.messaging.microsoft.com (db3ehsobe006.messaging.microsoft.com [213.199.154.144]) by ietfa.amsl.com (Postfix) with ESMTP id D4B8021F8534 for <ietf@ietf.org>; Sat, 10 Nov 2012 04:17:59 -0800 (PST)
Received: from mail80-db3-R.bigfish.com (10.3.81.251) by DB3EHSOBE001.bigfish.com (10.3.84.21) with Microsoft SMTP Server id 14.1.225.23; Sat, 10 Nov 2012 12:17:58 +0000
Received: from mail80-db3 (localhost [127.0.0.1])	by mail80-db3-R.bigfish.com (Postfix) with ESMTP id 85115C032B; Sat, 10 Nov 2012 12:17:58 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.249.85; KIP:(null); UIP:(null); IPV:NLI; H:AMSPRD0710HT004.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -26
X-BigFish: PS-26(zzbb2dI98dI9371Ic89bh936eI542M1432Izz1de0h1202h1d1ah1d2ahzz1033IL8275bh8275dhz2dh2a8h5a9h668h839hd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h304l1155h)
Received: from mail80-db3 (localhost.localdomain [127.0.0.1]) by mail80-db3 (MessageSwitch) id 1352549875582185_14697; Sat, 10 Nov 2012 12:17:55 +0000 (UTC)
Received: from DB3EHSMHS002.bigfish.com (unknown [10.3.81.251])	by mail80-db3.bigfish.com (Postfix) with ESMTP id 8BFB78004E; Sat, 10 Nov 2012 12:17:55 +0000 (UTC)
Received: from AMSPRD0710HT004.eurprd07.prod.outlook.com (157.56.249.85) by DB3EHSMHS002.bigfish.com (10.3.87.102) with Microsoft SMTP Server (TLS) id 14.1.225.23; Sat, 10 Nov 2012 12:17:55 +0000
Received: from SN2PRD0310HT005.namprd03.prod.outlook.com (157.56.234.5) by pod51017.outlook.com (10.255.160.167) with Microsoft SMTP Server (TLS) id 14.16.233.3; Sat, 10 Nov 2012 12:17:54 +0000
Message-ID: <004d01cdbf3d$4be324e0$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: "Carlos M. martinez" <carlosm3011@gmail.com>, <ietf@ietf.org>
References: <50985590.5080507@gmail.com> <50985769.1040704@viagenie.ca> <509D3C52.1020007@gmail.com>
Subject: Re: Is there ongoing work on SNMP IPv6 mibs ?
Date: Sat, 10 Nov 2012 12:16:55 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [157.56.234.5]
Content-Transfer-Encoding: quoted-printable
X-OriginatorOrg: btconnect.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 10 Nov 2012 12:18:01 -0000

---- Original Message -----
From: "Carlos M. martinez" <carlosm3011@gmail.com>
To: <ietf@ietf.org>
Sent: Friday, November 09, 2012 5:24 PM

I'll take the silence as a NO :-)
<tp>
IETF protocols have since long required to countenance both IPv6 and
Management, which for the most part means SNMP, so the developers of a
protocol to support e.g. left-hand flange-benders would be expected to
provide a suitable SNMP MIB module which includes IPv6, so the answer is
everywhere.

There is an IETFMIBS mailing list which provides a home for SNMP matters
of a general nature, while, since management falls within the Operations
Area, the Operations Area Working Group provides a home for SNMP work
which does not naturally fall within the remit of another Working Group.

Details, how to subscribe, view the archives and so on are all available
via the IETF website.

Tom Petch


So, as a humble kinda newcomer, where should I take some ideas regarding
IPv6 mibs ? Which should be the appropiate WG ?

Cheers!

~Carlos

On 11/5/2012 7:18 PM, Simon Perreault wrote:
> Le 2012-11-05 19:10, Carlos M. martinez a =E9crit :
>> Other than the CGN-mib we discussed today in sunset4, I wondered
whether
>> is there ongoing work on this topic.
>
> What do you mean exactly? Because there is nothing IPv6-specific in
the
> CGN MIB (or NAT MIB), it's all address-family agnostic...
>
> Simon



From arturo.servin@gmail.com  Sat Nov 10 06:35:38 2012
Return-Path: <arturo.servin@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 305F821F8650 for <ietf@ietfa.amsl.com>; Sat, 10 Nov 2012 06:35:38 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4L714Pl9mFzo for <ietf@ietfa.amsl.com>; Sat, 10 Nov 2012 06:35:37 -0800 (PST)
Received: from mail-yh0-f44.google.com (mail-yh0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 9561921F8629 for <ietf@ietf.org>; Sat, 10 Nov 2012 06:35:37 -0800 (PST)
Received: by mail-yh0-f44.google.com with SMTP id 56so1018648yhq.31 for <ietf@ietf.org>; Sat, 10 Nov 2012 06:35:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=xR71Dxzs0+p3Gd1yL+7S6sfINES5tru2K4k90JcBn9U=; b=zXmsYSETVeWqtNUYPqhPeLVqnvr44C04F7oEEUI2nsU8geYwo8OkAPFKlegjULm6kd XYXXJpyIqV3Owr2Ds/lxJdl02bffLakcSoPy23yJM00yHjBESmiYj9m7S7PLZJga90km UL9tZdzYYiaC/7DuYo8i0RkJb+DuAJx/BFaT0UZGasctIgMlw+RRfr5I7gw/K/g6LDCb M0XHAtxacZ0kBee3qLreA8AW6ZFkLtieFMWSxFeI+0cgT/coTVHeHW41rvFiRIWZKUV3 SvXoYNthe2Obz4zLcb4uxu5p50gw7IhI9mRKwvSYso1w6tYWdlOqyF0C90UXBHGT3xdq detA==
Received: by 10.236.121.98 with SMTP id q62mr15136556yhh.8.1352558137040; Sat, 10 Nov 2012 06:35:37 -0800 (PST)
Received: from [192.168.1.133] (r186-48-242-159.dialup.adsl.anteldata.net.uy. [186.48.242.159]) by mx.google.com with ESMTPS id e7sm1325402ang.8.2012.11.10.06.35.34 (version=SSLv3 cipher=OTHER); Sat, 10 Nov 2012 06:35:35 -0800 (PST)
Message-ID: <509E6634.2010203@gmail.com>
Date: Sat, 10 Nov 2012 12:35:32 -0200
From: Arturo Servin <arturo.servin@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: Randy Bush <randy@psg.com>
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
References: <CADnDZ8-fjxfgJys8sE10DdZ08tB8HdaTQXbPj2d7-OuQOGi9Pg@mail.gmail.com> <CADnDZ8_v3M1fNtkOV4rU1F-iaMC+2qvKhR353vwESiQsfh70MQ@mail.gmail.com> <6.2.5.6.2.20121109074113.0b2000f8@resistor.net> <8C48B86A895913448548E6D15DA7553B19E215@xmb-rcd-x09.cisco.com> <509D910D.7060503@gmail.com> <509DA4E7.1090504@gmail.com> <509DA723.7030703@gmail.com> <m2390hq3ge.wl%randy@psg.com>
In-Reply-To: <m2390hq3ge.wl%randy@psg.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 10 Nov 2012 14:35:38 -0000

Randy,

    It's not bitching, it self criticism. I think that the IETF thinks
that it is very open but in reality it could do better.

    And about your suggestion, it is my todo list.

Regards,
as

On 10/11/2012 06:14, Randy Bush wrote:
> arturo,
>
> many of us have the message that you think the ietf should meet in alyc.
> so qui bitching, find a locale/hotel, a host, and the connectivity in
> somewhere not too hard to reach (i.e. not a puddle-jumper for the last
> hour).  then propose it for one or more of dates which are open.
>
> i'll leave my biases out of it, but there are many lovely cities in
> south america which i would love to see again.  of course, all i will
> see is the inside of a frelling hotel, but that's life i guess.
>
> randy


From randy@psg.com  Sat Nov 10 06:54:58 2012
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 363F621F84E0 for <ietf@ietfa.amsl.com>; Sat, 10 Nov 2012 06:54:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.543
X-Spam-Level: 
X-Spam-Status: No, score=-2.543 tagged_above=-999 required=5 tests=[AWL=0.056,  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 CubxSsoo2Jsm for <ietf@ietfa.amsl.com>; Sat, 10 Nov 2012 06:54:57 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id D7F2321F84C4 for <ietf@ietf.org>; Sat, 10 Nov 2012 06:54:57 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from <randy@psg.com>) id 1TXCSW-000Piy-3s; Sat, 10 Nov 2012 14:54:56 +0000
Date: Sat, 10 Nov 2012 23:54:52 +0900
Message-ID: <m21ug1pkxv.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Arturo Servin <arturo.servin@gmail.com>
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
In-Reply-To: <509E6634.2010203@gmail.com>
References: <CADnDZ8-fjxfgJys8sE10DdZ08tB8HdaTQXbPj2d7-OuQOGi9Pg@mail.gmail.com> <CADnDZ8_v3M1fNtkOV4rU1F-iaMC+2qvKhR353vwESiQsfh70MQ@mail.gmail.com> <6.2.5.6.2.20121109074113.0b2000f8@resistor.net> <8C48B86A895913448548E6D15DA7553B19E215@xmb-rcd-x09.cisco.com> <509D910D.7060503@gmail.com> <509DA4E7.1090504@gmail.com> <509DA723.7030703@gmail.com> <m2390hq3ge.wl%randy@psg.com> <509E6634.2010203@gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 10 Nov 2012 14:54:58 -0000

> about your suggestion, it is my todo list.

if i can be of help, holler

randy

From bob.hinden@gmail.com  Sat Nov 10 07:26:36 2012
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A0EC121F8669 for <ietf@ietfa.amsl.com>; Sat, 10 Nov 2012 07:26:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, 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 dD4k+GbSjSGl for <ietf@ietfa.amsl.com>; Sat, 10 Nov 2012 07:26:36 -0800 (PST)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id E651F21F8660 for <ietf@ietf.org>; Sat, 10 Nov 2012 07:26:35 -0800 (PST)
Received: by mail-pb0-f44.google.com with SMTP id uo1so109655pbc.31 for <ietf@ietf.org>; Sat, 10 Nov 2012 07:26:35 -0800 (PST)
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 :content-transfer-encoding:message-id:references:to:x-mailer; bh=WIZXLNlZVl86pSyUp1U+xyMdkEKWqQBYaCGNi0b+NlI=; b=ZKXDgEI+zDaIN9tCgh5ENnpZAG8oYdzZEkozY+kIFekdr58BO3ptBqzC5qzPToFI/u 0xvBq6XDZIw5l/wk0kklK9/kBliWgdb+2IycI8PyVjuAqVeIP7p5SoWYOvyLz9gZUWSB YWRPPikQtSaYDd5EPesQ/6aAPr23Ri2CeK7680X0XHmwad7JbEhdgIMpTiJy7Q8CA6nH KonCe/1J3GeBbkPHTSOvLe466tVRFX6Fy0y42rH93HRWpbzzUfIRx2An8AANN+W1s63m mbLSm8PjlkEMHCCjR1Ht0kTHPS0HslxAcemUcd5fa6foZmfHTsMN2/CwhqDMGp9Hz2n+ tI0A==
Received: by 10.68.235.2 with SMTP id ui2mr36524637pbc.163.1352561195750; Sat, 10 Nov 2012 07:26:35 -0800 (PST)
Received: from [192.168.1.240] (dsl-29-242.cofs.net. [68.142.29.242]) by mx.google.com with ESMTPS id hc4sm1096419pbc.30.2012.11.10.07.26.32 (version=SSLv3 cipher=OTHER); Sat, 10 Nov 2012 07:26:34 -0800 (PST)
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=us-ascii
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <m21ug1pkxv.wl%randy@psg.com>
Date: Sat, 10 Nov 2012 10:26:32 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <FEE09A38-287F-4C37-93CB-1F839F1AC7E1@gmail.com>
References: <CADnDZ8-fjxfgJys8sE10DdZ08tB8HdaTQXbPj2d7-OuQOGi9Pg@mail.gmail.com> <CADnDZ8_v3M1fNtkOV4rU1F-iaMC+2qvKhR353vwESiQsfh70MQ@mail.gmail.com> <6.2.5.6.2.20121109074113.0b2000f8@resistor.net> <8C48B86A895913448548E6D15DA7553B19E215@xmb-rcd-x09.cisco.com> <509D910D.7060503@gmail.com> <509DA4E7.1090504@gmail.com> <509DA723.7030703@gmail.com> <m2390hq3ge.wl%randy@psg.com> <509E6634.2010203@gmail.com> <m21ug1pkxv.wl%randy@psg.com>
To: Randy Bush <randy@psg.com>
X-Mailer: Apple Mail (2.1283)
Cc: Arturo Servin <arturo.servin@gmail.com>, Bob Hinden <bob.hinden@gmail.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 10 Nov 2012 15:26:36 -0000

The IAOC site team is planning to visit several potential venues early =
next year in Latin America / South America.  We are open to suggestions =
for potential venues to evaluate.

Thanks,
Bob

On Nov 10, 2012, at 9:54 AM, Randy Bush wrote:

>> about your suggestion, it is my todo list.
>=20
> if i can be of help, holler
>=20
> randy


From melinda.shore@gmail.com  Sat Nov 10 08:51:49 2012
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C5B421F86F4 for <ietf@ietfa.amsl.com>; Sat, 10 Nov 2012 08:51:49 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cDekaj5LZZAs for <ietf@ietfa.amsl.com>; Sat, 10 Nov 2012 08:51:48 -0800 (PST)
Received: from mail-gh0-f172.google.com (mail-gh0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id 9431C21F86EB for <ietf@ietf.org>; Sat, 10 Nov 2012 08:51:48 -0800 (PST)
Received: by mail-gh0-f172.google.com with SMTP id g10so1049741ghb.31 for <ietf@ietf.org>; Sat, 10 Nov 2012 08:51:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=k2yvBUIzhOX3WXF2xsOXTFd6SyrPf5J4CKiMwlQQzuA=; b=MctXm9Q/dlSNOlUYGX0SoEiLoq8nqEaZ7PeZVXuMGrPi48WgleiFGuVZIjJUmTvj63 E/g5MjQX5J3DX6oj+1dR+0U/I/vIWCzosNDBcb62zswUy9aQujk9Q1yxYeHIVKVmCPYl A2Cyb+tgLuHEVV4C5pLBbgh6opgwR8gR4jTVfMH9jR3TPEOrMnT4h6AtEIozVRufbvGG kFidRfk2Q0EaNC5xUbW9VapyU0IYZhzdW/pKvPPnD01DV5zOZhTjDyUYF6R1Izaipb8V WdgrgIj5Rwpm7LIybUHUbvYoI9pR8kgkH4QkU4eVvfUMYZ0jemt0NJwc4lSJGmAu1xrQ ixlA==
Received: by 10.236.131.138 with SMTP id m10mr15250301yhi.101.1352566308108; Sat, 10 Nov 2012 08:51:48 -0800 (PST)
Received: from [107.17.123.237] (dhcp107-17-123-237.hil-atlahhh.atl.wayport.net. [107.17.123.237]) by mx.google.com with ESMTPS id s21sm1795496yhb.5.2012.11.10.08.51.47 (version=SSLv3 cipher=OTHER); Sat, 10 Nov 2012 08:51:47 -0800 (PST)
Message-ID: <509E8622.8050803@gmail.com>
Date: Sat, 10 Nov 2012 07:51:46 -0900
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
References: <CADnDZ8-fjxfgJys8sE10DdZ08tB8HdaTQXbPj2d7-OuQOGi9Pg@mail.gmail.com> <CADnDZ8_v3M1fNtkOV4rU1F-iaMC+2qvKhR353vwESiQsfh70MQ@mail.gmail.com> <6.2.5.6.2.20121109074113.0b2000f8@resistor.net> <8C48B86A895913448548E6D15DA7553B19E215@xmb-rcd-x09.cisco.com> <509D910D.7060503@gmail.com> <509DA4E7.1090504@gmail.com> <509DA723.7030703@gmail.com> <m2390hq3ge.wl%randy@psg.com> <509E6634.2010203@gmail.com>
In-Reply-To: <509E6634.2010203@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 10 Nov 2012 16:51:49 -0000

On 11/10/2012 5:35 AM, Arturo Servin wrote:
>     It's not bitching, it self criticism. I think that the IETF thinks
> that it is very open but in reality it could do better.

I'm not sure the IETF can "think" anything, but openness is
an institutional value and goal, and we're sometimes more
successful and sometimes less.  That said, I find it a little
difficult to believe that meeting location is a particularly
significant contributor to meeting openness objectives.  I'd
agree that face-to-face meetings have become more important
to IETF process than they probably should be, but I think it's
still probably the case that you can be a significant
contributor without actually attending a meeting.

I think that we haven't done a sufficiently good job of
acculturating newer participants and that can probably make
the organization look more opaque and closed than it actually
is.  Most (but not all) working groups don't have enough help
with document review, and I think that's probably the fast
path to agency within the IETF.  Being a body in a chair at a
meeting is not.

Melinda


From mary.ietf.barnes@gmail.com  Sat Nov 10 08:57:22 2012
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3FFFE21F86EB for <ietf@ietfa.amsl.com>; Sat, 10 Nov 2012 08:57:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.424
X-Spam-Level: 
X-Spam-Status: No, score=-103.424 tagged_above=-999 required=5 tests=[AWL=0.174, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, 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 bsNnC37uGbLB for <ietf@ietfa.amsl.com>; Sat, 10 Nov 2012 08:57:21 -0800 (PST)
Received: from mail-la0-f44.google.com (mail-la0-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id 7A15921F87CC for <ietf@ietf.org>; Sat, 10 Nov 2012 08:57:21 -0800 (PST)
Received: by mail-la0-f44.google.com with SMTP id b11so4025260lam.31 for <ietf@ietf.org>; Sat, 10 Nov 2012 08:57:20 -0800 (PST)
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 :cc:content-type; bh=mqHTqgyo9Oh8Z/1pfeG6tpgnU2YTFoVFphdHtIWxgBQ=; b=fXh8tncrvLX1dpxlITfSbVNfe3EzuZCnm+4leohZtGYVG6z/CpYAXmWp+ZnVF/JCI7 lGE/72mlW26DnuX/yF1Hc5sROHTuM1arQYxbzAsJ3QB0ZV9Rl8gQVhqb6j9wIyvlilC4 sIC69r51+I1tVaNg3sH676mTpVira9Z0rQ+Y8DnbI14WHD00bl1psQIRxtR1Jdrn2a7A MosZIcYNzNqON+MMvyXnzc8YCb3aYXqyXXDOmxNJd9R5fmAOFOZLjwE3VvfMiUvWHdfE hu0lUsjy5ogFRPNo3/ZVoNm4tLjJOBvMGUz2dfZjg0VmCPJqoFB1b0GAKfALav0DEdbo klHQ==
MIME-Version: 1.0
Received: by 10.112.38.163 with SMTP id h3mr5845651lbk.134.1352566640473; Sat, 10 Nov 2012 08:57:20 -0800 (PST)
Received: by 10.114.69.139 with HTTP; Sat, 10 Nov 2012 08:57:20 -0800 (PST)
In-Reply-To: <509E8622.8050803@gmail.com>
References: <CADnDZ8-fjxfgJys8sE10DdZ08tB8HdaTQXbPj2d7-OuQOGi9Pg@mail.gmail.com> <CADnDZ8_v3M1fNtkOV4rU1F-iaMC+2qvKhR353vwESiQsfh70MQ@mail.gmail.com> <6.2.5.6.2.20121109074113.0b2000f8@resistor.net> <8C48B86A895913448548E6D15DA7553B19E215@xmb-rcd-x09.cisco.com> <509D910D.7060503@gmail.com> <509DA4E7.1090504@gmail.com> <509DA723.7030703@gmail.com> <m2390hq3ge.wl%randy@psg.com> <509E6634.2010203@gmail.com> <509E8622.8050803@gmail.com>
Date: Sat, 10 Nov 2012 10:57:20 -0600
Message-ID: <CAHBDyN6VEBkqNHYFK7A0P8S8wrAwNYaAeVnnxkiJ=79iVQR4=Q@mail.gmail.com>
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: Melinda Shore <melinda.shore@gmail.com>
Content-Type: multipart/alternative; boundary=e0cb4efe2a7a23f50d04ce26f6e0
Cc: IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 10 Nov 2012 16:57:22 -0000

--e0cb4efe2a7a23f50d04ce26f6e0
Content-Type: text/plain; charset=ISO-8859-1

On Sat, Nov 10, 2012 at 10:51 AM, Melinda Shore <melinda.shore@gmail.com>wrote:

>
>
> I think that we haven't done a sufficiently good job of
> acculturating newer participants and that can probably make
> the organization look more opaque and closed than it actually
> is.  Most (but not all) working groups don't have enough help
> with document review, and I think that's probably the fast
> path to agency within the IETF.  Being a body in a chair at a
> meeting is not.
>

[MB] Exactly!  That's what I did when I first started participating in
IETF.  I would review documents and comment on the mailing.   I also would
volunteer to take meeting minutes as that really does force you to pay
attention to the meeting and not spend the meeting reading email or playing
solitaire.  Or, volunteer to at least follow the jabber room.  Those are
all extremely important for working group effectiveness.  [/MB]

>
> Melinda
>
>

--e0cb4efe2a7a23f50d04ce26f6e0
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Sat, Nov 1=
0, 2012 at 10:51 AM, Melinda Shore <span dir=3D"ltr">&lt;<a href=3D"mailto:=
melinda.shore@gmail.com" target=3D"_blank">melinda.shore@gmail.com</a>&gt;<=
/span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><br>
<br>
I think that we haven&#39;t done a sufficiently good job of<br>
acculturating newer participants and that can probably make<br>
the organization look more opaque and closed than it actually<br>
is. =A0Most (but not all) working groups don&#39;t have enough help<br>
with document review, and I think that&#39;s probably the fast<br>
path to agency within the IETF. =A0Being a body in a chair at a<br>
meeting is not.<br></blockquote><div>=A0</div><div>[MB] Exactly! =A0That&#3=
9;s what I did when I first started participating in IETF. =A0I would revie=
w documents and comment on the mailing. =A0 I also would volunteer to take =
meeting minutes as that really does force you to pay attention to the meeti=
ng and not spend the meeting reading email or playing solitaire. =A0Or, vol=
unteer to at least follow the jabber room. =A0Those are all extremely impor=
tant for working group effectiveness. =A0[/MB]=A0</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Melinda<br>
<br>
</font></span></blockquote></div><br></div>

--e0cb4efe2a7a23f50d04ce26f6e0--

From arturo.servin@gmail.com  Sat Nov 10 11:31:10 2012
Return-Path: <arturo.servin@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 42BCA21F8511 for <ietf@ietfa.amsl.com>; Sat, 10 Nov 2012 11:31:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.299
X-Spam-Level: 
X-Spam-Status: No, score=-3.299 tagged_above=-999 required=5 tests=[AWL=0.300,  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 OCUwo4xO5BMY for <ietf@ietfa.amsl.com>; Sat, 10 Nov 2012 11:31:09 -0800 (PST)
Received: from mail-gh0-f172.google.com (mail-gh0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id 4745221F850A for <ietf@ietf.org>; Sat, 10 Nov 2012 11:31:09 -0800 (PST)
Received: by mail-gh0-f172.google.com with SMTP id g10so1062953ghb.31 for <ietf@ietf.org>; Sat, 10 Nov 2012 11:31:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=bBCW4DHX0STfbGQatE0TJg9O7JMdBLIb5qX68tSqUwc=; b=jiWqkt2U+RgYKZd3OqItCESrkbxqyIFvZ4Wkj1FqDAWX7CWztIscA70sSXkpJVp8Wt FSaJha6/nehPEfy8nLFqUUXZgWXXb/zJnE6r+Fv08nD7MisdlGBSJM4zHG+pN2Xa0YR3 tgTjgOkbK/yAVEAPh6oWuIiwhhmSbokxaHsFjqY15lEg7oDJmPTAa4iXreF3tYg3eiLl 4k69bNr74kVE8notkCbmZMHw3frDxb8YH3TnrwAiy+DrtuIjl7c4COyvIrVlclrPFOVN 1Dzncj6CQ0u6qsO9+W7Iu/iZ01VHBjgv/ufwztCmyDLMZ4o7jzuZVA/NHYa2xMCoO0F2 nmzQ==
Received: by 10.236.141.207 with SMTP id g55mr15547758yhj.71.1352575868854; Sat, 10 Nov 2012 11:31:08 -0800 (PST)
Received: from ?IPv6:2800:af:ba30:f29f:cd0f:6a71:8a65:bfd3? ([2800:af:ba30:f29f:cd0f:6a71:8a65:bfd3]) by mx.google.com with ESMTPS id t46sm2124870yhi.3.2012.11.10.11.31.06 (version=SSLv3 cipher=OTHER); Sat, 10 Nov 2012 11:31:07 -0800 (PST)
Message-ID: <509EAB77.7020900@gmail.com>
Date: Sat, 10 Nov 2012 17:31:03 -0200
From: Arturo Servin <arturo.servin@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
References: <CADnDZ8-fjxfgJys8sE10DdZ08tB8HdaTQXbPj2d7-OuQOGi9Pg@mail.gmail.com> <CADnDZ8_v3M1fNtkOV4rU1F-iaMC+2qvKhR353vwESiQsfh70MQ@mail.gmail.com> <6.2.5.6.2.20121109074113.0b2000f8@resistor.net> <8C48B86A895913448548E6D15DA7553B19E215@xmb-rcd-x09.cisco.com> <509D910D.7060503@gmail.com> <509DA4E7.1090504@gmail.com> <509DA723.7030703@gmail.com> <m2390hq3ge.wl%randy@psg.com> <509E6634.2010203@gmail.com> <m21ug1pkxv.wl%randy@psg.com> <FEE09A38-287F-4C37-93CB-1F839F1AC7E1@gmail.com>
In-Reply-To: <FEE09A38-287F-4C37-93CB-1F839F1AC7E1@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 10 Nov 2012 19:31:10 -0000

Bob,

	Nice to hear that.

	I will send off-list to the IAOC some venues, possible hosts and people
that could help in finding a good place.

Regards
as

On 10/11/2012 13:26, Bob Hinden wrote:
> The IAOC site team is planning to visit several potential venues early next year in Latin America / South America.  We are open to suggestions for potential venues to evaluate.
> 
> Thanks,
> Bob
> 
> On Nov 10, 2012, at 9:54 AM, Randy Bush wrote:
> 
>>> about your suggestion, it is my todo list.
>>
>> if i can be of help, holler
>>
>> randy

From bob.hinden@gmail.com  Sat Nov 10 11:35:47 2012
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C5F421F84F2 for <ietf@ietfa.amsl.com>; Sat, 10 Nov 2012 11:35:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.203
X-Spam-Level: 
X-Spam-Status: No, score=-102.203 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_LOW=-1,  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 I8IdF7xyzr0P for <ietf@ietfa.amsl.com>; Sat, 10 Nov 2012 11:35:46 -0800 (PST)
Received: from mail-ob0-f172.google.com (mail-ob0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id 8B5A321F84F0 for <ietf@ietf.org>; Sat, 10 Nov 2012 11:35:46 -0800 (PST)
Received: by mail-ob0-f172.google.com with SMTP id wo10so1728764obc.31 for <ietf@ietf.org>; Sat, 10 Nov 2012 11:35:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:in-reply-to:mime-version:content-transfer-encoding :content-type:message-id:cc:x-mailer:from:subject:date:to; bh=ieNSh00OHvW3r+pZrKesYUPykqQl9WYBirLSCcVi44k=; b=aZSuSlz8+q+f1ASfv/0rI/9IDGx25hL7FXmewhcB1nIJzJJ6nIDPHxpEZRWDv7UI3O C1vKmrudkGaKCzgAgKvG75plPICyz3XflBZf6XfpFfg64mHDzMva/96KEMuQkza6JJuQ yEXD8b7bT/W62cCRFwFfqzLPSlqifjMe07T0JBhI8d+MYqW+SP+AVWd/rzzyPjvy6q10 95KSv6IOIS70wDxGiTtNWRhKJRs+pJevO3I2jEzzeEUuZthiGlkGRL4OltMWyxSNpKsX JjrKOaJ+W5cVp95oyq2dytt1tTHdpYTU7b7LJjZy0DxoBHcpbhPIDm+Zrch++suYFfzd nVJw==
Received: by 10.60.11.68 with SMTP id o4mr8435816oeb.89.1352576146108; Sat, 10 Nov 2012 11:35:46 -0800 (PST)
Received: from [10.198.159.237] (mobile-166-147-071-158.mycingular.net. [166.147.71.158]) by mx.google.com with ESMTPS id g17sm1707331oei.10.2012.11.10.11.35.43 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 10 Nov 2012 11:35:45 -0800 (PST)
References: <CADnDZ8-fjxfgJys8sE10DdZ08tB8HdaTQXbPj2d7-OuQOGi9Pg@mail.gmail.com> <CADnDZ8_v3M1fNtkOV4rU1F-iaMC+2qvKhR353vwESiQsfh70MQ@mail.gmail.com> <6.2.5.6.2.20121109074113.0b2000f8@resistor.net> <8C48B86A895913448548E6D15DA7553B19E215@xmb-rcd-x09.cisco.com> <509D910D.7060503@gmail.com> <509DA4E7.1090504@gmail.com> <509DA723.7030703@gmail.com> <m2390hq3ge.wl%randy@psg.com> <509E6634.2010203@gmail.com> <m21ug1pkxv.wl%randy@psg.com> <FEE09A38-287F-4C37-93CB-1F839F1AC7E1@gmail.com> <509EAB77.7020900@gmail.com>
In-Reply-To: <509EAB77.7020900@gmail.com>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <D372CE6F-3216-48B0-A726-C91B2B764E46@gmail.com>
X-Mailer: iPhone Mail (10A523)
From: Bob Hinden <bob.hinden@gmail.com>
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
Date: Sat, 10 Nov 2012 13:35:35 -0600
To: Arturo Servin <arturo.servin@gmail.com>
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 10 Nov 2012 19:35:47 -0000

Arturo,

On Nov 10, 2012, at 13:31, Arturo Servin <arturo.servin@gmail.com> wrote:

> Bob,
>=20
>    Nice to hear that.
>=20
>    I will send off-list to the IAOC some venues, possible hosts and people=

> that could help in finding a good place.=20

Thanks,
Bob


>=20
> Regards
> as
>=20
> On 10/11/2012 13:26, Bob Hinden wrote:
>> The IAOC site team is planning to visit several potential venues early ne=
xt year in Latin America / South America.  We are open to suggestions for po=
tential venues to evaluate.
>>=20
>> Thanks,
>> Bob
>>=20
>> On Nov 10, 2012, at 9:54 AM, Randy Bush wrote:
>>=20
>>>> about your suggestion, it is my todo list.
>>>=20
>>> if i can be of help, holler
>>>=20
>>> randy

From arturo.servin@gmail.com  Sat Nov 10 11:38:22 2012
Return-Path: <arturo.servin@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC8CA21F8433 for <ietf@ietfa.amsl.com>; Sat, 10 Nov 2012 11:38:21 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yq4slDhB5YxG for <ietf@ietfa.amsl.com>; Sat, 10 Nov 2012 11:38:21 -0800 (PST)
Received: from mail-gg0-f172.google.com (mail-gg0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 41D0121F84F2 for <ietf@ietf.org>; Sat, 10 Nov 2012 11:38:21 -0800 (PST)
Received: by mail-gg0-f172.google.com with SMTP id i4so1042200ggn.31 for <ietf@ietf.org>; Sat, 10 Nov 2012 11:38:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=VkrpzbYykMvggAgPiJR1ffeVchElIhbVCwAQ2et/PJI=; b=naeAjfJ0RSasoLxM6VqQrCLmtCpNR4E7dL6O1cBq+3Frd5KR65m9BNX7CRQF86kDbc Ik0qDkX3KdfP9EeS/l8m7nWIt/cYBbtqBML1cJTbYBCy+76G1UCBr7DsKhzd/6e35q9O op8eUbo9ftgkWO65YRymJRk2Q3fTQ/PE4YOtICnEUYvqQTm/ddebFW9HSs+jZd0HgMzN 0MVPB6HP2KwYeENZ9LTT7E5hwYULB3bsQyremVRR9FqiWw2sl1YBXFJOYjuDm3wN6/Cj CGqfLRNl4ArVm80oxFr08bhTPJdUqasWzUvVQ9gfm2A7nzUyFFKDM2knJOGL7WSA++hr hTfw==
Received: by 10.236.85.78 with SMTP id t54mr15237019yhe.48.1352576300826; Sat, 10 Nov 2012 11:38:20 -0800 (PST)
Received: from [192.168.1.133] (r186-48-242-159.dialup.adsl.anteldata.net.uy. [186.48.242.159]) by mx.google.com with ESMTPS id d66sm2147242yhe.1.2012.11.10.11.38.19 (version=SSLv3 cipher=OTHER); Sat, 10 Nov 2012 11:38:20 -0800 (PST)
Message-ID: <509EAD29.6040404@gmail.com>
Date: Sat, 10 Nov 2012 17:38:17 -0200
From: Arturo Servin <arturo.servin@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
References: <CADnDZ8-fjxfgJys8sE10DdZ08tB8HdaTQXbPj2d7-OuQOGi9Pg@mail.gmail.com> <CADnDZ8_v3M1fNtkOV4rU1F-iaMC+2qvKhR353vwESiQsfh70MQ@mail.gmail.com> <6.2.5.6.2.20121109074113.0b2000f8@resistor.net> <8C48B86A895913448548E6D15DA7553B19E215@xmb-rcd-x09.cisco.com> <509D910D.7060503@gmail.com> <509DA4E7.1090504@gmail.com> <509DA723.7030703@gmail.com> <m2390hq3ge.wl%randy@psg.com> <509E6634.2010203@gmail.com> <509E8622.8050803@gmail.com>
In-Reply-To: <509E8622.8050803@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 10 Nov 2012 19:38:22 -0000

Melinda,

	When I said "the ietf thinks" I reefer about the consciousness of the
IETF as a group.

	I disagree with you about meeting location as a factor "openness". I
think that it is an important one to consider. Language is another, but
I am not going there now.

Regards,
as


	

On 10/11/2012 14:51, Melinda Shore wrote:
> On 11/10/2012 5:35 AM, Arturo Servin wrote:
>>     It's not bitching, it self criticism. I think that the IETF thinks
>> that it is very open but in reality it could do better.
> 
> I'm not sure the IETF can "think" anything, but openness is
> an institutional value and goal, and we're sometimes more
> successful and sometimes less.  That said, I find it a little
> difficult to believe that meeting location is a particularly
> significant contributor to meeting openness objectives.  I'd
> agree that face-to-face meetings have become more important
> to IETF process than they probably should be, but I think it's
> still probably the case that you can be a significant
> contributor without actually attending a meeting.
> 
> I think that we haven't done a sufficiently good job of
> acculturating newer participants and that can probably make
> the organization look more opaque and closed than it actually
> is.  Most (but not all) working groups don't have enough help
> with document review, and I think that's probably the fast
> path to agency within the IETF.  Being a body in a chair at a
> meeting is not.
> 
> Melinda
> 

From ajs@anvilwalrusden.com  Sat Nov 10 17:28:15 2012
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A5FCE21F8468 for <ietf@ietfa.amsl.com>; Sat, 10 Nov 2012 17:28:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.847
X-Spam-Level: 
X-Spam-Status: No, score=-0.847 tagged_above=-999 required=5 tests=[AWL=-0.007, BAYES_00=-2.599, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311]
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 Aq-44RmcjtXM for <ietf@ietfa.amsl.com>; Sat, 10 Nov 2012 17:28:15 -0800 (PST)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id 3DFC721F843D for <ietf@ietf.org>; Sat, 10 Nov 2012 17:28:15 -0800 (PST)
Received: from mx1.yitter.info (69-196-144-227.dsl.teksavvy.com [69.196.144.227]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id C51598A031 for <ietf@ietf.org>; Sun, 11 Nov 2012 01:28:12 +0000 (UTC)
Date: Sat, 10 Nov 2012 20:28:12 -0500
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
Message-ID: <20121111012811.GB81504@mx1.yitter.info>
References: <CADnDZ8-fjxfgJys8sE10DdZ08tB8HdaTQXbPj2d7-OuQOGi9Pg@mail.gmail.com> <CADnDZ8_v3M1fNtkOV4rU1F-iaMC+2qvKhR353vwESiQsfh70MQ@mail.gmail.com> <6.2.5.6.2.20121109074113.0b2000f8@resistor.net> <8C48B86A895913448548E6D15DA7553B19E215@xmb-rcd-x09.cisco.com> <509D910D.7060503@gmail.com> <509DA4E7.1090504@gmail.com> <509DA723.7030703@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <509DA723.7030703@gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 11 Nov 2012 01:28:15 -0000

On Fri, Nov 09, 2012 at 08:00:19PM -0500, Arturo Servin wrote:
>     Hard times may come, some people will ask why the Internet standards
> are just developed in some places and will challenge us.

And here I thought that the standards were developed on the list.

(For the record, I am not opposed at all to holding a meeting in Latin
America -- I'm personally in favour of it.  But we also don't hold
meetings in India or Myanmar, and for much the same reason: we have a
tiny minority of participants from those places, and given the funding
model the IETF can't afford to hold full-on meetings as a matter of
outreach.  There may be ways to fix that, and I understand the IAOC is
investigating options.  Note that the IETF is always looking for
sponsors for meetings!)

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From d3e3e3@gmail.com  Sat Nov 10 17:46:28 2012
Return-Path: <d3e3e3@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A27D21F8840 for <ietf@ietfa.amsl.com>; Sat, 10 Nov 2012 17:46:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, 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 22FsbK8p8AN8 for <ietf@ietfa.amsl.com>; Sat, 10 Nov 2012 17:46:27 -0800 (PST)
Received: from mail-ia0-f172.google.com (mail-ia0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id B609F21F86DC for <ietf@ietf.org>; Sat, 10 Nov 2012 17:46:27 -0800 (PST)
Received: by mail-ia0-f172.google.com with SMTP id x24so4047486iak.31 for <ietf@ietf.org>; Sat, 10 Nov 2012 17:46:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=cujN8s75x/9s4Lwz+v9vqayuVVwq783NgpRRO8uU4Ek=; b=khpQKkZQF7WLLaAyHp0GsWOtYar6X4tfW5tsoEi/GUq+spllL8Thh12QUzvgWOVem8 WWLBySdIZx14OvL+HezK78UBhiUf7e+kQ2paVDhw9Pk2zqJnhVlb9XLbi9qSY7oOmYAJ xHG2syMxBgTCEKWHb0khwilcsLIyTYWevG8FnUa+H6alrMsG5Lgvlt8x/qM7Ujn/zE57 kKu0mJ8/k5ybK0O6eNU+acsTdDLgO6TSYWtSY+nprw1I4FFVky9+StHxtpX8MHiUo9AT oMO84ifwbbcJEvqkaCmOCL8JQcfTNetW212jsxFOVitIRIDkAlhKf8y9Frhw/mVW8JyW +cnw==
Received: by 10.50.40.229 with SMTP id a5mr4528173igl.59.1352598387391; Sat, 10 Nov 2012 17:46:27 -0800 (PST)
MIME-Version: 1.0
Received: by 10.64.176.134 with HTTP; Sat, 10 Nov 2012 17:46:04 -0800 (PST)
In-Reply-To: <CAHBDyN6VEBkqNHYFK7A0P8S8wrAwNYaAeVnnxkiJ=79iVQR4=Q@mail.gmail.com>
References: <CADnDZ8-fjxfgJys8sE10DdZ08tB8HdaTQXbPj2d7-OuQOGi9Pg@mail.gmail.com> <CADnDZ8_v3M1fNtkOV4rU1F-iaMC+2qvKhR353vwESiQsfh70MQ@mail.gmail.com> <6.2.5.6.2.20121109074113.0b2000f8@resistor.net> <8C48B86A895913448548E6D15DA7553B19E215@xmb-rcd-x09.cisco.com> <509D910D.7060503@gmail.com> <509DA4E7.1090504@gmail.com> <509DA723.7030703@gmail.com> <m2390hq3ge.wl%randy@psg.com> <509E6634.2010203@gmail.com> <509E8622.8050803@gmail.com> <CAHBDyN6VEBkqNHYFK7A0P8S8wrAwNYaAeVnnxkiJ=79iVQR4=Q@mail.gmail.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Sat, 10 Nov 2012 20:46:04 -0500
Message-ID: <CAF4+nEEr1fDU0XyUWXFHfZiOFHuVOW5hhc6XEoG1tzo9PFsa_g@mail.gmail.com>
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
To: Mary Barnes <mary.ietf.barnes@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 11 Nov 2012 01:46:28 -0000

Right. See RFC 4144.

Thanks,
Donald
=============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3@gmail.com

On Sat, Nov 10, 2012 at 11:57 AM, Mary Barnes
<mary.ietf.barnes@gmail.com> wrote:
>
>
> On Sat, Nov 10, 2012 at 10:51 AM, Melinda Shore <melinda.shore@gmail.com>
> wrote:
>>
>>
>>
>> I think that we haven't done a sufficiently good job of
>> acculturating newer participants and that can probably make
>> the organization look more opaque and closed than it actually
>> is.  Most (but not all) working groups don't have enough help
>> with document review, and I think that's probably the fast
>> path to agency within the IETF.  Being a body in a chair at a
>> meeting is not.
>
>
> [MB] Exactly!  That's what I did when I first started participating in IETF.
> I would review documents and comment on the mailing.   I also would
> volunteer to take meeting minutes as that really does force you to pay
> attention to the meeting and not spend the meeting reading email or playing
> solitaire.  Or, volunteer to at least follow the jabber room.  Those are all
> extremely important for working group effectiveness.  [/MB]
>>
>>
>> Melinda

From melinda.shore@gmail.com  Sat Nov 10 21:20:12 2012
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 07B7021F88CC for <ietf@ietfa.amsl.com>; Sat, 10 Nov 2012 21:20:12 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y70Vqs-yhHu0 for <ietf@ietfa.amsl.com>; Sat, 10 Nov 2012 21:20:11 -0800 (PST)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id 19DFE21F88CA for <ietf@ietf.org>; Sat, 10 Nov 2012 21:20:11 -0800 (PST)
Received: by mail-pb0-f44.google.com with SMTP id uo1so300495pbc.31 for <ietf@ietf.org>; Sat, 10 Nov 2012 21:20:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=FmsOat8qM/9RetX55b16UIrBpz78aL9E3cusvFQoCXI=; b=y+HX9WUx3GY6tM41AujmDGH/I6Cmc5fcH5RmwC2njbtLjElsAfa64VAqetbVmHrWKq /SmH3l4YpUeXpuMxPpcvzRzMsZZo3yODs8qh0qyEbbRl75Y2rvMFD0lGkousNu5niAGI woMx1h3/KdnbSEYA4CeMv7n6K3ZOcKUTDm26QqHCHIV2nsFKtzVYZR3BNsBiPLbJSzI/ oxx7I7bSmciXy+x31eR3WnVOaZEgpK5a/PTqTxmeJU60gOInwb1qxidAvYx8BLl1Ryjd dKqaaOi0y9z77QdhKRMWzC2gIj6Ri9+lWBkjsTr+dpabQUnH0b0mq2jh8gIrm0WVZjtN jQUw==
Received: by 10.68.243.10 with SMTP id wu10mr47417872pbc.85.1352611210824; Sat, 10 Nov 2012 21:20:10 -0800 (PST)
Received: from [10.252.170.246] ([198.134.90.134]) by mx.google.com with ESMTPS id pv8sm1994161pbc.26.2012.11.10.21.20.09 (version=SSLv3 cipher=OTHER); Sat, 10 Nov 2012 21:20:10 -0800 (PST)
Message-ID: <509F3589.1020203@gmail.com>
Date: Sat, 10 Nov 2012 20:20:09 -0900
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
References: <CADnDZ8-fjxfgJys8sE10DdZ08tB8HdaTQXbPj2d7-OuQOGi9Pg@mail.gmail.com> <CADnDZ8_v3M1fNtkOV4rU1F-iaMC+2qvKhR353vwESiQsfh70MQ@mail.gmail.com> <6.2.5.6.2.20121109074113.0b2000f8@resistor.net> <8C48B86A895913448548E6D15DA7553B19E215@xmb-rcd-x09.cisco.com> <509D910D.7060503@gmail.com> <509DA4E7.1090504@gmail.com> <509DA723.7030703@gmail.com> <m2390hq3ge.wl%randy@psg.com> <509E6634.2010203@gmail.com> <509E8622.8050803@gmail.com> <509EAD29.6040404@gmail.com>
In-Reply-To: <509EAD29.6040404@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 11 Nov 2012 05:20:12 -0000

On 11/10/2012 10:38 AM, Arturo Servin wrote:
> 	When I said "the ietf thinks" I reefer about the consciousness of the
> IETF as a group.

I know, I'm just not really sure it has one.  I think that
there's enormous diversity among the reasons people participate
and what it is they hope to get done.

> 	I disagree with you about meeting location as a factor "openness". I
> think that it is an important one to consider.

I think there's a lot of value in sharing the travel pain, but
I'm not sure that "openness" is one of them.  I'm actually pretty
sure it's not.  If you're not participating because travel is
onerous and you would participate if a meeting were held closer,
what happens when the meeting goes back to being held someplace
inconvenient four months later?  I'm certainly not arguing against
holding meetings in a wider range of places and going to countries/
continents we haven't in the past, but rather I'm concerned about
misplaced emphasis on meetings both as some sort of metric of
accessibility and as the mechanism for getting things done.

The IETF works by progressing documents.  Writing documents, reviewing
documents, editing documents - these things don't require meeting
participation, and indeed I'd suggest that requiring meeting
participation, either by fiat or by implication, would work to
reduce openness, discourage participation from both people working
as individuals and people working for small companies, etc., and
is likely to reduce the diversity of the participant pool while
effectively hiding IETF process by pulling it off mailing lists.  I'd
rather that didn't happen, and that has nothing to do with meeting
location.

Melinda



From brian.e.carpenter@gmail.com  Sun Nov 11 01:09:53 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4777E21F88CC for <ietf@ietfa.amsl.com>; Sun, 11 Nov 2012 01:09:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.126
X-Spam-Level: 
X-Spam-Status: No, score=-101.126 tagged_above=-999 required=5 tests=[AWL=-0.435, BAYES_00=-2.599, GB_AFFORDABLE=1, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, 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 dYFqvPc-OZCK for <ietf@ietfa.amsl.com>; Sun, 11 Nov 2012 01:09:52 -0800 (PST)
Received: from mail-wg0-f44.google.com (mail-wg0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id E563F21F86EC for <ietf@ietf.org>; Sun, 11 Nov 2012 01:09:51 -0800 (PST)
Received: by mail-wg0-f44.google.com with SMTP id dr13so2445557wgb.13 for <ietf@ietf.org>; Sun, 11 Nov 2012 01:09:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=NQv8UGxJPlin2vA14/8F0k2WTEwOmF/pz3d4cOdw16c=; b=LIYM0fHJhkiQJ261pcVkwWngTzoDV5h91m4mu2SUp8zNU4iz3+LVPdksZZv5dWJT4m pw0EnqCtpseB9FhpxFDBH0HzrsC/KaALJSqwPd2zEGl+JPbmH6vq08h7mGo43Zo8yfZV nNt6eWxq6zLxXPBisPB/kwK4E3oJMp+cLGBtPpnwjtr5r23+I98OWNMBDjQHUvY32Gmf 01/PEXcPtrNS4xJvBo6GcjAdaaEIR36xvSm5KrOwVzdUYssP3h1Dp3aooboQ6XU5Z1XO WzT+7HK4Hj7E3Pyo85Wd1i0FajYfOyoB0BeYfwb3IxHO/lBLl0BFHhm1KRnUSd4wXZ4Y 234Q==
Received: by 10.180.107.136 with SMTP id hc8mr10075858wib.9.1352624990835; Sun, 11 Nov 2012 01:09:50 -0800 (PST)
Received: from [192.168.1.65] (host-2-102-218-7.as13285.net. [2.102.218.7]) by mx.google.com with ESMTPS id f1sm9485068wiy.2.2012.11.11.01.09.48 (version=SSLv3 cipher=OTHER); Sun, 11 Nov 2012 01:09:49 -0800 (PST)
Message-ID: <509F6B69.5010909@gmail.com>
Date: Sun, 11 Nov 2012 09:10:01 +0000
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: joel jaeggli <joelja@bogus.com>
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
References: <CADnDZ8-fjxfgJys8sE10DdZ08tB8HdaTQXbPj2d7-OuQOGi9Pg@mail.gmail.com>	<CADnDZ8_v3M1fNtkOV4rU1F-iaMC+2qvKhR353vwESiQsfh70MQ@mail.gmail.com>	<6.2.5.6.2.20121109074113.0b2000f8@resistor.net>	<8C48B86A895913448548E6D15DA7553B19E215@xmb-rcd-x09.cisco.com> <509D910D.7060503@gmail.com> <509DA4E7.1090504@gmail.com> <509DA723.7030703@gmail.com> <509DD3E0.6050408@bogus.com>
In-Reply-To: <509DD3E0.6050408@bogus.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Arturo Servin <arturo.servin@gmail.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 11 Nov 2012 09:09:53 -0000

On 10/11/2012 04:11, joel jaeggli wrote:
> On 11/9/12 8:00 PM, Arturo Servin wrote:
>> Brian,
>>
>>      Your comment just reinforce my perception that the IETF is not
>> interested in being an global organization of standards.

Arturo: I think I didn't express myself well. As others have said since,
IETF standards development *is* global and that is one reason why
participation, and consensus-forming, via email is so important. IETF
standards are global too - despite the historical ASCII bias, there is
nothing regional about what we do. Our efforts at internationalisation
are aimed at maintaining that global approach at the same time as
supporting non-ASCII content. Where we happen to meet has little
to do with that, but a lot to do with cost, convenience, and travel
optimisation.

I have twice, in different places, been part of failed attempts to
host IETF meetings. Those failures were nothing to do with prejudice
against the locations and everything to do with cost, convenience
and travel. That's life.

>>
>>      People is asking how to evolve the IETF, well, one possibility is to
>> start thinking global and to reach more people outside the common
>> venues. It is more expensive, more complex, yes. But in my opinion is
>> worthy if we really want to show that we care about the multistakeholder
>> model that we preach.

> Multistakeholder is a loaded term from other contexts. IETF participants
> whether they attend the meeting or not are self-selected.

Exactly. I applaud the efforts of ISOC, the regional registries, and others
(going right back to the old Landweber meetings many years ago) to
encourage people from all over the world to join the Internet technical
community, but that is quite different from the stakeholder dialogue.

    Brian
> 
> I have some thoughts about interim meetings as an outreach tool in draft
> form and I would appreciate some feeback on those sections.
> 
> http://www.ietf.org/id/draft-jaeggli-interim-observations-03.txt
>>      Hard times may come, some people will ask why the Internet standards
>> are just developed in some places and will challenge us. Frankly, what I
>> see is that we do not care.
> Why shouldn't standards be developed elsewhere (oddly enough, they are)?
> IETF participants have never had a monopoly on either need or good ideas.
> 
>  Regards, as On 09/11/2012 19:50, Brian E Carpenter wrote:
>>> Arturo,
>>>
>>> On 09/11/2012 23:26, Arturo Servin wrote:
>>>>     So basically the IETF is roaming most of the time in  North
>>>> America,
>>>> sometimes in Europe and once in a while in Asia. Is that how the IETF
>>>> thinks about the global development of Internet standards?
>>> No. The criterion has always been to hold meetings where they can be
>>> most effective in making the Internet work better - as far as a
>>> standards organisation can do that. That means choosing places where
>>> a meeting can be run effectively and a reasonably high proportion
>>> of those actively participating can afford to attend. As participation
>>> in the IETF has evolved, so has the geographical part of site selection
>>> policy evolved, as Fred described. For example, the attendance data will
>>> tell you why the policy has recently led to two meetings in China.
>>>
>>> I think you'll find the policy is different for more operational
>>> meetings, which as far as I can tell have been taking place in Asia,
>>> Africa and Latin America for years. Those meetings have different
>>> criteria for their part in making the Internet work better.
>>>
>>>>     No wonder why some countries in Africa and Latin America are
>>>> approaching ITU.
>>> ITU-T does a great deal of its standards-making in Geneva. The meetings
>>> in other areas tend have a different purpose, as do many ISOC
>>> activities.
>>>
>>>>     If the IETF really wants to make a change we need to stop
>>>> thinking that
>>>> North-America/Europe = Global.
>>> I think nobody has thought that for at least 10 years (IETF 54).
>>>
>>>      Brian
>>>> Regards,
>>>> as
>>>>
>>>> On 09/11/2012 16:05, Fred Baker (fred) wrote:
>>>>> On Nov 9, 2012, at 12:28 PM, SM wrote:
>>>>>
>>>>>> At 06:31 09-11-2012, Abdussalam Baryun wrote:
>>>>>>> I am newcomer and not able to attend because most of meeting in
>>>>>>> America instead of Europe.
>>>>>> Most of the money comes from North Americans.  There is some
>>>>>> historical information in RFC 3717.
>>>>> I'd suggest a more thorough analysis.
>>>>>
>>>>> Data from https://www.ietf.org/meeting/upcoming.html and
>>>>> https://www.ietf.org/meeting/past.html. Take a look at the attached
>>>>> spreadsheet.
>>>>>
>>>>> IETF demographics and meeting location policy have changed over time.
>>>>>
>>>>> Originally, in 1986, not only was the IETF entirely American, it was
>>>>> entirely US Government, and nobody else was invited. That changed
>>>>> pretty
>>>>> quickly, but the community attending remained predominantly US for
>>>>> some
>>>>> time. So meetings before 1993 all occurred in North America, and if
>>>>> truth be told, the reason that the meeting in August 1990 was outside
>>>>> the US was that it had been intended to be in Seattle, the host had a
>>>>> problem, and UBC came to the rescue.
>>>>>
>>>>> Starting in 1993, we noted that the demographics had changed; about
>>>>> one
>>>>> in six IETF participants came from Europe. So, we tried to place one
>>>>> meeting in six in Europe. We had a small group attending from
>>>>> Australia,
>>>>> and in 2000 had a meeting there in recognition of the fact. But by
>>>>> that
>>>>> time, we were starting to have a more significant attendance from
>>>>> Asia,
>>>>> notably Japan. So we changed policy to trying to position three
>>>>> meetings
>>>>> in six in North America, two in Europe, and one in Asia+Australia. And
>>>>> starting (IIRC) in 2005, we simplified that policy to having one
>>>>> meeting
>>>>> each year in Asia, Europe, and North America.
>>>>>
>>>>> Regarding that last policy, we have unfortunately had some
>>>>> problems; one
>>>>> meeting that we intended to have in Asia recently fell through, and we
>>>>> had to move it somewhere, and in another recent case the Asian
>>>>> venues we
>>>>> were looking at essentially priced themselves out of the market. Our
>>>>> Asian friends told us that a meeting in Vancouver was an acceptable
>>>>> compromise; getting a visa wasn't as hard for them as a US visa,
>>>>> and it
>>>>> was not too hard to get to. So we have had at least two meetings in
>>>>> Vancouver that we fully intended to have in Asia.
>>>>>
>>>>> Since 2004, we have in fact had about 1/3 of our meetings in
>>>>> Europe. If
>>>>> anyone has been shortchanged, it has been our Asian friends. "Where
>>>>> the
>>>>> money came from" was an issue in the 1990's - we had to assume that a
>>>>> meeting outside the US would be financially short due to US
>>>>> participants
>>>>> not attending; in 2000, the meeting in San Diego had 2810 people
>>>>> and the
>>>>> meeting in Pittsburg 2344, but the meeting in Adelaide had 1431. By
>>>>> 2004, distribution had become roughly even - meetings that year had
>>>>> right around 1300 attendees regardless of location. The issues are now
>>>>> related to success in finding affordable venues.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
> 
> 

From vinayakh@gmail.com  Sun Nov 11 02:22:51 2012
Return-Path: <vinayakh@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6143321F8927 for <ietf@ietfa.amsl.com>; Sun, 11 Nov 2012 02:22:51 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id phrTvKTZlwwn for <ietf@ietfa.amsl.com>; Sun, 11 Nov 2012 02:22:50 -0800 (PST)
Received: from mail-ee0-f44.google.com (mail-ee0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id 443C721F8926 for <ietf@ietf.org>; Sun, 11 Nov 2012 02:22:50 -0800 (PST)
Received: by mail-ee0-f44.google.com with SMTP id b47so74634eek.31 for <ietf@ietf.org>; Sun, 11 Nov 2012 02:22:49 -0800 (PST)
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 :cc:content-type; bh=cQTV6EcvluNjazzCtQ5x+IxgQFip7LRngwLNdZIYr7c=; b=qZS77oWN7Z/vo4LsBo8Vy6AzeDn4sdGHuN1bYC1XSWIvrLgbRJ2qc/VouwHj/QA2vT 0UOQY2tEfXIG3qbr36ewgRiNBb3pV0PI3SudPTLD3u2m5PNdFMI2ZJ0jjvnYJU/9vyE8 mf9Gkq4VnOQSgFselD9TvXx77A+0g3sJHQgFUfw+KfD+k/Yro/ftRyMIikjaNJkexwUw ootfLlHzBmKhw+5V5/s4UGiBLSyCqYr16hgLq8ERV+TDc60bCRbMA/7DVD97nTTJXnXw 4uzgD/dibmGktHu7AwbnYxkCKaFKXftd9Ok+SHzZfYqTeb44o1el7hP4+vd2FlELfuSq p9sg==
MIME-Version: 1.0
Received: by 10.14.179.69 with SMTP id g45mr52638624eem.42.1352629369438; Sun, 11 Nov 2012 02:22:49 -0800 (PST)
Received: by 10.14.174.66 with HTTP; Sun, 11 Nov 2012 02:22:49 -0800 (PST)
In-Reply-To: <9009A606-ACB8-4F25-992E-DF126822C591@checkpoint.com>
References: <CADnDZ8-fjxfgJys8sE10DdZ08tB8HdaTQXbPj2d7-OuQOGi9Pg@mail.gmail.com> <CADnDZ8_v3M1fNtkOV4rU1F-iaMC+2qvKhR353vwESiQsfh70MQ@mail.gmail.com> <9009A606-ACB8-4F25-992E-DF126822C591@checkpoint.com>
Date: Sun, 11 Nov 2012 15:52:49 +0530
Message-ID: <CAKe6YvNbeRWvofqGCSDki3qs8LWpO0w-YBZVBGDeDQL+qn4m8A@mail.gmail.com>
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
From: Vinayak Hegde <vinayakh@gmail.com>
To: Yoav Nir <ynir@checkpoint.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf <ietf@ietf.org>, Abdussalam Baryun <abdussalambaryun@gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 11 Nov 2012 10:22:51 -0000

On Fri, Nov 9, 2012 at 8:37 PM, Yoav Nir <ynir@checkpoint.com> wrote:
> Adding US and Canada attendees (I counted last week, might have changed slightly) you get to about 51% of the attendees.
> When meetings are held in other parts of the world (like Taipei, Paris or Prague) Americans still make up over 40% of the attendees.
> Much as I prefer 4-hour flights to 12-hour flights, it minimizes the general pain to hold meetings in America.
> There's also the issue that finding good venues is considerably easier in America than in either Europe or Asia

I find this logic circular. There is more participation from Americans
(people from US) so more meetings are held there and so more people
from US attend. So it becomes a self-perpetuating cycle. The IAOC /
IETF has notably tried to break free of this pattern by having
meetings in Asia (Taipei/Hiroshima/Beijing). But in that aspect 2012 -
2013 -2014 are disappointing years as meetings are being held only in
North America/Europe. Granted the problem of finding good venues is an
issue in some place but holding a meeting a year outside of NA/Europe
would be nice. Maybe try to hold interim meetings in these places (but
cost could be prohibitive for some of the participants - No easy
answers I guess).

-- Vinayak

From vinayakh@gmail.com  Sun Nov 11 02:45:33 2012
Return-Path: <vinayakh@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5744C21F8877 for <ietf@ietfa.amsl.com>; Sun, 11 Nov 2012 02:45:33 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cF3IfBg8ACfi for <ietf@ietfa.amsl.com>; Sun, 11 Nov 2012 02:45:32 -0800 (PST)
Received: from mail-ee0-f44.google.com (mail-ee0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id B893D21F8819 for <ietf@ietf.org>; Sun, 11 Nov 2012 02:45:23 -0800 (PST)
Received: by mail-ee0-f44.google.com with SMTP id b47so80121eek.31 for <ietf@ietf.org>; Sun, 11 Nov 2012 02:45:23 -0800 (PST)
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 :cc:content-type; bh=TjjAiLI9GVzNWu7lyZRsu3QAivJm4OE9L4KE+Khbt0U=; b=jKr0OIb89DQ9gD25PNqMwxwWGgEyy02OKQ0oDW/5s/3ddEj3XnsJWrIl42XhtS82lI fTSp86+Hzp0sAnz32qxz6D0g/t2aKUxgsqhvWkJtTlvvz6G/fzss+87PrdST6SgpsAoi 0tWoAXMKDO+WTRa5Q4x1ENuTaWtwwfPZIIQ2GvWxzVOG4rjb28UF63CuJ7eotdJ6mSrg lTWeezi8DKiaMo5fDPNCkfc+j8a39nuzMBzb6WoIccLhSMONLHshvFreBvYYZgRV9R8N Pak8aqfFDbUS1hlmyZ901IygYDh9Jkl9o0i+eTKHVKhL1K/CFlKsI3BPYNI8nBY0vDrz s2mQ==
MIME-Version: 1.0
Received: by 10.14.209.136 with SMTP id s8mr52223378eeo.33.1352630722924; Sun, 11 Nov 2012 02:45:22 -0800 (PST)
Received: by 10.14.174.66 with HTTP; Sun, 11 Nov 2012 02:45:22 -0800 (PST)
In-Reply-To: <20121111012811.GB81504@mx1.yitter.info>
References: <CADnDZ8-fjxfgJys8sE10DdZ08tB8HdaTQXbPj2d7-OuQOGi9Pg@mail.gmail.com> <CADnDZ8_v3M1fNtkOV4rU1F-iaMC+2qvKhR353vwESiQsfh70MQ@mail.gmail.com> <6.2.5.6.2.20121109074113.0b2000f8@resistor.net> <8C48B86A895913448548E6D15DA7553B19E215@xmb-rcd-x09.cisco.com> <509D910D.7060503@gmail.com> <509DA4E7.1090504@gmail.com> <509DA723.7030703@gmail.com> <20121111012811.GB81504@mx1.yitter.info>
Date: Sun, 11 Nov 2012 16:15:22 +0530
Message-ID: <CAKe6YvPnLXgKSkzF9BzqFp1U8oo8p9_sh=uN-UAMG24E-iVbJw@mail.gmail.com>
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
From: Vinayak Hegde <vinayakh@gmail.com>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 11 Nov 2012 10:45:33 -0000

On Sun, Nov 11, 2012 at 6:58 AM, Andrew Sullivan <ajs@anvilwalrusden.com> wrote:
> On Fri, Nov 09, 2012 at 08:00:19PM -0500, Arturo Servin wrote:
>>     Hard times may come, some people will ask why the Internet standards
>> are just developed in some places and will challenge us.
>
> And here I thought that the standards were developed on the list.
>
> (For the record, I am not opposed at all to holding a meeting in Latin
> America -- I'm personally in favour of it.  But we also don't hold
> meetings in India or Myanmar, and for much the same reason: we have a
> tiny minority of participants from those places, and given the funding
> model the IETF can't afford to hold full-on meetings as a matter of
> outreach.  There may be ways to fix that, and I understand the IAOC is
> investigating options.  Note that the IETF is always looking for
> sponsors for meetings!)

I don't know enough to comment about Myanmar but the argument for not
holding a meeting in India rings quite hollow. There has been a rising
number of participants from India (both from Indians living in India
and abroad). This is due to two reasons:
1. Internet connectivity and awareness becoming better. Remote
participation has become easier.
2. Better understanding of web technology and relation of standards to
them (examples HTTP/2.0, websockets)
3. Several American MNCs such as Cisco / Juniper setting up offices
and engineers from these organizations getting involved.

SIGcomm (http://conferences.sigcomm.org/sigcomm/2010/) and W3C
(http://wwwconference.org/www2011/) have both happened here in India
in Delhi and Hyderabad respectively. I know the participant profile
and numbers are different for IETF but it is not an insurmountable
mountain to climb.
As is usual, I am willing to help if the IAOC is looking at this part
of the world to hold a meeting.

-- Vinayak

From abdussalambaryun@gmail.com  Sun Nov 11 03:59:59 2012
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 59B6A21F8819 for <ietf@ietfa.amsl.com>; Sun, 11 Nov 2012 03:59:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.409
X-Spam-Level: 
X-Spam-Status: No, score=-2.409 tagged_above=-999 required=5 tests=[AWL=-0.984, BAYES_20=-0.74, RCVD_IN_DNSWL_LOW=-1, SARE_MILLIONSOF=0.315]
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 F2WWr32TqnDB for <ietf@ietfa.amsl.com>; Sun, 11 Nov 2012 03:59:58 -0800 (PST)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 7CF7D21F8782 for <ietf@ietf.org>; Sun, 11 Nov 2012 03:59:58 -0800 (PST)
Received: by mail-vb0-f44.google.com with SMTP id fc26so5906928vbb.31 for <ietf@ietf.org>; Sun, 11 Nov 2012 03:59:58 -0800 (PST)
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 :cc:content-type; bh=swdFb/kOZDY3YbJRPr4qBIK1cSeeN5ZMWvhTZ+XAVvo=; b=peCDQVifPq9cWe9jsfk5RYwC/fpcpnuhYcaRSiN3R/zieDbFxstp0FQi0taxBTaG3x bNL9YI9mZmpXdgoaGmPhU5fH7AoL3+NyMoKUGf5JVQjp4Ap/ul/FQOZHfc7b/lxA5ULQ m24N1RcsXfQpbO1Tbabc1hsammEwJKlR+1HdLaXmLtvFiREzHvYrnLSI+o69iEw4jxYE GMJQow1iVl/0nICEP826trOGQiuAFevdDFWKKueGJVlrfg/V4jL59fo+RZVqK4nKbK9k +0D6hU8L1VR9waiM7WPCiPxPPa2KUg42h4DkbIKssJ1A1eRo3gwRl5L6VvnlAbYRtV3M jFCA==
MIME-Version: 1.0
Received: by 10.58.252.72 with SMTP id zq8mr14837288vec.20.1352635197839; Sun, 11 Nov 2012 03:59:57 -0800 (PST)
Received: by 10.220.204.9 with HTTP; Sun, 11 Nov 2012 03:59:57 -0800 (PST)
In-Reply-To: <9009A606-ACB8-4F25-992E-DF126822C591@checkpoint.com>
References: <CADnDZ8-fjxfgJys8sE10DdZ08tB8HdaTQXbPj2d7-OuQOGi9Pg@mail.gmail.com> <CADnDZ8_v3M1fNtkOV4rU1F-iaMC+2qvKhR353vwESiQsfh70MQ@mail.gmail.com> <9009A606-ACB8-4F25-992E-DF126822C591@checkpoint.com>
Date: Sun, 11 Nov 2012 12:59:57 +0100
Message-ID: <CADnDZ88BgQ03xOi4x1+16k6zKz0h_OyyJam-C=RVbrqz21crBQ@mail.gmail.com>
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Yoav Nir <ynir@checkpoint.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 11 Nov 2012 11:59:59 -0000

 I don't think that thoes Canada and US participants are paying for
the attendance, but their organisations, therefore, are we reducing
the cost of other organisations, or we are interested to bring more
participants. IMHO, IF the reason of making the events in America
because participation is mostly declining when events in Europe or
other, THEN the action of IETF to make more events in America will be
reasonable. We need facts not just expectations.

 The important question is how many users of the Internet now are
spreed in the world, and should the IETF consider making attending
easier to users than to old participants? Is n't three meeting events
in America  per two years enough as you mentioned 51% participants are
from America, as IETF meet 4 times a year?

Now 66% of meetings is done in America, which I think it should be
less or equal to 50%.

AB

On 11/9/12, Yoav Nir <ynir@checkpoint.com> wrote:
>
> On Nov 9, 2012, at 9:31 AM, Abdussalam Baryun wrote:
>
>>>> There is a direct contribution of US $2.2 million by the Internet
>>>> Society next year.  Is the plan to rely on Internet Society subsidies
>>>> or to fix the deficit?  One argument made was that the fees have not
>>>> been increased over the last years.  I'll point out that there hasn't
>>>> been significant increase in paid attendance over the years.  Either
>>>> the IETF is only relevant to the usual folks or else the meetings are
>>>> not made relevant enough for (new) people to attend.
>>
>> I am newcomer and not able to attend because most of meeting in
>> America instead of Europe.
>
> Adding US and Canada attendees (I counted last week, might have changed
> slightly) you get to about 51% of the attendees.
> When meetings are held in other parts of the world (like Taipei, Paris or
> Prague) Americans still make up over 40% of the attendees.
> Much as I prefer 4-hour flights to 12-hour flights, it minimizes the general
> pain to hold meetings in America.
> There's also the issue that finding good venues is considerably easier in
> America than in either Europe or Asia
>
>>> I am repeatedly struck by how many new people *do* attend.
>>>
>>
>> I don't know how long do they remain, for me I am feeling disapointed.
>
> Some come back, and some don't. Could you expand on what you're disappointed
> about?
>
>>> According to Russ's slides [1] 195/1098 are newcomers. And just to
>>> labour
>>> the
>>> point, a newcomer is not a returnee after 10 years, but someone who has
>>> never
>>> attended before.
>>
>> hope treated equal with all participants,
>
> The new attendee, same as the old attendee gets to have everyone shut up
> when they go to the mike. If you have a draft and a relevant presentation,
> you can usually get time at a WG meeting regardless of how many meetings
> you've attended. Knowing that you should do these things is the learning
> curve that every one of us must go through.
>
>>> This number (around 10%) seems consistent over all meetings. So naively,
>>> we
>>> should be growing our attendance by around 300 per year.
>>>
>>
>> agree
>
> But as both you and Adrian Farrel said, a lot of these don't come back.
> Maybe a more relevant statistic for the churn would be to count the
> third-time attendees.
>
> Millions of people go sailing for the first time each year. A huge
> proportion of those get sea sick or bored, and never do it again. That's not
> a useful metric to assess the size of the sailing community.
>
>>> That we are not reflects our inability to retain, not our inability to
>>> attract
>>> (assuming that we are not completely refreshing the IETF attendance
>>> every
>>> three
>>> or four years). Should not be rocket science to follow up with some
>>> newcomers to
>>> find out why they only attend once and never come back.
>>>
>>
>> For me I still did n't attend but understand that many old
>> participants are biased and there seems no equal opportunity, people
>> don't always follow the IETF mission and procedure, they just follow
>> their ways as long there was no complain.
>>
>> I call all newcomers to open a new WG and start complaining because we
>> have to discuss why we were disapointed of the IETF and IESG, and even
>> the Internet Society.
>>
>> Please note that I will focus my volunteering work in complaining and
>> fixing the discourage I found so far.
>
> OK, but if something or someone discouraged you, speak up. Existing members
> can't help you if you don't tell us what's wrong.
>
> Yoav
>
>
>

From abdussalambaryun@gmail.com  Sun Nov 11 04:02:46 2012
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D4C9C21F8819 for <ietf@ietfa.amsl.com>; Sun, 11 Nov 2012 04:02:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.319
X-Spam-Level: 
X-Spam-Status: No, score=-3.319 tagged_above=-999 required=5 tests=[AWL=-0.035, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, SARE_MILLIONSOF=0.315]
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 hio90SBEDpw2 for <ietf@ietfa.amsl.com>; Sun, 11 Nov 2012 04:02:46 -0800 (PST)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id F32AC21F8782 for <ietf@ietf.org>; Sun, 11 Nov 2012 04:02:45 -0800 (PST)
Received: by mail-vc0-f172.google.com with SMTP id fl11so5814177vcb.31 for <ietf@ietf.org>; Sun, 11 Nov 2012 04:02:45 -0800 (PST)
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 :cc:content-type; bh=dAymdrL215g9hp8a6TP6JOaGdtbLsQD1hdDpxzL8TzI=; b=UCTTv/moWe3Nzrr4lctmPmFy+LVElzcDHQ9Bkf2VOHZa0RAoPpdYK5fx8JOCDzx/P7 XrrKDESYzYsbLAmnMVf7tcYXIpqQo9e4OiZ5QIAFNVfpt4fqacxhs6fIDLDKbLADdoZz mAFeL/DMsdIfOQzLnt1y4Z1EoIMWxZ//AuEd370oTcuDxeRJ/G6bsZSyoBHJTpQwp9pV rgru8wk/r5wpYndU50ojoB39v6bl4c/LnUjeKckM6QgGsalw0SrILrGDoC1bZTwYLH3J 1PvWdvd1u9M4KpbCbE1fFWknrYkkHpIxBw06NCj+M0qqsxn9ibBDJ+8vhTBunyMs3fZ3 jaOA==
MIME-Version: 1.0
Received: by 10.52.35.82 with SMTP id f18mr16863080vdj.99.1352635365512; Sun, 11 Nov 2012 04:02:45 -0800 (PST)
Received: by 10.220.204.9 with HTTP; Sun, 11 Nov 2012 04:02:45 -0800 (PST)
In-Reply-To: <CADnDZ88BgQ03xOi4x1+16k6zKz0h_OyyJam-C=RVbrqz21crBQ@mail.gmail.com>
References: <CADnDZ8-fjxfgJys8sE10DdZ08tB8HdaTQXbPj2d7-OuQOGi9Pg@mail.gmail.com> <CADnDZ8_v3M1fNtkOV4rU1F-iaMC+2qvKhR353vwESiQsfh70MQ@mail.gmail.com> <9009A606-ACB8-4F25-992E-DF126822C591@checkpoint.com> <CADnDZ88BgQ03xOi4x1+16k6zKz0h_OyyJam-C=RVbrqz21crBQ@mail.gmail.com>
Date: Sun, 11 Nov 2012 13:02:45 +0100
Message-ID: <CADnDZ8_6=PoWq85FdCaPvkzbj5DyouKLH96teeoRBQh3BM53tA@mail.gmail.com>
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Yoav Nir <ynir@checkpoint.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 11 Nov 2012 12:02:47 -0000

Amending one line

On 11/11/12, Abdussalam Baryun <abdussalambaryun@gmail.com> wrote:
>  The important question is how many users of the Internet now are
> spreed in the world, and should the IETF consider making attending
> easier to users than to old participants? Is n't three meeting events
> in America  per two years enough as you mentioned 51% participants are
> from America, as IETF meet 4 times a year?

as IETF meet 6 times per two years?

>
> Now 66% of meetings is done in America, which I think it should be
> less or equal to 50%.
>
> AB
>
> On 11/9/12, Yoav Nir <ynir@checkpoint.com> wrote:
>>
>> On Nov 9, 2012, at 9:31 AM, Abdussalam Baryun wrote:
>>
>>>>> There is a direct contribution of US $2.2 million by the Internet
>>>>> Society next year.  Is the plan to rely on Internet Society subsidies
>>>>> or to fix the deficit?  One argument made was that the fees have not
>>>>> been increased over the last years.  I'll point out that there hasn't
>>>>> been significant increase in paid attendance over the years.  Either
>>>>> the IETF is only relevant to the usual folks or else the meetings are
>>>>> not made relevant enough for (new) people to attend.
>>>
>>> I am newcomer and not able to attend because most of meeting in
>>> America instead of Europe.
>>
>> Adding US and Canada attendees (I counted last week, might have changed
>> slightly) you get to about 51% of the attendees.
>> When meetings are held in other parts of the world (like Taipei, Paris or
>> Prague) Americans still make up over 40% of the attendees.
>> Much as I prefer 4-hour flights to 12-hour flights, it minimizes the
>> general
>> pain to hold meetings in America.
>> There's also the issue that finding good venues is considerably easier in
>> America than in either Europe or Asia
>>
>>>> I am repeatedly struck by how many new people *do* attend.
>>>>
>>>
>>> I don't know how long do they remain, for me I am feeling disapointed.
>>
>> Some come back, and some don't. Could you expand on what you're
>> disappointed
>> about?
>>
>>>> According to Russ's slides [1] 195/1098 are newcomers. And just to
>>>> labour
>>>> the
>>>> point, a newcomer is not a returnee after 10 years, but someone who has
>>>> never
>>>> attended before.
>>>
>>> hope treated equal with all participants,
>>
>> The new attendee, same as the old attendee gets to have everyone shut up
>> when they go to the mike. If you have a draft and a relevant
>> presentation,
>> you can usually get time at a WG meeting regardless of how many meetings
>> you've attended. Knowing that you should do these things is the learning
>> curve that every one of us must go through.
>>
>>>> This number (around 10%) seems consistent over all meetings. So
>>>> naively,
>>>> we
>>>> should be growing our attendance by around 300 per year.
>>>>
>>>
>>> agree
>>
>> But as both you and Adrian Farrel said, a lot of these don't come back.
>> Maybe a more relevant statistic for the churn would be to count the
>> third-time attendees.
>>
>> Millions of people go sailing for the first time each year. A huge
>> proportion of those get sea sick or bored, and never do it again. That's
>> not
>> a useful metric to assess the size of the sailing community.
>>
>>>> That we are not reflects our inability to retain, not our inability to
>>>> attract
>>>> (assuming that we are not completely refreshing the IETF attendance
>>>> every
>>>> three
>>>> or four years). Should not be rocket science to follow up with some
>>>> newcomers to
>>>> find out why they only attend once and never come back.
>>>>
>>>
>>> For me I still did n't attend but understand that many old
>>> participants are biased and there seems no equal opportunity, people
>>> don't always follow the IETF mission and procedure, they just follow
>>> their ways as long there was no complain.
>>>
>>> I call all newcomers to open a new WG and start complaining because we
>>> have to discuss why we were disapointed of the IETF and IESG, and even
>>> the Internet Society.
>>>
>>> Please note that I will focus my volunteering work in complaining and
>>> fixing the discourage I found so far.
>>
>> OK, but if something or someone discouraged you, speak up. Existing
>> members
>> can't help you if you don't tell us what's wrong.
>>
>> Yoav
>>
>>
>>
>

From ajs@anvilwalrusden.com  Sun Nov 11 06:51:25 2012
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 90F0F21F85ED for <ietf@ietfa.amsl.com>; Sun, 11 Nov 2012 06:51:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.846
X-Spam-Level: 
X-Spam-Status: No, score=-0.846 tagged_above=-999 required=5 tests=[AWL=-0.006, BAYES_00=-2.599, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311]
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 EVLCEQG7sxF1 for <ietf@ietfa.amsl.com>; Sun, 11 Nov 2012 06:51:23 -0800 (PST)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id 6A4D321F85C4 for <ietf@ietf.org>; Sun, 11 Nov 2012 06:51:23 -0800 (PST)
Received: from mx1.yitter.info (69-196-144-227.dsl.teksavvy.com [69.196.144.227]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 742FD8A031 for <ietf@ietf.org>; Sun, 11 Nov 2012 14:51:21 +0000 (UTC)
Date: Sun, 11 Nov 2012 09:51:19 -0500
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
Message-ID: <20121111145119.GB81680@mx1.yitter.info>
References: <CADnDZ8-fjxfgJys8sE10DdZ08tB8HdaTQXbPj2d7-OuQOGi9Pg@mail.gmail.com> <CADnDZ8_v3M1fNtkOV4rU1F-iaMC+2qvKhR353vwESiQsfh70MQ@mail.gmail.com> <6.2.5.6.2.20121109074113.0b2000f8@resistor.net> <8C48B86A895913448548E6D15DA7553B19E215@xmb-rcd-x09.cisco.com> <509D910D.7060503@gmail.com> <509DA4E7.1090504@gmail.com> <509DA723.7030703@gmail.com> <20121111012811.GB81504@mx1.yitter.info> <CAKe6YvPnLXgKSkzF9BzqFp1U8oo8p9_sh=uN-UAMG24E-iVbJw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAKe6YvPnLXgKSkzF9BzqFp1U8oo8p9_sh=uN-UAMG24E-iVbJw@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 11 Nov 2012 14:51:25 -0000

On Sun, Nov 11, 2012 at 04:15:22PM +0530, Vinayak Hegde wrote:
> I don't know enough to comment about Myanmar but the argument for not
> holding a meeting in India rings quite hollow. There has been a rising
> number of participants from India (both from Indians living in India
> and abroad).

I completely agree that there is a rising number, but in terms of
percentage of the participants, people actually living in India don't
seem to be a very significant population. 

Indians living abroad don't count for this argument: the whole point
of moving the meetings around is not to include new people, but to
spread the travel burden.  The principle is to travel to places near
where significant numbers of participants are.  (Note this also means
that more-active participants' location in principle ought to weigh
more.)  The important question about Indian contributors living abroad
is not their country of origin, but their location now.

Nevertheless, I think it is almost certainly true that, if the current
trend of involvement continues, we will eventually hold a meeting in
India, for exactly the same reason that we held (and will doubtless
eventually hold again) a meeting in China.  I'll be delighted when we
observe such involvement.

Best,

A
-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From sm@resistor.net  Sun Nov 11 09:47:03 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B40821F8587 for <ietf@ietfa.amsl.com>; Sun, 11 Nov 2012 09:47:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.483
X-Spam-Level: 
X-Spam-Status: No, score=-102.483 tagged_above=-999 required=5 tests=[AWL=0.116, 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 r0eBw3VZNIfC for <ietf@ietfa.amsl.com>; Sun, 11 Nov 2012 09:47:02 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id A381F21F8555 for <ietf@ietf.org>; Sun, 11 Nov 2012 09:47:02 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id qABHks5u007446; Sun, 11 Nov 2012 09:46:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1352656019; bh=BtKPWSaU03Z7ixR53Nu9TEAMti1Is+qTe+AbmsRPJII=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=GelWBPdHtgDeQrjtwQZ/v6b6jmoe6vllcRVZOM6cJtRs32+1726+eTuTA6sg7Ye/x JjWXn6PMVu/ZMhk6PXkRgs/zcmJzVfd9LUSB4I7LGbaHOun2jMTuTVyzKINRaDu/g0 9MMxlD/6Nx4mjfBxor4iyt/MQjLuoCdzqBQdl68s=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1352656019; i=@resistor.net; bh=BtKPWSaU03Z7ixR53Nu9TEAMti1Is+qTe+AbmsRPJII=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=OcPF4UE46l2Bc5/0raAW2INRdmstG0ICVGJ+PnPbsfr7hMY89nAn2xbl8LQPmMNqo 7h05+f+/xpeGPW8h4y+3ubo6Z1b7rjYBDX3CRd85yqLZv5JfZrxg8mUIDPCzBo+xIJ 7QzM5PXPeh+DSJciwDrWQtgtLyKVt+amKhenQQG8=
Message-Id: <6.2.5.6.2.20121111071204.09a88780@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sun, 11 Nov 2012 09:36:42 -0800
To: Vinayak Hegde <vinayakh@gmail.com>
From: SM <sm@resistor.net>
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
In-Reply-To: <CAKe6YvNbeRWvofqGCSDki3qs8LWpO0w-YBZVBGDeDQL+qn4m8A@mail.g mail.com>
References: <CADnDZ8-fjxfgJys8sE10DdZ08tB8HdaTQXbPj2d7-OuQOGi9Pg@mail.gmail.com> <CADnDZ8_v3M1fNtkOV4rU1F-iaMC+2qvKhR353vwESiQsfh70MQ@mail.gmail.com> <9009A606-ACB8-4F25-992E-DF126822C591@checkpoint.com> <CAKe6YvNbeRWvofqGCSDki3qs8LWpO0w-YBZVBGDeDQL+qn4m8A@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 11 Nov 2012 17:47:03 -0000

Hi Vinayak,
At 02:22 11-11-2012, Vinayak Hegde wrote:
>I find this logic circular. There is more participation from Americans
>(people from US) so more meetings are held there and so more people
>from US attend. So it becomes a self-perpetuating cycle. The IAOC /

I thought so too at some point.  I am not sure anymore.  Your views 
and the ones from Arturo Servin seem to converge.  There is some 
discontent on the question of meeting locations within the group of 
people who attend IETF meetings.  When someone raises the question 
the discussion turns towards the IAOC.  It is then pointed out that 
the IAOC does not do outreach.  I didn't use the "IETF" in the 
previous sentence as it is difficult for there to be any 
consciousness of the IETF as a group.

When Adrian Farrell commented about newcomers [1], he mentioned:

   "This number (around 10%) seems consistent over all meetings.
    So naively, we should be growing our attendance by around 300
    per year."

Andrew Malis replied [2] that:

   "Since attendance is largely flat over last few years, obviously
    newcomers that become regulars are offset by existing participants
    that drop out or cannot make a particular meeting."

Fred Baker posted some data and suggested a more thorough analysis 
[3].  His message also provides some insight about the change in 
meeting locations over the years.

Quoting a message which was posted to this mailing list [4]:

   "This specific programme is designed to increase IETF
    participation from emerging and developing economies."

Is there any analysis to determine whether there has been an increase 
in IETF participation from these economies?  Is the outreach effort a failure?

Regards,
-sm

1. http://www.ietf.org/mail-archive/web/ietf/current/msg75742.html
2. http://www.ietf.org/mail-archive/web/ietf/current/msg75745.html
3. http://www.ietf.org/mail-archive/web/ietf/current/msg75776.html
4. http://www.ietf.org/mail-archive/web/ietf/current/msg75140.html 


From swmike@swm.pp.se  Sun Nov 11 10:06:42 2012
Return-Path: <swmike@swm.pp.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 58EAE21F853A for <ietf@ietfa.amsl.com>; Sun, 11 Nov 2012 10:06:42 -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.042, BAYES_00=-2.599, SARE_RMML_Stock10=0.13]
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 OfPShAYheDxI for <ietf@ietfa.amsl.com>; Sun, 11 Nov 2012 10:06:42 -0800 (PST)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) by ietfa.amsl.com (Postfix) with ESMTP id C34AC21F852E for <ietf@ietf.org>; Sun, 11 Nov 2012 10:06:41 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id AD6D19C; Sun, 11 Nov 2012 19:06:37 +0100 (CET)
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id A75B49A for <ietf@ietf.org>; Sun, 11 Nov 2012 19:06:37 +0100 (CET)
Date: Sun, 11 Nov 2012 19:06:37 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: ietf@ietf.org
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
In-Reply-To: <6.2.5.6.2.20121111071204.09a88780@resistor.net>
Message-ID: <alpine.DEB.2.00.1211111856180.27834@uplift.swm.pp.se>
References: <CADnDZ8-fjxfgJys8sE10DdZ08tB8HdaTQXbPj2d7-OuQOGi9Pg@mail.gmail.com> <CADnDZ8_v3M1fNtkOV4rU1F-iaMC+2qvKhR353vwESiQsfh70MQ@mail.gmail.com> <9009A606-ACB8-4F25-992E-DF126822C591@checkpoint.com> <CAKe6YvNbeRWvofqGCSDki3qs8LWpO0w-YBZVBGDeDQL+qn4m8A@mail.gmail.com> <6.2.5.6.2.20121111071204.09a88780@resistor.net>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 11 Nov 2012 18:06:42 -0000

On Sun, 11 Nov 2012, SM wrote:

> Is there any analysis to determine whether there has been an increase in 
> IETF participation from these economies?  Is the outreach effort a 
> failure?

Personally I believe there could be value in describing what the value is 
to attend the meeting physically. I attended the last meeting in Stockholm 
because it meant I only had to pay the entrence fee, since I live there.

Getting buy-in from management to allow me to go for a week somewhere and 
not be available in the office, pay for hotel and travel, plus the 
entrence fee, it's hard to justify to management. What is a good answer to 
the question "why?".

Remote participating works well in some WGs, in some WGs I have had a hard 
time getting through. People in different WGs treat the WG mailing list 
differently, culture seems to differ quite a lot.

So elaborating on what the benefit of being there physically would 
probably help. Remote participation both during and between meetings is 
crucial for a lot of people I would imagine (it is for me anyway, it's my 
only chance to participate). Getting a low bar for entry into the 
discussions is what I feel is the biggest advantage of the IETF model, 
some WGs really work well in this aspect.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se

From sant9442@gmail.com  Sun Nov 11 14:16:17 2012
Return-Path: <sant9442@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6258721F84FA for <ietf@ietfa.amsl.com>; Sun, 11 Nov 2012 14:16:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.469
X-Spam-Level: 
X-Spam-Status: No, score=-3.469 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, SARE_RMML_Stock10=0.13]
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 adaE7JXPZ3Ef for <ietf@ietfa.amsl.com>; Sun, 11 Nov 2012 14:16:16 -0800 (PST)
Received: from mail-ob0-f172.google.com (mail-ob0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id CE3E621F84E8 for <ietf@ietf.org>; Sun, 11 Nov 2012 14:16:16 -0800 (PST)
Received: by mail-ob0-f172.google.com with SMTP id wo10so2329859obc.31 for <ietf@ietf.org>; Sun, 11 Nov 2012 14:16:16 -0800 (PST)
Received: by 10.182.134.66 with SMTP id pi2mr6611750obb.42.1352672176417; Sun, 11 Nov 2012 14:16:16 -0800 (PST)
Received: from adsl-215-50-126.mia.bellsouth.net (99-3-147-93.lightspeed.miamfl.sbcglobal.net. [99.3.147.93]) by mx.google.com with ESMTPS id b20sm5344462obu.4.2012.11.11.14.16.15 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 11 Nov 2012 14:16:16 -0800 (PST)
Message-ID: <50A023C8.1040904@winserver.com>
Date: Sun, 11 Nov 2012 17:16:40 -0500
From: Hector Santos <gmail.sant9442@winserver.com>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
References: <CADnDZ8-fjxfgJys8sE10DdZ08tB8HdaTQXbPj2d7-OuQOGi9Pg@mail.gmail.com>	<CADnDZ8_v3M1fNtkOV4rU1F-iaMC+2qvKhR353vwESiQsfh70MQ@mail.gmail.com>	<9009A606-ACB8-4F25-992E-DF126822C591@checkpoint.com>	<CAKe6YvNbeRWvofqGCSDki3qs8LWpO0w-YBZVBGDeDQL+qn4m8A@mail.gmail.com>	<6.2.5.6.2.20121111071204.09a88780@resistor.net> <alpine.DEB.2.00.1211111856180.27834@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.2.00.1211111856180.27834@uplift.swm.pp.se>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 11 Nov 2012 22:16:17 -0000

The IETF should be leading the charge for easy to use, multi-device 
readiness cyberspacing virtual meeting places, including better 
electronic groupware collaboration tools, etc. It is undoubtedly and 
inevitably the "Achilles' Heel" for the IETF Meeting.  So the IETF 
needs to embrace it now, big time, before its too late. This includes 
getting on board with membership models to subsidize the business and 
its future.  This shouldn't take away "Face to Face" communications - 
in fact, it will increase it.  Its much more doable with today's 
higher universal bandwidth and the IETF needs to be prime examples of 
the various technology it is helping put together and standardize.  In 
fact, the IETF can probably learn and help improve groupware 
communications with new working groups focusing on groupware.

For the record, I do think it is getting better to do remote meeting 
and as expecting the general issues with real time communications is 
still there but its getting better.

--
HLS

Mikael Abrahamsson wrote:
> On Sun, 11 Nov 2012, SM wrote:
> 
>> Is there any analysis to determine whether there has been an increase 
>> in IETF participation from these economies?  Is the outreach effort a 
>> failure?
> 
> Personally I believe there could be value in describing what the value 
> is to attend the meeting physically. I attended the last meeting in 
> Stockholm because it meant I only had to pay the entrence fee, since I 
> live there.
> 
> Getting buy-in from management to allow me to go for a week somewhere 
> and not be available in the office, pay for hotel and travel, plus the 
> entrence fee, it's hard to justify to management. What is a good answer 
> to the question "why?".
> 
> Remote participating works well in some WGs, in some WGs I have had a 
> hard time getting through. People in different WGs treat the WG mailing 
> list differently, culture seems to differ quite a lot.
> 
> So elaborating on what the benefit of being there physically would 
> probably help. Remote participation both during and between meetings is 
> crucial for a lot of people I would imagine (it is for me anyway, it's 
> my only chance to participate). Getting a low bar for entry into the 
> discussions is what I feel is the biggest advantage of the IETF model, 
> some WGs really work well in this aspect.
> 

From hsantos@isdg.net  Sun Nov 11 14:17:36 2012
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E902821F84FC for <ietf@ietfa.amsl.com>; Sun, 11 Nov 2012 14:17:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.222
X-Spam-Level: 
X-Spam-Status: No, score=-102.222 tagged_above=-999 required=5 tests=[AWL=0.247, BAYES_00=-2.599, SARE_RMML_Stock10=0.13, 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 I6xttCyq65TX for <ietf@ietfa.amsl.com>; Sun, 11 Nov 2012 14:17:36 -0800 (PST)
Received: from winserver.com (mail.santronics.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id E934921F84EE for <ietf@ietf.org>; Sun, 11 Nov 2012 14:17:35 -0800 (PST)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=2356; t=1352672251; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=ZRiM3fyt779tx4X9Uyf0DtO1Dqw=; b=gmUoaURgsQEWvDzGfg2q 4rHL94lb9yDo4LFjU5RY4q3p/gpJiIwuebsxoIa28mwOmQQPTLCV16zs8aNi5KPO KFCQXdLtJ12eoAMDvlMQS8eaIBQs4XcrwBaFWbake38EupclqrU+JGz2W2LUQMY3 23eqTHvlU8oVTZWp82SuNuw=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Sun, 11 Nov 2012 17:17:31 -0500
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from hector.wildcatblog.com ([208.247.131.23]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 104034755.5087.2152; Sun, 11 Nov 2012 17:17:30 -0500
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=2356; t=1352671918; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=bP7mCjq JpkdGNObYBp4wqtHq2n2hF6dYBKj+jAVPZTQ=; b=pbhSSjw5+zSRgdUHyuo/9fP RXjLlZrBC+f+59JmaWExJCF7PwD1NnsnNc5Xiym3ZJaM6p0o9xu8rwT+PmA17Uai XYgosSUvn9E4Fyr3O9sQ5YGnqhqvEi8JTE2UJoOl7TORBzu4SK+4hslJhppqaNb2 OFEd///DpG1WGMb7W4xY=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Sun, 11 Nov 2012 17:11:58 -0500
Received: from [192.168.1.101] ([99.3.147.93]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 702781866.9.3756; Sun, 11 Nov 2012 17:11:57 -0500
Message-ID: <50A0240E.6030707@isdg.net>
Date: Sun, 11 Nov 2012 17:17:50 -0500
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
References: <CADnDZ8-fjxfgJys8sE10DdZ08tB8HdaTQXbPj2d7-OuQOGi9Pg@mail.gmail.com>	<CADnDZ8_v3M1fNtkOV4rU1F-iaMC+2qvKhR353vwESiQsfh70MQ@mail.gmail.com>	<9009A606-ACB8-4F25-992E-DF126822C591@checkpoint.com>	<CAKe6YvNbeRWvofqGCSDki3qs8LWpO0w-YBZVBGDeDQL+qn4m8A@mail.gmail.com>	<6.2.5.6.2.20121111071204.09a88780@resistor.net> <alpine.DEB.2.00.1211111856180.27834@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.2.00.1211111856180.27834@uplift.swm.pp.se>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 11 Nov 2012 22:17:37 -0000

The IETF should be leading the charge for easy to use, multi-device
readiness cyberspacing virtual meeting places, including better
electronic groupware collaboration tools, etc. It is undoubtedly and
inevitably the "Achilles' Heel" for the IETF Meeting.  So the IETF
needs to embrace it now, big time, before its too late. This includes
getting on board with membership models to subsidize the business and
its future.  This shouldn't take away "Face to Face" communications -
in fact, it will increase it.  Its much more doable with today's
higher universal bandwidth and the IETF needs to be prime examples of
the various technology it is helping put together and standardize.  In
fact, the IETF can probably learn and help improve groupware
communications with new working groups focusing on groupware.

For the record, I do think it is getting better to do remote meeting
and as expecting the general issues with real time communications is
still there but its getting better.

--
HLS

Mikael Abrahamsson wrote:
> On Sun, 11 Nov 2012, SM wrote:
> 
>> Is there any analysis to determine whether there has been an increase 
>> in IETF participation from these economies?  Is the outreach effort a 
>> failure?
> 
> Personally I believe there could be value in describing what the value 
> is to attend the meeting physically. I attended the last meeting in 
> Stockholm because it meant I only had to pay the entrence fee, since I 
> live there.
> 
> Getting buy-in from management to allow me to go for a week somewhere 
> and not be available in the office, pay for hotel and travel, plus the 
> entrence fee, it's hard to justify to management. What is a good answer 
> to the question "why?".
> 
> Remote participating works well in some WGs, in some WGs I have had a 
> hard time getting through. People in different WGs treat the WG mailing 
> list differently, culture seems to differ quite a lot.
> 
> So elaborating on what the benefit of being there physically would 
> probably help. Remote participation both during and between meetings is 
> crucial for a lot of people I would imagine (it is for me anyway, it's 
> my only chance to participate). Getting a low bar for entry into the 
> discussions is what I feel is the biggest advantage of the IETF model, 
> some WGs really work well in this aspect.
> 

-- 
HLS



From sm@resistor.net  Sun Nov 11 15:07:09 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4BD9B21F84DF for <ietf@ietfa.amsl.com>; Sun, 11 Nov 2012 15:07:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.422
X-Spam-Level: 
X-Spam-Status: No, score=-102.422 tagged_above=-999 required=5 tests=[AWL=0.047, BAYES_00=-2.599, SARE_RMML_Stock10=0.13, 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 tUAVE4JzBp5v for <ietf@ietfa.amsl.com>; Sun, 11 Nov 2012 15:07:08 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id E0DEA21F848D for <ietf@ietf.org>; Sun, 11 Nov 2012 15:07:04 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id qABN6wIe023678; Sun, 11 Nov 2012 15:07:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1352675223; bh=d4IeKAcnroPwlyaapn7LHNU3LEXx4XZpmiSOCkFhqco=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=FzCD/n1pLG/j6PVB8yMtvrP+OjEVLVB1/in9f9vcBl1iPD0hgF2X1LGQI1ORydOwS rtboMBgsHv/tiQ+FvqV2jZ7v9pApPwMU0yE7GqZe2Yr7PmzMT1aMbcJnAMs1qh7SJt 9Vw6VsNKUl9v/9MsRhHBzB8ncA7ljI2KfQQ3qpQM=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1352675223; i=@resistor.net; bh=d4IeKAcnroPwlyaapn7LHNU3LEXx4XZpmiSOCkFhqco=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=NX9lA4juFbIWYsSgX0V46WPcG8rCYWNYoRO0KfaupHyodJYz+pBYI6jLGeyH0bCSv bJWo1NjGa7khtod07806D8Oc5J8+OQHXSUJzGtg34THAKFUJPYBogYIYgvGroMnrmk DLzbFXAa6Et5Ya96JaV+wP5G992ZrHxGLXzZepf4=
Message-Id: <6.2.5.6.2.20121111132030.0b47a120@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sun, 11 Nov 2012 15:05:35 -0800
To: Mikael Abrahamsson <swmike@swm.pp.se>
From: SM <sm@resistor.net>
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
In-Reply-To: <alpine.DEB.2.00.1211111856180.27834@uplift.swm.pp.se>
References: <CADnDZ8-fjxfgJys8sE10DdZ08tB8HdaTQXbPj2d7-OuQOGi9Pg@mail.gmail.com> <CADnDZ8_v3M1fNtkOV4rU1F-iaMC+2qvKhR353vwESiQsfh70MQ@mail.gmail.com> <9009A606-ACB8-4F25-992E-DF126822C591@checkpoint.com> <CAKe6YvNbeRWvofqGCSDki3qs8LWpO0w-YBZVBGDeDQL+qn4m8A@mail.gmail.com> <6.2.5.6.2.20121111071204.09a88780@resistor.net> <alpine.DEB.2.00.1211111856180.27834@uplift.swm.pp.se>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 11 Nov 2012 23:07:09 -0000

Hi Mikael,

For newcomers http://www.youtube.com/watch?v=mk48xRzuNvA

At 10:06 11-11-2012, Mikael Abrahamsson wrote:
>Getting buy-in from management to allow me to go for a week 
>somewhere and not be available in the office, pay for hotel and 
>travel, plus the entrence fee, it's hard to justify to management. 
>What is a good answer to the question "why?".

I don't have an answer to the question.  I'd say that it depends on 
your company's goals and what it expects from you.  It also depends 
on your ability to assimilate.  If there's a specification that 
affects your company's bottom line it would be better to discuss 
about it as early as possible.  It's up to you to identify what work 
will be done or is being done and assess its impact.  It's difficult 
to justify if management does not have any understanding of what the 
IETF does.  Here's an argument: "the training course you offered me 
will cost you the same amount as my IETF attendance.  How about you 
sending me to the IETF instead of that training course"?  I am not 
equating training with IETF attendance.  If you are going to attend 
an IETF meeting to be trained you will end up being disappointed.

Now, how could your company determine whether you are going to play 
solitaire instead of doing work at the meeting?  If you have not 
showed any interest in remote participation or you have only posted 
"+1" on the mailing list the probability that you would do much at 
the meeting is, in my humble opinion, very low.

>Remote participating works well in some WGs, in some WGs I have had 
>a hard time getting through. People in different WGs treat the WG 
>mailing list differently, culture seems to differ quite a lot.

Yes.

>So elaborating on what the benefit of being there physically would 
>probably help. Remote

I'll quote Tom Petch [1]:

   "there is a spectrum in communication from the richest, when I am
    standing in front of you, looking you in the eye, to the poorest, a
    tweet."

On a different thread Ted Hardie commented about trust issues 
[2].  That's difficult to establish remotely.

Regards,
-sm

1. http://www.ietf.org/mail-archive/web/ietf/current/msg75764.html
2. http://www.ietf.org/mail-archive/web/ietf/current/msg75749.html 


From johnl@iecc.com  Sun Nov 11 16:34:51 2012
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9983221F84C6 for <ietf@ietfa.amsl.com>; Sun, 11 Nov 2012 16:34:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.725
X-Spam-Level: 
X-Spam-Status: No, score=-107.725 tagged_above=-999 required=5 tests=[AWL=-4.126, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, 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 LZzWavZdr+B5 for <ietf@ietfa.amsl.com>; Sun, 11 Nov 2012 16:34:51 -0800 (PST)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id AC0A721F84C5 for <ietf@ietf.org>; Sun, 11 Nov 2012 16:34:50 -0800 (PST)
Received: (qmail 17051 invoked from network); 11 Nov 2012 17:14:08 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 11 Nov 2012 17:14:08 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=509fdce0.xn--3zv.k1211; i=johnl@user.iecc.com; bh=vSxT2WtUtYgZHi+8l8FgScjO3+J1K6xofKiwQPmGU4Y=; b=I58xQS8MsJoguLUMDtKPdNzmDQHAk8oxeutP+a0u1R+nQcerOu7/C6mHpyvgAixHQHLh5NLA/iF3q5dYWVctloFqK9aatc+l+5piPpfaDibpRqRHNJrhuUHFarLXSte//2M/N/8mBMHrLdE4EbdTYD2DbaG5C3qSE0/cPFUkd0o=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=509fdce0.xn--3zv.k1211; olt=johnl@user.iecc.com; bh=vSxT2WtUtYgZHi+8l8FgScjO3+J1K6xofKiwQPmGU4Y=; b=Zu1Sw2FNqo9mREFX3VYEU5vUEWnA+bzYeBkoxZ03EbYM+OlfQgfcDX3ax91GYSi8WqrsM0ZIiMlHUzz2OvB2ZXufcIAWhhN30jviyUUlRnN8vDg+bJJMgNoxR3iWDTPcK94UAMPAIRY5jzUnC8jeID53gKRKCMhCyBBvUb2RP9E=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 11 Nov 2012 17:13:45 -0000
Message-ID: <20121111171345.45069.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: how do Newcomers work in the IETF [Was: Evolutionizing
In-Reply-To: <CAKe6YvNbeRWvofqGCSDki3qs8LWpO0w-YBZVBGDeDQL+qn4m8A@mail.gmail.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Nov 2012 00:34:51 -0000

>I find this logic circular. There is more participation from Americans
>(people from US) so more meetings are held there and so more people
>from US attend.

Anyone in the world with an e-mail address can participate in and
contribute to the IETF.  I did stuff on mailing lists for years before
I went to a meeting, which is not unusual.  You do need to be able to
read and write English, but beyond that, nobody cares who or where you
are so long as you do useful work.

If people can only get work done by meeting in person, they're not
going to be very effective in the IETF.

R's,
John

From johnl@iecc.com  Sun Nov 11 16:37:22 2012
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A3BC621F84C7 for <ietf@ietfa.amsl.com>; Sun, 11 Nov 2012 16:37:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.537
X-Spam-Level: 
X-Spam-Status: No, score=-107.537 tagged_above=-999 required=5 tests=[AWL=-3.938, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, 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 4BRom6kZLkfK for <ietf@ietfa.amsl.com>; Sun, 11 Nov 2012 16:37:21 -0800 (PST)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 79F0B21F84C5 for <ietf@ietf.org>; Sun, 11 Nov 2012 16:37:21 -0800 (PST)
Received: (qmail 22689 invoked from network); 11 Nov 2012 17:24:30 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 11 Nov 2012 17:24:30 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=509fdf4e.xn--30v786c.k1211; i=johnl@user.iecc.com; bh=zS7gFgJJi16ByTanpNBH7hFVh+vFNfpeFhspBqGgQGA=; b=pT8exmuPXkJZ19ftsP6xcduQnGkCVwkvz/kemTWJFYkNWPVZkm+xer9btih+4o3Q5xTXmTXi6lFvE7hAAi93NK9Uigphv19i0yMXtS0UpCpwSOOBogoUb50x64aRNWsgyhO58FREd7tEhdDQqGoMP8FCZcU8m42RS/FpICO64OM=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=509fdf4e.xn--30v786c.k1211; olt=johnl@user.iecc.com; bh=zS7gFgJJi16ByTanpNBH7hFVh+vFNfpeFhspBqGgQGA=; b=J9cUNvW2kFzdSxTihQpmBEiade8JndwqnXIHWFYNuIe25oWx1VNFrqVlIkzkSPK2GoLVKVQOzCeSvYokvFZAUIMvv4Wf+/eB//qtBuwUXNEcsdBuPbCqVXCyTZS75YbFBnNbDBTVyLdstpQOwDPxR4sVDlYoC5h0aq4G0uiCiLA=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 11 Nov 2012 17:24:07 -0000
Message-ID: <20121111172407.45480.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
In-Reply-To: <CADnDZ88BgQ03xOi4x1+16k6zKz0h_OyyJam-C=RVbrqz21crBQ@mail.gmail.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Cc: abdussalambaryun@gmail.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Nov 2012 00:37:22 -0000

> I don't think that thoes Canada and US participants are paying for
>the attendance, but their organisations, ...

In many cases, you are mistaken.


From brian.e.carpenter@gmail.com  Mon Nov 12 00:08:57 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D10EF21F847D for <ietf@ietfa.amsl.com>; Mon, 12 Nov 2012 00:08:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.599
X-Spam-Level: 
X-Spam-Status: No, score=-101.599 tagged_above=-999 required=5 tests=[AWL=0.092, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, 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 B8ILZSTF2mZL for <ietf@ietfa.amsl.com>; Mon, 12 Nov 2012 00:08:57 -0800 (PST)
Received: from mail-bk0-f44.google.com (mail-bk0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id 07B7B21F847B for <ietf@ietf.org>; Mon, 12 Nov 2012 00:08:56 -0800 (PST)
Received: by mail-bk0-f44.google.com with SMTP id jg9so779470bkc.31 for <ietf@ietf.org>; Mon, 12 Nov 2012 00:08:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=oo3pXfj/EWOKeeSWQcXg1GGl0DY8BVO+xoxIq7ZDW8k=; b=nyviltZXxEbDv8muOCAwy8Vkm4RnjsFNJrH7u3oAaw7NoAM1rGUUqiL46avS+8P141 aawt1EarnR9XSzmK4hie8wC6ScEDV9TUhWwc45ekDH6wwYzhOcY6tpTPVMgJgeAmT7wJ 5CBMAisdrr7nlAO9TOUuD7353MeD86BxDwSCjps5gJTlk6Ka8yfoZ+JYJ1xllCxoqwhP OXZMU5O+GkTPznAROjPxuMypWXaNl8BbwfrxrVjk30xtpbFPYKxQxqN9MDSSjeVxhLfD ngFqjBk3f+jp6kM6tVLr9p+TgyaeXXeR6G76lrWDnLGVlNAODz7leP1y5ioAcOPG7ZeJ WIQg==
Received: by 10.204.146.1 with SMTP id f1mr1130368bkv.130.1352707735713; Mon, 12 Nov 2012 00:08:55 -0800 (PST)
Received: from [192.168.1.65] (host-2-102-217-222.as13285.net. [2.102.217.222]) by mx.google.com with ESMTPS id ht18sm2221612bkc.14.2012.11.12.00.08.53 (version=SSLv3 cipher=OTHER); Mon, 12 Nov 2012 00:08:54 -0800 (PST)
Message-ID: <50A0AE92.8000300@gmail.com>
Date: Mon, 12 Nov 2012 08:08:50 +0000
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
References: <CADnDZ8-fjxfgJys8sE10DdZ08tB8HdaTQXbPj2d7-OuQOGi9Pg@mail.gmail.com>	<CADnDZ8_v3M1fNtkOV4rU1F-iaMC+2qvKhR353vwESiQsfh70MQ@mail.gmail.com>	<9009A606-ACB8-4F25-992E-DF126822C591@checkpoint.com>	<CAKe6YvNbeRWvofqGCSDki3qs8LWpO0w-YBZVBGDeDQL+qn4m8A@mail.gmail.com>	<6.2.5.6.2.20121111071204.09a88780@resistor.net> <alpine.DEB.2.00.1211111856180.27834@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.2.00.1211111856180.27834@uplift.swm.pp.se>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Nov 2012 08:08:57 -0000

On 11/11/2012 18:06, Mikael Abrahamsson wrote:
...
> So elaborating on what the benefit of being there physically would
> probably help. Remote participation both during and between meetings is
> crucial for a lot of people I would imagine (it is for me anyway, it's
> my only chance to participate). Getting a low bar for entry into the
> discussions is what I feel is the biggest advantage of the IETF model,
> some WGs really work well in this aspect.

For WGs that do *not* have a low bar for entry, a detailed complaint to the
chairs and the AD would be very appropriate (and probably more effective than
a rant on this list).

There's no doubt that personal attendance is the best way to get a full
understanding of how the IETF works, but remote participation is
supposed to work.

BTW, I originated the http://www.ietf.org/newcomers.html page and
if any newcomers have comments on the text please send them to me
off-list.

    Brian

From swmike@swm.pp.se  Mon Nov 12 00:18:42 2012
Return-Path: <swmike@swm.pp.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4557121F8487 for <ietf@ietfa.amsl.com>; Mon, 12 Nov 2012 00:18:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.555
X-Spam-Level: 
X-Spam-Status: No, score=-2.555 tagged_above=-999 required=5 tests=[AWL=0.044,  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 IgJh6eRnlf0T for <ietf@ietfa.amsl.com>; Mon, 12 Nov 2012 00:18:41 -0800 (PST)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) by ietfa.amsl.com (Postfix) with ESMTP id BD46F21F847D for <ietf@ietf.org>; Mon, 12 Nov 2012 00:18:41 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 9327B9C; Mon, 12 Nov 2012 09:18:40 +0100 (CET)
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 8FEDE9A; Mon, 12 Nov 2012 09:18:40 +0100 (CET)
Date: Mon, 12 Nov 2012 09:18:40 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
In-Reply-To: <50A0AE92.8000300@gmail.com>
Message-ID: <alpine.DEB.2.00.1211120913130.27834@uplift.swm.pp.se>
References: <CADnDZ8-fjxfgJys8sE10DdZ08tB8HdaTQXbPj2d7-OuQOGi9Pg@mail.gmail.com> <CADnDZ8_v3M1fNtkOV4rU1F-iaMC+2qvKhR353vwESiQsfh70MQ@mail.gmail.com> <9009A606-ACB8-4F25-992E-DF126822C591@checkpoint.com> <CAKe6YvNbeRWvofqGCSDki3qs8LWpO0w-YBZVBGDeDQL+qn4m8A@mail.gmail.com> <6.2.5.6.2.20121111071204.09a88780@resistor.net> <alpine.DEB.2.00.1211111856180.27834@uplift.swm.pp.se> <50A0AE92.8000300@gmail.com>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Nov 2012 08:18:42 -0000

On Mon, 12 Nov 2012, Brian E Carpenter wrote:

> For WGs that do *not* have a low bar for entry, a detailed complaint to 
> the chairs and the AD would be very appropriate (and probably more 
> effective than a rant on this list).

Well, it's hard to say what caused an email I sent (new thread, pitching 
idea, asking if it was relevant to the WG) to not get responded to.

Perhaps it was irrelevant or uninteresting but nobody wanted to say so. I 
don't know, if I don't get a response, I tend not to push the issue.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se

From framefritti@gmail.com  Mon Nov 12 04:24:50 2012
Return-Path: <framefritti@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E9EB21F8487 for <ietf@ietfa.amsl.com>; Mon, 12 Nov 2012 04:24:50 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7OvSGL3+5kTy for <ietf@ietfa.amsl.com>; Mon, 12 Nov 2012 04:24:49 -0800 (PST)
Received: from mail-ia0-f172.google.com (mail-ia0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 7FD2121F8475 for <ietf@ietf.org>; Mon, 12 Nov 2012 04:24:49 -0800 (PST)
Received: by mail-ia0-f172.google.com with SMTP id j26so360880iaf.31 for <ietf@ietf.org>; Mon, 12 Nov 2012 04:24:49 -0800 (PST)
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=26XuS7te4teX65PCMojpeK0yF1fehuUNuvVqg5qQtAE=; b=BasJZRGBGCmtZLhum0meD6v55GiPwLXMBp/MLSDXVddW9jTeNPZjXMG3FB0Nwl+IW1 8/Z1Abc+zOslf15Ev7Em1irDChjIQYWmSF/IRp+l6ikrS4WHyDYRVrxglo6zTZBBX41D dausk3aAgToBEEEFYY+Kj43i21YyhiAS70HP5WD60p7UzJXx0XD51ed4SUxexlS4wUt/ N9AqcoRrxvHfR1O8bY7FNUl1yJyjTNrolgVh8TLn7rjp0sKs09/BH86gaFgXMq3ZqQtZ NFN/w1u0v3vflC9L+b2IXtNis5YOTW/uc06EICBPZePdwz+u0O7P0eB3j43ayd4744RP Iasg==
MIME-Version: 1.0
Received: by 10.43.96.138 with SMTP id cg10mr2330310icc.46.1352723089143; Mon, 12 Nov 2012 04:24:49 -0800 (PST)
Received: by 10.64.98.202 with HTTP; Mon, 12 Nov 2012 04:24:48 -0800 (PST)
In-Reply-To: <alpine.DEB.2.00.1211120913130.27834@uplift.swm.pp.se>
References: <CADnDZ8-fjxfgJys8sE10DdZ08tB8HdaTQXbPj2d7-OuQOGi9Pg@mail.gmail.com> <CADnDZ8_v3M1fNtkOV4rU1F-iaMC+2qvKhR353vwESiQsfh70MQ@mail.gmail.com> <9009A606-ACB8-4F25-992E-DF126822C591@checkpoint.com> <CAKe6YvNbeRWvofqGCSDki3qs8LWpO0w-YBZVBGDeDQL+qn4m8A@mail.gmail.com> <6.2.5.6.2.20121111071204.09a88780@resistor.net> <alpine.DEB.2.00.1211111856180.27834@uplift.swm.pp.se> <50A0AE92.8000300@gmail.com> <alpine.DEB.2.00.1211120913130.27834@uplift.swm.pp.se>
Date: Mon, 12 Nov 2012 13:24:48 +0100
Message-ID: <CABSMSPXzq6WmDewORfuGDAEdmjZN98qc1z_9yHzedo4r=woAFw@mail.gmail.com>
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
From: Riccardo Bernardini <framefritti@gmail.com>
To: ietf@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Nov 2012 12:24:50 -0000

On Mon, Nov 12, 2012 at 9:18 AM, Mikael Abrahamsson <swmike@swm.pp.se> wrote:
> On Mon, 12 Nov 2012, Brian E Carpenter wrote:
>
>> For WGs that do *not* have a low bar for entry, a detailed complaint to
>> the chairs and the AD would be very appropriate (and probably more effective
>> than a rant on this list).
>
>
> Well, it's hard to say what caused an email I sent (new thread, pitching
> idea, asking if it was relevant to the WG) to not get responded to.
>
> Perhaps it was irrelevant or uninteresting but nobody wanted to say so. I
> don't know, if I don't get a response, I tend not to push the issue.

I can add another (likely) reason: low S/N ratio in everyone's
mailbox.  It happened to me too: I see an e-mail, I think it is
interesting and that I should reply, the reply is not just a
one-line-email and it requires so thought,  so I say "I'll reply
later," I get drowned under a ton of other mails and I forget about
this one...  It should not happen, I agree, but it does...

You could say that if the message had enough interest for me, I would
have replied at once and I can agree with that. The matter is that
"interesting" is somehow in between "totally boring" and
"life-or-death matter," so that an e-mail can have some interest and
still remains unresponded too.

About my strictly personal experience of the entry bar in IETF, I must
say that when I went to Maastricht I was really impressed how I felt
"welcomed" and part of the group, while carrying the red label of the
rookie :-).

   ( BTW, part of my "welcomed" feeling was due also to the "reception
for  new attendants" and the  "crash courses" for newcomers given the
first day [suggestion for potential newcomers: go to that courses, it
is worth it] )

I had my fair share of interaction (I am quite shy a guy, so it is not
really in my nature to jump for the mike at every occasion) without
feeling a "second class citizen" because of my newcomer status.
However, this was *my* personal experience and your mileage may vary.
Maybe if someone else interacts with people less friendly than the one
I interacted with, they could experience a different situation.

>
>
> --
> Mikael Abrahamsson    email: swmike@swm.pp.se

From ynir@checkpoint.com  Mon Nov 12 05:49:01 2012
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 76B3721F81FE for <ietf@ietfa.amsl.com>; Mon, 12 Nov 2012 05:49:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 Bi+5058cTZFo for <ietf@ietfa.amsl.com>; Mon, 12 Nov 2012 05:49:00 -0800 (PST)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 48A5021F81FF for <ietf@ietf.org>; Mon, 12 Nov 2012 05:48:59 -0800 (PST)
Received: from IL-EX10.ad.checkpoint.com ([194.29.34.147]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id qACDmqSV001347; Mon, 12 Nov 2012 15:48:52 +0200
X-CheckPoint: {50A0FB54-1-1B221DC2-1FFFF}
Received: from IL-EX10.ad.checkpoint.com ([169.254.2.194]) by IL-EX10.ad.checkpoint.com ([169.254.2.194]) with mapi id 14.02.0318.004; Mon, 12 Nov 2012 15:48:52 +0200
From: Yoav Nir <ynir@checkpoint.com>
To: Riccardo Bernardini <framefritti@gmail.com>
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
Thread-Topic: Newcomers [Was: Evolutionizing the IETF]
Thread-Index: Ac3A0MXd/LktpOa1R4KxniTfIleMPv//9aKA
Date: Mon, 12 Nov 2012 13:48:51 +0000
Message-ID: <4613980CFC78314ABFD7F85CC30277210119CA@IL-EX10.ad.checkpoint.com>
References: <CADnDZ8-fjxfgJys8sE10DdZ08tB8HdaTQXbPj2d7-OuQOGi9Pg@mail.gmail.com> <CADnDZ8_v3M1fNtkOV4rU1F-iaMC+2qvKhR353vwESiQsfh70MQ@mail.gmail.com> <9009A606-ACB8-4F25-992E-DF126822C591@checkpoint.com> <CAKe6YvNbeRWvofqGCSDki3qs8LWpO0w-YBZVBGDeDQL+qn4m8A@mail.gmail.com> <6.2.5.6.2.20121111071204.09a88780@resistor.net> <alpine.DEB.2.00.1211111856180.27834@uplift.swm.pp.se> <50A0AE92.8000300@gmail.com> <alpine.DEB.2.00.1211120913130.27834@uplift.swm.pp.se> <CABSMSPXzq6WmDewORfuGDAEdmjZN98qc1z_9yHzedo4r=woAFw@mail.gmail.com>
In-Reply-To: <CABSMSPXzq6WmDewORfuGDAEdmjZN98qc1z_9yHzedo4r=woAFw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [91.90.139.85]
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <F63B57F208FC7649A256C21E9CEA3C15@ad.checkpoint.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Nov 2012 13:49:01 -0000

On Nov 12, 2012, at 2:24 PM, Riccardo Bernardini wrote:

> On Mon, Nov 12, 2012 at 9:18 AM, Mikael Abrahamsson <swmike@swm.pp.se> wr=
ote:
>> On Mon, 12 Nov 2012, Brian E Carpenter wrote:
>>=20
>>> For WGs that do *not* have a low bar for entry, a detailed complaint to
>>> the chairs and the AD would be very appropriate (and probably more effe=
ctive
>>> than a rant on this list).
>>=20
>>=20
>> Well, it's hard to say what caused an email I sent (new thread, pitching
>> idea, asking if it was relevant to the WG) to not get responded to.
>>=20
>> Perhaps it was irrelevant or uninteresting but nobody wanted to say so. =
I
>> don't know, if I don't get a response, I tend not to push the issue.
>=20
> I can add another (likely) reason: low S/N ratio in everyone's
> mailbox.  It happened to me too: I see an e-mail, I think it is
> interesting and that I should reply, the reply is not just a
> one-line-email and it requires so thought,  so I say "I'll reply
> later," I get drowned under a ton of other mails and I forget about
> this one...  It should not happen, I agree, but it does=85

One way to get better responses is a targeted message. A message to a busy =
working group's list with "hey, I've had this idea. What do y'all think?" i=
s likely to be ignored by most if they weren't prepared for it.  A message =
to Jack saying "Hey, Jack, what do you think of this?" is much more likely =
to get a response, and a draft you're co-authoring with "Jack" might get mo=
re attention than a draft you're authoring by yourself, assuming that you a=
re either unknown or barely-known, and "Jack" is a pillar of the community.

That's one of the reasons to go to meetings. You get to know the "Jack"s pe=
rsonally, so that you can feel comfortable asking them directly for review =
of your ideas. If you don't have that, a good second-best is to send this d=
irectly to a working group chair. They will feel more obliged to answer tha=
n a random Jack, they know the "Jack"s (or they're not doing their job), an=
d they can introduce you and your idea better to both the group and the app=
ropriate "Jack".

> You could say that if the message had enough interest for me, I would
> have replied at once and I can agree with that. The matter is that
> "interesting" is somehow in between "totally boring" and
> "life-or-death matter," so that an e-mail can have some interest and
> still remains unresponded too.

It takes a lot of thinking and some careful reading to decide if you're rea=
lly interested. We don't have time to do that for every intriguing message =
on the mailing list.

> About my strictly personal experience of the entry bar in IETF, I must
> say that when I went to Maastricht I was really impressed how I felt
> "welcomed" and part of the group, while carrying the red label of the
> rookie :-).
>=20
>  ( BTW, part of my "welcomed" feeling was due also to the "reception
> for  new attendants" and the  "crash courses" for newcomers given the
> first day [suggestion for potential newcomers: go to that courses, it
> is worth it] )
>=20
> I had my fair share of interaction (I am quite shy a guy, so it is not
> really in my nature to jump for the mike at every occasion) without
> feeling a "second class citizen" because of my newcomer status.
> However, this was *my* personal experience and your mileage may vary.
> Maybe if someone else interacts with people less friendly than the one
> I interacted with, they could experience a different situation.

Yeah, me too. My first IETF meeting I went to the mike only once. You get u=
sed to it, and with time, you build a reputation. You can build a reputatio=
n with only the mailing list. You can even make the necessary social ties b=
y participating in the mailing list, but that's considerably harder.

Yoav


From worley@shell01.TheWorld.com  Mon Nov 12 06:57:37 2012
Return-Path: <worley@shell01.TheWorld.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9AF3821F8596 for <ietf@ietfa.amsl.com>; Mon, 12 Nov 2012 06:57:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.766
X-Spam-Level: 
X-Spam-Status: No, score=-2.766 tagged_above=-999 required=5 tests=[AWL=0.214,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, RCVD_IN_SORBS_WEB=0.619]
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 eZYho5quoCdd for <ietf@ietfa.amsl.com>; Mon, 12 Nov 2012 06:57:36 -0800 (PST)
Received: from TheWorld.com (pcls5.std.com [192.74.137.145]) by ietfa.amsl.com (Postfix) with ESMTP id 1ACDB21F8481 for <ietf@ietf.org>; Mon, 12 Nov 2012 06:57:35 -0800 (PST)
Received: from shell.TheWorld.com (root@shell01.theworld.com [192.74.137.71]) by TheWorld.com (8.14.5/8.14.5) with ESMTP id qACEuXXm009907 for <ietf@ietf.org>; Mon, 12 Nov 2012 09:56:35 -0500
Received: from shell01.TheWorld.com (localhost.theworld.com [127.0.0.1]) by shell.TheWorld.com (8.13.6/8.12.8) with ESMTP id qACEuXU5912287 for <ietf@ietf.org>; Mon, 12 Nov 2012 09:56:33 -0500 (EST)
Received: (from worley@localhost) by shell01.TheWorld.com (8.13.6/8.13.6/Submit) id qACEuWFN910936; Mon, 12 Nov 2012 09:56:32 -0500 (EST)
Date: Mon, 12 Nov 2012 09:56:32 -0500 (EST)
Message-Id: <201211121456.qACEuWFN910936@shell01.TheWorld.com>
From: worley@ariadne.com (Dale R. Worley)
Sender: worley@ariadne.com (Dale R. Worley)
To: ietf@ietf.org
In-reply-to: <alpine.DEB.2.00.1211120913130.27834@uplift.swm.pp.se> (swmike@swm.pp.se)
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Nov 2012 14:57:37 -0000

> From: Mikael Abrahamsson <swmike@swm.pp.se>
> 
> Well, it's hard to say what caused an email I sent (new thread, pitching 
> idea, asking if it was relevant to the WG) to not get responded to.
> 
> Perhaps it was irrelevant or uninteresting but nobody wanted to say so. I 
> don't know, if I don't get a response, I tend not to push the issue.

The operational rule in the IETF is "Everyone may speak.  Not everyone
is listened to."

More or less by definition, your message was uninteresting.  The
question is why was it considered uninteresting.  One way to find out
would be to send private messages to respected people in the WG and
ask what they think of the idea.  ("socializing the idea") Of course,
they might not answer either.  One way to build up enough credibility
to get respected people to answer you is to do thankless jobs.  In
most WGs, there are never enough people who are willing to read and
provide detailed critiques of drafts.  (And believe me, almost all
drafts need significant improvements of their presentation, and often
of the technology.)  And the quality of your critiques of drafts is a
good way to demonstrate your technical skills.

Dale

From adrian@olddog.co.uk  Mon Nov 12 07:18:08 2012
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 50B1821F85F0 for <ietf@ietfa.amsl.com>; Mon, 12 Nov 2012 07:18:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.166
X-Spam-Level: 
X-Spam-Status: No, score=-2.166 tagged_above=-999 required=5 tests=[AWL=0.433,  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 NSWPsKUMuUbq for <ietf@ietfa.amsl.com>; Mon, 12 Nov 2012 07:18:07 -0800 (PST)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249]) by ietfa.amsl.com (Postfix) with ESMTP id 98A6021F85C2 for <ietf@ietf.org>; Mon, 12 Nov 2012 07:18:07 -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 qACFI6FL015165 for <ietf@ietf.org>; Mon, 12 Nov 2012 15:18:06 GMT
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id qACFI5Tb015154 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <ietf@ietf.org>; Mon, 12 Nov 2012 15:18:05 GMT
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <ietf@ietf.org>
References: <alpine.DEB.2.00.1211120913130.27834@uplift.swm.pp.se>	(swmike@swm.pp.se) <201211121456.qACEuWFN910936@shell01.TheWorld.com>
In-Reply-To: <201211121456.qACEuWFN910936@shell01.TheWorld.com>
Subject: RE: Newcomers [Was: Evolutionizing the IETF]
Date: Mon, 12 Nov 2012 15:18:07 -0000
Message-ID: <016701cdc0e8$ebc67550$c3535ff0$@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: AQGoBzHTAjvIFPOTsbz5jMjlM+lFDpgxwv1A
Content-Language: en-gb
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Nov 2012 15:18:08 -0000

Dale said:

> One way to build up enough credibility
> to get respected people to answer you is to do thankless jobs.  In
> most WGs, there are never enough people who are willing to read and
> provide detailed critiques of drafts.  (And believe me, almost all
> drafts need significant improvements of their presentation, and often
> of the technology.)  And the quality of your critiques of drafts is a
> good way to demonstrate your technical skills.

Yes, this is how I started.
Review drafts. Send questions, comments, proposals, and suggest text.
This is not a thankless task! You will be thanked for valuable input.

Adrian


From bertietf@bwijnen.net  Mon Nov 12 07:58:51 2012
Return-Path: <bertietf@bwijnen.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 41A7E21F8625 for <ietf@ietfa.amsl.com>; Mon, 12 Nov 2012 07:58:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.61
X-Spam-Level: 
X-Spam-Status: No, score=-101.61 tagged_above=-999 required=5 tests=[AWL=-0.870, BAYES_20=-0.74, 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 8MN1zycQuNmy for <ietf@ietfa.amsl.com>; Mon, 12 Nov 2012 07:58:50 -0800 (PST)
Received: from postgirl.ripe.net (postgirl.ipv6.ripe.net [IPv6:2001:67c:2e8:11::c100:1342]) by ietfa.amsl.com (Postfix) with ESMTP id 5F0CE21F8623 for <ietf@ietf.org>; Mon, 12 Nov 2012 07:58:49 -0800 (PST)
Received: from dodo.ripe.net ([193.0.23.4]) by postgirl.ripe.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from <bertietf@bwijnen.net>) id 1TXwPP-0007kU-5D for ietf@ietf.org; Mon, 12 Nov 2012 16:58:48 +0100
Received: from cat.ripe.net ([193.0.1.249] helo=guest12.guestnet.ripe.net) by dodo.ripe.net with esmtp (Exim 4.72) (envelope-from <bertietf@bwijnen.net>) id 1TXwPP-0002JV-09 for ietf@ietf.org; Mon, 12 Nov 2012 16:58:47 +0100
Message-ID: <50A11CB6.6000408@bwijnen.net>
Date: Mon, 12 Nov 2012 16:58:46 +0100
From: "Bert Wijnen (IETF)" <bertietf@bwijnen.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: New on RIPE Labs: Global Effect of Hurricane Sandy as Seen in RIPE Atlas
References: <50A118D7.1020006@ripe.net>
In-Reply-To: <50A118D7.1020006@ripe.net>
X-Forwarded-Message-Id: <50A118D7.1020006@ripe.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Anti-Virus: Kaspersky Anti-Virus for Linux Mail Server 5.6.48/RELEASE, bases: 20120425 #7816575, check: 20121112 clean
X-RIPE-Spam-Level: -
X-RIPE-Spam-Report: Spam Total Points:   -1.4 points pts rule name              description ---- ---------------------- ------------------------------------ -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP 1.5 SUBJ_AS_SEEN           Subject contains "As Seen" -1.9 BAYES_00               BODY: Bayes spam probability is 0 to 1% [score: 0.0000]
X-RIPE-Signature: 86ab03e524994f79ca2c75a176445dd41246395305bb4b0957bb229750c6a0cd
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Nov 2012 15:58:51 -0000

Emile Aben, a colleague of mine did some more analysis.

In this new RIPE Labs article he looks at some of the effects Hurricane
Sandy had on the Internet data plane, as we can see them in traceroutes
done by RIPE Atlas:

https://labs.ripe.net/Members/emileaben/ripe-atlas-hurricane-sandy-global-effects

I figured that some of you might find this interesting.
Bert

From azuremesa@gmail.com  Sat Nov 10 04:18:51 2012
Return-Path: <azuremesa@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F169F21F84D8; Sat, 10 Nov 2012 04:18:51 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S8YSpt0uazNR; Sat, 10 Nov 2012 04:18:51 -0800 (PST)
Received: from mail-ie0-f172.google.com (mail-ie0-f172.google.com [209.85.223.172]) by ietfa.amsl.com (Postfix) with ESMTP id 58BD821F84D6; Sat, 10 Nov 2012 04:18:51 -0800 (PST)
Received: by mail-ie0-f172.google.com with SMTP id 9so7885415iec.31 for <multiple recipients>; Sat, 10 Nov 2012 04:18:51 -0800 (PST)
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 :cc:content-type; bh=4hcsJvtm/KxOylSuqXT+nzxyoDabkpknKiwk+BY9F2s=; b=pbjFbZ/kzzy9oKxLLes1+26Dmnyj8g0mMNa8xKVrhaFTGWe2o5g54i+wKJy14FIMei OUZn6JBdPGQcqVHhf5V/Yqzi4WCMgMcJysrCDAE2H5a7/YDpRX/DvU8+yaZejM2NdqJh QN3/DNiLWBpw8Jox8GAgCs135fB9WPyoJWKoNxFR1gbYksi2gPTBR8QWFVSB0szi3o2H gHriF11JIqQ2VV/mLtOQhiKs5j1zYxhO7LGeRjIxcYX3VT9RAReAM9MXrEU6g7KTK6ja /v1sf4OIbhaqfxEBAb/u5qohptQAFEHrdLjtPDB2wIcFzCRZQSVbyJJLub+hG4wzHwNK mwEQ==
MIME-Version: 1.0
Received: by 10.43.98.196 with SMTP id cp4mr14279432icc.25.1352549930905; Sat, 10 Nov 2012 04:18:50 -0800 (PST)
Received: by 10.64.23.4 with HTTP; Sat, 10 Nov 2012 04:18:50 -0800 (PST)
In-Reply-To: <55D046F8-5DD2-42E8-9B8C-36C612C4B3F8@ietf.org>
References: <55D046F8-5DD2-42E8-9B8C-36C612C4B3F8@ietf.org>
Date: Sat, 10 Nov 2012 04:18:50 -0800
Message-ID: <CAPeNrjnFd655O4R+TzqZf3r_rmXWjGx+gQ8V1c4PdSTxDVkuNQ@mail.gmail.com>
Subject: Re: IESG Considering a Revision to NOTE WELL
From: bill manning <azuremesa@gmail.com>
To: IETF <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
X-Mailman-Approved-At: Mon, 12 Nov 2012 08:05:42 -0800
Cc: Keio <bmanning@sfc.keio.ac.jp>, IETF Announce <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 10 Nov 2012 12:18:52 -0000

is "...an IETF context..."  well defined?

/bill

On 11/6/12, IETF Chair <chair@ietf.org> wrote:
> The IESG is considering a revision to the NOTE WELL text.  Please review and
> comment.
>
> Russ
>
>
>
> === Proposed Revised NOTE WELL Text ===
>
> Note Well
>
> This summary is only meant to point you in the right direction, and
> doesn't have all the nuances. The IETF's IPR Policy is set forth in
> BCP 79; please read it carefully.
>
> The brief summary:
>   - By participating with the IETF, you agree to follow IETF processes.
>   - If you are aware that a contribution of yours (something you write,
>     say, or discuss in any IETF context) is covered by patents or patent
>     applications, you need to disclose that fact.
>   - You understand that meetings might be recorded, broadcast, and
>    publicly archived.
>
> For further information: Talk to a chair, ask an Area Director, or
> review  BCP 9 (on the Internet Standards Process), BCP 25 (on the
> Working Group processes), BCP 78 (on the IETF Trust), and BCP 79 (on
> Intellectual Property Rights in the IETF).

From rsk@gsp.org  Sat Nov 10 09:08:35 2012
Return-Path: <rsk@gsp.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE2BB21F8493 for <ietf@ietfa.amsl.com>; Sat, 10 Nov 2012 09:08:35 -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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LZz3B6KwnN0M for <ietf@ietfa.amsl.com>; Sat, 10 Nov 2012 09:08:35 -0800 (PST)
Received: from taos.firemountain.net (taos.firemountain.net [207.114.3.54]) by ietfa.amsl.com (Postfix) with ESMTP id E69C921F8496 for <ietf@ietf.org>; Sat, 10 Nov 2012 09:08:34 -0800 (PST)
Received: from gsp.org (bltmd-207.114.17.40.dsl.charm.net [207.114.17.40]) by taos.firemountain.net (8.14.5/8.14.5) with ESMTP id qAAH8Wwq026841 for <ietf@ietf.org>; Sat, 10 Nov 2012 12:08:33 -0500 (EST)
Date: Sat, 10 Nov 2012 12:08:26 -0500
From: Rich Kulawiec <rsk@gsp.org>
To: ietf@ietf.org
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
Message-ID: <20121110170826.GA24595@gsp.org>
References: <CADnDZ8-fjxfgJys8sE10DdZ08tB8HdaTQXbPj2d7-OuQOGi9Pg@mail.gmail.com> <CADnDZ8_v3M1fNtkOV4rU1F-iaMC+2qvKhR353vwESiQsfh70MQ@mail.gmail.com> <6.2.5.6.2.20121109074113.0b2000f8@resistor.net> <8C48B86A895913448548E6D15DA7553B19E215@xmb-rcd-x09.cisco.com> <509D910D.7060503@gmail.com> <509DA4E7.1090504@gmail.com> <509DA723.7030703@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <509DA723.7030703@gmail.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
X-Mailman-Approved-At: Mon, 12 Nov 2012 08:05:42 -0800
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 10 Nov 2012 17:08:36 -0000

On Fri, Nov 09, 2012 at 08:00:19PM -0500, Arturo Servin wrote:
>     People is asking how to evolve the IETF, well, one possibility is to
> start thinking global and to reach more people outside the common venues. 

Another is to not have any (physical) meetings, ever.  I've heard
all the arguments against this approach for years, and I think they're
all oudated: every kind of interaction that's possible in a physical
meeting is now possible in an online one.  It's simply a matter of
having the will to commit to the technology and to work through the
(no doubt numerous) issues that will surface while using it.

This facilitates more involvement.  It dramatically cuts costs.
It avoids the hassles and risks of travel, including the increasingly
privacy-hostile intrusions of various governments.  It's more flexible.
It allows near-global participation regardless of geography, schedule,
budget, etc.

And more than anything, it would show that the IETF is actually committed
to, you know, *using the Internet*.

---rsk

From dhc@dcrocker.net  Mon Nov 12 08:12:53 2012
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 220C521F862C; Mon, 12 Nov 2012 08:12:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.937
X-Spam-Level: 
X-Spam-Status: No, score=-4.937 tagged_above=-999 required=5 tests=[AWL=0.019,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, RCVD_IN_NJABL_PROXY=1.643]
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 EbtH-CPa7MJQ; Mon, 12 Nov 2012 08:12:52 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 4F74321F858A; Mon, 12 Nov 2012 08:12:52 -0800 (PST)
Received: from [192.168.1.6] (adsl-67-127-56-94.dsl.pltn13.pacbell.net [67.127.56.94]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id qACGCoGG029015 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 12 Nov 2012 08:12:51 -0800
Message-ID: <50A11FFF.3040401@dcrocker.net>
Date: Mon, 12 Nov 2012 08:12:47 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: bill manning <azuremesa@gmail.com>
Subject: Re: IESG Considering a Revision to NOTE WELL
References: <55D046F8-5DD2-42E8-9B8C-36C612C4B3F8@ietf.org> <CAPeNrjnFd655O4R+TzqZf3r_rmXWjGx+gQ8V1c4PdSTxDVkuNQ@mail.gmail.com>
In-Reply-To: <CAPeNrjnFd655O4R+TzqZf3r_rmXWjGx+gQ8V1c4PdSTxDVkuNQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Mon, 12 Nov 2012 08:12:51 -0800 (PST)
Cc: Keio <bmanning@sfc.keio.ac.jp>, IETF <ietf@ietf.org>, IETF Announce <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Nov 2012 16:12:53 -0000

On 11/10/2012 4:18 AM, bill manning wrote:
> is "...an IETF context..."  well defined?


For example, is a Bar BOF an IETF context?

What about a dinner among some attendees, on their own, during IETF week?

What about outside of IETF week?

What about a private email exchange by a couple of attendees, about an 
IETF topic?  Outside of IETF week?

And these really are questions for an attorney.

Sometimes, legal language that is ambiguous is helpful.  This isn't one 
of those times, since it needs to have clarity for average participants.

d/

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From joelja@bogus.com  Mon Nov 12 08:23:00 2012
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4AEA121F8654 for <ietf@ietfa.amsl.com>; Mon, 12 Nov 2012 08:23:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.099
X-Spam-Level: 
X-Spam-Status: No, score=-102.099 tagged_above=-999 required=5 tests=[AWL=0.500, 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 zfTnG-5TKdC1 for <ietf@ietfa.amsl.com>; Mon, 12 Nov 2012 08:22:59 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id A452721F8529 for <ietf@ietf.org>; Mon, 12 Nov 2012 08:22:59 -0800 (PST)
Received: from joels-MacBook-Air.local (c-98-234-216-143.hsd1.ca.comcast.net [98.234.216.143]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id qACGLaWL026716 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Mon, 12 Nov 2012 16:21:36 GMT (envelope-from joelja@bogus.com)
Message-ID: <50A12210.9000506@bogus.com>
Date: Mon, 12 Nov 2012 08:21:36 -0800
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
References: <CADnDZ8-fjxfgJys8sE10DdZ08tB8HdaTQXbPj2d7-OuQOGi9Pg@mail.gmail.com> <CADnDZ8_v3M1fNtkOV4rU1F-iaMC+2qvKhR353vwESiQsfh70MQ@mail.gmail.com> <9009A606-ACB8-4F25-992E-DF126822C591@checkpoint.com> <CADnDZ88BgQ03xOi4x1+16k6zKz0h_OyyJam-C=RVbrqz21crBQ@mail.gmail.com>
In-Reply-To: <CADnDZ88BgQ03xOi4x1+16k6zKz0h_OyyJam-C=RVbrqz21crBQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Mon, 12 Nov 2012 16:21:38 +0000 (UTC)
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Nov 2012 16:23:00 -0000

On 11/11/12 3:59 AM, Abdussalam Baryun wrote:
>   I don't think that thoes Canada and US participants are paying for
> the attendance, but their organisations, therefore, are we reducing
> the cost of other organisations, or we are interested to bring more
> participants.
Many participants, myself included are footing our own bill for attendance.

From wesley.george@twcable.com  Mon Nov 12 08:29:23 2012
Return-Path: <wesley.george@twcable.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3FA0B21F8618 for <ietf@ietfa.amsl.com>; Mon, 12 Nov 2012 08:29:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.115
X-Spam-Level: 
X-Spam-Status: No, score=0.115 tagged_above=-999 required=5 tests=[AWL=-0.911,  BAYES_05=-1.11, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368]
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 OfQtNOtR10BH for <ietf@ietfa.amsl.com>; Mon, 12 Nov 2012 08:29:22 -0800 (PST)
Received: from cdpipgw02.twcable.com (cdpipgw02.twcable.com [165.237.59.23]) by ietfa.amsl.com (Postfix) with ESMTP id 64EE521F860D for <ietf@ietf.org>; Mon, 12 Nov 2012 08:29:21 -0800 (PST)
X-SENDER-IP: 10.136.163.15
X-SENDER-REPUTATION: None
X-IronPort-AV: E=McAfee;i="5400,1158,6893"; a="450163203"
Received: from unknown (HELO PRVPEXHUB06.corp.twcable.com) ([10.136.163.15]) by cdpipgw02.twcable.com with ESMTP/TLS/RC4-MD5; 12 Nov 2012 11:28:56 -0500
Received: from PRVPEXVS15.corp.twcable.com ([10.136.163.78]) by PRVPEXHUB06.corp.twcable.com ([10.136.163.15]) with mapi; Mon, 12 Nov 2012 11:29:08 -0500
From: "George, Wes" <wesley.george@twcable.com>
To: Hector Santos <gmail.sant9442@winserver.com>, Mikael Abrahamsson <swmike@swm.pp.se>
Date: Mon, 12 Nov 2012 11:29:10 -0500
Subject: in-person vs remote participation (was: Newcomers [Was: Evolutionizing the IETF])
Thread-Topic: in-person vs remote participation (was: Newcomers [Was: Evolutionizing the IETF])
Thread-Index: Ac3A8tbgkPRn+CpNTvGOINlZYV/Bug==
Message-ID: <2671C6CDFBB59E47B64C10B3E0BD59230337252921@PRVPEXVS15.corp.twcable.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Nov 2012 16:29:23 -0000

PiBGcm9tOiBpZXRmLWJvdW5jZXNAaWV0Zi5vcmcgW21haWx0bzppZXRmLWJvdW5jZXNAaWV0Zi5v
cmddIE9uIEJlaGFsZiBPZg0KPiBIZWN0b3IgU2FudG9zDQo+DQo+IFRoZSBJRVRGIHNob3VsZCBi
ZSBsZWFkaW5nIHRoZSBjaGFyZ2UgZm9yIGVhc3kgdG8gdXNlLCBtdWx0aS1kZXZpY2UNCj4gcmVh
ZGluZXNzIGN5YmVyc3BhY2luZyB2aXJ0dWFsIG1lZXRpbmcgcGxhY2VzLCBpbmNsdWRpbmcgYmV0
dGVyDQo+IGVsZWN0cm9uaWMgZ3JvdXB3YXJlIGNvbGxhYm9yYXRpb24gdG9vbHMsIGV0Yy4gSXQg
aXMgdW5kb3VidGVkbHkgYW5kDQo+IGluZXZpdGFibHkgdGhlICJBY2hpbGxlcycgSGVlbCIgZm9y
IHRoZSBJRVRGIE1lZXRpbmcuICBTbyB0aGUgSUVURiBuZWVkcw0KPiB0byBlbWJyYWNlIGl0IG5v
dywgYmlnIHRpbWUsIGJlZm9yZSBpdHMgdG9vIGxhdGUuIFRoaXMgaW5jbHVkZXMgZ2V0dGluZw0K
PiBvbiBib2FyZCB3aXRoIG1lbWJlcnNoaXAgbW9kZWxzIHRvIHN1YnNpZGl6ZSB0aGUgYnVzaW5l
c3MgYW5kIGl0cw0KPiBmdXR1cmUuICBUaGlzIHNob3VsZG4ndCB0YWtlIGF3YXkgIkZhY2UgdG8g
RmFjZSIgY29tbXVuaWNhdGlvbnMgLSBpbg0KPiBmYWN0LCBpdCB3aWxsIGluY3JlYXNlIGl0LiAg
SXRzIG11Y2ggbW9yZSBkb2FibGUgd2l0aCB0b2RheSdzIGhpZ2hlcg0KPiB1bml2ZXJzYWwgYmFu
ZHdpZHRoIGFuZCB0aGUgSUVURiBuZWVkcyB0byBiZSBwcmltZSBleGFtcGxlcyBvZiB0aGUNCj4g
dmFyaW91cyB0ZWNobm9sb2d5IGl0IGlzIGhlbHBpbmcgcHV0IHRvZ2V0aGVyIGFuZCBzdGFuZGFy
ZGl6ZS4gIEluIGZhY3QsDQo+IHRoZSBJRVRGIGNhbiBwcm9iYWJseSBsZWFybiBhbmQgaGVscCBp
bXByb3ZlIGdyb3Vwd2FyZSBjb21tdW5pY2F0aW9ucw0KPiB3aXRoIG5ldyB3b3JraW5nIGdyb3Vw
cyBmb2N1c2luZyBvbiBncm91cHdhcmUuDQo+DQoNCltXRUddIGFzIHNvbWVvbmUgd2hvIG5vcm1h
bGx5IGF0dGVuZHMgbWVldGluZ3MgaW4gcGVyc29uLCBhbmQgaGFkIG5vIGNob2ljZSBidXQgdG8g
cGFydGljaXBhdGUgcmVtb3RlbHkgdGhpcyB0aW1lIG9uIGFjY291bnQgb2YgaW5qdXJ5LCBJIGFn
cmVlIHRoYXQgSUVURiBuZWVkcyB0byBiZSBmb2N1c2VkIG9uIHdheXMgdG8gaW1wcm92ZSByZW1v
dGUgcGFydGljaXBhdGlvbiBhcyBhIG1lYW5zIHRvIHJlZHVjZSB0aGUgYmFycmllciB0byBwYXJ0
aWNpcGF0aW9uIHRoYXQgb3VyIGN1cnJlbnQgdHJhdmVsIHJlcXVpcmVtZW50cyByZXByZXNlbnQu
IEhvd2V2ZXIsIHRoaXMgaXMgbm90IG9ubHkgYSB0ZWNobm9sb2d5IHByb2JsZW0uIFJlbW90ZSBw
YXJ0aWNpcGFudHMgc3VmZmVyIGZyb20gYSBjdWx0dXJhbCBwcm9ibGVtIHRoYXQgaXMgbWVyZWx5
IGJlaW5nIGV4YWNlcmJhdGVkIGJ5IHRoZSB0ZWNobm9sb2d5J3MgbGltaXRhdGlvbnMuIEl0IGlz
IGJ5IG5vIG1lYW5zIHVuaXF1ZSB0byB0aGUgSUVURiwgYmVjYXVzZSBJJ3ZlIGV4cGVyaWVuY2Vk
IGl0IHBsZW50eSBvZiB0aW1lcyB3aGlsZSB3b3JraW5nIGZvciBjb21wYW5pZXMgdGhhdCBoYXZl
IHJlbW90ZSBvZmZpY2VzIGFuZCB0ZWxld29ya2VycywgYnV0IHdlIGRlZmluaXRlbHkgbmVlZCB0
byBhY2tub3dsZWRnZSBpdCBhbmQgbG9vayBmb3Igc29sdXRpb25zIHRvIGl0IGlmIHdlJ3JlIGdv
aW5nIHRvIGJlIHN1Y2Nlc3NmdWwgd2l0aCByZW1vdGUgcGFydGljaXBhdGlvbi4gUmVtb3RlIHBh
cnRpY2lwYW50cyBhcmUgZmlndXJhdGl2ZWx5IChhbmQgb2Z0ZW4gbGl0ZXJhbGx5KSBpbnZpc2li
bGUsIGFuZCB0aGVyZWZvcmUgcGVvcGxlIGZvcmdldCBhYm91dCB0aGVtLCBhbmQgdGhleSBnZXQg
cmVsZWdhdGVkIHRvIHNlY29uZC1jbGFzcyBzdGF0dXMgYXMgYSBwYXJ0aWNpcGFudC4gRXZlbiBp
ZiBpdCdzIG9ubHkgc3ViY29uc2Npb3VzbHksIHRoZSBpbi1wZXJzb24gcGFydGljaXBhbnRzIGRv
bid0IHNlZSByZW1vdGUgcGFydGljaXBhbnRzIHRvIGJlICJhcyBjb21taXR0ZWQiIHRvIHBhcnRp
Y2lwYXRpb24gYXMgdGhvc2Ugd2hvIGdhdmUgdXAgYSB3ZWVrLCB0cmF2ZWxlZCwgcGFpZCBmb3Ig
aG90ZWwsIG1lYWxzLCByZWdpc3RyYXRpb24sIGV0Yy4gYW5kIG9mdGVuIHRoZSBsYWNrIG9mIGEg
ZmFjZSB0byBnbyB3aXRoIHRoZSBuYW1lIG1ha2VzIGEgdGFuZ2libGUgZGlmZmVyZW5jZSBpbiB0
aGUgaW50ZXJhY3Rpb25zLiBUaGUgb25seSByZWFzb24gdGhhdCByZW1vdGUgcGFydGljaXBhdGlv
biBldmVuIHNvcnQgb2Ygd29ya3MgaW4gdGhlIElFVEYgaXMgdGhhdCB0aGVyZSBhcmUgZW5vdWdo
IHBlb3BsZSB3aG8gaGF2ZSBkb25lIGl0IGJlZm9yZSBhbmQga25vdyBob3cgbXVjaCBpdCBjYW4g
c3VjayB3aGVuIGl0IGdvZXMgcG9vcmx5IHRoYXQgdGhleSBtYWtlIGEgY29uc2Npb3VzIGVmZm9y
dCB0byB0cmVhdCByZW1vdGUgcGFydGljaXBhbnRzIGFzIGFuIGVxdWFsIHBhcnQgb2YgdGhlIG1l
ZXRpbmcgYXR0ZW5kZWVzIHN1Y2ggdGhhdCB0aGV5IGVuZm9yY2UgZ29vZCBtaWMgZXRpcXVldHRl
LCB2b2x1bnRlZXIgdG8gYmUgamFiYmVyIHNjcmliZXMsIGVuc3VyZSBwcmVzZW50YXRpb25zIGFy
ZSBwb3N0ZWQsIGV0Yy4gZXZlbiB3aGVuIHRoZSBXRyBjaGFpcnMgZmFpbCB0byBkbyBzby4gV2hp
bGUgSSBhbSB2ZXJ5IGdyYXRlZnVsIGZvciB0aG9zZSBmb2xrcywgdGhhdCdzIGFuIHVucmVsaWFi
bGUgbWVjaGFuaXNtLCBvbmUgdGhhdCBmYWlsZWQgb24gbnVtZXJvdXMgb2NjYXNpb25zIGluIHNl
dmVyYWwgV0dzIEkgdHJpZWQgdG8gcGFydGljaXBhdGUgaW4gdGhpcyBwYXN0IHdlZWsuIEkgZG9u
J3QgcG9zdCB0aGlzIG1lc3NhZ2UgdG8gd2hpbmUsIGJ1dCB0byBub3RlIHRoYXQgaWYgd2UncmUg
Z29pbmcgdG8gZ2V0IHNlcmlvdXMgYWJvdXQgcmVtb3RlIHBhcnRpY2lwYXRpb24sIGl0J3Mgbm90
IGFsbCBhYm91dCBzaGlueSBuZXcgdG9vbHMsIGJ1dCBpbnN0ZWFkIHRoZSBtZW50YWxpdHkgb2Yg
dGhvc2Ugd2hvIHN0aWxsIHBhcnRpY2lwYXRlIGluIHBlcnNvbi4gVGhlcmUgYXJlIG90aGVyIGxl
c3MgdGFuZ2libGUgaXNzdWVzIHRoYXQgSSdsbCBhZGRyZXNzIGluIGFub3RoZXIgbWVzc2FnZS4N
Cg0KV2VzIEdlb3JnZQ0KDQpUaGlzIEUtbWFpbCBhbmQgYW55IG9mIGl0cyBhdHRhY2htZW50cyBt
YXkgY29udGFpbiBUaW1lIFdhcm5lciBDYWJsZSBwcm9wcmlldGFyeSBpbmZvcm1hdGlvbiwgd2hp
Y2ggaXMgcHJpdmlsZWdlZCwgY29uZmlkZW50aWFsLCBvciBzdWJqZWN0IHRvIGNvcHlyaWdodCBi
ZWxvbmdpbmcgdG8gVGltZSBXYXJuZXIgQ2FibGUuIFRoaXMgRS1tYWlsIGlzIGludGVuZGVkIHNv
bGVseSBmb3IgdGhlIHVzZSBvZiB0aGUgaW5kaXZpZHVhbCBvciBlbnRpdHkgdG8gd2hpY2ggaXQg
aXMgYWRkcmVzc2VkLiBJZiB5b3UgYXJlIG5vdCB0aGUgaW50ZW5kZWQgcmVjaXBpZW50IG9mIHRo
aXMgRS1tYWlsLCB5b3UgYXJlIGhlcmVieSBub3RpZmllZCB0aGF0IGFueSBkaXNzZW1pbmF0aW9u
LCBkaXN0cmlidXRpb24sIGNvcHlpbmcsIG9yIGFjdGlvbiB0YWtlbiBpbiByZWxhdGlvbiB0byB0
aGUgY29udGVudHMgb2YgYW5kIGF0dGFjaG1lbnRzIHRvIHRoaXMgRS1tYWlsIGlzIHN0cmljdGx5
IHByb2hpYml0ZWQgYW5kIG1heSBiZSB1bmxhd2Z1bC4gSWYgeW91IGhhdmUgcmVjZWl2ZWQgdGhp
cyBFLW1haWwgaW4gZXJyb3IsIHBsZWFzZSBub3RpZnkgdGhlIHNlbmRlciBpbW1lZGlhdGVseSBh
bmQgcGVybWFuZW50bHkgZGVsZXRlIHRoZSBvcmlnaW5hbCBhbmQgYW55IGNvcHkgb2YgdGhpcyBF
LW1haWwgYW5kIGFueSBwcmludG91dC4NCg==

From ynir@checkpoint.com  Mon Nov 12 09:09:45 2012
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA2E821F8618 for <ietf@ietfa.amsl.com>; Mon, 12 Nov 2012 09:09:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 RAQ--CB0CLmU for <ietf@ietfa.amsl.com>; Mon, 12 Nov 2012 09:09:45 -0800 (PST)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id C526621F85ED for <ietf@ietf.org>; Mon, 12 Nov 2012 09:09:44 -0800 (PST)
Received: from IL-EX10.ad.checkpoint.com ([194.29.34.147]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id qACH9T3t024570; Mon, 12 Nov 2012 19:09:34 +0200
X-CheckPoint: {50A12A58-1-1B221DC2-1FFFF}
Received: from IL-EX10.ad.checkpoint.com ([169.254.2.194]) by IL-EX10.ad.checkpoint.com ([169.254.2.194]) with mapi id 14.02.0318.004; Mon, 12 Nov 2012 19:09:29 +0200
From: Yoav Nir <ynir@checkpoint.com>
To: joel jaeggli <joelja@bogus.com>
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
Thread-Topic: Newcomers [Was: Evolutionizing the IETF]
Thread-Index: Ac3ABBv9azFBUP+KSLOLrbDo1lYx/AA3Om8AAAGr9gA=
Date: Mon, 12 Nov 2012 17:09:29 +0000
Message-ID: <4613980CFC78314ABFD7F85CC3027721012EDF@IL-EX10.ad.checkpoint.com>
References: <CADnDZ8-fjxfgJys8sE10DdZ08tB8HdaTQXbPj2d7-OuQOGi9Pg@mail.gmail.com> <CADnDZ8_v3M1fNtkOV4rU1F-iaMC+2qvKhR353vwESiQsfh70MQ@mail.gmail.com> <9009A606-ACB8-4F25-992E-DF126822C591@checkpoint.com> <CADnDZ88BgQ03xOi4x1+16k6zKz0h_OyyJam-C=RVbrqz21crBQ@mail.gmail.com> <50A12210.9000506@bogus.com>
In-Reply-To: <50A12210.9000506@bogus.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [91.90.139.85]
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <C0524960E190B14BACDCFCF99C84151F@ad.checkpoint.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: ietf <ietf@ietf.org>, Abdussalam Baryun <abdussalambaryun@gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Nov 2012 17:09:45 -0000

On Nov 12, 2012, at 6:21 PM, joel jaeggli wrote:

> On 11/11/12 3:59 AM, Abdussalam Baryun wrote:
>>  I don't think that thoes Canada and US participants are paying for
>> the attendance, but their organisations, therefore, are we reducing
>> the cost of other organisations, or we are interested to bring more
>> participants.
> Many participants, myself included are footing our own bill for attendanc=
e.

And I'm guessing that this is much more common in the US than in Asia, and =
somewhat more common than in Europe.

OTOH US companies tend to have bigger travel budgets.

OTTH US companies tend to consider travel abroad as weird thing much more t=
han European or Asian companies.

My personal experience (which I think can be proven with some airfare site)=
 is that travel to the US is considerably cheaper and easier than similar-l=
ength travel to other places.

Airfare tends to be cheaper, because there are a lot more flights to the US=
 than to pretty much anywhere else, with many more airlines competing. So a=
 flight to Prague would be cheaper for me, but a flight to China, India or =
Japan would be much more expensive.

The US has some expensive hotels, but it's also much easier to find cheaper=
 hotels. We can (and have) meet a block away from Disneyland, and I can fin=
d a cheap motel less than 2 km away. This is considerably harder in Europe,=
 and pretty much impossible for a non-local in Asia.

Everyone's mileage varies, of course, and US immigration tends to be more b=
othersome than most, but I think a meeting in the US or Canada leaves the l=
east amount of people not able to attend. Paris and Prague are a close seco=
nd. I have no idea how easy it would be to find a reasonably-priced hotel i=
n London, for example.

Yoav


From wesley.george@twcable.com  Mon Nov 12 09:16:04 2012
Return-Path: <wesley.george@twcable.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A33321F8696 for <ietf@ietfa.amsl.com>; Mon, 12 Nov 2012 09:16:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.044
X-Spam-Level: 
X-Spam-Status: No, score=-0.044 tagged_above=-999 required=5 tests=[AWL=-0.570, BAYES_20=-0.74, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, RCVD_IN_DNSWL_LOW=-1, SARE_RMML_Stock10=0.13]
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 GrNi6BaC7G2s for <ietf@ietfa.amsl.com>; Mon, 12 Nov 2012 09:16:03 -0800 (PST)
Received: from cdpipgw01.twcable.com (cdpipgw01.twcable.com [165.237.59.22]) by ietfa.amsl.com (Postfix) with ESMTP id 8364D21F85D5 for <ietf@ietf.org>; Mon, 12 Nov 2012 09:16:03 -0800 (PST)
X-SENDER-IP: 10.136.163.12
X-SENDER-REPUTATION: None
X-IronPort-AV: E=McAfee;i="5400,1158,6894"; a="469236996"
Received: from unknown (HELO PRVPEXHUB03.corp.twcable.com) ([10.136.163.12]) by cdpipgw01.twcable.com with ESMTP/TLS/RC4-MD5; 12 Nov 2012 12:15:46 -0500
Received: from PRVPEXVS15.corp.twcable.com ([10.136.163.78]) by PRVPEXHUB03.corp.twcable.com ([10.136.163.12]) with mapi; Mon, 12 Nov 2012 12:15:55 -0500
From: "George, Wes" <wesley.george@twcable.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>, "ietf@ietf.org" <ietf@ietf.org>
Date: Mon, 12 Nov 2012 12:15:56 -0500
Subject: in-person vs remote participation (was: Newcomers [Was: Evolutionizing the IETF])
Thread-Topic: in-person vs remote participation (was: Newcomers [Was: Evolutionizing the IETF])
Thread-Index: Ac3A+Vsv5fvbNg53QeSITgEzws2kaA==
Message-ID: <2671C6CDFBB59E47B64C10B3E0BD592303372529DB@PRVPEXVS15.corp.twcable.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Nov 2012 17:16:04 -0000

> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> Mikael Abrahamsson
>
> Personally I believe there could be value in describing what the value
> is to attend the meeting physically. I attended the last meeting in
> Stockholm because it meant I only had to pay the entrence fee, since I
> live there.
>
> Getting buy-in from management to allow me to go for a week somewhere
> and not be available in the office, pay for hotel and travel, plus the
> entrence fee, it's hard to justify to management. What is a good answer
> to the question "why?".
>
[WEG] I've had to justify my participation in IETF multiple times in the la=
st few years, and while official duties as a presenter or WG chair made jus=
tifying travel easier, prior to that point, I had to try to articulate exac=
tly this. As noted in my other message, this was the first remote meeting f=
or a while for me, and it put into sharp relief the difference between in-p=
erson and remote participation. While most folks do indeed attend IETF to a=
ttend WG meetings, I think that's only part of the story, and you're right,=
 it's something we need to do a better job of articulating and considering =
when we attempt to replicate IETF attendance virtually or help new particip=
ants feel included.

First and foremost, the act of getting away from the office and the financi=
al and time commitments involved in traveling to a physical meeting a few t=
imes a year tends to reinforce the need to "prepare" for the meeting by rea=
ding drafts, catching up on IETF work that has languished, etc. The travel =
and meeting schedule imposes a deadline of sorts, in addition to providing =
physical separation that allows people to reprioritize their work so that f=
or that week or so, $dayjob becomes secondary to focusing on what's happeni=
ng in IETF, since everyone "traveled all that way" and "spent all that mone=
y" to meet together. The proximity provides an excuse to get work done, whe=
ther in a WG meeting, or sitting in the hall collaborating with a co-author=
 in real-time. I don't know how you replicate that virtually, especially in=
 the extremes of timezone differential. I know for me, life intrudes a lot =
when I haven't physically *left* my normal location and therefore I should =
be available for the things I would normally do when I am home or in the of=
fice. Perhaps if we move to a virtual-only model, we would be able to sprea=
d the work out in smaller chunks over more time so that it's more manageabl=
e as a portion of your overall workload, or perhaps we keep the defined mee=
ting time as a way to ensure coordination across many timezones, I don't kn=
ow.

The other things that become important are the "hallway track" and the "man=
y fine lunches and dinners". Those come up when talking about attending IET=
F in person, but often it's meant to imply that those involved are there fo=
r the wrong reasons (i.e. IETF as company-sponsored tourism or job search) =
rather than to acknowledge its value in ensuring that IETF does make progre=
ss by forging personal and professional relationships between its participa=
nts. There is so much networking that happens during those that is mostly l=
ost to remote participants, and it really is invaluable. Whether it's tryin=
g to work out a compromise on a particularly contentious part of a draft, o=
r stumbling across a problem or solution in a freewheeling conversation, or=
 just talking shop with like-minded folks, I find that this makes IETF a mu=
ch more rewarding experience. I also find that this makes it easier to make=
 progress in WGs when limited to low-bandwidth communications channels like=
 email, because you now know the other people involved. In person attendanc=
e, food and drink provide the opportunity, and are the means, rather than t=
he end. But that requires you to know people well enough at least professio=
nally that you can take advantage of that. I can see that being challenging=
 for those who are newcomers or have only met someone virtually. I am quite=
 sure that there are ways to replicate those more unofficial/social interac=
tions virtually with the improvements in video conferencing and telepresenc=
e technology, but I'm not sure it's possible to get past the strong psychol=
ogy that makes doing it over food and drink more effective.

The whole meatspace vs cyberspace argument has been going on ever since the=
re has been a cyberspace, so I'm not going to act like this is new, but I t=
hink we're getting to the point now where the technology is catching up wit=
h the science fiction portrayal such that it's worth having the discussion =
again.

Wes George

This E-mail and any of its attachments may contain Time Warner Cable propri=
etary information, which is privileged, confidential, or subject to copyrig=
ht belonging to Time Warner Cable. This E-mail is intended solely for the u=
se of the individual or entity to which it is addressed. If you are not the=
 intended recipient of this E-mail, you are hereby notified that any dissem=
ination, distribution, copying, or action taken in relation to the contents=
 of and attachments to this E-mail is strictly prohibited and may be unlawf=
ul. If you have received this E-mail in error, please notify the sender imm=
ediately and permanently delete the original and any copy of this E-mail an=
d any printout.

From framefritti@gmail.com  Mon Nov 12 09:33:05 2012
Return-Path: <framefritti@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8309D21F862E for <ietf@ietfa.amsl.com>; Mon, 12 Nov 2012 09:33:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.534
X-Spam-Level: 
X-Spam-Status: No, score=-3.534 tagged_above=-999 required=5 tests=[AWL=-0.065, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, SARE_RMML_Stock10=0.13]
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 A7mV+k0zg8N3 for <ietf@ietfa.amsl.com>; Mon, 12 Nov 2012 09:33:04 -0800 (PST)
Received: from mail-ie0-f172.google.com (mail-ie0-f172.google.com [209.85.223.172]) by ietfa.amsl.com (Postfix) with ESMTP id 6C5C421F8472 for <ietf@ietf.org>; Mon, 12 Nov 2012 09:32:58 -0800 (PST)
Received: by mail-ie0-f172.google.com with SMTP id 9so10432496iec.31 for <ietf@ietf.org>; Mon, 12 Nov 2012 09:32:58 -0800 (PST)
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:content-transfer-encoding; bh=tJDs+EIPCEuNgqFsH4YACfw1hUmlR4FQ3Lgb+FTx+ag=; b=DqNY7ZoBm6CwrQi5fqyk2VZeIjmOsvMgEgAav4aznls1Og9o7v5JYiiD5u3AXc1Fa1 MuyE4Fuvs606F1dXvSV4ZXuExp2TmVPkAPvWsvCRwoW+UEmgLFfugBEiEuBuU6tuGtFT 7FL4yAjmB4jBfGzQ3et0DpOTnNT3kSm3CuTJNP4ZM49vm1ke8yHg/HeyKfbaU3aVBWYz qvzhbvNnHZ++Pnl4AhrxMOtLRZ6fV6plYYpDwh6tIyKVKlDiIzds+JzmWqXbHq6SiO3u JOezF+ddLjnwrk+EeNrzVg7pgedowJR85OHkqCeyZZGEj5DlrEaR0CJXoSU0oFqEe/uN J+Sw==
MIME-Version: 1.0
Received: by 10.50.36.200 with SMTP id s8mr8584685igj.25.1352741578050; Mon, 12 Nov 2012 09:32:58 -0800 (PST)
Received: by 10.64.98.202 with HTTP; Mon, 12 Nov 2012 09:32:58 -0800 (PST)
In-Reply-To: <2671C6CDFBB59E47B64C10B3E0BD592303372529DB@PRVPEXVS15.corp.twcable.com>
References: <2671C6CDFBB59E47B64C10B3E0BD592303372529DB@PRVPEXVS15.corp.twcable.com>
Date: Mon, 12 Nov 2012 18:32:58 +0100
Message-ID: <CABSMSPWrzOhsULOjUYaNaiVwx9euKngYts2kgYMnns1a=HuAXA@mail.gmail.com>
Subject: Re: in-person vs remote participation (was: Newcomers [Was: Evolutionizing the IETF])
From: Riccardo Bernardini <framefritti@gmail.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Nov 2012 17:33:05 -0000

On Mon, Nov 12, 2012 at 6:15 PM, George, Wes <wesley.george@twcable.com> wr=
ote:
>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
>> Mikael Abrahamsson
>>
>> Personally I believe there could be value in describing what the value
>> is to attend the meeting physically. I attended the last meeting in
>> Stockholm because it meant I only had to pay the entrence fee, since I
>> live there.
>>
>> Getting buy-in from management to allow me to go for a week somewhere
>> and not be available in the office, pay for hotel and travel, plus the
>> entrence fee, it's hard to justify to management. What is a good answer
>> to the question "why?".
>>
> [WEG] I've had to justify my participation in IETF multiple times in the =
last few years, and while official duties as a presenter or WG chair made j=
ustifying travel easier, prior to that point, I had to try to articulate ex=
actly this. As noted in my other message, this was the first remote meeting=
 for a while for me, and it put into sharp relief the difference between in=
-person and remote participation. While most folks do indeed attend IETF to=
 attend WG meetings, I think that's only part of the story, and you're righ=
t, it's something we need to do a better job of articulating and considerin=
g when we attempt to replicate IETF attendance virtually or help new partic=
ipants feel included.
>
> First and foremost, the act of getting away from the office and the finan=
cial and time commitments involved in traveling to a physical meeting a few=
 times a year tends to reinforce the need to "prepare" for the meeting by r=
eading drafts, catching up on IETF work that has languished, etc. The trave=
l and meeting schedule imposes a deadline of sorts, in addition to providin=
g physical separation that allows people to reprioritize their work so that=
 for that week or so, $dayjob becomes secondary to focusing on what's happe=
ning in IETF, since everyone "traveled all that way" and "spent all that mo=
ney" to meet together. The proximity provides an excuse to get work done, w=
hether in a WG meeting, or sitting in the hall collaborating with a co-auth=
or in real-time. I don't know how you replicate that virtually, especially =
in the extremes of timezone differential. I know for me, life intrudes a lo=
t when I haven't physically *left* my normal location and therefore I shoul=
d be available for the things I would normally do when I am home or in the =
office. Perhaps if we move to a virtual-only model, we would be able to spr=
ead the work out in smaller chunks over more time so that it's more managea=
ble as a portion of your overall workload, or perhaps we keep the defined m=
eeting time as a way to ensure coordination across many timezones, I don't =
know.
>
> The other things that become important are the "hallway track" and the "m=
any fine lunches and dinners". Those come up when talking about attending I=
ETF in person, but often it's meant to imply that those involved are there =
for the wrong reasons (i.e. IETF as company-sponsored tourism or job search=
) rather than to acknowledge its value in ensuring that IETF does make prog=
ress by forging personal and professional relationships between its partici=
pants. There is so much networking that happens during those that is mostly=
 lost to remote participants, and it really is invaluable. Whether it's try=
ing to work out a compromise on a particularly contentious part of a draft,=
 or stumbling across a problem or solution in a freewheeling conversation, =
or just talking shop with like-minded folks, I find that this makes IETF a =
much more rewarding experience. I also find that this makes it easier to ma=
ke progress in WGs when limited to low-bandwidth communications channels li=
ke email, because you now know the other people involved. In person attenda=
nce, food and drink provide the opportunity, and are the means, rather than=
 the end. But that requires you to know people well enough at least profess=
ionally that you can take advantage of that. I can see that being challengi=
ng for those who are newcomers or have only met someone virtually. I am qui=
te sure that there are ways to replicate those more unofficial/social inter=
actions virtually with the improvements in video conferencing and teleprese=
nce technology, but I'm not sure it's possible to get past the strong psych=
ology that makes doing it over food and drink more effective.

Let me add my own experience here, related to a different environment
(scientific conferences), but also very similar to yours.  Usually, if
I go to a conference it is because I have a paper to present, but that
it is not the only payback of being there.  There is the hall (or bar)
talking with old colleagues of mine, there is the casual meeting of
other researchers (old and young) working in my field with which I
exchange experiences, point of view and maybe a new collaboration can
be born.  Actually, I do not know how this could be replicated with an
online tool.

Let's face it: we are social animals, evolved with  "socialization
tools" that work best in a face-to-face context.

>
> The whole meatspace vs cyberspace argument has been going on ever since t=
here has been a cyberspace, so I'm not going to act like this is new, but I=
 think we're getting to the point now where the technology is catching up w=
ith the science fiction portrayal such that it's worth having the discussio=
n again.
>
> Wes George
>
> This E-mail and any of its attachments may contain Time Warner Cable prop=
rietary information, which is privileged, confidential, or subject to copyr=
ight belonging to Time Warner Cable. This E-mail is intended solely for the=
 use of the individual or entity to which it is addressed. If you are not t=
he intended recipient of this E-mail, you are hereby notified that any diss=
emination, distribution, copying, or action taken in relation to the conten=
ts of and attachments to this E-mail is strictly prohibited and may be unla=
wful. If you have received this E-mail in error, please notify the sender i=
mmediately and permanently delete the original and any copy of this E-mail =
and any printout.

From melinda.shore@gmail.com  Mon Nov 12 09:42:29 2012
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6EF5B21F86CE for <ietf@ietfa.amsl.com>; Mon, 12 Nov 2012 09:42:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.703
X-Spam-Level: 
X-Spam-Status: No, score=-3.703 tagged_above=-999 required=5 tests=[AWL=-0.104, 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 QVTlOe6ZgD4X for <ietf@ietfa.amsl.com>; Mon, 12 Nov 2012 09:42:28 -0800 (PST)
Received: from mail-da0-f44.google.com (mail-da0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id E442721F868B for <ietf@ietf.org>; Mon, 12 Nov 2012 09:42:28 -0800 (PST)
Received: by mail-da0-f44.google.com with SMTP id h15so2925010dan.31 for <ietf@ietf.org>; Mon, 12 Nov 2012 09:42:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=vcLYhUmlLOoPxYKknxQQ8ZOeOmgPiKPygM16Icc71LE=; b=WuN5Tz9cGyp752kLHocvzQUBrv0kLTyg887Y4/uyT0ZdOLMVugI1c0KiZ0+e5jXo1d 6sGMExlj8vJQYI/lfac/g0VmHy3ZeIdCJXLNsqqoldaR3l9C8ysSVrBOyGWqgJ0AyUX8 CTjXeP8FuuQsx2PZ4JWpYShwZM/tkYOzI8feTvDV9vlpzh4vaym6uJfIAi+6tUcd2zI1 RVwkTxNOQI0wQ7CYCrmxs5i9+ZZ01yVs3w/y2Y2MihIYdDMNmJrnlKKt0ergDN0TqeRD a8rNTdqDmtXxYO3T+bKHlTD2NM0bNRx6reaNvNBmMnRRNiSi1XlUawR/p4XWQ/O4f2vi qlTA==
Received: by 10.68.202.7 with SMTP id ke7mr13895413pbc.114.1352742148672; Mon, 12 Nov 2012 09:42:28 -0800 (PST)
Received: from spandex.local (216-67-71-89-rb1.fai.dsl.dynamic.acsalaska.net. [216.67.71.89]) by mx.google.com with ESMTPS id oi2sm4487275pbb.62.2012.11.12.09.42.27 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 12 Nov 2012 09:42:28 -0800 (PST)
Message-ID: <50A13502.1070202@gmail.com>
Date: Mon, 12 Nov 2012 08:42:26 -0900
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: in-person vs remote participation
References: <2671C6CDFBB59E47B64C10B3E0BD592303372529DB@PRVPEXVS15.corp.twcable.com> <CABSMSPWrzOhsULOjUYaNaiVwx9euKngYts2kgYMnns1a=HuAXA@mail.gmail.com>
In-Reply-To: <CABSMSPWrzOhsULOjUYaNaiVwx9euKngYts2kgYMnns1a=HuAXA@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Nov 2012 17:42:29 -0000

On 11/12/12 8:32 AM, Riccardo Bernardini wrote:
> Let me add my own experience here, related to a different
> environment (scientific conferences), but also very similar to yours.
> Usually, if I go to a conference it is because I have a paper to
> present, but that it is not the only payback of being there.  There
> is the hall (or bar) talking with old colleagues of mine, there is
> the casual meeting of other researchers (old and young) working in my
> field with which I exchange experiences, point of view and maybe a
> new collaboration can be born.  Actually, I do not know how this
> could be replicated with an online tool.

Well, I think it's important to be clear that IETF meetings are working
meetings and they exist largely to progress documents, so the goals are
somewhat different.  I think that at this point I've done the remote
participation thing as much as anybody and from my perspective the main
problem is not the tools but that the quality of the experience varies
enormously with the attention/skill of the session chairs.  Some are
attentive to remote participants, some don't even bother to acknowledge
we exist.  There's a WG chairs wiki page on facilitating remote
participation at
http://wiki.tools.ietf.org/group/wgchairs/wiki/RemoteParticipation.

I've also had very good experiences using email to make the kind of
contacts you've mentioned - something comes up in a session and sending
out-of-band email directly to the person who said something interesting.

In-person participation brings with it benefits that remote
participation doesn't (and is mandatory for people in certain roles).
But the cost-benefit tradeoff?  I'm not sure, frankly.

Melinda

From worley@shell01.TheWorld.com  Mon Nov 12 09:46:04 2012
Return-Path: <worley@shell01.TheWorld.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A1F5321F8618 for <ietf@ietfa.amsl.com>; Mon, 12 Nov 2012 09:46:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.982
X-Spam-Level: 
X-Spam-Status: No, score=-1.982 tagged_above=-999 required=5 tests=[AWL=-0.491, BAYES_05=-1.11, RCVD_IN_DNSWL_LOW=-1, RCVD_IN_SORBS_WEB=0.619]
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 kdf5C9ZFx0-V for <ietf@ietfa.amsl.com>; Mon, 12 Nov 2012 09:46:03 -0800 (PST)
Received: from TheWorld.com (pcls6.std.com [192.74.137.146]) by ietfa.amsl.com (Postfix) with ESMTP id 7824D21F8609 for <ietf@ietf.org>; Mon, 12 Nov 2012 09:46:02 -0800 (PST)
Received: from shell.TheWorld.com (root@shell01.theworld.com [192.74.137.71]) by TheWorld.com (8.14.5/8.14.5) with ESMTP id qACHjjQs001766; Mon, 12 Nov 2012 12:45:47 -0500
Received: from shell01.TheWorld.com (localhost.theworld.com [127.0.0.1]) by shell.TheWorld.com (8.13.6/8.12.8) with ESMTP id qACHjj7W919699; Mon, 12 Nov 2012 12:45:45 -0500 (EST)
Received: (from worley@localhost) by shell01.TheWorld.com (8.13.6/8.13.6/Submit) id qACHjiXS919660; Mon, 12 Nov 2012 12:45:44 -0500 (EST)
Date: Mon, 12 Nov 2012 12:45:44 -0500 (EST)
Message-Id: <201211121745.qACHjiXS919660@shell01.TheWorld.com>
From: worley@ariadne.com (Dale R. Worley)
Sender: worley@ariadne.com (Dale R. Worley)
To: Arturo Servin <arturo.servin@gmail.com>, ietf@ietf.org
In-reply-to: <509DA723.7030703@gmail.com> (arturo.servin@gmail.com)
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Nov 2012 17:46:04 -0000

> From: Arturo Servin <arturo.servin@gmail.com>
> 
> Your comment just reinforce my perception that the IETF is not
> interested in being an global organization of standards.
> 
> People is asking how to evolve the IETF, well, one possibility is to
> start thinking global and to reach more people outside the common
> venues. It is more expensive, more complex, yes. But in my opinion is
> worthy if we really want to show that we care about the multistakeholder
> model that we preach.

In my opinion, the *location* of IETF meetings is not important for
the technological openness of the standards, but it *is* important
for its *symbolism*.  My observation is that members have been
supportive of attempts to hold IETF meetings in diverse locations, but
there are constraints that limit the locations that are practical.

I am in no way involved with IETF site selection, but based on the
extensive discussions of site selection on this mailing list, the
constraints seem to be as follows.  The list suggests some things that
individuals can do to help find suitable locations, which I've listed
at the end.

    The meetings require a certain number of hotel rooms, a fairly large
    array of meeting rooms, and large common spaces, in one or a small
    cluster of hotels.  (These arrangements are fairly easy to find in
    North America and Europe, but are much less common in the rest of the
    world.)

    The hotel has to be willing to allow the IETF to install its wireless
    network and to take control of the hotel's Internet connectivity.

    Members desire locations that offer tourism possibilities, which
    generally means that the meeting site is in or near a city center.

    Because IETF participation is not of immediate commercial value to the
    employers of most participants, cost is of significant concern.  In
    practice, the cost and availability of air transportation seems to be
    the most variable factor, and the less international traffic to a
    given location, the more expensive air fares seem to be.  (You can
    explore the available air fares at http://matrix.itasoftware.com/search.htm.)

    The meeting fees cover only part of the meeting costs, so it is
    necessary to find sponsors to pay the remainder of the costs.  The
    sponsors usually are associated with the meeting location in some way.
    Since finding sponsors is difficult, meeting locations are harder to
    set than meeting dates.

What an individual can do to encourage selecting a particular location
is to find hotels that have the necessary meeting spaces.  If
possible, it would be helpful to determine that the management would
be willing to let the IETF take over their network.  Most importantly,
a local individual can find local sponsors for the meeting.

Dale

From adrian@olddog.co.uk  Mon Nov 12 09:52:36 2012
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 943BA21F8679 for <ietf@ietfa.amsl.com>; Mon, 12 Nov 2012 09:52:36 -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 xL+zwBE1-zkl for <ietf@ietfa.amsl.com>; Mon, 12 Nov 2012 09:52:36 -0800 (PST)
Received: from asmtp5.iomartmail.com (asmtp5.iomartmail.com [62.128.201.176]) by ietfa.amsl.com (Postfix) with ESMTP id A2DD621F866B for <ietf@ietf.org>; Mon, 12 Nov 2012 09:52:35 -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 qACHqQO2004577;  Mon, 12 Nov 2012 17:52:26 GMT
Received: from 950129200 ([149.254.235.205]) (authenticated bits=0) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id qACHqK1t004508 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 12 Nov 2012 17:52:25 GMT
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <dcrocker@bbiw.net>, "'bill manning'" <azuremesa@gmail.com>
References: <55D046F8-5DD2-42E8-9B8C-36C612C4B3F8@ietf.org>	<CAPeNrjnFd655O4R+TzqZf3r_rmXWjGx+gQ8V1c4PdSTxDVkuNQ@mail.gmail.com> <50A11FFF.3040401@dcrocker.net>
In-Reply-To: <50A11FFF.3040401@dcrocker.net>
Subject: RE: IESG Considering a Revision to NOTE WELL
Date: Mon, 12 Nov 2012 17:52:10 -0000
Message-ID: <019601cdc0fe$7bbb96d0$7332c470$@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: AQDY+wvClJPAlqq2E5BFzs8DMdIGLQHtPli9AW77uGSZtSKdoA==
Content-Language: en-gb
Cc: 'IETF' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Nov 2012 17:52:36 -0000

I think you miss the point of "This summary is only meant to point you in the
right direction, and doesn't have all the nuances. The IETF's IPR Policy is set
forth in BCP 79; please read it carefully."

That point is: this Note Well is not intended to reproduce the entirety of
BCP79.

Adrian

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Dave
> Crocker
> Sent: 12 November 2012 16:13
> To: bill manning
> Cc: Keio; IETF; IETF Announce
> Subject: Re: IESG Considering a Revision to NOTE WELL
> 
> 
> On 11/10/2012 4:18 AM, bill manning wrote:
> > is "...an IETF context..."  well defined?
> 
> 
> For example, is a Bar BOF an IETF context?
> 
> What about a dinner among some attendees, on their own, during IETF week?
> 
> What about outside of IETF week?
> 
> What about a private email exchange by a couple of attendees, about an
> IETF topic?  Outside of IETF week?
> 
> And these really are questions for an attorney.
> 
> Sometimes, legal language that is ambiguous is helpful.  This isn't one
> of those times, since it needs to have clarity for average participants.
> 
> d/
> 
> --
>   Dave Crocker
>   Brandenburg InternetWorking
>   bbiw.net


From dhc@dcrocker.net  Mon Nov 12 10:09:11 2012
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4649F21F8596 for <ietf@ietfa.amsl.com>; Mon, 12 Nov 2012 10:09:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.94
X-Spam-Level: 
X-Spam-Status: No, score=-4.94 tagged_above=-999 required=5 tests=[AWL=0.016,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, RCVD_IN_NJABL_PROXY=1.643]
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 nEbbUSg49GMf for <ietf@ietfa.amsl.com>; Mon, 12 Nov 2012 10:09:10 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id A321E21F84F3 for <ietf@ietf.org>; Mon, 12 Nov 2012 10:09:10 -0800 (PST)
Received: from [192.168.1.6] (adsl-67-127-56-94.dsl.pltn13.pacbell.net [67.127.56.94]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id qACI9AN6031287 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Mon, 12 Nov 2012 10:09:10 -0800
Message-ID: <50A13B43.7000309@dcrocker.net>
Date: Mon, 12 Nov 2012 10:09:07 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
References: <201211121745.qACHjiXS919660@shell01.TheWorld.com>
In-Reply-To: <201211121745.qACHjiXS919660@shell01.TheWorld.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Mon, 12 Nov 2012 10:09:10 -0800 (PST)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Nov 2012 18:09:11 -0000

> In my opinion, the *location* of IETF meetings is not important for
> the technological openness of the standards, but it *is* important
> for its *symbolism*.


Many people seem to hold similar views about the social, political or 
emotional potential of IETF venue choice.

In the 1990s, when the Internet was developing as a global 
infrastructure, such roles for the IETF made sense, because the IETF 
meeting helped to promote the Internet.  Indeed, local Internet 
infrastructure often was significantly improved in order to accommodate 
the arrival of an IETF.

In my opinion, today, such factors are distractions from the primary 
purpose of the IETF meeting venue, which is getting IETF work 
accomplished.

Work is accomplished by being maximally accessible to the widest range 
of /active/ IETF participants.  Accessibility is affected by effort, 
cost and local resources.  This means easy travel to the venue, a good 
choice of convenient, personal accommodation at different price points, 
a good meeting venue layout, and good choices for nearby eating.  (The 
list is simplified, of course; I'm choosing the ones I think most 
important.)

Extra travel effort and time, extra travel cost and/or inconvenient 
venue logistics serve as barriers to participation.  They make an IETF 
meeting less inclusive.

Meetings venues are placed around the world in order to distribute the 
pain of travel for actual participants, not to promote the IETF or the 
Internet.  Since so many participants are well-funded by their companies 
and do quite a bit of travel every year, many of us are less sensitive 
to these issues as barrier.  In that regard, we lack empathy and for 
those with less funding or less experience.

Some people believe that the presence of an IETF meeting serves as a 
kind of recruitment marketing to a region, for IETF participation. 
Beyond the single-meeting boost in 'local' attendance, I believe we have 
no data confirming any on-going increase in participation by people from 
that region.  After 20 years, we ought to have hard data.

Further, going to an area that typically has a tiny (and relatively 
stable) percentage of IETF meeting participants mostly serves to make 
meeting attendance more painful for /everyone/, rather than only a portion.

It is difficult enough to find high quality meeting sites.  Adding 
social, political or emotional concerns makes it /more/ difficult.


d/

ps. I'm speaking for myself only, of course.  And I've held the above 
views since Marshall Rose and I first suggested a significantly 
simplified meeting venue process in the 1990s.  My time on the IAOC has 
only strengthened my view.

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From dhc@dcrocker.net  Mon Nov 12 10:16:26 2012
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3DA0421F868B for <ietf@ietfa.amsl.com>; Mon, 12 Nov 2012 10:16:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.943
X-Spam-Level: 
X-Spam-Status: No, score=-4.943 tagged_above=-999 required=5 tests=[AWL=0.013,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, RCVD_IN_NJABL_PROXY=1.643]
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 dj2Tb1nolgQY for <ietf@ietfa.amsl.com>; Mon, 12 Nov 2012 10:16:25 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 574FD21F85E6 for <ietf@ietf.org>; Mon, 12 Nov 2012 10:16:25 -0800 (PST)
Received: from [192.168.1.6] (adsl-67-127-56-94.dsl.pltn13.pacbell.net [67.127.56.94]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id qACIGC81031474 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 12 Nov 2012 10:16:13 -0800
Message-ID: <50A13CE9.7040308@dcrocker.net>
Date: Mon, 12 Nov 2012 10:16:09 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: "George, Wes" <wesley.george@twcable.com>
Subject: Re: in-person vs remote participation (was: Newcomers [Was: Evolutionizing the IETF])
References: <2671C6CDFBB59E47B64C10B3E0BD59230337252921@PRVPEXVS15.corp.twcable.com>
In-Reply-To: <2671C6CDFBB59E47B64C10B3E0BD59230337252921@PRVPEXVS15.corp.twcable.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Mon, 12 Nov 2012 10:16:13 -0800 (PST)
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Nov 2012 18:16:26 -0000

On 11/12/2012 8:29 AM, George, Wes wrote:
>    Remote participants are figuratively (and often
> literally) invisible, and therefore people forget about them, and
> they get relegated to second-class status as a participant.

It is easy for this to be true; it takes effort to make it not true.

I believe the Meetecho facility for displaying both slides and the 
jabber transcript on the screen, simultaneous, significantly changes the 
dynamic.  Everyone naturally sees postings from remote participants.

It still takes meeting management effort to include remote folks into 
the face-to-face discussion flow, but their presence is more universally 
seen automatically.


>  Even if
> it's only subconsciously, the in-person participants don't see remote
> participants to be "as committed" to participation as those who gave

Interesting point.  I think that remote participants who already have 
established a strong participation role are less likely to be viewed 
that way.  But frankly, I think even local participants with little IETF 
history are more likely to be discounted (or at least less counted.)


d/
-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From ben@nostrum.com  Mon Nov 12 13:48:19 2012
Return-Path: <ben@nostrum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF40921F8614; Mon, 12 Nov 2012 13:48:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001, 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 DVtdDy3PXS8X; Mon, 12 Nov 2012 13:48:13 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id DEC3921F85EA; Mon, 12 Nov 2012 13:48:12 -0800 (PST)
Received: from [10.12.11.26] ([4.30.77.1]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id qACLmBlo077546 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 12 Nov 2012 15:48:12 -0600 (CST) (envelope-from ben@nostrum.com)
From: Ben Campbell <ben@nostrum.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Gen-ART Telechat Review of draft-ietf-mptcp-api-06
Date: Mon, 12 Nov 2012 15:48:11 -0600
Message-Id: <F8E095B8-9E98-4986-80B5-7C498BC07733@nostrum.com>
To: "<draft-ietf-mptcp-api.all@tools.ietf.org>" <draft-ietf-mptcp-api.all@tools.ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
X-Mailer: Apple Mail (2.1499)
Received-SPF: pass (nostrum.com: 4.30.77.1 is authenticated by a trusted mechanism)
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, "ietf@ietf.org List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Nov 2012 21:48:19 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
< http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please wait for direction from your document shepherd
or AD before posting a new version of the draft.

Document: draft-ietf-mptcp-api-06
Reviewer: Ben Campbell=09
Review Date: 2012-11-12
IESG Telechat date: 2012-11-15

Summary: This draft is basically ready for publication as an =
informational RFC. All of the comments from my Gen-ART review of version =
05 at IETF last call have been dealt with to my satisfaction in the =
draft or in email, save the one minor issue below.

Major issues:

Minor issues:

I made the following comment at last call. It's not a show stopper, but =
I think it should be considered:

> -- It seems like at least passing knowledge of the sockets API is =
needed to understand this document. I'm curious why the POSIX reference =
is informational rather than normative?

The authors indicated they believed the reference at the end of =
paragraph 3 of section 1 to be truly informational. However, I called =
out an mention at the beginning of the same paragraph that should have =
included a citation, and that I thought that citation would justify a =
normative reference. The authors added the citation in version 06, but =
the reference is still informational.


Nits/editorial comments:

IDNits reports that "A later version (-12) exists of
     draft-ietf-mptcp-multiaddressed-09"


From ben@nostrum.com  Mon Nov 12 14:05:55 2012
Return-Path: <ben@nostrum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4FED421F8578; Mon, 12 Nov 2012 14:05:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001, 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 EQUwJoX5Os-e; Mon, 12 Nov 2012 14:05:54 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 46BC221F8580; Mon, 12 Nov 2012 14:05:53 -0800 (PST)
Received: from [10.12.11.26] ([4.30.77.1]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id qACM5k6s079224 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 12 Nov 2012 16:05:46 -0600 (CST) (envelope-from ben@nostrum.com)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Gen-ART Telechat Review of draft-leiba-extended-doc-shepherd-06
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <8414B0C3-C97E-4A1A-8F21-6387E85C8D84@nostrum.com>
Date: Mon, 12 Nov 2012 16:05:46 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <B46696E7-0199-48D6-B8BC-81BE4F35474C@nostrum.com>
References: <8414B0C3-C97E-4A1A-8F21-6387E85C8D84@nostrum.com>
To: draft-leiba-extended-doc-shepherd.all@tools.ietf.org
X-Mailer: Apple Mail (2.1499)
Received-SPF: pass (nostrum.com: 4.30.77.1 is authenticated by a trusted mechanism)
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, "ietf@ietf.org List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Nov 2012 22:05:55 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
< http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please wait for direction from your document shepherd
or AD before posting a new version of the draft.

Document: draft-leiba-extended-doc-shepherd-01
Reviewer: Ben Campbell=09
Review Date: 2012-11-12
IESG Telechat date: 2012-11-15

Summary: I have mixed feelings about this draft being published as an =
IETF stream RFC in it's current form.

Major issues:

This draft is not substantially changed since my Gen-ART review of =
version 00 at last call. I've copied that review in it's entirety below. =
There is a new section indicating that the ideas herein should be =
adapted to the circumstances. This helps, but I think my original =
comments still stand.

I am sympathetic to Adrian Farrel's DISCUSS position as updated on =
2012-11-05. OTOH, it seems like there should be a place to capture this =
sort of opinion document, and it's a bit large and involved to simply =
send to a mailing list for discussion.

On Oct 23, 2012, at 5:07 PM, Ben Campbell <ben@nostrum.com> wrote:

> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
>=20
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please resolve these comments along with any other Last Call comments
> you may receive.
>=20
> Document:  draft-leiba-extended-doc-shepherd-00
>=20
> Reviewer: Ben Campbell
> Review Date: 2012-10-23
> IETF LC End Date: 2012-10-23
>=20
> Summary: I'm not sure what to make of this draft. I think the opinions =
herein are worth capturing, but have mixed feelings about it belong in =
an informational RFC.
>=20
> Major issues:
>=20
> -- Process: I share some of the concerns that have been mentioned by =
others, namely that I'm not sure whether an individual opinion paper =
should be published as an informational RFC. OTOH, I'm not sure that it =
shouldn't. The operative words here are "I'm not sure." The opinions =
contained in the document are interesting, and likely of use to the =
community. I just wonder if another publication form might not be more =
appropriate.
>=20
> -- Content: It's hard to disagree with most of the activities in =
general, but it seems to me that much of the pre pubreq processes here =
are just things that Chairs should be doing anyway. I guess it doesn't =
hurt to call all of that "shepherding", but I don't think it's the same =
thing as "having a shepherd" in the PROTO sense.  I see the potential =
value of having continuity of responsibility throughout the entire =
process, but I also see value in the flexibility of deferring the =
shepherd selection until time for the proto writeup. (I recognize that =
you don't necessarily expect the same person to shepherd all phases--but =
if I read correctly you also seem to indicate a preference that they do =
so.)
>=20
> Minor issues:
>=20
> -- section 1, 4th paragraph: "It adds to what=92s in RFC 4858, =
intending to extend it, not replace it."
>=20
> Do you intend this to formally update 4858? It doesn't seem like it =
from the rest of the text, but one might infer otherwise from this =
sentence.
>=20
> -- section 4, 2nd paragraph: "... What it all boils down to is setting =
up one person who takes responsibility for following the progress of a =
document from Call for Adoption through Publication ..."
>=20
> The text offers examples of changing the responsible person during the =
process, but also mentions the advantages of continuity. If continuity =
is the real goal, then are the examples that show the role changing over =
the life of the draft are counterproductive?
>=20
>=20
> Nits/editorial comments:
>=20
> None.


From spencer@wonderhamster.org  Mon Nov 12 14:35:22 2012
Return-Path: <spencer@wonderhamster.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 734A321F84BC for <ietf@ietfa.amsl.com>; Mon, 12 Nov 2012 14:35:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.855
X-Spam-Level: 
X-Spam-Status: No, score=-102.855 tagged_above=-999 required=5 tests=[AWL=-0.255, 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 X0tbQNcsGibE for <ietf@ietfa.amsl.com>; Mon, 12 Nov 2012 14:35:22 -0800 (PST)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.195]) by ietfa.amsl.com (Postfix) with ESMTP id C97AA21F8462 for <ietf@ietf.org>; Mon, 12 Nov 2012 14:35:21 -0800 (PST)
Received: from [192.168.12.170] ([50.58.7.243]) by mrelay.perfora.net (node=mrus4) with ESMTP (Nemesis) id 0LyVQs-1TDiQF20X8-015guI; Mon, 12 Nov 2012 17:35:20 -0500
Message-ID: <50A179A7.8040501@wonderhamster.org>
Date: Mon, 12 Nov 2012 16:35:19 -0600
From: Spencer Dawkins <spencer@wonderhamster.org>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: Mary Barnes <mary.ietf.barnes@gmail.com>
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
References: <CADnDZ8-fjxfgJys8sE10DdZ08tB8HdaTQXbPj2d7-OuQOGi9Pg@mail.gmail.com> <CADnDZ8_v3M1fNtkOV4rU1F-iaMC+2qvKhR353vwESiQsfh70MQ@mail.gmail.com> <6.2.5.6.2.20121109074113.0b2000f8@resistor.net> <8C48B86A895913448548E6D15DA7553B19E215@xmb-rcd-x09.cisco.com> <509D910D.7060503@gmail.com> <509DA4E7.1090504@gmail.com> <509DA723.7030703@gmail.com> <m2390hq3ge.wl%randy@psg.com> <509E6634.2010203@gmail.com> <509E8622.8050803@gmail.com> <CAHBDyN6VEBkqNHYFK7A0P8S8wrAwNYaAeVnnxkiJ=79iVQR4=Q@mail.gmail.com>
In-Reply-To: <CAHBDyN6VEBkqNHYFK7A0P8S8wrAwNYaAeVnnxkiJ=79iVQR4=Q@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V02:K0:Dy2DxAAVULpeBk0eAYH67nsOtQsEIhivKEDnIXCd8d5 UVaf5I3Zvq+/dY1+lbMWg9ZZOOzmJotTtvctE9OwfWKENniMSZ pboaEVVqC6/p5QWEAwxxHHNEuazlF8GWTh/zvnkR28NeK4CImC hKDGv7iDTuyV6Pw9/HJMvZha9Q6Vl+6v/bQe6C+qMtaOY7qCra ORA7EHkOKo/LZNpx/NP8n45hJNXfaE8X+Wq/+lIli/MDHGQLyx R0YP/6/pQmRP9+LLWufNyuYLBrcn4jec0HMdHv0COmllmkD3Zb mnvO4r01BBgEq4gd71M4CoxfVuJpjUDao7SDvIQddvLTRHnFY0 d5xO7RHZW/g4SwM23FnsKsv69BTt4N3ca5GUFHd4k
Cc: IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Nov 2012 22:35:22 -0000

On 11/10/2012 10:57 AM, Mary Barnes wrote:
> On Sat, Nov 10, 2012 at 10:51 AM, Melinda Shore <melinda.shore@gmail.com>wrote:
>
>>
>>
>> I think that we haven't done a sufficiently good job of
>> acculturating newer participants and that can probably make
>> the organization look more opaque and closed than it actually
>> is.  Most (but not all) working groups don't have enough help
>> with document review, and I think that's probably the fast
>> path to agency within the IETF.  Being a body in a chair at a
>> meeting is not.
>>
>
> [MB] Exactly!  That's what I did when I first started participating in
> IETF.  I would review documents and comment on the mailing.   I also would
> volunteer to take meeting minutes as that really does force you to pay
> attention to the meeting and not spend the meeting reading email or playing
> solitaire.  Or, volunteer to at least follow the jabber room.  Those are
> all extremely important for working group effectiveness.  [/MB]

What Melinda and Mary are suggesting is what's worked best for me.

The only additions I'd make are:

- It's worth noting that, this being the IETF, your ideas are going 
nowhere unless other people agree with and support those ideas (if 
working group participants won't work on your proposal, the working 
group won't adopt it!). If you contribute to other people's proposals, 
either by providing text or helpful review comments, it's easier to find 
people who will contribute to your proposals.

- It's worth noting that *committing to* taking minutes is also useful, 
whether on a one-time basis, by e-mailing the chairs and volunteering a 
week before the face-to-face meeting, or on an ongoing basis as a 
working group secretary (most working groups still don't have one), is 
also appreciated (not least by working group chairs who can't start a 
meeting until they find a note-taker!). You still have to actually show 
up and take minutes, but if they know you're coming, you get extra 
points ...

Best wishes, of course. The IETF needs more effective participants.

Spencer

From mcr@sandelman.ca  Mon Nov 12 14:38:14 2012
Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 356A321F878E for <ietf@ietfa.amsl.com>; Mon, 12 Nov 2012 14:38:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.917
X-Spam-Level: 
X-Spam-Status: No, score=-1.917 tagged_above=-999 required=5 tests=[AWL=0.037,  BAYES_00=-2.599, HOST_MISMATCH_NET=0.311, IP_NOT_FRIENDLY=0.334]
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 4g1aFbspbRLP for <ietf@ietfa.amsl.com>; Mon, 12 Nov 2012 14:38:13 -0800 (PST)
Received: from relay.sandelman.ca (relay.cooperix.net [67.23.6.41]) by ietfa.amsl.com (Postfix) with ESMTP id C3FC121F858A for <ietf@ietf.org>; Mon, 12 Nov 2012 14:38:13 -0800 (PST)
Received: from sandelman.ca (unknown [75.98.19.134]) by relay.sandelman.ca (Postfix) with ESMTPS id 98DA081A9 for <ietf@ietf.org>; Mon, 12 Nov 2012 17:29:45 -0500 (EST)
Received: from sandelman.ca (quigon.sandelman.ca [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 5264CCA0BC for <ietf@ietf.org>; Mon, 12 Nov 2012 17:37:58 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: in-person vs remote participation (was: Newcomers [Was: Evolutionizing the IETF])
In-reply-to: <2671C6CDFBB59E47B64C10B3E0BD592303372529DB@PRVPEXVS15.corp.twcable.com>
References: <2671C6CDFBB59E47B64C10B3E0BD592303372529DB@PRVPEXVS15.corp.twcable.com>
Comments: In-reply-to "George, Wes" <wesley.george@twcable.com> message dated "Mon, 12 Nov 2012 12:15:56 -0500."
X-Mailer: MH-E 8.3; nmh 1.3; XEmacs 21.4 (patch 22)
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Mon, 12 Nov 2012 17:37:58 -0500
Message-ID: <10564.1352759878@sandelman.ca>
Sender: mcr@sandelman.ca
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Nov 2012 22:38:14 -0000

--=-=-=
Content-Transfer-Encoding: quoted-printable


>>>>> "George" =3D=3D George, Wes <wesley.george@twcable.com> writes:
    George> First and foremost, the act of getting away from the office
    George> and the financial and time commitments involved in traveling
    George> to a physical meeting a few times a year tends to reinforce
    George> the need to "prepare" for the meeting by reading drafts,
    George> catching up on IETF work that has languished, etc. The

+1
I don't see how we will reproduce this online.

also, we talk about cross-area review, and sometimes this is faciliated=20
by "WG tourists"...

When participating remotely when there were 12 hours TZ differences, a
really really really hard part was explaining to my kid, that really, I
wasn't home.=20=20

    George> The other things that become important are the "hallway
    George> track" and the "many fine lunches and dinners". Those come
    George> up when talking about attending IETF in person, but often
    George> it's meant to imply that those involved are there for the
    George> wrong reasons (i.e. IETF as company-sponsored tourism or job
    George> search) rather than to acknowledge its value in ensuring

+1

=2D-=20
Michael Richardson
=2Don the road-


--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iQEcBAABAgAGBQJQoXpFAAoJEKD0KQ7Gj3P284QH/iHixW+w+lbrNjM+8JLW1MN8
bE5qCll1TaufTEsxBQm2ywKsdjfvhNCe17CkZksvnxqBKBwtQPr7qMlFNXu91rX/
g6XXTLXUHO+eiRU3nErwnMQ0G4E0saqzJ1m8KrcMSLcbnSGElKCr/1yrvTrSQCaw
+w5i/x3gbrPzB/T0P4I56CU7/zOgB36XW5vkPd5tN/1oKZZUFsiX0UCV0L7zxvuj
SS8i70FQCIuxujDZ4F9pBjKXHEHCCOCogl4pkQJNwMJzWD/XnZSEHRrVyK0VKcYU
AJKeEjx3+9LLqQF7Uxsp3OOzu6crVdXgTMmJYCO6BetC8Qn3SFlX5v1GueGpvDM=
=a559
-----END PGP SIGNATURE-----
--=-=-=--

From dcrocker@bbiw.net  Mon Nov 12 15:23:08 2012
Return-Path: <dcrocker@bbiw.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 77FDD21F8769 for <ietf@ietfa.amsl.com>; Mon, 12 Nov 2012 15:23:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.956
X-Spam-Level: 
X-Spam-Status: No, score=-4.956 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, RCVD_IN_NJABL_PROXY=1.643]
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 ytOdYIO2u56P for <ietf@ietfa.amsl.com>; Mon, 12 Nov 2012 15:23:07 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id CAD5721F8625 for <ietf@ietf.org>; Mon, 12 Nov 2012 15:23:07 -0800 (PST)
Received: from [192.168.1.6] (adsl-67-127-56-94.dsl.pltn13.pacbell.net [67.127.56.94]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id qACNN6pw003775 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 12 Nov 2012 15:23:06 -0800
Message-ID: <50A184D5.8060209@bbiw.net>
Date: Mon, 12 Nov 2012 15:23:01 -0800
From: Dave Crocker <dcrocker@bbiw.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: adrian@olddog.co.uk
Subject: Re: IESG Considering a Revision to NOTE WELL
References: <55D046F8-5DD2-42E8-9B8C-36C612C4B3F8@ietf.org>	<CAPeNrjnFd655O4R+TzqZf3r_rmXWjGx+gQ8V1c4PdSTxDVkuNQ@mail.gmail.com> <50A11FFF.3040401@dcrocker.net> <019601cdc0fe$7bbb96d0$7332c470$@olddog.co.uk>
In-Reply-To: <019601cdc0fe$7bbb96d0$7332c470$@olddog.co.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Mon, 12 Nov 2012 15:23:06 -0800 (PST)
Cc: 'bill manning' <azuremesa@gmail.com>, 'IETF' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Nov 2012 23:23:08 -0000

On 11/12/2012 9:52 AM, Adrian Farrel wrote:
> I think you miss the point of "This summary is only meant to point you in the
> right direction, and doesn't have all the nuances. The IETF's IPR Policy is set
> forth in BCP 79; please read it carefully."


as in 1.c of the doc, I believe.

d/


-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From bortzmeyer@nic.fr  Tue Nov 13 02:47:26 2012
Return-Path: <bortzmeyer@nic.fr>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5824621F866C for <ietf@ietfa.amsl.com>; Tue, 13 Nov 2012 02:47:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.961
X-Spam-Level: 
X-Spam-Status: No, score=-99.961 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, HELO_EQ_FR=0.35, SARE_SUB_RAND_LETTRS4=0.799, 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 DTEzAtFIyqyu for <ietf@ietfa.amsl.com>; Tue, 13 Nov 2012 02:47:22 -0800 (PST)
Received: from mx4.nic.fr (mx4.nic.fr [192.134.4.12]) by ietfa.amsl.com (Postfix) with ESMTP id 157AE21F866F for <ietf@ietf.org>; Tue, 13 Nov 2012 02:47:22 -0800 (PST)
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id 4F1F8280136 for <ietf@ietf.org>; Tue, 13 Nov 2012 11:46:45 +0100 (CET)
Received: from relay1.nic.fr (relay1.nic.fr [192.134.4.162]) by mx4.nic.fr (Postfix) with ESMTP id 4B933280127 for <ietf@ietf.org>; Tue, 13 Nov 2012 11:46:45 +0100 (CET)
Received: from bortzmeyer.nic.fr (batilda.nic.fr [IPv6:2001:67c:2219:8::6:69]) by relay1.nic.fr (Postfix) with ESMTP id 3F6DB4C0053 for <ietf@ietf.org>; Tue, 13 Nov 2012 11:46:15 +0100 (CET)
Date: Tue, 13 Nov 2012 11:46:15 +0100
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: ietf@ietf.org
Subject: NASA just bought IRTF
Message-ID: <20121113104615.GA13863@nic.fr>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Operating-System: Debian GNU/Linux wheezy/sid
X-Kernel: Linux 3.2.0-3-686-pae i686
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: Mutt/1.5.21 (2010-09-15)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Nov 2012 10:47:26 -0000

http://anewdomain.net/2012/11/10/nasa-dtn-protocol-bp-protocol-vint-cerf-interplanetary-internet-how-it-works-what-legos-have-to-to-with-it/#

> According to NASA's Delay-Tolerant Networking Research Group
> (DTNRG), "the DTN protocol is under active development."

From stephen.farrell@cs.tcd.ie  Tue Nov 13 02:54:12 2012
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D3BE921F869A for <ietf@ietfa.amsl.com>; Tue, 13 Nov 2012 02:54:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.2
X-Spam-Level: 
X-Spam-Status: No, score=-102.2 tagged_above=-999 required=5 tests=[AWL=-0.399, BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799, 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 j1dBA0CA7-Kv for <ietf@ietfa.amsl.com>; Tue, 13 Nov 2012 02:54:10 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id EAC8A21F8680 for <ietf@ietf.org>; Tue, 13 Nov 2012 02:54:09 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id B1F1BBE50; Tue, 13 Nov 2012 10:53:45 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Lj35FGuVZ-n1; Tue, 13 Nov 2012 10:53:44 +0000 (GMT)
Received: from [IPv6:2001:770:10:203:fc16:33b:6a79:3b11] (unknown [IPv6:2001:770:10:203:fc16:33b:6a79:3b11]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 5426EBE47; Tue, 13 Nov 2012 10:53:44 +0000 (GMT)
Message-ID: <50A226B8.5070909@cs.tcd.ie>
Date: Tue, 13 Nov 2012 10:53:44 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121028 Thunderbird/16.0.2
MIME-Version: 1.0
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
Subject: Re: NASA just bought IRTF
References: <20121113104615.GA13863@nic.fr>
In-Reply-To: <20121113104615.GA13863@nic.fr>
X-Enigmail-Version: 1.4.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Nov 2012 10:54:12 -0000

On 11/13/2012 10:46 AM, Stephane Bortzmeyer wrote:
> http://anewdomain.net/2012/11/10/nasa-dtn-protocol-bp-protocol-vint-cerf-interplanetary-internet-how-it-works-what-legos-have-to-to-with-it/#
> 
>> According to NASA's Delay-Tolerant Networking Research Group
>> (DTNRG), "the DTN protocol is under active development."
> 

Well, I think the NASA press release was accurate enough,
but that article isn't perhaps the best in that respect
though even it does say down the bottom that DTNRG is owned
part of the IRTF.

Could be a money-spinner though, if someone wants to purchase
DTNRG, contact the chairs with cash offers:-)

S.


From arturo.servin@gmail.com  Tue Nov 13 04:24:53 2012
Return-Path: <arturo.servin@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7DEA421F86A8 for <ietf@ietfa.amsl.com>; Tue, 13 Nov 2012 04:24:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.399
X-Spam-Level: 
X-Spam-Status: No, score=-3.399 tagged_above=-999 required=5 tests=[AWL=0.200,  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 yWxhmF6nFImk for <ietf@ietfa.amsl.com>; Tue, 13 Nov 2012 04:24:53 -0800 (PST)
Received: from mail-ye0-f172.google.com (mail-ye0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id 2CE7021F8648 for <ietf@ietf.org>; Tue, 13 Nov 2012 04:24:51 -0800 (PST)
Received: by mail-ye0-f172.google.com with SMTP id l13so1420393yen.31 for <ietf@ietf.org>; Tue, 13 Nov 2012 04:24:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=TjObcQLIPVhfDVXt9W/a7tdy8Hoyu2jCy9d8Wc9WZL0=; b=ZuYv/gah1xgYKXyPcpAyiy4GbTT9Bq1mJFZwM11IUxNyujBmy/PYt8cKK5Hgfi8WU2 pUgLK6Cb93ZanLZZAzgZ3QhwdeBkDTEZYGQJyM0t+0jB2qdnU/bXBHegX6blK8Q437Kw 5emj6tihRR9wJlEin4T9IQuqNojKlHiKex0FllH7iw7fFUOt5onH3zpjdREWQtnHpmn0 kXk6DTLSz8jjKW/zsywXrmN5wwG8DuQJctJxon5akNv/tnp6SQeg/0Z67cBxFpvqztrm XuIcV03iniNjdzAfEMrv5MGEOCz17X7F5mLUEM9vTpJDhUwZSzCCpJFvSbZgh3rqG9JB i24A==
Received: by 10.100.250.2 with SMTP id x2mr6249470anh.14.1352809489752; Tue, 13 Nov 2012 04:24:49 -0800 (PST)
Received: from 85-7-200.lacnic.net.uy ([2001:13c7:7001:5128:6c20:9c06:8a4f:c68f]) by mx.google.com with ESMTPS id z6sm9565668yhl.8.2012.11.13.04.24.47 (version=SSLv3 cipher=OTHER); Tue, 13 Nov 2012 04:24:48 -0800 (PST)
Message-ID: <50A23C0C.6020100@gmail.com>
Date: Tue, 13 Nov 2012 10:24:44 -0200
From: Arturo Servin <arturo.servin@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
References: <CADnDZ8-fjxfgJys8sE10DdZ08tB8HdaTQXbPj2d7-OuQOGi9Pg@mail.gmail.com> <CADnDZ8_v3M1fNtkOV4rU1F-iaMC+2qvKhR353vwESiQsfh70MQ@mail.gmail.com> <6.2.5.6.2.20121109074113.0b2000f8@resistor.net> <8C48B86A895913448548E6D15DA7553B19E215@xmb-rcd-x09.cisco.com> <509D910D.7060503@gmail.com> <509DA4E7.1090504@gmail.com> <509DA723.7030703@gmail.com> <20121110170826.GA24595@gsp.org>
In-Reply-To: <20121110170826.GA24595@gsp.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Nov 2012 12:24:53 -0000

	I won't cut all the meetings but for I would encourage to have some (or
all) interim WG meetings fully online.

	We tried once in sidr, it didn't work very well but I am sure that we
can improve it.

Regards,
as

On 10/11/2012 15:08, Rich Kulawiec wrote:
> On Fri, Nov 09, 2012 at 08:00:19PM -0500, Arturo Servin wrote:
>>     People is asking how to evolve the IETF, well, one possibility is to
>> start thinking global and to reach more people outside the common venues. 
> 
> Another is to not have any (physical) meetings, ever.  I've heard
> all the arguments against this approach for years, and I think they're
> all oudated: every kind of interaction that's possible in a physical
> meeting is now possible in an online one.  It's simply a matter of
> having the will to commit to the technology and to work through the
> (no doubt numerous) issues that will surface while using it.
> 
> This facilitates more involvement.  It dramatically cuts costs.
> It avoids the hassles and risks of travel, including the increasingly
> privacy-hostile intrusions of various governments.  It's more flexible.
> It allows near-global participation regardless of geography, schedule,
> budget, etc.
> 
> And more than anything, it would show that the IETF is actually committed
> to, you know, *using the Internet*.
> 
> ---rsk
> 

From tglassey@earthlink.net  Tue Nov 13 07:48:09 2012
Return-Path: <tglassey@earthlink.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 883D621F86BB for <ietf@ietfa.amsl.com>; Tue, 13 Nov 2012 07:48:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.118
X-Spam-Level: 
X-Spam-Status: No, score=-2.118 tagged_above=-999 required=5 tests=[AWL=-0.318, BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799]
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 SHTPdk9uK1zJ for <ietf@ietfa.amsl.com>; Tue, 13 Nov 2012 07:48:05 -0800 (PST)
Received: from elasmtp-banded.atl.sa.earthlink.net (elasmtp-banded.atl.sa.earthlink.net [209.86.89.70]) by ietfa.amsl.com (Postfix) with ESMTP id 2B45821F85E1 for <ietf@ietf.org>; Tue, 13 Nov 2012 07:48:04 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=ggSh7MNQK5pWzNPmuYORjaDoo4kI6WsubmdbI1ax3uZpbHUZdT1iUfhbo++pttbf; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [67.180.133.21] (helo=[192.168.15.2]) by elasmtp-banded.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <tglassey@earthlink.net>) id 1TYIiX-0002IZ-Vb for ietf@ietf.org; Tue, 13 Nov 2012 10:48:02 -0500
Message-ID: <50A26BAD.4010203@earthlink.net>
Date: Tue, 13 Nov 2012 07:47:57 -0800
From: tglassey <tglassey@earthlink.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: NASA just bought IRTF
References: <20121113104615.GA13863@nic.fr>
In-Reply-To: <20121113104615.GA13863@nic.fr>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec7949cb47f1ae51d058144f9faffa692521350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 67.180.133.21
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Nov 2012 15:48:09 -0000

On 11/13/2012 2:46 AM, Stephane Bortzmeyer wrote:
> http://anewdomain.net/2012/11/10/nasa-dtn-protocol-bp-protocol-vint-cerf-interplanetary-internet-how-it-works-what-legos-have-to-to-with-it/#
>
>> According to NASA's Delay-Tolerant Networking Research Group
>> (DTNRG), "the DTN protocol is under active development."
Laughing out loud...

-- 
Regards TSG
"Ex-Cruce-Leo"

//Confidential Mailing - Please destroy this if you are not the intended recipient.


From tglassey@earthlink.net  Tue Nov 13 09:58:57 2012
Return-Path: <tglassey@earthlink.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2420F21F861A for <ietf@ietfa.amsl.com>; Tue, 13 Nov 2012 09:58:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level: 
X-Spam-Status: No, score=-2.095 tagged_above=-999 required=5 tests=[AWL=-0.295, BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799]
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 dg7-wPrr-tqz for <ietf@ietfa.amsl.com>; Tue, 13 Nov 2012 09:58:56 -0800 (PST)
Received: from elasmtp-junco.atl.sa.earthlink.net (elasmtp-junco.atl.sa.earthlink.net [209.86.89.63]) by ietfa.amsl.com (Postfix) with ESMTP id 12EB021F85BF for <ietf@ietf.org>; Tue, 13 Nov 2012 09:58:56 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=CvYzqqHsA18cBnE3ePdlDlok38Iu+fxhPkYbmdDPTSYvS1jgECOFPpUCyG0bg8Fk; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [67.180.133.21] (helo=[192.168.15.2]) by elasmtp-junco.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <tglassey@earthlink.net>) id 1TYKlB-00055t-NO for ietf@ietf.org; Tue, 13 Nov 2012 12:58:53 -0500
Message-ID: <50A28A5C.5060404@earthlink.net>
Date: Tue, 13 Nov 2012 09:58:52 -0800
From: tglassey <tglassey@earthlink.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: NASA just bought IRTF
References: <20121113104615.GA13863@nic.fr> <50A226B8.5070909@cs.tcd.ie>
In-Reply-To: <50A226B8.5070909@cs.tcd.ie>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec7994261f13b61d27b886078e2922e90652350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 67.180.133.21
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Nov 2012 17:58:57 -0000

On 11/13/2012 2:53 AM, Stephen Farrell wrote:
>
> On 11/13/2012 10:46 AM, Stephane Bortzmeyer wrote:
>> http://anewdomain.net/2012/11/10/nasa-dtn-protocol-bp-protocol-vint-cerf-interplanetary-internet-how-it-works-what-legos-have-to-to-with-it/#
>>
>>> According to NASA's Delay-Tolerant Networking Research Group
>>> (DTNRG), "the DTN protocol is under active development."
> Well, I think the NASA press release was accurate enough,
> but that article isn't perhaps the best in that respect
> though even it does say down the bottom that DTNRG is owned
> part of the IRTF.
>
> Could be a money-spinner though, if someone wants to purchase
> DTNRG, contact the chairs with cash offers:-)
>
> S.
>
>
DTNRG because it is location based will likely also impact US6370629...

T

-- 
Regards TSG
"Ex-Cruce-Leo"

//Confidential Mailing - Please destroy this if you are not the intended recipient.


From iad@ietf.org  Tue Nov 13 11:17:33 2012
Return-Path: <iad@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B63EC21F85FF; Tue, 13 Nov 2012 11:17:33 -0800 (PST)
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=-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 rwTLpcba9eLy; Tue, 13 Nov 2012 11:17:33 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3139A21F85DB; Tue, 13 Nov 2012 11:17:33 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: IETF Administrative Director <iad@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
Subject: RFP for IETF Meeting Network Services
X-Test-IDTracker: no
X-IETF-IDTracker: 4.36
Message-ID: <20121113191733.29415.73020.idtracker@ietfa.amsl.com>
Date: Tue, 13 Nov 2012 11:17:33 -0800
Cc: iaoc@ietf.org, iab@iab.org, ietf@ietf.org, wgchairs@ietf.org, iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Nov 2012 19:17:34 -0000

The IETF Administrative Oversight Committee (IAOC), on behalf of the Intern=
et Engineering Task Force
(IETF), announces this Request for Proposals for IETF Meeting Network Servi=
ces.  The successful bidder =

will enter into a contract with the Internet Society.

The IAOC is seeking vendors to perform network services for  (IETF) meeting=
s beginning in 2013 for a =

three-year (3) period, with an opportunity for two (2) one-year extensions.=
 Generally, the services would
include: performing a pre-meeting site survey; developing a detailed networ=
k design; installing all equipment; =

conducting tests; and providing operations, systems management; user suppor=
t functions during the meeting; =

and storage of IETF equipment. This is an indefinite delivery, indefinite q=
uantity (IDIQ) contract.

The IETF conducts three, one-week meetings a year throughout the world.  At=
tendance is in the range of =

1,100 to 1,300 per meeting.  The meetings are typically conducted in March,=
 July and November.  Meeting =

venues include hotels with conference space (the preference), as well as st=
andalone conference centers.  =

Meeting space requirements are typically 40,000 square feet, comprised of 8=
 meeting rooms holding between =

100 =E2=80=93 500 people; one Plenary room holding 1,000 people; a 120-seat=
 terminal room; 8 offices; and a =

registration area.  =


Generally, the wireless network must service all meeting rooms, terminal ro=
om, offices, the registration area, =

and public spaces.  Limited wired services are required in the meeting room=
s and registration area, however,
the terminal room requires upwards of 150 drops.  Audio streaming and Jabbe=
r conference rooms are provided =

in addition to the wired and wireless network services for the meeting.

Connecting the IETF meeting to the Internet is done through a pair of redun=
dant circuits. These circuits =

historically consist of a highspeed primary link and a lower speed backup l=
ink.  These links are generally
brought in specifically for the event, though existing venue links can some=
times be utilized for backup =

purposes.  =


The IETF has equipment available to be used by the vendor, which is subject=
 to change over time.  Vendor is =

to provide all other networking equipment including network servers, router=
s, switches, access points, and
cabling, and any equipment required by its staff in fulfilling the requirem=
ents of this contract.

Performance goals of the network are support of up to 2000 simultaneous con=
nected devices with connectivity =

availability of at least 99% during the hours when session meetings are in =
progress, as well as the provision of =

Internet connectivity for headquarters hotel IETF guest rooms.

The RFP can be found at: <http://iaoc.ietf.org/rfpsrfis.html>

The anticipated schedule is as follows:

	a. RFP Issued:  November 13, 2012.

	b. Questions must be submitted by November 26, 2012 to tmc@ietf-bids.org.
	Responses will be posted by December 3, 2012 at =

	< http://iaoc.ietf.org/rfpsrfis.html>

	c. Proposal submitted by email due no later than 5 PM ET on December 17, 2=
012.

	d. Proposal Review Period:  December 17 - 31, 2012.

	e. Notification of selection:  January 10, 2013

	f. Contract Negotiation and Agreement:  January 14 - 28, 2013.

	g. Contract Accepted:  February 14, 2013.

	h. Contract Commencement: March 1, 2013.

Proposals must be received via email at tmc@ietf-bids.org no later than Dec=
ember 17, 2012 5:00 P.M. ET.  All =

questions/inquiries must be submitted in writing and must be received no la=
ter than midnight, November 26, =

2012.  Responses to questions and inquiries shall be posted online at:  <ht=
tp://iaoc.ietf.org/rfpsrfis.html> by =

December 3, 2012. =


The point of contact regarding this RFP is the IETF Administrative Director=
, Ray Pelletier, iad@ietf.org.

Ray Pelletier


From rogerj@gmail.com  Wed Nov 14 01:42:28 2012
Return-Path: <rogerj@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 629FE21F8554; Wed, 14 Nov 2012 01:42:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.299
X-Spam-Level: 
X-Spam-Status: No, score=-3.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, 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 abR7extTdTP9; Wed, 14 Nov 2012 01:42:27 -0800 (PST)
Received: from mail-wg0-f42.google.com (mail-wg0-f42.google.com [74.125.82.42]) by ietfa.amsl.com (Postfix) with ESMTP id 11EA621F84FF; Wed, 14 Nov 2012 01:42:26 -0800 (PST)
Received: by mail-wg0-f42.google.com with SMTP id fm10so2616212wgb.1 for <multiple recipients>; Wed, 14 Nov 2012 01:42:26 -0800 (PST)
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 :cc:content-type; bh=6Hjd7fBAD8r0/3Y65Not/tjUjKYawmWTD66GmpS9fAk=; b=EBk4eSG9Qgci4SEtFYFy5x8hBq0FWg7JW1prAUs8LyG+OX6lcZOhKWHdRA25jxySP7 X17/tER4iiXajyqqmTf5T4hEXX/Jczc1ddaSxOFCLpZjP68zN8jbzNNQl6goyRmHR2L1 Xutrz5DIhZcQn6fbWYj5drYrOhiiGadoLeDoPtPg5Z/wp2EruYEN9eRc0CdLxnpHT1vX iOY4DyXtF0xn8PqZ91O306VkMI5N5oOx2QFisUmfXq8VyrdH/i34PS2byVuf8Cl029HH aaZ+dBy0wrn/AslxqkYgbzV10htN+HO9CgffIS7bfxjsjkUt1GJiHhH97m+ccmp458Z+ FP5w==
MIME-Version: 1.0
Received: by 10.180.14.73 with SMTP id n9mr24833864wic.15.1352886146158; Wed, 14 Nov 2012 01:42:26 -0800 (PST)
Received: by 10.217.83.4 with HTTP; Wed, 14 Nov 2012 01:42:26 -0800 (PST)
In-Reply-To: <20121113144545.12836.71935.idtracker@ietfa.amsl.com>
References: <20121113144545.12836.71935.idtracker@ietfa.amsl.com>
Date: Wed, 14 Nov 2012 10:42:26 +0100
Message-ID: <CAKFn1SFy2+hXJLVtEpkdXfNuXA31ybmYnBFFPXj-73kb3tD+yw@mail.gmail.com>
Subject: Re: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
From: =?ISO-8859-1?Q?Roger_J=F8rgensen?= <rogerj@gmail.com>
To: ietf@ietf.org, lisp@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Nov 2012 09:42:28 -0000

On Tue, Nov 13, 2012 at 3:45 PM, The IESG <iesg-secretary@ietf.org> wrote:
>
> The IESG has received a request from the Locator/ID Separation Protocol
> WG (lisp) to consider the following document:
> - 'LISP EID Block'
>   <draft-ietf-lisp-eid-block-03.txt> as Informational RFC
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2012-11-27. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>
> Abstract
>
>
>    This is a direction to IANA to allocate a /16 IPv6 prefix for use
>    with the Locator/ID Separation Protocol (LISP).  The prefix will be
>    used for local intra-domain routing and global endpoint
>    identification, by sites deploying LISP as EID (Endpoint IDentifier)
>    addressing space.

I have to ask, who can request an netblock from this address space and
from where?
I might be blind but I couldn't find it mentioned anywhere.



-- 

Roger Jorgensen           | ROJO9-RIPE
rogerj@gmail.com          | - IPv6 is The Key!
http://www.jorgensen.no   | roger@jorgensen.no

From sm@resistor.net  Wed Nov 14 03:21:26 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EFC0A21F847B for <ietf@ietfa.amsl.com>; Wed, 14 Nov 2012 03:21:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.488
X-Spam-Level: 
X-Spam-Status: No, score=-102.488 tagged_above=-999 required=5 tests=[AWL=0.111, 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 eGU2++coEl-X for <ietf@ietfa.amsl.com>; Wed, 14 Nov 2012 03:21:26 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4097B21F8503 for <ietf@ietf.org>; Wed, 14 Nov 2012 03:21:26 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id qAEBLKRo014257 for <ietf@ietf.org>; Wed, 14 Nov 2012 03:21:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1352892084; bh=ASZICUVWPiENnfghzQhxqBE9C05ye8HeJ89H9PmPOog=; h=Date:To:From:Subject:In-Reply-To:References:Cc; b=Z12YhjaYPfb2d0aP6fs8SkMTGOTJbc34Jj+dHod9O0VeoNe6OSUEx6ipQ9PUurBaI inHO1atnwDVQBEs/Xh3CMtOLqN7GsFxpCO44+4yhhBuYG0QwRhP4M8FfCQ7gl6o364 Irl3BNkyD8xAN7STCPRIz2jIFJtq08ltyx1GOLzE=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1352892084; i=@resistor.net; bh=ASZICUVWPiENnfghzQhxqBE9C05ye8HeJ89H9PmPOog=; h=Date:To:From:Subject:In-Reply-To:References:Cc; b=Z1m122J6A3pOlUg30YUnKabYJDnR5EC2agU5LiCuqH7uL0B0n/x7vggTbjifmOQF1 jqZ9DVDiSzD64CNsx930SaTBUCRkdTyZtTBaL4bG6K0r74Fpi2s0Bn/4RqHqbceiRd iQeesRtVa6So9rMV3BDNYQlCLqjzFKtFWicL6oqI=
Message-Id: <6.2.5.6.2.20121114030352.0da0e888@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 14 Nov 2012 03:19:14 -0800
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
In-Reply-To: <20121113144545.12836.71935.idtracker@ietfa.amsl.com>
References: <20121113144545.12836.71935.idtracker@ietfa.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Nov 2012 11:21:27 -0000

At 06:45 13-11-2012, The IESG wrote:
>The IESG has received a request from the Locator/ID Separation Protocol
>WG (lisp) to consider the following document:
>- 'LISP EID Block'
>   <draft-ietf-lisp-eid-block-03.txt> as Informational RFC
>
>The IESG plans to make a decision in the next few weeks, and solicits
>final comments on this action. Please send substantive comments to the
>ietf@ietf.org mailing lists by 2012-11-27. Exceptionally, comments may be

The document does not clearly define how the address space will be 
managed.  This might end up being problematic in future.

In Section 4:

  "Too guarantee reachability from the Legacy Internet the prefix could"

There is a typo for "Too".

In Section 6:

   "It is suggested to IANA to temporarily avoid allocating any
    other address block the same /12 prefix the EID /16 prefix
    belongs to.  This is to accommodate future requests of EID
    space without fragmenting the EID addressing space."

Shouldn't that be under IANA Considerations?

   "If in the future there will be need for a larger EID Block the
    address space adjacent the EID Block could be allocate by IANA
    according to the current policies."

Which policies does the above refer to?

In Section 10:

   "This document instructs the IANA to assign a /16 IPv6 prefix for use
    as the global LISP EID space using a hierarchical allocation as
    outlined in [RFC5226]."

Who will be the delegated managers?

   "Following the policies outlined in [RFC5226], such space
    will be assigned only upon IETF Review."

The previous sentence mentions hierarchical allocation and the above 
sentence mentions IETF Review.  It is not clear how assignments from 
this space will be made.

Regards,
-sm 


From carlosm3011@gmail.com  Wed Nov 14 08:49:03 2012
Return-Path: <carlosm3011@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 216C321F8669 for <ietf@ietfa.amsl.com>; Wed, 14 Nov 2012 08:49:03 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D+S9dXyYv4zk for <ietf@ietfa.amsl.com>; Wed, 14 Nov 2012 08:49:02 -0800 (PST)
Received: from mail-yh0-f44.google.com (mail-yh0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 9513821F8485 for <ietf@ietf.org>; Wed, 14 Nov 2012 08:49:02 -0800 (PST)
Received: by mail-yh0-f44.google.com with SMTP id 56so127529yhq.31 for <ietf@ietf.org>; Wed, 14 Nov 2012 08:49:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=kA5oXH79mJwrepzyQ5nUYuY9huP0LUrLlKCcdvri7Qw=; b=h8noyyMHpiNvObzzNIkwuty30f29hEiXAyFIJ2YeSHFureJ7ZhXNUYJto8FBZOxp1i yQ2T90Z2f7D31DSPYTxMwlRyGTbDx3ffZxHZfQNCc9MMfmaYkN2Y+jJu23IMbmUAyvXf 7YzvH13ci0Bz6/UsHBBtK0HBz61NrP4BHzEZlUuq5pjMAMRRAPyo9Bzoo2CpHatsTUhr jz/5b/XW9PdkeVb3pqsLDXKsoV9V3etvMxq2GfQ1YmWkWp/VxU0Wn2wamfI8IB4psSHB h358YiAVUZSEH3nPjIT9TRRORxFNJl3s6jgjhb2wZJqHcc6+plhTLac9MUUDi84A1zNy C/VA==
Received: by 10.236.176.8 with SMTP id a8mr26432467yhm.54.1352911741976; Wed, 14 Nov 2012 08:49:01 -0800 (PST)
Received: from europa.local ([200.7.85.162]) by mx.google.com with ESMTPS id a7sm13265735yhe.14.2012.11.14.08.49.00 (version=SSLv3 cipher=OTHER); Wed, 14 Nov 2012 08:49:01 -0800 (PST)
Message-ID: <50A3CB79.9000208@gmail.com>
Date: Wed, 14 Nov 2012 14:48:57 -0200
From: "Carlos M. Martinez" <carlosm3011@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
References: <CADnDZ8-fjxfgJys8sE10DdZ08tB8HdaTQXbPj2d7-OuQOGi9Pg@mail.gmail.com>	<CADnDZ8_v3M1fNtkOV4rU1F-iaMC+2qvKhR353vwESiQsfh70MQ@mail.gmail.com>	<9009A606-ACB8-4F25-992E-DF126822C591@checkpoint.com>	<CAKe6YvNbeRWvofqGCSDki3qs8LWpO0w-YBZVBGDeDQL+qn4m8A@mail.gmail.com>	<6.2.5.6.2.20121111071204.09a88780@resistor.net> <alpine.DEB.2.00.1211111856180.27834@uplift.swm.pp.se> <50A0AE92.8000300@gmail.com>
In-Reply-To: <50A0AE92.8000300@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Nov 2012 16:49:03 -0000

On 11/12/12 6:08 AM, Brian E Carpenter wrote:
> On 11/11/2012 18:06, Mikael Abrahamsson wrote:
> ...
... snip ...
> 
> There's no doubt that personal attendance is the best way to get a full
> understanding of how the IETF works, but remote participation is
> supposed to work.

I fully agree. However, I've found that the tools we use for remote
participation in the IETF are, IMO, a bit archaic. Don't get me wrong, I
fully support having Jabber rooms and audio streams, but, its really
difficult to follow a meeting that way, but I've had much better remote
participation experiences in other conferences than I've had with the IETF.

Meetecho is a good starting point, but it's not available in most
sessions and the quality of the video feed is very poor. It also suffers
from reliability issues where people get dropped from the session.

Having Meetecho available in most WG sessions would be a great bonus for
remote participants. If this is not possible, I think we should consider
having a registration mechanism for remote participants so the resources
can be better managed.

The key here is having the remote participants in mind, as a real
constituency. So far this is not the case, they are almost an
afterthought. Meetecho service can be improved including using real
cameras (not webcams attached to a notebook's display) and providing
adequate mounting points for the cameras, adequate lighting and marking
the space where the speakers should stand in order to be better captured
by the camera.

Warm regards,

~Carlos

From stephen.farrell@cs.tcd.ie  Wed Nov 14 09:01:04 2012
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 921DA21F9234 for <ietf@ietfa.amsl.com>; Wed, 14 Nov 2012 09:01:04 -0800 (PST)
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=[AWL=0.000, 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 9pHmRNTpPQOe for <ietf@ietfa.amsl.com>; Wed, 14 Nov 2012 09:01:03 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 3ED4E21F916D for <ietf@ietf.org>; Wed, 14 Nov 2012 09:01:03 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 57272BDCA; Wed, 14 Nov 2012 17:00:41 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uL7zvjI6t++P; Wed, 14 Nov 2012 17:00:40 +0000 (GMT)
Received: from [IPv6:2001:770:10:203:5c60:aea5:1779:debf] (unknown [IPv6:2001:770:10:203:5c60:aea5:1779:debf]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 70137BE1C; Wed, 14 Nov 2012 17:00:37 +0000 (GMT)
Message-ID: <50A3CE34.2080702@cs.tcd.ie>
Date: Wed, 14 Nov 2012 17:00:36 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121028 Thunderbird/16.0.2
MIME-Version: 1.0
To: "Carlos M. Martinez" <carlosm3011@gmail.com>
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
References: <CADnDZ8-fjxfgJys8sE10DdZ08tB8HdaTQXbPj2d7-OuQOGi9Pg@mail.gmail.com>	<CADnDZ8_v3M1fNtkOV4rU1F-iaMC+2qvKhR353vwESiQsfh70MQ@mail.gmail.com>	<9009A606-ACB8-4F25-992E-DF126822C591@checkpoint.com>	<CAKe6YvNbeRWvofqGCSDki3qs8LWpO0w-YBZVBGDeDQL+qn4m8A@mail.gmail.com>	<6.2.5.6.2.20121111071204.09a88780@resistor.net> <alpine.DEB.2.00.1211111856180.27834@uplift.swm.pp.se> <50A0AE92.8000300@gmail.com> <50A3CB79.9000208@gmail.com>
In-Reply-To: <50A3CB79.9000208@gmail.com>
X-Enigmail-Version: 1.4.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Nov 2012 17:01:04 -0000

On 11/14/2012 04:48 PM, Carlos M. Martinez wrote:
>  I've had much better remote
> participation experiences in other conferences than I've had with the IETF.

Can you provide pointers?

Ta,
S.

From tglassey@earthlink.net  Wed Nov 14 09:06:10 2012
Return-Path: <tglassey@earthlink.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 73C6721F85C4 for <ietf@ietfa.amsl.com>; Wed, 14 Nov 2012 09:06:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.175
X-Spam-Level: 
X-Spam-Status: No, score=-2.175 tagged_above=-999 required=5 tests=[AWL=-0.176, BAYES_00=-2.599, J_CHICKENPOX_21=0.6]
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 NVAaAMIUtaWd for <ietf@ietfa.amsl.com>; Wed, 14 Nov 2012 09:06:09 -0800 (PST)
Received: from elasmtp-kukur.atl.sa.earthlink.net (elasmtp-kukur.atl.sa.earthlink.net [209.86.89.65]) by ietfa.amsl.com (Postfix) with ESMTP id AD96E21F86CB for <ietf@ietf.org>; Wed, 14 Nov 2012 09:06:09 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=MCklioFY+j2yH70iUVrFPZoDnrFhVZcff6XGmPhKNWUM/YFw9mqWcSFFfbi7xqOW; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [67.180.133.21] (helo=[192.168.15.2]) by elasmtp-kukur.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <tglassey@earthlink.net>) id 1TYgPg-0003UK-PN; Wed, 14 Nov 2012 12:06:08 -0500
Message-ID: <50A3CF7F.9040707@earthlink.net>
Date: Wed, 14 Nov 2012 09:06:07 -0800
From: tglassey <tglassey@earthlink.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: ietf@ietf.org, Jorge Contreras <contreraslegal@att.net>
Subject: REMOTE PARTICIPATION TEMPLATES: was Re: Newcomers [Was: Evolutionizing the IETF]
References: <CADnDZ8-fjxfgJys8sE10DdZ08tB8HdaTQXbPj2d7-OuQOGi9Pg@mail.gmail.com>	<CADnDZ8_v3M1fNtkOV4rU1F-iaMC+2qvKhR353vwESiQsfh70MQ@mail.gmail.com>	<9009A606-ACB8-4F25-992E-DF126822C591@checkpoint.com>	<CAKe6YvNbeRWvofqGCSDki3qs8LWpO0w-YBZVBGDeDQL+qn4m8A@mail.gmail.com>	<6.2.5.6.2.20121111071204.09a88780@resistor.net> <alpine.DEB.2.00.1211111856180.27834@uplift.swm.pp.se> <50A0AE92.8000300@gmail.com> <50A3CB79.9000208@gmail.com>
In-Reply-To: <50A3CB79.9000208@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec796b08468e6e09889cf1d11ee63e09b941350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 67.180.133.21
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Nov 2012 17:06:10 -0000

On 11/14/2012 8:48 AM, Carlos M. Martinez wrote:
>
> On 11/12/12 6:08 AM, Brian E Carpenter wrote:
>> On 11/11/2012 18:06, Mikael Abrahamsson wrote:
>> ...
> ... snip ...
>> There's no doubt that personal attendance is the best way to get a full
>> understanding of how the IETF works, but remote participation is
>> supposed to work.
> I fully agree. However, I've found that the tools we use for remote
> participation in the IETF are, IMO, a bit archaic.
There is no reason ComeToMeeting or other service like it is not used to 
fully integrate a WG allowing remote participation. For those that dont 
their charter is the key thing - i.e. whether they also need to actually 
not do any formal deciding of anything at meetings and votes or work 
done at meeting is like all other NoteWell constrained IP, tied to the 
IETF's collection-consensus processes.
> Don't get me wrong, I
> fully support having Jabber rooms and audio streams, but, its really
> difficult to follow a meeting that way, but I've had much better remote
> participation experiences in other conferences than I've had with the IETF.

That said - there is a larger issue and its how individual WG's operate 
relative to any responsibility to provide online access to meetings. I 
think that the Remote Participation Rules for the WG are part of the WG 
charter and need to be included so everyone knows what the IP collection 
and NoteWell Management Practice for that WG is going to be since each 
standard process is different to some extent. That said - the process 
and framework for each WG effort is also independent from most others as 
well with the limited exception of instances where a WG served a whole 
class of layer-2 or layer-3 application contexts like PKIX did for 
instance.

What I propose - and this may sound initially wonky but think about it - 
that someone, and it should be one or a group of the IPR people I think, 
put together a set of "WG Charter Templates" as an Internet-Draft(s). 
What no one has stepped to yet is that processes inside WG;s need the 
same type of resolution in their make up as things like the BCP78/79 
specify for the higher-level (boilerplate) issues.

The template should have in it a set of models which can be selected in 
a cafeteria style selection for "REMOTE PARTICIPATION RULES AND 
IMPLICATIONS". This would specify IP processing workflows for how 
NoteWell controlled content was brought into the group through meetings 
and what archival processes would be necessary for that as well. That 
way everyone knows what they are getting into and the framework for the 
WG's practices are set during its operations.

This actually will work and would help the organization out a lot - I 
hope you can address the idea and what power it would give the IETF 
without cringing that it is me suggesting it.

Todd
>
> Meetecho is a good starting point, but it's not available in most
> sessions and the quality of the video feed is very poor. It also suffers
> from reliability issues where people get dropped from the session.
>
> Having Meetecho available in most WG sessions would be a great bonus for
> remote participants. If this is not possible, I think we should consider
> having a registration mechanism for remote participants so the resources
> can be better managed.
>
> The key here is having the remote participants in mind, as a real
> constituency. So far this is not the case, they are almost an
> afterthought. Meetecho service can be improved including using real
> cameras (not webcams attached to a notebook's display) and providing
> adequate mounting points for the cameras, adequate lighting and marking
> the space where the speakers should stand in order to be better captured
> by the camera.
>
> Warm regards,
>
> ~Carlos
>
>
> -----
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2013.0.2793 / Virus Database: 2629/5893 - Release Date: 11/13/12
>
>


-- 
Regards TSG
"Ex-Cruce-Leo"

//Confidential Mailing - Please destroy this if you are not the intended recipient.


From nick@inex.ie  Wed Nov 14 09:11:50 2012
Return-Path: <nick@inex.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A737621F8660 for <ietf@ietfa.amsl.com>; Wed, 14 Nov 2012 09:11:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-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 0yAPfqxvnyzP for <ietf@ietfa.amsl.com>; Wed, 14 Nov 2012 09:11:49 -0800 (PST)
Received: from mail.acquirer.com (mail.acquirer.com [IPv6:2a03:8900:0:100::5]) by ietfa.amsl.com (Postfix) with ESMTP id 586B021F865D for <ietf@ietf.org>; Wed, 14 Nov 2012 09:11:48 -0800 (PST)
X-Envelope-To: ietf@ietf.org
Received: from crumpet.dyn.netability.ie ([IPv6:2001:1bb8:2004:200:711d:6aed:9344:9dde]) (authenticated bits=0) by mail.acquirer.com (8.14.4/8.14.4) with ESMTP id qAEH89Os095374 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 14 Nov 2012 17:08:09 GMT (envelope-from nick@inex.ie)
Message-ID: <50A3D039.9060009@inex.ie>
Date: Wed, 14 Nov 2012 17:09:13 +0000
From: Nick Hilliard <nick@inex.ie>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
References: <CADnDZ8-fjxfgJys8sE10DdZ08tB8HdaTQXbPj2d7-OuQOGi9Pg@mail.gmail.com>	<CADnDZ8_v3M1fNtkOV4rU1F-iaMC+2qvKhR353vwESiQsfh70MQ@mail.gmail.com>	<9009A606-ACB8-4F25-992E-DF126822C591@checkpoint.com>	<CAKe6YvNbeRWvofqGCSDki3qs8LWpO0w-YBZVBGDeDQL+qn4m8A@mail.gmail.com>	<6.2.5.6.2.20121111071204.09a88780@resistor.net> <alpine.DEB.2.00.1211111856180.27834@uplift.swm.pp.se> <50A0AE92.8000300@gmail.com> <50A3CB79.9000208@gmail.com> <50A3CE34.2080702@cs.tcd.ie>
In-Reply-To: <50A3CE34.2080702@cs.tcd.ie>
X-Enigmail-Version: 1.4.5
X-Company-Info-1: Internet Neutral Exchange Association Limited. Registered in Ireland No. 253804
X-Company-Info-2: Registered Offices: 1-2, Marino Mart, Fairview, Dublin 3
X-Company-Info-3: Internet Neutral Exchange Association Limited is limited by guarantee
X-Company-Info-4: Offices: 4027 Kingswood Road, Citywest, Dublin 24.
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Nov 2012 17:11:50 -0000

On 14/11/2012 17:00, Stephen Farrell wrote:
> Can you provide pointers?

Lots of meetings (e.g. ixp meetings, etc) do live video, although I'd
accept that not that many meetings have as many parallel tracks as IETF.

RIPE meetings provide both live video streaming and live stenography (they
use dcr.ie for this, who are now trained to be very good with tech topics
and people with strong accents).  This is very cool, but I understand that
it is also expensive.

Nick


From cabo@tzi.org  Wed Nov 14 09:34:41 2012
Return-Path: <cabo@tzi.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC65C21F86FF for <ietf@ietfa.amsl.com>; Wed, 14 Nov 2012 09:34:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.467
X-Spam-Level: 
X-Spam-Status: No, score=-106.467 tagged_above=-999 required=5 tests=[AWL=-0.218, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, 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 4q2-Kw6yFBGM for <ietf@ietfa.amsl.com>; Wed, 14 Nov 2012 09:34:41 -0800 (PST)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id 0D6D521F86B8 for <ietf@ietf.org>; Wed, 14 Nov 2012 09:34:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.3/8.14.3) with ESMTP id qAEHYQa4025607; Wed, 14 Nov 2012 18:34:26 +0100 (CET)
Received: from [192.168.217.105] (p54891ABE.dip.t-dialin.net [84.137.26.190]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id C5519B53; Wed, 14 Nov 2012 18:34:25 +0100 (CET)
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Content-Type: text/plain; charset=iso-8859-1
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <50A13B43.7000309@dcrocker.net>
Date: Wed, 14 Nov 2012 18:34:24 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <72F0897C-D473-4F34-8D21-B9A60DDBBB09@tzi.org>
References: <201211121745.qACHjiXS919660@shell01.TheWorld.com> <50A13B43.7000309@dcrocker.net>
To: dcrocker@bbiw.net
X-Mailer: Apple Mail (2.1499)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Nov 2012 17:34:41 -0000

On Nov 12, 2012, at 19:09, Dave Crocker <dhc@dcrocker.net> wrote:

> Some people believe that the presence of an IETF meeting serves as a =
kind of recruitment marketing to a region, for IETF participation. =
Beyond the single-meeting boost in 'local' attendance, I believe we have =
no data confirming any on-going increase in participation by people from =
that region.  After 20 years, we ought to have hard data.

I don't have hard data, but anecdotally, I'm not so sure about that.
Historically, while the IETF still as in its growth phase in the 1990s, =
the touring around was useful.
I'd even say the 2002 (JP) and 2004 (KR) meetings were useful for =
broadening the base.

After that, not so much.

(Another aspect beyond capturing regular attendees, of course, is =
gaining local mindshare and relevance. =20
Being a German, I do expect the Berlin meeting to help in that =
dimension, as did Maastricht (a bit less so), Munich, and Amsterdam.
Similarly, I think the meetings in Prague were very useful for =
visibility in other central European countries.
Hitting the focal points of economy and culture is more important here =
than a close-by airport.
There *is* an -- indirect and more long-term -- effect of this on =
participation from the parts of the world we reach this way.)

Gr=FC=DFe, Carsten


From carlosm3011@gmail.com  Wed Nov 14 11:09:20 2012
Return-Path: <carlosm3011@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F9E421F8721 for <ietf@ietfa.amsl.com>; Wed, 14 Nov 2012 11:09:20 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j9lTPujlVK98 for <ietf@ietfa.amsl.com>; Wed, 14 Nov 2012 11:09:19 -0800 (PST)
Received: from mail-yh0-f44.google.com (mail-yh0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id C297D21F8695 for <ietf@ietf.org>; Wed, 14 Nov 2012 11:09:19 -0800 (PST)
Received: by mail-yh0-f44.google.com with SMTP id 56so175626yhq.31 for <ietf@ietf.org>; Wed, 14 Nov 2012 11:09:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=rrit3WTkCRfZngGrbgUHaDQlbLdeWm1ENpd6Uq3Yvdw=; b=XtuH9526/pV3eHgBiBy797TySMi25IT4yjgWnPvjAiMYWUQdOXWusyPa3MeqpXptkl V1evGMYBwBR9qbH9LQXOd7srvTP0CEtGCC7pPE9j2SJ/ZeZRru/QLnokZWS7cVaBLO5Y 5zO0VX8BB5CiyO0wMe4IBxWk7XEe0x1lDS4oR8U7V1b9m6Om+5b8o3PqP1BlFIrK78vH 2sZwIl9lNKZi/2GmyqZxP6ENLOSHE14jCvPaql8yoehzTBiqz1hgSaBWTvibR7Q1l7QG S/VHhdcbXM8g10wm7qhUnzxye9yhZ3aTiYfb+5pEo2fUTdp4OKqd+L5ewg+UlaFFYH0E IxsA==
Received: by 10.236.86.73 with SMTP id v49mr27666678yhe.31.1352920159391; Wed, 14 Nov 2012 11:09:19 -0800 (PST)
Received: from europa.local ([200.7.85.162]) by mx.google.com with ESMTPS id u49sm13655716yhd.18.2012.11.14.11.09.17 (version=SSLv3 cipher=OTHER); Wed, 14 Nov 2012 11:09:18 -0800 (PST)
Message-ID: <50A3EC5A.7090600@gmail.com>
Date: Wed, 14 Nov 2012 17:09:14 -0200
From: "Carlos M. Martinez" <carlosm3011@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
References: <CADnDZ8-fjxfgJys8sE10DdZ08tB8HdaTQXbPj2d7-OuQOGi9Pg@mail.gmail.com>	<CADnDZ8_v3M1fNtkOV4rU1F-iaMC+2qvKhR353vwESiQsfh70MQ@mail.gmail.com>	<9009A606-ACB8-4F25-992E-DF126822C591@checkpoint.com>	<CAKe6YvNbeRWvofqGCSDki3qs8LWpO0w-YBZVBGDeDQL+qn4m8A@mail.gmail.com>	<6.2.5.6.2.20121111071204.09a88780@resistor.net> <alpine.DEB.2.00.1211111856180.27834@uplift.swm.pp.se> <50A0AE92.8000300@gmail.com> <50A3CB79.9000208@gmail.com> <50A3CE34.2080702@cs.tcd.ie>
In-Reply-To: <50A3CE34.2080702@cs.tcd.ie>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Nov 2012 19:09:20 -0000

Sure!

- ICANN (Adobe Connect, so far the best I've experienced)

- Various training webinars, both as an attendee and as instructor using
the training edition of WebEx

- NANOG's video feeds are very good, although I don't recall the
platform they use (I'm sure someone will point us to it)

- Our own video feeds (LACNIC) are quite good, although we're lacking
adequate integration with the slides. Whenever possible we have two
cameras, one pointing to the speaker and one pointing to the projection
screen and the camera director switches from the speaker to the slides
when the slides change.

We even have managed to provide multi-language simultaneous translation
using the same video feed and different audio channels. Mileage varies
from venue to venue but our different language communities are usually
able to follow the presentations and the public policy forum.

regards,

~Carlos


On 11/14/12 3:00 PM, Stephen Farrell wrote:
> 
> 
> On 11/14/2012 04:48 PM, Carlos M. Martinez wrote:
>>  I've had much better remote
>> participation experiences in other conferences than I've had with the IETF.
> 
> Can you provide pointers?
> 
> Ta,
> S.
> 

From dhc@dcrocker.net  Wed Nov 14 11:59:25 2012
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0751121F8602 for <ietf@ietfa.amsl.com>; Wed, 14 Nov 2012 11:59:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.945
X-Spam-Level: 
X-Spam-Status: No, score=-4.945 tagged_above=-999 required=5 tests=[AWL=0.011,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, RCVD_IN_NJABL_PROXY=1.643]
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 Gqjz2AFwjUTZ for <ietf@ietfa.amsl.com>; Wed, 14 Nov 2012 11:59:24 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 2920A21F885D for <ietf@ietf.org>; Wed, 14 Nov 2012 11:59:24 -0800 (PST)
Received: from [192.168.1.9] (adsl-67-127-56-94.dsl.pltn13.pacbell.net [67.127.56.94]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id qAEJxMuC015011 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 14 Nov 2012 11:59:23 -0800
Message-ID: <50A3F814.1030509@dcrocker.net>
Date: Wed, 14 Nov 2012 11:59:16 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: Carsten Bormann <cabo@tzi.org>
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
References: <201211121745.qACHjiXS919660@shell01.TheWorld.com> <50A13B43.7000309@dcrocker.net> <72F0897C-D473-4F34-8D21-B9A60DDBBB09@tzi.org>
In-Reply-To: <72F0897C-D473-4F34-8D21-B9A60DDBBB09@tzi.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Wed, 14 Nov 2012 11:59:23 -0800 (PST)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Nov 2012 19:59:25 -0000

On 11/14/2012 9:34 AM, Carsten Bormann wrote:
> (Another aspect beyond capturing regular attendees, of course, is
> gaining local mindshare and relevance.

I believe I understand the concepts that are meant by such language. 
But I do not know what you mean, with respect to the IETF.  I especially 
do not know what you mean, in terms of the IETF's getting its work done.

Ultimately, if the IETF does not have the mindshare among the people who 
consume our work, I believe that it is better accomplished by doing work 
that has more community involvement and more operational relevance.  If 
we do that, it won't matter where we hold our meetings.

One argument for our going to many different places is that it makes the 
IETF more 'credible' because the IETF is "seen".  However I believe few 
International standards groups do traveling shows like the IETF, and 
they manage to be seen as credible.

In other words, I would have that our relevance is determined more by 
the quality and utility of our work than by the marketing effects of 
meeting venue.


> Similarly, I think the meetings
> in Prague were very useful for visibility in other central European
> countries. Hitting the focal points of economy and culture is more
> important here than a close-by airport. There *is* an -- indirect and
> more long-term -- effect of this on participation from the parts of
> the world we reach this way.)

Again, finding meeting venues that work well for an IETF venue is quite 
difficult. When we add other goals, such as marketing the IETF to the 
community, we make venue selection especially difficult.

In fact I believe, we actually wind up making the IETF more 
/exclusionary/ rather than more /inclusive/ because we raise the barrier 
to participation for serious participants, most notably participants 
with less time and money that the average, corporate-funded attendee...

Showing up in various places does not make the work better.  It might 
have outward marketing benefits for the image of the IETF. 
Historically, the IETF has done better by worrying less about its image 
and more about the utility of its work.

d/

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From hartmans@mit.edu  Wed Nov 14 12:53:14 2012
Return-Path: <hartmans@mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C94F621F8512 for <ietf@ietfa.amsl.com>; Wed, 14 Nov 2012 12:53:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.521
X-Spam-Level: 
X-Spam-Status: No, score=-102.521 tagged_above=-999 required=5 tests=[AWL=0.078, 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 BF3qEIiGKBW1 for <ietf@ietfa.amsl.com>; Wed, 14 Nov 2012 12:53:13 -0800 (PST)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id 242A021F84FC for <ietf@ietf.org>; Wed, 14 Nov 2012 12:53:12 -0800 (PST)
Received: from carter-zimmerman.suchdamage.org (c-98-217-126-210.hsd1.ma.comcast.net [98.217.126.210]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.painless-security.com (Postfix) with ESMTPS id 35EB720178; Wed, 14 Nov 2012 15:52:00 -0500 (EST)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 875684149; Wed, 14 Nov 2012 15:53:07 -0500 (EST)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: "Carlos M. Martinez" <carlosm3011@gmail.com>
Subject: Re: Newcomers
References: <CADnDZ8-fjxfgJys8sE10DdZ08tB8HdaTQXbPj2d7-OuQOGi9Pg@mail.gmail.com> <CADnDZ8_v3M1fNtkOV4rU1F-iaMC+2qvKhR353vwESiQsfh70MQ@mail.gmail.com> <9009A606-ACB8-4F25-992E-DF126822C591@checkpoint.com> <CAKe6YvNbeRWvofqGCSDki3qs8LWpO0w-YBZVBGDeDQL+qn4m8A@mail.gmail.com> <6.2.5.6.2.20121111071204.09a88780@resistor.net> <alpine.DEB.2.00.1211111856180.27834@uplift.swm.pp.se> <50A0AE92.8000300@gmail.com> <50A3CB79.9000208@gmail.com> <50A3CE34.2080702@cs.tcd.ie> <50A3EC5A.7090600@gmail.com>
Date: Wed, 14 Nov 2012 15:53:07 -0500
In-Reply-To: <50A3EC5A.7090600@gmail.com> (Carlos M. Martinez's message of "Wed, 14 Nov 2012 17:09:14 -0200")
Message-ID: <tslzk2jlxe4.fsf@mit.edu>
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
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Nov 2012 20:53:14 -0000

>>>>> "Carlos" == Carlos M Martinez <carlosm3011@gmail.com> writes:

    Carlos> Sure!  - ICANN (Adobe Connect, so far the best I've
    Carlos> experienced)


I had my first Adobe connect experience today.  I care a lot more about
accessibility than most participants do.  On this metric Adobe Connect
seems to score very badly. If we went to Adobe Connect it would
significantly decrease my ability to participate to the extent that
using Adobe Connect was a requirement.  I could not interact with the
chat room associated with a meeting at all.

From dhc@dcrocker.net  Wed Nov 14 13:01:15 2012
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 169D921F857D for <ietf@ietfa.amsl.com>; Wed, 14 Nov 2012 13:01:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.946
X-Spam-Level: 
X-Spam-Status: No, score=-5.946 tagged_above=-999 required=5 tests=[AWL=1.010,  BAYES_00=-2.599, GB_I_INVITATION=-2, RCVD_IN_DNSWL_MED=-4, RCVD_IN_NJABL_PROXY=1.643]
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 hAC+p7HP+mok for <ietf@ietfa.amsl.com>; Wed, 14 Nov 2012 13:01:14 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 6601321F8563 for <ietf@ietf.org>; Wed, 14 Nov 2012 13:01:14 -0800 (PST)
Received: from [192.168.1.9] (adsl-67-127-56-94.dsl.pltn13.pacbell.net [67.127.56.94]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id qAEL1Dbb016083 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 14 Nov 2012 13:01:13 -0800
Message-ID: <50A40693.5000206@dcrocker.net>
Date: Wed, 14 Nov 2012 13:01:07 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: Sam Hartman <hartmans-ietf@mit.edu>
Subject: Accessible remote participation usability (was -- Re: Newcomers)
References: <CADnDZ8-fjxfgJys8sE10DdZ08tB8HdaTQXbPj2d7-OuQOGi9Pg@mail.gmail.com> <CADnDZ8_v3M1fNtkOV4rU1F-iaMC+2qvKhR353vwESiQsfh70MQ@mail.gmail.com> <9009A606-ACB8-4F25-992E-DF126822C591@checkpoint.com> <CAKe6YvNbeRWvofqGCSDki3qs8LWpO0w-YBZVBGDeDQL+qn4m8A@mail.gmail.com> <6.2.5.6.2.20121111071204.09a88780@resistor.net> <alpine.DEB.2.00.1211111856180.27834@uplift.swm.pp.se> <50A0AE92.8000300@gmail.com> <50A3CB79.9000208@gmail.com> <50A3CE34.2080702@cs.tcd.ie> <50A3EC5A.7090600@gmail.com> <tslzk2jlxe4.fsf@mit.edu>
In-Reply-To: <tslzk2jlxe4.fsf@mit.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Wed, 14 Nov 2012 13:01:14 -0800 (PST)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Nov 2012 21:01:15 -0000

On 11/14/2012 12:53 PM, Sam Hartman wrote:
> I had my first Adobe connect experience today.  I care a lot more about
> accessibility than most participants do.  On this metric Adobe Connect
> seems to score very badly.


Sam, it could be quite helpful for you to suggest factors that you find 
relevant in using remote participation tools and provide details about 
how well they are accomplished by not only Adobe Connect, but Webex and 
Meetecho.

To the extent that you have suggestions for what would work "best", that 
could be useful too, of course.

d/

ps. this is meant as an open invitation for anyone with a serious basis 
for commenting on accessible usability in remote participation tools.

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From ben@nostrum.com  Wed Nov 14 15:39:47 2012
Return-Path: <ben@nostrum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 524A521F8660; Wed, 14 Nov 2012 15:39:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.45
X-Spam-Level: 
X-Spam-Status: No, score=-101.45 tagged_above=-999 required=5 tests=[AWL=-1.150, BAYES_00=-2.599, MANGLED_LIST=2.3, SPF_PASS=-0.001,  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 OGeYkFykbtEv; Wed, 14 Nov 2012 15:39:46 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 60E8721F8651; Wed, 14 Nov 2012 15:39:46 -0800 (PST)
Received: from [10.12.11.26] ([4.30.77.1]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id qAENddqH070040 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 14 Nov 2012 17:39:41 -0600 (CST) (envelope-from ben@nostrum.com)
From: Ben Campbell <ben@nostrum.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Subject: Gen-ART LC Review of draft-ietf-karp-routing-tcp-analysis-05.txt
Date: Wed, 14 Nov 2012 17:39:39 -0600
Message-Id: <18E6B18A-D465-47C6-9E06-886DFBFA1F67@nostrum.com>
To: draft-ietf-karp-routing-tcp-analysis.all@tools.ietf.org
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
X-Mailer: Apple Mail (2.1499)
Received-SPF: pass (nostrum.com: 4.30.77.1 is authenticated by a trusted mechanism)
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, "ietf@ietf.org List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Nov 2012 23:39:47 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at

<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments
you may receive.

Document: draft-ietf-karp-routing-tcp-analysis-05.txt
Reviewer: Ben Campbell
Review Date: 2012-11-14
IETF LC End Date: 2012-11-19

Summary: This draft is almost ready for publication as an informational =
RFC. There are a few minor issues and a number of editorial issues that =
should be considered prior to publication.

*** Major issues ***:

None

*** Minor issues *** :

-- section 2.2, last paragraph:

The IKE mention lacks context. Do you mean to suggest IKE with IPSec? I =
assume so, but there's been no mention of IPSec so far.

-- section 2.3.2:

It would be helpful for this section to describe whether privacy issues =
actually matter or not, rather than just stating the issues to be =
similar to those for other routing protocols.

-- section 3.1, 2nd paragraph:

Does this mean that privacy is really not needed, or just that LDP does =
not state a requirement for privacy?

-- Section 6 (Security Considerations), 4th paragraph:

If replay protection is required, shouldn't the draft discuss the =
details somewhere? I see only one mention in passing outside of this =
section.

*** Nits/editorial comments ***:

-- IDNits indicates some unused and obsoleted references. Please check.

-- The IANA considerations section is missing. If the draft makes =
requests of IANA, it should include the section and state that.

-- the short title is "The IANA considerations section is missing. If =
the draft makes requests of IANA, it should include the section and say =
that

-- The short title is "draft-ietf-karp-routing-tcp-analysis-05.txt". Is =
this draft in any way specific to TCP? If so, it would be helpful to =
mention that in the abstract and introduction.

-- Punctuation errors are pervasive, particularly in the early and late =
sections. These make it harder to read than it needs to be. In =
particular, I suggest the draft be proofread for missing commas and =
missing quotes (or other marks) around document titles.

-- Section 1, paragraph 1:

The cited doc name should be quoted, or otherwise marked. Also, it's not =
necessary to put the full reference here, since you are citing the =
references section.

-- Section 1, paragraph 1: "Four main steps were identified for that =
tightening:"

For what tightening? This is the first mention. Perhaps the previous =
sentence should have gone on to say "... and suggests steps to tighten =
the infrastructure against the attack"?

-- section 1, 1st paragraph after numbered list:

The end of the paragraph does not seem related to the beginning. I =
suggest a paragraph split before the sentence starting with "The OPSEC =
working group..."=20

-- section 1, 2nd to last paragraph: "current state of security method"

Missing article before "security method".

-- section 1.1:

Why is 2119 language needed? I see two potentially normative =
statements--but both of those merely describe the existing MAC =
requirements in TCP-AO. It would be better to state those in descriptive =
language (e.g. TCP-AO requires=85) and to drop the 2119 section =
entirely.=20

-- section 2.1,  5th paragraph:

A mention of SHA1 seems needed here. Section 2.3.1.2 states the concerns =
about TCP-md5 more clearly.

-- section 2.3.1.2, 1st paragraph: "As stated above..."

A section reference would be helpful.

-- section 4, 2nd paragraph: "In addition Improving TCP=92s Robustness =
to Blind In-Window Attacks."

sentence fragment.

-- section 4, 3rd paragraph:

It would have been helpful to mention the MKT manual config issue back =
in the "state of the security method" sections.



From arturo.servin@gmail.com  Wed Nov 14 17:24:16 2012
Return-Path: <arturo.servin@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9DA4E21F86D1 for <ietf@ietfa.amsl.com>; Wed, 14 Nov 2012 17:24:16 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wjKQj7cPottC for <ietf@ietfa.amsl.com>; Wed, 14 Nov 2012 17:24:16 -0800 (PST)
Received: from mail-gh0-f181.google.com (mail-gh0-f181.google.com [209.85.160.181]) by ietfa.amsl.com (Postfix) with ESMTP id 083BE21F867F for <ietf@ietf.org>; Wed, 14 Nov 2012 17:24:15 -0800 (PST)
Received: by mail-gh0-f181.google.com with SMTP id z22so299914ghb.26 for <ietf@ietf.org>; Wed, 14 Nov 2012 17:24:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=uN76EE80hKAXIw2vOgqSCli7tBupF/mjo+toyMZXnLI=; b=Y5HBH+aMFaQBlbSM1AyW6VizFtzQZepSBv8oK7eJzPAJAkcQV9FLOWce7NoWnv/27e IKmbzIBeeUgMJxtFTwSiBrUiaJUM06fHKKiFk51El/Et4g0010cQ8cmIsdzD2Wu2OiUp rS4nWRDnrThveI0ZUyelpQMRbbJSmlOUWIGhcfrcI/7qvgY2oHN9oDwysPguDXfc9AZr KyA+FMIiW0tiS75xlpvmoPC98WhNufwGRZG5pMDARYVEgGq0BlqV+q6Qj/iHi7j9NcJ5 2azZqx1si1NKAW47EAqNjgFm1S9NgtlC4VTZCtlE/ApANeOsunhSGDolUUtRy3cynAB+ hHiA==
Received: by 10.236.82.169 with SMTP id o29mr28095750yhe.116.1352942655577; Wed, 14 Nov 2012 17:24:15 -0800 (PST)
Received: from [192.168.1.133] (r186-48-250-8.dialup.adsl.anteldata.net.uy. [186.48.250.8]) by mx.google.com with ESMTPS id e24sm14607111yhh.4.2012.11.14.17.24.12 (version=SSLv3 cipher=OTHER); Wed, 14 Nov 2012 17:24:14 -0800 (PST)
Message-ID: <50A44418.2010707@gmail.com>
Date: Wed, 14 Nov 2012 23:23:36 -0200
From: Arturo Servin <arturo.servin@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
References: <201211121745.qACHjiXS919660@shell01.TheWorld.com> <50A13B43.7000309@dcrocker.net> <72F0897C-D473-4F34-8D21-B9A60DDBBB09@tzi.org> <50A3F814.1030509@dcrocker.net>
In-Reply-To: <50A3F814.1030509@dcrocker.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Nov 2012 01:24:16 -0000

Dave

On 14/11/2012 17:59, Dave Crocker wrote:
> 
> 
> On 11/14/2012 9:34 AM, Carsten Bormann wrote:
>> (Another aspect beyond capturing regular attendees, of course, is
>> gaining local mindshare and relevance.
> 
> I believe I understand the concepts that are meant by such language. But
> I do not know what you mean, with respect to the IETF.  I especially do
> not know what you mean, in terms of the IETF's getting its work done.
> 
> Ultimately, if the IETF does not have the mindshare among the people who
> consume our work, I believe that it is better accomplished by doing work
> that has more community involvement and more operational relevance.  If
> we do that, it won't matter where we hold our meetings.
> 
> One argument for our going to many different places is that it makes the
> IETF more 'credible' because the IETF is "seen".  However I believe few
> International standards groups do traveling shows like the IETF, and
> they manage to be seen as credible.

	I wouldn't count today's "traveling shows" as "traveling". It gives the
idea that the IETF goes to many places, it is not.


> 
> In other words, I would have that our relevance is determined more by
> the quality and utility of our work than by the marketing effects of
> meeting venue.

	Agree on that. But I disagree that going to other countries outside
north america is marketing.

> 
> 
>> Similarly, I think the meetings
>> in Prague were very useful for visibility in other central European
>> countries. Hitting the focal points of economy and culture is more
>> important here than a close-by airport. There *is* an -- indirect and
>> more long-term -- effect of this on participation from the parts of
>> the world we reach this way.)
> 
> Again, finding meeting venues that work well for an IETF venue is quite
> difficult. When we add other goals, such as marketing the IETF to the
> community, we make venue selection especially difficult.
> 
> In fact I believe, we actually wind up making the IETF more
> /exclusionary/ rather than more /inclusive/ because we raise the barrier
> to participation for serious participants, most notably participants
> with less time and money that the average, corporate-funded attendee...

	Agree. But also people (and perhaps organisations, that also are
serious participants) in Latin America, Africa, and some parts of Asia
has less income than their counterparts in North America. Some of the
people from those places do serious efforts to attend the IETF.

	So, are where is the exclusionary?

> 
> Showing up in various places does not make the work better.  It might
> have outward marketing benefits for the image of the IETF. Historically,
> the IETF has done better by worrying less about its image and more about
> the utility of its work.

	Again, I disagree that is pure marketing.

	The IETF has done a great job, but it is time to evolve.

Regards,
as


> 
> d/
> 

From melinda.shore@gmail.com  Wed Nov 14 17:55:18 2012
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5DFCB21F84D8 for <ietf@ietfa.amsl.com>; Wed, 14 Nov 2012 17:55:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.688
X-Spam-Level: 
X-Spam-Status: No, score=-3.688 tagged_above=-999 required=5 tests=[AWL=-0.089, 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 8qiBLU4Otmzv for <ietf@ietfa.amsl.com>; Wed, 14 Nov 2012 17:55:12 -0800 (PST)
Received: from mail-da0-f44.google.com (mail-da0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id 8145321F84D5 for <ietf@ietf.org>; Wed, 14 Nov 2012 17:55:12 -0800 (PST)
Received: by mail-da0-f44.google.com with SMTP id h15so445609dan.31 for <ietf@ietf.org>; Wed, 14 Nov 2012 17:55:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=ltkJYyfcSQ0U/0YUqjWjcaHiJUkzbZOimz0OG27kIn8=; b=iGPJvrQSDqZBuBNVDxrMWLFrOQjIJVDnBzBTuR8J1LYgTRboKLpNqz1I1kCuJxlwht z/pNdDzWpNgw3wShIN2QVpq4JlrEtLDoWMz1bn9Dw77sY0LM5Y+IL3wzAWJLpP0pIQKC uiD13QM2EA/HTvLYeBSn9RECrCPrD0al7gszWiU+V2NRygE4SapW07cu5ATz1xw1m3lY OmgPWOlpDlwU/knihSvBqbn8zrg8B73M1ZrbSq3s1eI6tf7FM711CbtaBo8ckWsLyYRf IVPABh7eV2dxJ9MhjWIXvkZmSo6oOw1j63KpI7RDQcvlUEDWjjTAzgU/8CJqLYU8zN87 LR6Q==
Received: by 10.68.189.70 with SMTP id gg6mr54241133pbc.97.1352944512225; Wed, 14 Nov 2012 17:55:12 -0800 (PST)
Received: from spandex.local (216-67-46-210-rb1.fai.dsl.dynamic.acsalaska.net. [216.67.46.210]) by mx.google.com with ESMTPS id v9sm8823122paz.6.2012.11.14.17.55.10 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 14 Nov 2012 17:55:11 -0800 (PST)
Message-ID: <50A44B7C.10103@gmail.com>
Date: Wed, 14 Nov 2012 16:55:08 -0900
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
References: <201211121745.qACHjiXS919660@shell01.TheWorld.com> <50A13B43.7000309@dcrocker.net> <72F0897C-D473-4F34-8D21-B9A60DDBBB09@tzi.org> <50A3F814.1030509@dcrocker.net> <50A44418.2010707@gmail.com>
In-Reply-To: <50A44418.2010707@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Nov 2012 01:55:18 -0000

On 11/14/12 4:23 PM, Arturo Servin wrote:
> 	Agree. But also people (and perhaps organisations, that also are
> serious participants) in Latin America, Africa, and some parts of Asia
> has less income than their counterparts in North America. Some of the
> people from those places do serious efforts to attend the IETF.

I have very, very little doubt that operators in less wealthy
countries are running into problems that are unfamiliar to most
IETF participants, and that need some attention from protocol
weenies.  But, that said, work in the IETF is focused on
progressing documents and that requires continuity on the part
of participants.  If someone can only attend when a meeting
is geographically close, that suggests that they'll attend
one meeting every <bignum> years.  If they feel that remote
participation is sufficient, that's available now.  So, I'm
not sure that what you're arguing addresses the reason there's
an IETF in the first place, and IETF working method, in the
second.  I think that's probably the reason you're running into
pushback, even from people who think that the meetings should
move around more.

Melinda


From aservin@lacnic.net  Wed Nov 14 18:55:25 2012
Return-Path: <aservin@lacnic.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 313DA21E803F for <ietf@ietfa.amsl.com>; Wed, 14 Nov 2012 18:55:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.267
X-Spam-Level: 
X-Spam-Status: No, score=-2.267 tagged_above=-999 required=5 tests=[AWL=0.333,  BAYES_00=-2.599, NO_RELAYS=-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 svXQV1sPs3Fq for <ietf@ietfa.amsl.com>; Wed, 14 Nov 2012 18:55:24 -0800 (PST)
Received: from mail.lacnic.net.uy (mail.lacnic.net.uy [IPv6:2001:13c7:7001:4000::3]) by ietfa.amsl.com (Postfix) with ESMTP id 6F7AB21E802E for <ietf@ietf.org>; Wed, 14 Nov 2012 18:55:24 -0800 (PST)
Received: from [IPv6:2800:af:ba30:fa08:d4ff:760d:af8:6568] (unknown [IPv6:2800:af:ba30:fa08:d4ff:760d:af8:6568]) by mail.lacnic.net.uy (Postfix) with ESMTP id 0932D308446 for <ietf@ietf.org>; Thu, 15 Nov 2012 00:55:23 -0200 (UYST)
Message-ID: <50A4599A.8080507@lacnic.net>
Date: Thu, 15 Nov 2012 00:55:22 -0200
From: Arturo Servin <aservin@lacnic.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
References: <201211121745.qACHjiXS919660@shell01.TheWorld.com> <50A13B43.7000309@dcrocker.net> <72F0897C-D473-4F34-8D21-B9A60DDBBB09@tzi.org> <50A3F814.1030509@dcrocker.net> <50A44418.2010707@gmail.com> <50A44B7C.10103@gmail.com>
In-Reply-To: <50A44B7C.10103@gmail.com>
X-Enigmail-Version: 1.4.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-LACNIC.uy-MailScanner-Information: Please contact the ISP for more information
X-LACNIC.uy-MailScanner: Found to be clean
X-LACNIC.uy-MailScanner-SpamCheck: 
X-LACNIC.uy-MailScanner-From: aservin@lacnic.net
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Nov 2012 02:55:25 -0000

Melinda,

On 14/11/2012 23:55, Melinda Shore wrote:
> On 11/14/12 4:23 PM, Arturo Servin wrote:
>> 	Agree. But also people (and perhaps organisations, that also are
>> serious participants) in Latin America, Africa, and some parts of Asia
>> has less income than their counterparts in North America. Some of the
>> people from those places do serious efforts to attend the IETF.
> 
> I have very, very little doubt that operators in less wealthy
> countries are running into problems that are unfamiliar to most
> IETF participants, and that need some attention from protocol
> weenies.  But, that said, work in the IETF is focused on
> progressing documents and that requires continuity on the part
> of participants.  If someone can only attend when a meeting
> is geographically close, that suggests that they'll attend
> one meeting every <bignum> years.  If they feel that remote
> participation is sufficient, that's available now.  So, I'm
> not sure that what you're arguing addresses the reason there's
> an IETF in the first place, and IETF working method, in the
> second.  I think that's probably the reason you're running into
> pushback, even from people who think that the meetings should
> move around more.

	I was refuting an argument about "/exclusionary/" in a previous email
but you erased. The same argument can be used in both ways, to support
Dave's or mine.

	And let's do not lose the focus. My point is not about venues, it is
about something more: Evolving the IETF. That includes asking ourselves
if we are enough open and international; and if open and international
make us a better standarization body (perhaps no). That includes going
to other venues, to have more official languages, doing more outreach
activities, etc.

	 My opinion is that being more open and international make us a better
standarization body and today the IETF is not doing enough.

Regards,
as

> 
> Melinda
> 

From melinda.shore@gmail.com  Wed Nov 14 18:58:59 2012
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6CEBD21E8041 for <ietf@ietfa.amsl.com>; Wed, 14 Nov 2012 18:58:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.677
X-Spam-Level: 
X-Spam-Status: No, score=-3.677 tagged_above=-999 required=5 tests=[AWL=-0.078, 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 7UiUG2BejiFt for <ietf@ietfa.amsl.com>; Wed, 14 Nov 2012 18:58:58 -0800 (PST)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id D314221E802E for <ietf@ietf.org>; Wed, 14 Nov 2012 18:58:58 -0800 (PST)
Received: by mail-pb0-f44.google.com with SMTP id uo1so830214pbc.31 for <ietf@ietf.org>; Wed, 14 Nov 2012 18:58:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=yo/SOZ9oFMmH7eNlgJbhmwQ6JKkfUwjftNYBe19qEd0=; b=whHHrHrquZgSHzUAOl0W3AMkyUVwMHZU/DP11Qq+BpkJmM9XWCCgsTqMvpqYM3PxAw Dk1hS/UAYlZVi9GFeWTHH6jzkfcnnAJP0F4WtW/A3q8hYTdSv/GRpTDDaz24fSY7gtrA EgPLm3BMp7b8bp1n1GmUE1Gwqx2x+fcXxj4gS4NcoGQTP7e19yafJ9FH4VpaILxrwmU4 5B4p2VDsuVx436xT4ILJTc/2GmsyE1QOv96/xITk1ABC6SNsfJYZz6yxZAjgALhAqgbx Ro3JWBsyqHc6jRheJYn0CxgREn5rKTJi1fOWjjOxukWkZ7yDo+1i+T485lxbik+Gs0gV dPwA==
Received: by 10.66.87.167 with SMTP id az7mr9879773pab.69.1352948338649; Wed, 14 Nov 2012 18:58:58 -0800 (PST)
Received: from spandex.local (216-67-46-210-rb1.fai.dsl.dynamic.acsalaska.net. [216.67.46.210]) by mx.google.com with ESMTPS id a8sm2291415paz.18.2012.11.14.18.58.57 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 14 Nov 2012 18:58:57 -0800 (PST)
Message-ID: <50A45A6F.70900@gmail.com>
Date: Wed, 14 Nov 2012 17:58:55 -0900
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
References: <201211121745.qACHjiXS919660@shell01.TheWorld.com> <50A13B43.7000309@dcrocker.net> <72F0897C-D473-4F34-8D21-B9A60DDBBB09@tzi.org> <50A3F814.1030509@dcrocker.net> <50A44418.2010707@gmail.com> <50A44B7C.10103@gmail.com> <50A4599A.8080507@lacnic.net>
In-Reply-To: <50A4599A.8080507@lacnic.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Nov 2012 02:58:59 -0000

On 11/14/12 5:55 PM, Arturo Servin wrote:
> 	 My opinion is that being more open and international make us a better
> standarization body and today the IETF is not doing enough.

We're a bunch of nerds, and I think that it would help if you
could be more specific about the problem you're perceiving, what
you mean by "better," and how moving the meetings would help.
I'm finding your problem description extremely vague.

Melinda



From aservin@lacnic.net  Wed Nov 14 19:40:13 2012
Return-Path: <aservin@lacnic.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B2271F0C67 for <ietf@ietfa.amsl.com>; Wed, 14 Nov 2012 19:40:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.351
X-Spam-Level: 
X-Spam-Status: No, score=-2.351 tagged_above=-999 required=5 tests=[AWL=0.250,  BAYES_00=-2.599, NO_RELAYS=-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 SmdxBE+KiQRg for <ietf@ietfa.amsl.com>; Wed, 14 Nov 2012 19:40:13 -0800 (PST)
Received: from mail.lacnic.net.uy (mail.lacnic.net.uy [IPv6:2001:13c7:7001:4000::3]) by ietfa.amsl.com (Postfix) with ESMTP id BD3E01F041A for <ietf@ietf.org>; Wed, 14 Nov 2012 19:40:12 -0800 (PST)
Received: from [IPv6:2800:af:ba30:fa08:d4ff:760d:af8:6568] (unknown [IPv6:2800:af:ba30:fa08:d4ff:760d:af8:6568]) by mail.lacnic.net.uy (Postfix) with ESMTP id 42DE930843E for <ietf@ietf.org>; Thu, 15 Nov 2012 01:40:00 -0200 (UYST)
Message-ID: <50A4640D.1060800@lacnic.net>
Date: Thu, 15 Nov 2012 01:39:57 -0200
From: Arturo Servin <aservin@lacnic.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
References: <201211121745.qACHjiXS919660@shell01.TheWorld.com> <50A13B43.7000309@dcrocker.net> <72F0897C-D473-4F34-8D21-B9A60DDBBB09@tzi.org> <50A3F814.1030509@dcrocker.net> <50A44418.2010707@gmail.com> <50A44B7C.10103@gmail.com> <50A4599A.8080507@lacnic.net> <50A45A6F.70900@gmail.com>
In-Reply-To: <50A45A6F.70900@gmail.com>
X-Enigmail-Version: 1.4.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-LACNIC.uy-MailScanner-Information: Please contact the ISP for more information
X-LACNIC.uy-MailScanner: Found to be clean
X-LACNIC.uy-MailScanner-SpamCheck: 
X-LACNIC.uy-MailScanner-From: aservin@lacnic.net
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Nov 2012 03:40:13 -0000

Melinda,

	My point is beyond about venues.

	But answering your question in how moving venues could help.

	Diversity.

	Going to other places would help bring people from other backgrounds,
different ideas, new ways of thinking, break paradigms, etc. People that
in other way would find difficult to participate in the IETF or probably
wouldn't even know that a such thing as the IETF exists. Also, for it
would be good for the ietf community know, see and live other realities,
different needs, and perhaps more constrained that the normal that we
used to.

Regards,
as



On 15/11/2012 00:58, Melinda Shore wrote:
> On 11/14/12 5:55 PM, Arturo Servin wrote:
>> 	 My opinion is that being more open and international make us a better
>> standarization body and today the IETF is not doing enough.
> 
> We're a bunch of nerds, and I think that it would help if you
> could be more specific about the problem you're perceiving, what
> you mean by "better," and how moving the meetings would help.
> I'm finding your problem description extremely vague.
> 
> Melinda
> 

From melinda.shore@gmail.com  Wed Nov 14 19:43:37 2012
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 42D4021E8040 for <ietf@ietfa.amsl.com>; Wed, 14 Nov 2012 19:43:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.668
X-Spam-Level: 
X-Spam-Status: No, score=-3.668 tagged_above=-999 required=5 tests=[AWL=-0.069, 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 gk+yhDlfSJ3H for <ietf@ietfa.amsl.com>; Wed, 14 Nov 2012 19:43:36 -0800 (PST)
Received: from mail-pa0-f44.google.com (mail-pa0-f44.google.com [209.85.220.44]) by ietfa.amsl.com (Postfix) with ESMTP id B167221E802E for <ietf@ietf.org>; Wed, 14 Nov 2012 19:43:36 -0800 (PST)
Received: by mail-pa0-f44.google.com with SMTP id fb11so784162pad.31 for <ietf@ietf.org>; Wed, 14 Nov 2012 19:43:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=tpb/c9sEcbweR1cWYCc19NkYo9B4j71QECthKmYc3jc=; b=dMsDYCntSiNFiAlqna0Psuvk3beBXV/+nmzfrz6S2Rn4lfKx/6rO/0hwp9RoY8b1AJ K4N5u7I0yLSSeDmMXCXIAovp9biRKUcdk1YY/wpOKLkM16D9s1cq7NZTjp3C4p/kHC8j 3bY2Zs5wP3D6Pqqz9mo2y2r8+bn3sv+QW99u9rAmLN0F41CIRhuCRoP9vVCQ+mNeU9Sx OJWTjnJTU+c//nLXGRt4QSzYv6Fq2PkZ35JdzeK24UKgPuNOBfOJM1kOjcwCKeSK5pmD IEXcEVgAKCi0911NGMZfNWxDcrPD9MyAV1zncEMnyd8kiPRWR5Vo3GNbTEhQgKXISyYB m9Rw==
Received: by 10.66.87.202 with SMTP id ba10mr13410935pab.72.1352951016487; Wed, 14 Nov 2012 19:43:36 -0800 (PST)
Received: from spandex.local (216-67-46-210-rb1.fai.dsl.dynamic.acsalaska.net. [216.67.46.210]) by mx.google.com with ESMTPS id oj1sm8775229pbb.19.2012.11.14.19.43.34 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 14 Nov 2012 19:43:35 -0800 (PST)
Message-ID: <50A464E5.5050104@gmail.com>
Date: Wed, 14 Nov 2012 18:43:33 -0900
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
References: <201211121745.qACHjiXS919660@shell01.TheWorld.com> <50A13B43.7000309@dcrocker.net> <72F0897C-D473-4F34-8D21-B9A60DDBBB09@tzi.org> <50A3F814.1030509@dcrocker.net> <50A44418.2010707@gmail.com> <50A44B7C.10103@gmail.com> <50A4599A.8080507@lacnic.net> <50A45A6F.70900@gmail.com> <50A4640D.1060800@lacnic.net>
In-Reply-To: <50A4640D.1060800@lacnic.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Nov 2012 03:43:37 -0000

On 11/14/12 6:39 PM, Arturo Servin wrote:
> 	Going to other places would help bring people from other backgrounds,
> different ideas, new ways of thinking, break paradigms, etc. People that
> in other way would find difficult to participate in the IETF or probably
> wouldn't even know that a such thing as the IETF exists. Also, for it
> would be good for the ietf community know, see and live other realities,
> different needs, and perhaps more constrained that the normal that we
> used to.

Right, I understand that (better than you might think - I live in
Alaska).  But.  I'm trying to understand the value in having people
attend one meeting.  I've asked about that several times.

Melinda


From aservin@lacnic.net  Wed Nov 14 20:01:43 2012
Return-Path: <aservin@lacnic.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8301A21E8042 for <ietf@ietfa.amsl.com>; Wed, 14 Nov 2012 20:01:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.4
X-Spam-Level: 
X-Spam-Status: No, score=-2.4 tagged_above=-999 required=5 tests=[AWL=0.200, BAYES_00=-2.599, NO_RELAYS=-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 aYfHAOY+cuqf for <ietf@ietfa.amsl.com>; Wed, 14 Nov 2012 20:01:43 -0800 (PST)
Received: from mail.lacnic.net.uy (mail.lacnic.net.uy [IPv6:2001:13c7:7001:4000::3]) by ietfa.amsl.com (Postfix) with ESMTP id E36B521E8039 for <ietf@ietf.org>; Wed, 14 Nov 2012 20:01:42 -0800 (PST)
Received: from [IPv6:2800:af:ba30:fa08:d4ff:760d:af8:6568] (unknown [IPv6:2800:af:ba30:fa08:d4ff:760d:af8:6568]) by mail.lacnic.net.uy (Postfix) with ESMTP id 1221B30843E for <ietf@ietf.org>; Thu, 15 Nov 2012 02:01:40 -0200 (UYST)
Message-ID: <50A46922.9040600@lacnic.net>
Date: Thu, 15 Nov 2012 02:01:38 -0200
From: Arturo Servin <aservin@lacnic.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
References: <201211121745.qACHjiXS919660@shell01.TheWorld.com> <50A13B43.7000309@dcrocker.net> <72F0897C-D473-4F34-8D21-B9A60DDBBB09@tzi.org> <50A3F814.1030509@dcrocker.net> <50A44418.2010707@gmail.com> <50A44B7C.10103@gmail.com> <50A4599A.8080507@lacnic.net> <50A45A6F.70900@gmail.com> <50A4640D.1060800@lacnic.net> <50A464E5.5050104@gmail.com>
In-Reply-To: <50A464E5.5050104@gmail.com>
X-Enigmail-Version: 1.4.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-LACNIC.uy-MailScanner-Information: Please contact the ISP for more information
X-LACNIC.uy-MailScanner: Found to be clean
X-LACNIC.uy-MailScanner-SpamCheck: 
X-LACNIC.uy-MailScanner-From: aservin@lacnic.net
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Nov 2012 04:01:43 -0000

	That it could the first of many, or the trigger to start participating
by email or remotely.

	But that is my untested hypothesis. I will try to get some numbers (and
time to run the experiment) and I'll come back (hopefully kinda soon).

Cheers,
as

On 15/11/2012 01:43, Melinda Shore wrote:
> On 11/14/12 6:39 PM, Arturo Servin wrote:
>> 	Going to other places would help bring people from other backgrounds,
>> different ideas, new ways of thinking, break paradigms, etc. People that
>> in other way would find difficult to participate in the IETF or probably
>> wouldn't even know that a such thing as the IETF exists. Also, for it
>> would be good for the ietf community know, see and live other realities,
>> different needs, and perhaps more constrained that the normal that we
>> used to.
> 
> Right, I understand that (better than you might think - I live in
> Alaska).  But.  I'm trying to understand the value in having people
> attend one meeting.  I've asked about that several times.
> 
> Melinda
> 

From joelja@bogus.com  Wed Nov 14 20:40:22 2012
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0FEE021F8502 for <ietf@ietfa.amsl.com>; Wed, 14 Nov 2012 20:40:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.516
X-Spam-Level: 
X-Spam-Status: No, score=-102.516 tagged_above=-999 required=5 tests=[AWL=0.083, 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 cjT+FScn1++N for <ietf@ietfa.amsl.com>; Wed, 14 Nov 2012 20:40:21 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 9B50221F84C1 for <ietf@ietf.org>; Wed, 14 Nov 2012 20:40:21 -0800 (PST)
Received: from joels-MacBook-Air.local (c-98-234-216-143.hsd1.ca.comcast.net [98.234.216.143]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id qAF4eKBb062624 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Thu, 15 Nov 2012 04:40:21 GMT (envelope-from joelja@bogus.com)
Message-ID: <50A47234.3060407@bogus.com>
Date: Wed, 14 Nov 2012 20:40:20 -0800
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Arturo Servin <aservin@lacnic.net>
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
References: <201211121745.qACHjiXS919660@shell01.TheWorld.com> <50A13B43.7000309@dcrocker.net> <72F0897C-D473-4F34-8D21-B9A60DDBBB09@tzi.org> <50A3F814.1030509@dcrocker.net> <50A44418.2010707@gmail.com> <50A44B7C.10103@gmail.com> <50A4599A.8080507@lacnic.net> <50A45A6F.70900@gmail.com> <50A4640D.1060800@lacnic.net>
In-Reply-To: <50A4640D.1060800@lacnic.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Thu, 15 Nov 2012 04:40:21 +0000 (UTC)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Nov 2012 04:40:22 -0000

On 11/14/12 7:39 PM, Arturo Servin wrote:
>   Also, for it
> would be good for the ietf community know, see and live other realities,
> different needs, and perhaps more constrained that the normal that we
> used to.
>
> Regards,
> as
>
>
I have not contributed to the IETF activity since the 44th meeting 
because I wanted the participants to suffer. The goal of the volunteers 
and paid staff in various roles is to make the meeting successful not 
add hardship. It's hard enough already.

joel

From johnl@iecc.com  Wed Nov 14 21:08:39 2012
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DEB1221F856F for <ietf@ietfa.amsl.com>; Wed, 14 Nov 2012 21:08:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.566
X-Spam-Level: 
X-Spam-Status: No, score=-105.566 tagged_above=-999 required=5 tests=[AWL=-5.567, BAYES_50=0.001, 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 JO4bRuUqH0F7 for <ietf@ietfa.amsl.com>; Wed, 14 Nov 2012 21:08:39 -0800 (PST)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id B5C1521F8569 for <ietf@ietf.org>; Wed, 14 Nov 2012 21:08:38 -0800 (PST)
Received: (qmail 1800 invoked from network); 15 Nov 2012 05:08:35 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 15 Nov 2012 05:08:35 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=50a478d3.xn--9vv.k1211; i=johnl@user.iecc.com; bh=H0zcCGiN+4eOvwMVh7m87clyTpVqadJ8NONfJrjXesg=; b=IVJCJihIB4RUCLiQMwPOvZtewSaQXGqOITkOyPRsGpF6BvPn1ZRPVROG/7DRns1RyasHPu4qjG721MpetWoPXW9tiT+44MpSRdqt4tMjHENoNQ7sZM5O7badqT/xStn6O0X6bOByJ4mBOWjVawFXMzEWyE1HTMzvv+xgKz2OEoA=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=50a478d3.xn--9vv.k1211; olt=johnl@user.iecc.com; bh=H0zcCGiN+4eOvwMVh7m87clyTpVqadJ8NONfJrjXesg=; b=VIhYHOIs4lt+sO3AaoR8gwaBc4WJPXsSjeNjKhzNZY30ppBy6r12AsDIuD0skGXj8o5lNjyQFQYeBknEUBqAUiIhNUFZykEP6GqTCYA11+lOL3H2ElRrG8spZDlJn+iYi4wCo4j95LpH00JyPXbjApw6gkDTE+WnlElyJzpKejU=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 15 Nov 2012 05:08:13 -0000
Message-ID: <20121115050813.4158.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
In-Reply-To: <50A4640D.1060800@lacnic.net>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Nov 2012 05:08:40 -0000

>	Going to other places would help bring people from other backgrounds,
>different ideas, new ways of thinking, break paradigms, etc.

If these people are unable or unwilling to join IETF mailing lists, why
do you think it would be useful for them to go to an IETF meeting?

If they are able and willing to join IETF mailing lists, why does the
location of the meeting matter?

-- 
Regards,
John Levine, johnl@iecc.com, Primary Perpetrator of "The Internet for Dummies",
Please consider the environment before reading this e-mail. http://jl.ly

From paf@frobbit.se  Wed Nov 14 22:02:14 2012
Return-Path: <paf@frobbit.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 01C3921F866E for <ietf@ietfa.amsl.com>; Wed, 14 Nov 2012 22:02:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.199
X-Spam-Level: 
X-Spam-Status: No, score=-2.199 tagged_above=-999 required=5 tests=[AWL=0.100,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
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 dn4w+-OKRP1M for <ietf@ietfa.amsl.com>; Wed, 14 Nov 2012 22:02:12 -0800 (PST)
Received: from srv01.frobbit.se (ns2.frobbit.se [IPv6:2a02:80:3ffe::39]) by ietfa.amsl.com (Postfix) with ESMTP id C5D4721F866D for <ietf@ietf.org>; Wed, 14 Nov 2012 22:02:11 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by srv01.frobbit.se (Postfix) with ESMTP id D784A1781A6C2; Thu, 15 Nov 2012 07:02:08 +0100 (CET)
X-Virus-Scanned: amavisd-new at frobbit.se
Received: from srv01.frobbit.se ([127.0.0.1]) by localhost (srv01.frobbit.se [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GproB95LiNhd; Thu, 15 Nov 2012 07:02:08 +0100 (CET)
Received: from [10.59.26.74] (unknown [209.133.29.2]) (Authenticated sender: paf01) by srv01.frobbit.se (Postfix) with ESMTP id 2B3421781A6BF; Thu, 15 Nov 2012 07:02:07 +0100 (CET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
From: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
In-Reply-To: <20121115050813.4158.qmail@joyce.lan>
Date: Wed, 14 Nov 2012 22:02:06 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <103721F2-BA44-4EA5-BA9D-A7941EA4D5ED@frobbit.se>
References: <20121115050813.4158.qmail@joyce.lan>
To: "John Levine" <johnl@taugh.com>
X-Mailer: Apple Mail (2.1499)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Nov 2012 06:02:14 -0000

On 14 nov 2012, at 21:08, "John Levine" <johnl@taugh.com> wrote:

>> 	Going to other places would help bring people from other =
backgrounds,
>> different ideas, new ways of thinking, break paradigms, etc.
>=20
> If these people are unable or unwilling to join IETF mailing lists, =
why
> do you think it would be useful for them to go to an IETF meeting?
>=20
> If they are able and willing to join IETF mailing lists, why does the
> location of the meeting matter?


As Arturo says, having people that traditionally go to an IETF meeting =
travel to (for them) far away places and (for them) new cultures, do =
definitely open their eyes to how large our world is.

I completely agree with Arturo here.

It is enough to be on one of the mailing lists (one of many) where =
complaints come in regarding a venue. Regardless of whether it has to do =
with weather, temperature indoors, cookies, water, visa, walking, train =
tickets or whatever.

Then you understand how local the IETF culture is. Regarding both =
culture and geography.

   Patrik


From cabo@tzi.org  Wed Nov 14 23:08:44 2012
Return-Path: <cabo@tzi.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C4A5421F87AD for <ietf@ietfa.amsl.com>; Wed, 14 Nov 2012 23:08:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.447
X-Spam-Level: 
X-Spam-Status: No, score=-106.447 tagged_above=-999 required=5 tests=[AWL=-0.198, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, 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 RF1DcSpBED4s for <ietf@ietfa.amsl.com>; Wed, 14 Nov 2012 23:08:43 -0800 (PST)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id E06E321F87B4 for <ietf@ietf.org>; Wed, 14 Nov 2012 23:08:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.3/8.14.3) with ESMTP id qAF78R2h028767; Thu, 15 Nov 2012 08:08:28 +0100 (CET)
Received: from [192.168.217.105] (p54891ABE.dip.t-dialin.net [84.137.26.190]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 9000CC87; Thu, 15 Nov 2012 08:08:27 +0100 (CET)
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Content-Type: text/plain; charset=iso-8859-1
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <50A3F814.1030509@dcrocker.net>
Date: Thu, 15 Nov 2012 08:08:27 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <3C8B46A8-1D7C-481F-883D-7CC7D4946BA1@tzi.org>
References: <201211121745.qACHjiXS919660@shell01.TheWorld.com> <50A13B43.7000309@dcrocker.net> <72F0897C-D473-4F34-8D21-B9A60DDBBB09@tzi.org> <50A3F814.1030509@dcrocker.net>
To: dcrocker@bbiw.net
X-Mailer: Apple Mail (2.1499)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Nov 2012 07:08:44 -0000

On Nov 14, 2012, at 20:59, Dave Crocker <dhc@dcrocker.net> wrote:
> On 11/14/2012 9:34 AM, Carsten Bormann wrote:
>> (Another aspect beyond capturing regular attendees, of course, is
>> gaining local mindshare and relevance.
>=20
> I believe I understand the concepts that are meant by such language. =
But I do not know what you mean, with respect to the IETF.  I especially =
do not know what you mean, in terms of the IETF's getting its work done.

My comment was not about getting work done, but about impact of this =
work.

> Ultimately, if the IETF does not have the mindshare among the people =
who consume our work, I believe that it is better accomplished by doing =
work that has more community involvement and more operational relevance. =
=20

Sure.

> If we do that, it won't matter where we hold our meetings.

And I was pointing out that this isn't true.
It may not matter nearly as much as the quality of the work, but there =
is an effect.
Increasing visibility and mindshare, in particular at level 9, can very =
much help enabling involvement.

> One argument for our going to many different places is that it makes =
the IETF more 'credible' because the IETF is "seen".  However I believe =
few International standards groups do traveling shows like the IETF, and =
they manage to be seen as credible.
>=20
> In other words, I would have that our relevance is determined more by =
the quality and utility of our work than by the marketing effects of =
meeting venue.

I certainly subscribe to that.

I believe the IETF has pretty much struck the right notes here in the =
most recent years.
(And I know about the contingencies that made us fall back to having two =
US meetings in a row right now, and I hope that those won't recur.
I was part of the 85 % for which it was quite pleasant to fall back to =
Atlanta, BTW, and I hope this venue can become our second Minneapolis.
If fallbacks do occur frequently, we may have to make plans for more =
non-US meetings so that with the inevitable fallbacks we return to the =
right mix.)

> Again, finding meeting venues that work well for an IETF venue is =
quite difficult. When we add other goals, such as marketing the IETF to =
the community, we make venue selection especially difficult.

Again, you are trying to argue against my point by saying your point is =
more important.
That is certainly so, but doesn't make my point wrong or irrelevant.

Practically speaking, e.g., if we can get a reasonable venue in Brazil =
or in a Spanish-speaking country, we should go there.
That's a big if, but I would argue that it is worth investing some =
(limited amount of) effort trying to find it.

Gr=FC=DFe, Carsten


From brian.e.carpenter@gmail.com  Thu Nov 15 00:11:29 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7753B21F85A9 for <ietf@ietfa.amsl.com>; Thu, 15 Nov 2012 00:11:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.54
X-Spam-Level: 
X-Spam-Status: No, score=-101.54 tagged_above=-999 required=5 tests=[AWL=0.151, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, 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 wWj1cQMJ+mHY for <ietf@ietfa.amsl.com>; Thu, 15 Nov 2012 00:11:29 -0800 (PST)
Received: from mail-wg0-f44.google.com (mail-wg0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id AA69C21F85A3 for <ietf@ietf.org>; Thu, 15 Nov 2012 00:11:28 -0800 (PST)
Received: by mail-wg0-f44.google.com with SMTP id dr13so484337wgb.13 for <ietf@ietf.org>; Thu, 15 Nov 2012 00:11:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=s0RcClJUQaC7+KR0inQqTxECb2DsWt5gQPDU3fb71CM=; b=vv2xkbUSOSC2zgeVobDob9ef6jUVBcD6FXhCoqn76yKAQtNZlL8g3TUIye80gN1/H0 E9QqJHDNSb3lc9Tj8YleW5vusoVeRMU3NlKpNlm9r9n8DQ3McktkETFbybbbgb4HM60K zjCJsQd5pXlIgj3FJsE7N2Z40nGsAc/OdLPfipdGX7BhUlVUNPsbH7jES3k+VwKfHmmA xHTdQijyh/D3MHF/Kp+XsLpbonVGxLzgY0a9eaDdDolnx9HCz61ohAE9mYQllhD2hMRB HmahJxiiIn5hdV3wCp6gl2eZWlGs/Y1bVUT0Zhq9MSCk8e4Fnnd33JvgqHd2OujtjsYS erfw==
Received: by 10.216.27.84 with SMTP id d62mr159175wea.3.1352967087535; Thu, 15 Nov 2012 00:11:27 -0800 (PST)
Received: from [192.168.1.65] (host-2-102-216-172.as13285.net. [2.102.216.172]) by mx.google.com with ESMTPS id w5sm6139961wiz.10.2012.11.15.00.11.23 (version=SSLv3 cipher=OTHER); Thu, 15 Nov 2012 00:11:24 -0800 (PST)
Message-ID: <50A4A3AF.1060704@gmail.com>
Date: Thu, 15 Nov 2012 08:11:27 +0000
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Melinda Shore <melinda.shore@gmail.com>
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
References: <201211121745.qACHjiXS919660@shell01.TheWorld.com>	<50A13B43.7000309@dcrocker.net>	<72F0897C-D473-4F34-8D21-B9A60DDBBB09@tzi.org>	<50A3F814.1030509@dcrocker.net> <50A44418.2010707@gmail.com>	<50A44B7C.10103@gmail.com> <50A4599A.8080507@lacnic.net>	<50A45A6F.70900@gmail.com> <50A4640D.1060800@lacnic.net> <50A464E5.5050104@gmail.com>
In-Reply-To: <50A464E5.5050104@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Nov 2012 08:11:29 -0000

On 15/11/2012 03:43, Melinda Shore wrote:
...
> Right, I understand that (better than you might think - I live in
> Alaska).  But.  I'm trying to understand the value in having people
> attend one meeting.  I've asked about that several times.

There are people who have attended one, or a very small number,
of meetings and who participate actively in IETF work. That's
certainly the case for a few people in Australia and New
Zealand, for example. I have a co-author on a current draft who
attended IETF 83 in Paris, because he happens to live there and
doesn't have business justification for the time and money for
longer trips. I think people in this class do get a lot out of
occasional participation - enough to encourage them to
participate remotely. I've gone through phases of attending one
meeting a year, and that's definitely enough to stay in touch.

However, that is very different from meetings in unusual places
*attracting* new participants who stay with us. Would we get a
cohort of new active participants if we met in Anchorage?

We'd reached 50 attendees from China at IETF 63 before we even
started seriously negotiating the Beijing meeting. It seems to
me that the causality is mainly in the opposite direction:
participation causes meetings, not meetings cause participation.

(IMHO, there is some value to the IETF in having one-off
attendees who don't subsequently participate: they learn what
the IETF is and hopefully tell others about it. This can't be a
bad thing, but it's definitely secondary.)

   Brian

From daedulus@btconnect.com  Thu Nov 15 01:47:19 2012
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BDAE921F8639 for <ietf@ietfa.amsl.com>; Thu, 15 Nov 2012 01:47:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.813
X-Spam-Level: 
X-Spam-Status: No, score=-3.813 tagged_above=-999 required=5 tests=[AWL=-0.214, 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 BhEY-3ThVzui for <ietf@ietfa.amsl.com>; Thu, 15 Nov 2012 01:47:19 -0800 (PST)
Received: from va3outboundpool.messaging.microsoft.com (va3ehsobe010.messaging.microsoft.com [216.32.180.30]) by ietfa.amsl.com (Postfix) with ESMTP id F371E21F85E6 for <ietf@ietf.org>; Thu, 15 Nov 2012 01:47:18 -0800 (PST)
Received: from mail178-va3-R.bigfish.com (10.7.14.238) by VA3EHSOBE004.bigfish.com (10.7.40.24) with Microsoft SMTP Server id 14.1.225.23; Thu, 15 Nov 2012 09:47:13 +0000
Received: from mail178-va3 (localhost [127.0.0.1])	by mail178-va3-R.bigfish.com (Postfix) with ESMTP id 7D6BDC0211; Thu, 15 Nov 2012 09:47:13 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.249.85; KIP:(null); UIP:(null); IPV:NLI; H:AMSPRD0710HT003.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -26
X-BigFish: PS-26(zzbb2dI98dI9371I542M1432I1418Izz1de0h1202h1d1ah1d2ahzz1033IL8275bh8275dhz2dh2a8h5a9h668h839h93fhd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h304l1155h)
Received: from mail178-va3 (localhost.localdomain [127.0.0.1]) by mail178-va3 (MessageSwitch) id 1352972831992316_22295; Thu, 15 Nov 2012 09:47:11 +0000 (UTC)
Received: from VA3EHSMHS038.bigfish.com (unknown [10.7.14.243])	by mail178-va3.bigfish.com (Postfix) with ESMTP id E50EF38004A; Thu, 15 Nov 2012 09:47:11 +0000 (UTC)
Received: from AMSPRD0710HT003.eurprd07.prod.outlook.com (157.56.249.85) by VA3EHSMHS038.bigfish.com (10.7.99.48) with Microsoft SMTP Server (TLS) id 14.1.225.23; Thu, 15 Nov 2012 09:47:11 +0000
Received: from DB3PRD0310HT005.eurprd03.prod.outlook.com (157.56.252.5) by pod51017.outlook.com (10.255.160.166) with Microsoft SMTP Server (TLS) id 14.16.239.5; Thu, 15 Nov 2012 09:47:10 +0000
Message-ID: <003901cdc316$0d19bda0$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Melinda Shore <melinda.shore@gmail.com>
References: <201211121745.qACHjiXS919660@shell01.TheWorld.com>	<50A13B43.7000309@dcrocker.net>	<72F0897C-D473-4F34-8D21-B9A60DDBBB09@tzi.org>	<50A3F814.1030509@dcrocker.net><50A44418.2010707@gmail.com>	<50A44B7C.10103@gmail.com><50A4599A.8080507@lacnic.net>	<50A45A6F.70900@gmail.com><50A4640D.1060800@lacnic.net> <50A464E5.5050104@gmail.com> <50A4A3AF.1060704@gmail.com>
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
Date: Thu, 15 Nov 2012 09:45:45 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [157.56.252.5]
X-OriginatorOrg: btconnect.com
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Nov 2012 09:47:19 -0000

----- Original Message -----
From: "Brian E Carpenter" <brian.e.carpenter@gmail.com>
To: "Melinda Shore" <melinda.shore@gmail.com>
Cc: <ietf@ietf.org>
Sent: Thursday, November 15, 2012 8:11 AM
> On 15/11/2012 03:43, Melinda Shore wrote:
> ...
> > Right, I understand that (better than you might think - I live in
> > Alaska).  But.  I'm trying to understand the value in having people
> > attend one meeting.  I've asked about that several times.
>
> There are people who have attended one, or a very small number,
> of meetings and who participate actively in IETF work. That's
> certainly the case for a few people in Australia and New
> Zealand, for example. I have a co-author on a current draft who
> attended IETF 83 in Paris, because he happens to live there and
> doesn't have business justification for the time and money for
> longer trips. I think people in this class do get a lot out of
> occasional participation - enough to encourage them to
> participate remotely. I've gone through phases of attending one
> meeting a year, and that's definitely enough to stay in touch.
>
> However, that is very different from meetings in unusual places
> *attracting* new participants who stay with us. Would we get a
> cohort of new active participants if we met in Anchorage?
>
> We'd reached 50 attendees from China at IETF 63 before we even
> started seriously negotiating the Beijing meeting. It seems to
> me that the causality is mainly in the opposite direction:
> participation causes meetings, not meetings cause participation.

I started, some years ago, with a meeting, because the culture that I
was used to was that conferences, be they annual or triannual, were
where things really happened and that e-mail filled in the gaps in
between (and I think that this remains the case in other, related,
fora).  That attendance showed me that most of the IETF meeting was a
waste of time, that it was e-mail that was the main vehicle for work,
and I think that the IETF web site has it about right when it says

"People interested in particular technical issues join the mailing list
of a WG  and occasionally attend one or more of the three IETF meetings
held every year."
and
"After participating by email for a while, it may be time to attend your
first meeting."

which is not exactly sellling the idea of attending meetings:-)  But as
I say, I think that that is the nature of the IETF.

Tom Petch

> (IMHO, there is some value to the IETF in having one-off
> attendees who don't subsequently participate: they learn what
> the IETF is and hopefully tell others about it. This can't be a
> bad thing, but it's definitely secondary.)
>
>    Brian
>
>



From ggm+ietf@apnic.net  Thu Nov 15 02:50:11 2012
Return-Path: <ggm+ietf@apnic.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC85621F8577; Thu, 15 Nov 2012 02:50:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, 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 J2S1K9qEaXEf; Thu, 15 Nov 2012 02:50:11 -0800 (PST)
Received: from asmtp.apnic.net (asmtp.apnic.net [IPv6:2001:dc0:2001:11::199]) by ietfa.amsl.com (Postfix) with ESMTP id 423EA21F8508; Thu, 15 Nov 2012 02:50:10 -0800 (PST)
Received: from [IPv6:2001:67c:2e8:13:3966:7593:b81e:73fc] (unknown [IPv6:2001:67c:2e8:13:3966:7593:b81e:73fc]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by asmtp.apnic.net (Postfix) with ESMTP id 9D24EB68D4; Thu, 15 Nov 2012 20:50:07 +1000 (EST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
From: George Michaelson <ggm+ietf@apnic.net>
In-Reply-To: <CAKFn1SFy2+hXJLVtEpkdXfNuXA31ybmYnBFFPXj-73kb3tD+yw@mail.gmail.com>
Date: Thu, 15 Nov 2012 11:50:03 +0100
Content-Transfer-Encoding: 7bit
Message-Id: <1C49DB9E-6BD3-4A8A-8B19-2D5A8F4DAC94@apnic.net>
References: <20121113144545.12836.71935.idtracker@ietfa.amsl.com> <CAKFn1SFy2+hXJLVtEpkdXfNuXA31ybmYnBFFPXj-73kb3tD+yw@mail.gmail.com>
To: ietf@ietf.org
X-Mailer: Apple Mail (2.1499)
Cc: lisp@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Nov 2012 10:50:12 -0000

I think this document isn't ready for IETF last call.

I think the context of an experimental assignment which heads to
distributing IPv6 addresses to end-entities, even if the experiment
is not intended to be globally routable, poses questions about how
the address management function is going to work. Can the working
group be asked to discuss how this is meant to be interpreted in
the light of RFC2050 based processes? It might avoid future pain
if its clear how the IAB and the RIR understand these addresses and
their management.

The experiment has all the attributes of a general, wide-ranging
address distribution and management activity. I haven't seen any
substantive discussion of this in the WG mailing lists, and I'm
worried this hasn't been documented, or understood.

cheers

-George

From bertietf@bwijnen.net  Thu Nov 15 02:55:20 2012
Return-Path: <bertietf@bwijnen.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2217C21F84C5; Thu, 15 Nov 2012 02:55:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.431
X-Spam-Level: 
X-Spam-Status: No, score=-102.431 tagged_above=-999 required=5 tests=[AWL=0.169, 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 uDZWYWFuRGPf; Thu, 15 Nov 2012 02:55:19 -0800 (PST)
Received: from postgirl.ripe.net (postgirl.ipv6.ripe.net [IPv6:2001:67c:2e8:11::c100:1342]) by ietfa.amsl.com (Postfix) with ESMTP id 10FF921F849A; Thu, 15 Nov 2012 02:55:19 -0800 (PST)
Received: from dodo.ripe.net ([193.0.23.4]) by postgirl.ripe.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from <bertietf@bwijnen.net>) id 1TYx6L-0008Pm-2S; Thu, 15 Nov 2012 11:55:18 +0100
Received: from cat.ripe.net ([193.0.1.249] helo=guest165.guestnet.ripe.net) by dodo.ripe.net with esmtp (Exim 4.72) (envelope-from <bertietf@bwijnen.net>) id 1TYx6K-0004Ed-Um; Thu, 15 Nov 2012 11:55:17 +0100
Message-ID: <50A4CA14.9010909@bwijnen.net>
Date: Thu, 15 Nov 2012 11:55:16 +0100
From: "Bert Wijnen (IETF)" <bertietf@bwijnen.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Anti-Virus: Kaspersky Anti-Virus for Linux Mail Server 5.6.48/RELEASE, bases: 20120425 #7816575, check: 20121115 clean
X-RIPE-Spam-Level: --
X-RIPE-Spam-Report: Spam Total Points:   -2.9 points pts rule name              description ---- ---------------------- ------------------------------------ -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP -1.9 BAYES_00               BODY: Bayes spam probability is 0 to 1% [score: 0.0000]
X-RIPE-Signature: 86ab03e524994f79ca2c75a176445dd4e2ba3b8c90244e04af6f0a2d86ef9a00
Cc: "iesg@ietf.org" <iesg@ietf.org>, lisp@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Nov 2012 10:55:20 -0000

On Tue, Nov 13, 2012 at 3:45 PM, The IESG <iesg-secretary at ietf.org> wrote:
 >
 > The IESG has received a request from the Locator/ID Separation Protocol
 > WG (lisp) to consider the following document:
 > - 'LISP EID Block'
 >   <draft-ietf-lisp-eid-block-03.txt> as Informational RFC
 >
 > The IESG plans to make a decision in the next few weeks, and solicits
 > final comments on this action. Please send substantive comments to the
 > ietf at ietf.org mailing lists by 2012-11-27. Exceptionally, comments may be
 > sent to iesg at ietf.org instead. In either case, please retain the
 > beginning of the Subject line to allow automated sorting.
 >
 > Abstract
 >
 >
 >    This is a direction to IANA to allocate a /16 IPv6 prefix for use
 >    with the Locator/ID Separation Protocol (LISP).  The prefix will be
 >    used for local intra-domain routing and global endpoint
 >    identification, by sites deploying LISP as EID (Endpoint IDentifier)
 >    addressing space.

Mmm... In section 5 it states:

    The working group reached consensus on an initial allocation of a /16
    prefix out of a /12 block which is asked to remain reserved for
    future use as EID space.  The reason of such consensus is manifold:

So it is not asking just a /16 but also asking for reservation of a /12.

Pretty big space.

And in the list of reasons, I mainly read that it is "sufficiently large",
but not much about why it needs to be this big. Why would a smaller
allocation not be sufficient?

Bert

From daedulus@btconnect.com  Thu Nov 15 04:52:35 2012
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8425821F888E for <ietf@ietfa.amsl.com>; Thu, 15 Nov 2012 04:52:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.787
X-Spam-Level: 
X-Spam-Status: No, score=-3.787 tagged_above=-999 required=5 tests=[AWL=-0.188, 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 7-v53R7KY8jo for <ietf@ietfa.amsl.com>; Thu, 15 Nov 2012 04:52:34 -0800 (PST)
Received: from va3outboundpool.messaging.microsoft.com (va3ehsobe001.messaging.microsoft.com [216.32.180.11]) by ietfa.amsl.com (Postfix) with ESMTP id 9287E21F869A for <ietf@ietf.org>; Thu, 15 Nov 2012 04:52:33 -0800 (PST)
Received: from mail168-va3-R.bigfish.com (10.7.14.243) by VA3EHSOBE003.bigfish.com (10.7.40.23) with Microsoft SMTP Server id 14.1.225.23; Thu, 15 Nov 2012 12:52:33 +0000
Received: from mail168-va3 (localhost [127.0.0.1])	by mail168-va3-R.bigfish.com (Postfix) with ESMTP id 3541C2A0084; Thu, 15 Nov 2012 12:52:33 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.253.85; KIP:(null); UIP:(null); IPV:NLI; H:DB3PRD0710HT003.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -27
X-BigFish: PS-27(zz9371I936eI542M1432I1418I1a09Jzz1de0h1202h1d1ah1d2ahzz1033IL17326ah8275bh8275dhz2dh2a8h5a9h668h839hd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h304l1155h)
Received: from mail168-va3 (localhost.localdomain [127.0.0.1]) by mail168-va3 (MessageSwitch) id 1352983951674911_16268; Thu, 15 Nov 2012 12:52:31 +0000 (UTC)
Received: from VA3EHSMHS046.bigfish.com (unknown [10.7.14.252])	by mail168-va3.bigfish.com (Postfix) with ESMTP id 975CC100045; Thu, 15 Nov 2012 12:52:31 +0000 (UTC)
Received: from DB3PRD0710HT003.eurprd07.prod.outlook.com (157.56.253.85) by VA3EHSMHS046.bigfish.com (10.7.99.56) with Microsoft SMTP Server (TLS) id 14.1.225.23; Thu, 15 Nov 2012 12:52:31 +0000
Received: from DB3PRD0610HT002.eurprd06.prod.outlook.com (157.56.252.53) by pod51017.outlook.com (10.255.75.38) with Microsoft SMTP Server (TLS) id 14.16.239.5; Thu, 15 Nov 2012 12:52:03 +0000
Message-ID: <017b01cdc32f$e149c5c0$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: Mach Chen <mach.chen@huawei.com>, <ietf@ietf.org>
References: <20121024213116.29724.2375.idtracker@ietfa.amsl.com>, <028101cdb924$b77260a0$4001a8c0@gateway.2wire.net> <F73A3CB31E8BE34FA1BBE3C8F0CB2AE22CAE869D@SZXEML511-MBX.china.huawei.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-ipv6-pw-lsp-ping-03.txt>(LabelSwitched Path (LSP) Ping for IPv6 Pseudowire FECs)	toProposed Standard
Date: Thu, 15 Nov 2012 12:26:37 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [157.56.252.53]
X-OriginatorOrg: btconnect.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Nov 2012 12:52:35 -0000

More thoughts inline <tp> three times (and apologies for the slow
response).

----- Original Message -----
From: "Mach Chen" <mach.chen@huawei.com>
To: "t.p." <daedulus@btconnect.com>; <ietf@ietf.org>
Sent: Wednesday, November 07, 2012 12:24 PM

Hi Tom,
Many thanks for your comments!
Please see my reply inline with [Mach]

Best regards,
Mach
________________________________________
From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] on behalf of t.p.
[daedulus@btconnect.com]
Sent: Saturday, November 03, 2012 2:05
To: ietf@ietf.org

I worry about the allocation of sub-TLVs in this I-D.

It calls for
"The following Sub-TLV changes, which comprise three updates and two
   additions, are made for two TLV Types in the aforementioned sub-
   registry: TLV Type 1 for "Target FEC Stack", and TLV Type 21 for
   "Reply Path"."
and it is the Type 21 that worries me.

[Mach] Since draft-ietf-mpls-return-path-specified-lsp-ping has already
defined the rule and policy on how to inhirent the sub-TLVs from type 1
TLV, IMHO, here it may be no need to explicitly mention how to registry
the sub-TLVs for Type 21. So, how about this:
"The following Sub-TLV changes, which comprise three updates and two
additions, are made for TLV Type 1."

<tp>
I do not see this rule defined in draft-ietf-mpls-return-path-specified,
at least, not for any sub-TLVs that may be defined in future for Type 1
TLVs, that is, that I-D covers the present but not the future and that
is what I worry about.  The ipv6 I-D as initially written did not take
account of return-path-specified and vice versa, so I expect this
situation to recur and do not see a good solution to it.
</tp>

IANA has, for Type 21,

Reply Path (TEMPORARY - expires 2012-01-20)
[draft-ietf-mpls-return-path-specified-lsp-ping]

and I am unclear what the rules are about updates to expired, TEMPORARY,
allocations.

[Mach] As Loa pointed out, the current IANA registry for Type 21 TLV is
not reflecting the proposal in
[draft-ietf-mpls-return-path-specified-lsp-ping].

<tp>
Yes, and my reading is that the removal of temporary allocations is (yet
another) duty of the WG chair, so doubtless that will be taken care
of:-)
</tp>

I worry too that
[draft-ietf-mpls-return-path-specified-lsp-ping]
while confirming the reservation of Type 21 takes a different tack for
sub-TLVs, namely
"
According to the guidelines defined in [RFC5226], the sub-TLV range
   of Reply Path TLV are partitioned as following:
   0-31743 - Reserved, and MUST NOT be allocated."
so quite what this I-D will do to that I-D worries me.

[Mach] This is intended for the Type 21 TLV to have a common part code
range shared with Type 1 TLV and a TLV specific code range for its own
dedicaed sub-TLV. I think we should have an agreement on this solution
:-)

<tp>
Yes, we have long had agreement on the general idea of the solution but
it is not clear to me that the current wording got that message across,
for example to the AD, in which case we need better wording.  I realise
that this has come up on the MPLS list but I am unsure what the proposed
wording now is.  In fact, I am unclear whether the change proposed in
return-path-specified is intended to apply to all TLVs, present and
future - I think that it should, for safety, but the wording is unclear
to me on that point

Which point is of course nothing to do with the IETF Last Call of ipv6,
no need to mention it there, but it seems better to keep it on one
thread for the moment.

</tp>

Best regards,
Mach

And I worry yet more that other I-Ds, such as
draft-zjns-mpls-lsp-ping-relay-reply-00
are heading down the track with further updates in this area of the MPLS
namespace (except that this particular one seems to have abandoned
sub-TLVs).

Tom Petch

----- Original Message -----
From: "The IESG" <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
Cc: <mpls@ietf.org>
Sent: Wednesday, October 24, 2012 9:31 PM

>
> The IESG has received a request from the Multiprotocol Label Switching
WG
> (mpls) to consider the following document:
> - 'Label Switched Path (LSP) Ping for IPv6 Pseudowire FECs'
>   <draft-ietf-mpls-ipv6-pw-lsp-ping-03.txt> as Proposed Standard
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2012-11-09. Exceptionally, comments may
be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>
> Abstract
>
>    Multi-Protocol Label Switching (MPLS) Label Switched Path (LSP)
Ping
>    and traceroute mechanisms are commonly used to detect and isolate
>    data plane failures in all MPLS LSPs including Pseudowire (PW)
LSPs.
>    The PW LSP Ping and traceroute elements, however, are not specified
>    for IPv6 address usage.
>
>    This document extends the PW LSP Ping and traceroute mechanisms so
>    they can be used with IPv6 PWs, and updates RFC 4379.
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-mpls-ipv6-pw-lsp-ping/
>
> IESG discussion can be tracked via
>
http://datatracker.ietf.org/doc/draft-ietf-mpls-ipv6-pw-lsp-ping/ballot/
>
>
> No IPR declarations have been submitted directly on this I-D.
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
>



From ggx@gigix.net  Thu Nov 15 05:17:41 2012
Return-Path: <ggx@gigix.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0AB3B21F88D9 for <ietf@ietfa.amsl.com>; Thu, 15 Nov 2012 05:17:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.299
X-Spam-Level: 
X-Spam-Status: No, score=-3.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, 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 epUYKapwfZrb for <ietf@ietfa.amsl.com>; Thu, 15 Nov 2012 05:17:39 -0800 (PST)
Received: from mail-wi0-f178.google.com (mail-wi0-f178.google.com [209.85.212.178]) by ietfa.amsl.com (Postfix) with ESMTP id 98D6721F88D1 for <ietf@ietf.org>; Thu, 15 Nov 2012 05:17:39 -0800 (PST)
Received: by mail-wi0-f178.google.com with SMTP id hm14so838633wib.13 for <ietf@ietf.org>; Thu, 15 Nov 2012 05:17:38 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=U0QL3FjV/3rQ6Mf8arz/s2c4QMfNgPHpeMIaQOHq+Hs=; b=a8Ok40y4gEEvLhidLJX7ueniFuL3gtvHQDj0/qWoj5/WlLGuKRPNiPv27X05SDHKMD FlmbF76S4Cj7oXzpf59ligVd/eQMQueC7clybc1ydi8ALD3LQu8F5bWdjLaYLjBGpeht bdZykONvIOkrnmuQ8xs9gKOIkQ+zdsfX74pzAbZpubEkBgxIWPrOc2XXtkCy9Fb9SjNG 1Bg14hrLqyACPthyL1iZmu4gFYAbbqOiSezL4DpKhTGKirgce2XVt0cZ5GqgNW07s3cq GyjEXl+jEvhtw0CGhfSg+bJv7fM0qO3D4gV4wxJKaIsI7jPnltjSHKH6vy/W5kmjNmw9 4A5Q==
Received: by 10.180.96.226 with SMTP id dv2mr2240936wib.1.1352985458573; Thu, 15 Nov 2012 05:17:38 -0800 (PST)
Received: from ?IPv6:2001:660:330f:a4:6c55:486d:3ba1:398a? ([2001:660:330f:a4:6c55:486d:3ba1:398a]) by mx.google.com with ESMTPS id eq2sm7324793wib.1.2012.11.15.05.17.37 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 15 Nov 2012 05:17:37 -0800 (PST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
From: Luigi Iannone <ggx@gigix.net>
In-Reply-To: <CAKFn1SFy2+hXJLVtEpkdXfNuXA31ybmYnBFFPXj-73kb3tD+yw@mail.gmail.com>
Date: Thu, 15 Nov 2012 14:22:50 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <8B4C4FF9-0967-42EC-80E6-89EC87D28B04@gigix.net>
References: <20121113144545.12836.71935.idtracker@ietfa.amsl.com> <CAKFn1SFy2+hXJLVtEpkdXfNuXA31ybmYnBFFPXj-73kb3tD+yw@mail.gmail.com>
To: =?iso-8859-1?Q?Roger_J=F8rgensen?= <rogerj@gmail.com>
X-Mailer: Apple Mail (2.1499)
X-Gm-Message-State: ALoCoQkssRNoDgsvA2hRUaryu2gLuanD240r4JnSzfqN9i8lSpiO3ZGPpqbT5rd8rtBCw1h/5kCa
Cc: ietf@ietf.org, lisp@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Nov 2012 13:17:41 -0000

Hi Roger,

On 14 Nov. 2012, at 10:42 , Roger J=F8rgensen <rogerj@gmail.com> wrote:

> On Tue, Nov 13, 2012 at 3:45 PM, The IESG <iesg-secretary@ietf.org> =
wrote:
>>=20
>> The IESG has received a request from the Locator/ID Separation =
Protocol
>> WG (lisp) to consider the following document:
>> - 'LISP EID Block'
>>  <draft-ietf-lisp-eid-block-03.txt> as Informational RFC
>>=20
>> The IESG plans to make a decision in the next few weeks, and solicits
>> final comments on this action. Please send substantive comments to =
the
>> ietf@ietf.org mailing lists by 2012-11-27. Exceptionally, comments =
may be
>> sent to iesg@ietf.org instead. In either case, please retain the
>> beginning of the Subject line to allow automated sorting.
>>=20
>> Abstract
>>=20
>>=20
>>   This is a direction to IANA to allocate a /16 IPv6 prefix for use
>>   with the Locator/ID Separation Protocol (LISP).  The prefix will be
>>   used for local intra-domain routing and global endpoint
>>   identification, by sites deploying LISP as EID (Endpoint =
IDentifier)
>>   addressing space.
>=20
> I have to ask, who can request an netblock from this address space and
> from where?

Who: whoever is willing to deploy LISP.

Where: your RIR?=20


> I might be blind but I couldn't find it mentioned anywhere.
>=20

The purpose of the document is not to create a new way to distribute =
prefixes with its own policies, rather to use the existing "process" but =
just creating a code point specific for LISP.


Luigi

>=20
>=20
> --=20
>=20
> Roger Jorgensen           | ROJO9-RIPE
> rogerj@gmail.com          | - IPv6 is The Key!
> http://www.jorgensen.no   | roger@jorgensen.no


From ggx@gigix.net  Thu Nov 15 06:26:56 2012
Return-Path: <ggx@gigix.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 527FE21F8842 for <ietf@ietfa.amsl.com>; Thu, 15 Nov 2012 06:26:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.455
X-Spam-Level: 
X-Spam-Status: No, score=-2.455 tagged_above=-999 required=5 tests=[AWL=1.144,  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 5dvWslXh851t for <ietf@ietfa.amsl.com>; Thu, 15 Nov 2012 06:26:55 -0800 (PST)
Received: from mail-wg0-f44.google.com (mail-wg0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id 4BDAE21F86D1 for <ietf@ietf.org>; Thu, 15 Nov 2012 06:26:55 -0800 (PST)
Received: by mail-wg0-f44.google.com with SMTP id dr13so633198wgb.13 for <ietf@ietf.org>; Thu, 15 Nov 2012 06:26:54 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=nMR/BP85cTHquyCLHqVKg/OpBqSeZB8fV8TQtqpc770=; b=gJ2W9IxLhRSfBv8CTTsVsWSRG8eBIipxI6U8yh6Z+TB0BI/AytEtCnS6AK3AfJ7O+W 2Irt+AR1slwE3HIY5jFioy3TmEWQ6C7JeCGiASU9uan2ig0ADHhVijvh0e6uaHQ6uEcw w3Yz1U/bq5A3saJsNlQFgIGaua5dh456Ko8pgoQoMy7OMrTgYy4a49hmoVEO4oNuCV1u Y+axuvnTDvu5E/7JBnTwaxdc5IaSHgYHAavx1VYT9Zl3Fqkg5vZxq9s+6qggoqE73YZm bU2BkfiXnCD/F5TVq5h33nZeWqSATiftL76bn+1OoCzFyapYa+4DOhhZ6OurSNdo7IqT eb6A==
Received: by 10.181.11.233 with SMTP id el9mr109180wid.3.1352989614495; Thu, 15 Nov 2012 06:26:54 -0800 (PST)
Received: from ?IPv6:2001:660:330f:a4:6c55:486d:3ba1:398a? ([2001:660:330f:a4:6c55:486d:3ba1:398a]) by mx.google.com with ESMTPS id az2sm27878726wib.7.2012.11.15.06.26.52 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 15 Nov 2012 06:26:53 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
From: Luigi Iannone <ggx@gigix.net>
In-Reply-To: <6.2.5.6.2.20121114030352.0da0e888@resistor.net>
Date: Thu, 15 Nov 2012 15:32:06 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <63359CE6-0009-45D1-B2AE-3F2B4384D5D4@gigix.net>
References: <20121113144545.12836.71935.idtracker@ietfa.amsl.com> <6.2.5.6.2.20121114030352.0da0e888@resistor.net>
To: SM <sm@resistor.net>
X-Mailer: Apple Mail (2.1499)
X-Gm-Message-State: ALoCoQmT0gG2UmsTqZuucqsrJyYG7OLEjLPqMlnyAVk/3r7Z6eLIGc6dHjde9yAZ6piMskFV0pxJ
Cc: ietf@ietf.org, "lisp@ietf.org" <lisp@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Nov 2012 14:26:56 -0000

Hi,

 thanks for the comments. Few answers inline.


On 14 Nov. 2012, at 12:19 , SM <sm@resistor.net> wrote:

> At 06:45 13-11-2012, The IESG wrote:
>> The IESG has received a request from the Locator/ID Separation =
Protocol
>> WG (lisp) to consider the following document:
>> - 'LISP EID Block'
>>  <draft-ietf-lisp-eid-block-03.txt> as Informational RFC
>>=20
>> The IESG plans to make a decision in the next few weeks, and solicits
>> final comments on this action. Please send substantive comments to =
the
>> ietf@ietf.org mailing lists by 2012-11-27. Exceptionally, comments =
may be
>=20
> The document does not clearly define how the address space will be =
managed.  This might end up being problematic in future.
>=20
> In Section 4:
>=20
> "Too guarantee reachability from the Legacy Internet the prefix could"
>=20
> There is a typo for "Too".

thanks, will fix.

>=20
> In Section 6:
>=20
>  "It is suggested to IANA to temporarily avoid allocating any
>   other address block the same /12 prefix the EID /16 prefix
>   belongs to.  This is to accommodate future requests of EID
>   space without fragmenting the EID addressing space."
>=20
> Shouldn't that be under IANA Considerations?

Well, if we go along that road we should put the whole document in a =
single "IANA Considerations" Section. ;-)

Actually the current IANA Considerations section states the same request =
but does not specify "/12".
You are right that it should be clearly stated, to make the document =
coherent. Will fix. thanks


>=20
>  "If in the future there will be need for a larger EID Block the
>   address space adjacent the EID Block could be allocate by IANA
>   according to the current policies."
>=20
> Which policies does the above refer to?
>=20

It refers to the IANA allocation policies. May be it could be changed in =
the following way:

	If in the future there will be need for a larger EID Block the
  	address space adjacent the EID Block could be allocate by IANA
  	according to its current allocation policies."

Would that work?

> In Section 10:
>=20
>  "This document instructs the IANA to assign a /16 IPv6 prefix for use
>   as the global LISP EID space using a hierarchical allocation as
>   outlined in [RFC5226]."
>=20
> Who will be the delegated managers?

I agree that this point has been not discussed thoroughly, the idea is =
not to create any new "manager", rather to make ISPs (or whoever =
interested in deploying LISP) to request an EID address sub-block  as =
they do with usual prefixes.=20

>=20
>  "Following the policies outlined in [RFC5226], such space
>   will be assigned only upon IETF Review."
>=20

Well, this is standard, to have a reserved space we have to go through =
the (now called) "IETF Review", which is what we are doing ;-)


ciao

Luigi


> The previous sentence mentions hierarchical allocation and the above =
sentence mentions IETF Review.  It is not clear how assignments from =
this space will be made.
>=20
> Regards,
> -sm=20


From ggx@gigix.net  Thu Nov 15 06:28:26 2012
Return-Path: <ggx@gigix.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E767B21F888C for <ietf@ietfa.amsl.com>; Thu, 15 Nov 2012 06:28:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.249
X-Spam-Level: 
X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, 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 cz+qp9I92Lay for <ietf@ietfa.amsl.com>; Thu, 15 Nov 2012 06:28:26 -0800 (PST)
Received: from mail-we0-f172.google.com (mail-we0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id 3EEB821F8772 for <ietf@ietf.org>; Thu, 15 Nov 2012 06:28:26 -0800 (PST)
Received: by mail-we0-f172.google.com with SMTP id u46so651443wey.31 for <ietf@ietf.org>; Thu, 15 Nov 2012 06:28:25 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=3G3DwCh93Uf/dcC1FZvmYm5osHvS+Lx7kYO/hwp0E1U=; b=FXi54fHkJHg88VMNgdNIbbgwEcHqr/L/rvYBaI9eBCSK5GCOxYAa2l2QEt3EJjSwLQ tmOVqxPOW14e6JtMSIueFl93aALO4i2/thvIx/Q86EctVr9CW4Om4yG7jlAvFmVB0mn1 pAfMFaQLGYOGmVfwi0wBSBW/IYvhCTwfV+g/N+9m16JDA2TNpLExt2JSSvgUTOpol+HP L15exR7FGVnp1VNm8IN2LfdWsyyeDWSCo1/cjtJ7cAqxVf5Nq4BCgidXXQeBLdAcaTsy sHqelt3zkgv0Edvqtk/8gz1wcJEVZACZLfH0eUq72G4oAl2xd6puzM4BZKNHtuda2HnL yqoQ==
Received: by 10.180.77.38 with SMTP id p6mr128180wiw.1.1352989705309; Thu, 15 Nov 2012 06:28:25 -0800 (PST)
Received: from dhcp164-04.enst.fr (dhcp164-04.enst.fr. [137.194.165.4]) by mx.google.com with ESMTPS id hv4sm27883239wib.0.2012.11.15.06.28.23 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 15 Nov 2012 06:28:24 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
From: Luigi Iannone <ggx@gigix.net>
In-Reply-To: <5FCB8A98-4984-427C-9468-1DFDEBD206FD@steffann.nl>
Date: Thu, 15 Nov 2012 15:33:36 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <87676878-B077-4B4C-96DC-9F755F78018A@gigix.net>
References: <20121113144545.12836.71935.idtracker@ietfa.amsl.com> <CAKFn1SFy2+hXJLVtEpkdXfNuXA31ybmYnBFFPXj-73kb3tD+yw@mail.gmail.com> <5FCB8A98-4984-427C-9468-1DFDEBD206FD@steffann.nl>
To: Sander Steffann <sander@steffann.nl>
X-Mailer: Apple Mail (2.1499)
X-Gm-Message-State: ALoCoQl4Vz9IBbyURQ9CCz2s3grn+uhEXbgsrQR8WQInls+ZgE2ppH7a2LRNKvXaeYAPU0dp4Iga
Cc: ietf@ietf.org, lisp@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Nov 2012 14:28:27 -0000

On 15 Nov. 2012, at 10:43 , Sander Steffann <sander@steffann.nl> wrote:

> Hi,
>=20
>> I have to ask, who can request an netblock from this address space =
and
>> from where?
>> I might be blind but I couldn't find it mentioned anywhere.
>=20
> Good question. Will there be a central registry, or will parts of the =
space be delegated to i.e. LISP based ISPs?
>=20

Hi Sander,

no central registry has been ever discussed, was more about delegated =
the space to LISP ISPs.

Luigi


> - Sander
>=20
> _______________________________________________
> lisp mailing list
> lisp@ietf.org
> https://www.ietf.org/mailman/listinfo/lisp


From ggx@gigix.net  Thu Nov 15 06:33:43 2012
Return-Path: <ggx@gigix.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E258E21F88DE for <ietf@ietfa.amsl.com>; Thu, 15 Nov 2012 06:33:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.249
X-Spam-Level: 
X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, 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 y6DI5TDQCoTs for <ietf@ietfa.amsl.com>; Thu, 15 Nov 2012 06:33:43 -0800 (PST)
Received: from mail-wg0-f44.google.com (mail-wg0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id 3490121F8891 for <ietf@ietf.org>; Thu, 15 Nov 2012 06:33:43 -0800 (PST)
Received: by mail-wg0-f44.google.com with SMTP id dr13so636137wgb.13 for <ietf@ietf.org>; Thu, 15 Nov 2012 06:33:42 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=ebMAfPyVqptKTc8EBTiMiK15f4za92RTQLdg4IDPUFY=; b=BuehJglkzKoNLaoYIIGLycK5c2/MntMSoNV7kM/RpVVLpM0LX0ojW9P72ENt7XFrAR rtwagPMduJ1NXhFfL1lAqbzHr/D13sFXoORY8VGRntfuxqy/mNTskfTt6i9NkcR+FORi wcfIJkGI/7xs+UFB5I1//F571Mj+jOIH27guVSf50/Nvr7ond290R4qodUuUazLk7wF7 gjVrnhoA06j1lOoPe3bwY0wTSjTvmcGULWddXf8WFoFCNOu+lKXpDuId3eskiZD8WGt7 RXec0P3rEsFTzDnrnVhRxvY2unFGWY3WC5iuh3uTdFa4myMHfjcUOKSTyHby9clohfyo vNOg==
Received: by 10.180.7.197 with SMTP id l5mr83383wia.13.1352990022350; Thu, 15 Nov 2012 06:33:42 -0800 (PST)
Received: from dhcp164-04.enst.fr (dhcp164-04.enst.fr. [137.194.165.4]) by mx.google.com with ESMTPS id fa9sm7625419wib.5.2012.11.15.06.33.40 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 15 Nov 2012 06:33:41 -0800 (PST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
From: Luigi Iannone <ggx@gigix.net>
In-Reply-To: <1C49DB9E-6BD3-4A8A-8B19-2D5A8F4DAC94@apnic.net>
Date: Thu, 15 Nov 2012 15:38:54 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <7617A74B-6E11-4C9B-A1B8-73C3E332983C@gigix.net>
References: <20121113144545.12836.71935.idtracker@ietfa.amsl.com> <CAKFn1SFy2+hXJLVtEpkdXfNuXA31ybmYnBFFPXj-73kb3tD+yw@mail.gmail.com> <1C49DB9E-6BD3-4A8A-8B19-2D5A8F4DAC94@apnic.net>
To: George Michaelson <ggm+ietf@apnic.net>
X-Mailer: Apple Mail (2.1499)
X-Gm-Message-State: ALoCoQnFmjLfz1zSmXP19tJr9rHP2N4fjK7So90ExRvwepr1ngTL7ZUkrjCJ1iSuC2LTDCHQC6x9
Cc: ietf@ietf.org, lisp@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Nov 2012 14:33:44 -0000

 Hi George,

On 15 Nov. 2012, at 11:50 , George Michaelson <ggm+ietf@apnic.net> =
wrote:

> I think this document isn't ready for IETF last call.

We are open to any suggestion to make the document ready for it. ;-)


>=20
> I think the context of an experimental assignment which heads to
> distributing IPv6 addresses to end-entities, even if the experiment
> is not intended to be globally routable, poses questions about how
> the address management function is going to work. Can the working
> group be asked to discuss how this is meant to be interpreted in
> the light of RFC2050 based processes? It might avoid future pain
> if its clear how the IAB and the RIR understand these addresses and
> their management.
>=20
> The experiment has all the attributes of a general, wide-ranging
> address distribution and management activity. I haven't seen any
> substantive discussion of this in the WG mailing lists, and I'm
> worried this hasn't been documented, or understood.

Well, clearly I am missing something. WOuld you mind be a bit more =
specific? Are you asking to have rough consensus on specific points? =
Which points?

thanks

Luigi

>=20
> cheers
>=20
> -George


From ggx@gigix.net  Thu Nov 15 06:41:46 2012
Return-Path: <ggx@gigix.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E32321F8904 for <ietf@ietfa.amsl.com>; Thu, 15 Nov 2012 06:41:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.912
X-Spam-Level: 
X-Spam-Status: No, score=-2.912 tagged_above=-999 required=5 tests=[AWL=0.687,  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 hwUxP4khI6Ko for <ietf@ietfa.amsl.com>; Thu, 15 Nov 2012 06:41:45 -0800 (PST)
Received: from mail-wg0-f44.google.com (mail-wg0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id 1EA3321F88E9 for <ietf@ietf.org>; Thu, 15 Nov 2012 06:41:41 -0800 (PST)
Received: by mail-wg0-f44.google.com with SMTP id dr13so639315wgb.13 for <ietf@ietf.org>; Thu, 15 Nov 2012 06:41:41 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=VhXy1oSQIKK6CkBWBYF+i1OSWgelFshFVhxWzrjnCyM=; b=LsafSicgjjwPzPsE4Xg/Qvtqn1fnK9GAPHGFmWaqKe4RYD/KtSavHn7VP3QxVROWo/ pFjErh/qGhryA1mtO9kKMXxpjFiH3EJ1OIofV98eqD4I7tkc+vospdLSnt/Q/1L2wLx8 nnPHKCBn9mUfVtGMfhHS/4k3lW18cN3QqVH1CAMRhNRM3YduHCoCPDYiVEK12ej6etrG 844dktqDwEzeWOTPX/K+2m9RwNmENSqbUiJkFKWXpvvVCcELHuzWDUkXaJKaQOWzKZQ0 OA4QjivK/jOh7GAFiNeNCUV4MDE8WZwnZvQz/Vor2J4UEqgXM9kM0aUjfezkdfBdlrjI QOJQ==
Received: by 10.180.100.97 with SMTP id ex1mr101310wib.17.1352990501144; Thu, 15 Nov 2012 06:41:41 -0800 (PST)
Received: from ?IPv6:2001:660:330f:a4:6c55:486d:3ba1:398a? ([2001:660:330f:a4:6c55:486d:3ba1:398a]) by mx.google.com with ESMTPS id q10sm7662739wie.2.2012.11.15.06.41.39 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 15 Nov 2012 06:41:40 -0800 (PST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
From: Luigi Iannone <ggx@gigix.net>
In-Reply-To: <50A4CA14.9010909@bwijnen.net>
Date: Thu, 15 Nov 2012 15:46:53 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <79AB8650-BB45-4F56-B7C2-B1D36DF5ADDD@gigix.net>
References: <50A4CA14.9010909@bwijnen.net>
To: Bert Wijnen (IETF) <bertietf@bwijnen.net>
X-Mailer: Apple Mail (2.1499)
X-Gm-Message-State: ALoCoQmE7lX33Lw5gmfuXiM55DGCPiLaT61knIhO0eLR2QnVzb9FmiBYkRHSJsAwLk3AL7zs2UWd
Cc: lisp@ietf.org, "ietf@ietf.org" <ietf@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Nov 2012 14:41:46 -0000

Hi Bert,

On 15 Nov. 2012, at 11:55 , Bert Wijnen (IETF) <bertietf@bwijnen.net> =
wrote:

[snip]
>=20
> So it is not asking just a /16 but also asking for reservation of a =
/12.
>=20
> Pretty big space.
>=20
> And in the list of reasons, I mainly read that it is "sufficiently =
large",
> but not much about why it needs to be this big. Why would a smaller
> allocation not be sufficient?
>=20

Well, to keep it short, the WG felt that /16 is the "right size", and =
that if the growth of LISP would be so important as to need a bigger =
space would be nice to have it contiguous (so implementations can just =
change the prefix length).=20

Luigi

> Bert


From bertietf@bwijnen.net  Thu Nov 15 06:46:57 2012
Return-Path: <bertietf@bwijnen.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EA98321F88B7; Thu, 15 Nov 2012 06:46:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.449
X-Spam-Level: 
X-Spam-Status: No, score=-102.449 tagged_above=-999 required=5 tests=[AWL=0.150, 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 q0-FHuNo6W21; Thu, 15 Nov 2012 06:46:57 -0800 (PST)
Received: from postgirl.ripe.net (postgirl.ipv6.ripe.net [IPv6:2001:67c:2e8:11::c100:1342]) by ietfa.amsl.com (Postfix) with ESMTP id 2241B21F8928; Thu, 15 Nov 2012 06:46:57 -0800 (PST)
Received: from dodo.ripe.net ([193.0.23.4]) by postgirl.ripe.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from <bertietf@bwijnen.net>) id 1TZ0iT-00018J-Op; Thu, 15 Nov 2012 15:46:54 +0100
Received: from cat.ripe.net ([193.0.1.249] helo=guest165.guestnet.ripe.net) by dodo.ripe.net with esmtp (Exim 4.72) (envelope-from <bertietf@bwijnen.net>) id 1TZ0iT-0004Ec-EU; Thu, 15 Nov 2012 15:46:53 +0100
Message-ID: <50A5005D.2080704@bwijnen.net>
Date: Thu, 15 Nov 2012 15:46:53 +0100
From: "Bert Wijnen (IETF)" <bertietf@bwijnen.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: Luigi Iannone <ggx@gigix.net>
Subject: Re: Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
References: <50A4CA14.9010909@bwijnen.net> <79AB8650-BB45-4F56-B7C2-B1D36DF5ADDD@gigix.net>
In-Reply-To: <79AB8650-BB45-4F56-B7C2-B1D36DF5ADDD@gigix.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Anti-Virus: Kaspersky Anti-Virus for Linux Mail Server 5.6.48/RELEASE, bases: 20120425 #7816575, check: 20121115 clean
X-RIPE-Spam-Level: --
X-RIPE-Spam-Report: Spam Total Points:   -2.9 points pts rule name              description ---- ---------------------- ------------------------------------ -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP -1.9 BAYES_00               BODY: Bayes spam probability is 0 to 1% [score: 0.0000]
X-RIPE-Signature: 86ab03e524994f79ca2c75a176445dd49c4d59811551b7ded1ee84cc640e623a
Cc: lisp@ietf.org, "ietf@ietf.org" <ietf@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Nov 2012 14:46:58 -0000

Nice to try and keep it short.

But I was hoping for some more detail and explanation.
I have not followed the discussions (if any) in the WG
so I may be missing the reasons why you need this much
space. I would hope that the WG (if they have consensus
(which may be something different than "the WG felt"))
could elaborate or summarize the discussions that lead
to the conclusion that this amount of space is needed
and makes sense.

Pointers to the WG mlist discussions where the pros
and cons of various prefixes sizes are discussed or
summarize would also be welcome.

Bert

On 11/15/12 3:46 PM, Luigi Iannone wrote:
> Hi Bert,
>
> On 15 Nov. 2012, at 11:55 , Bert Wijnen (IETF) <bertietf@bwijnen.net> wrote:
>
> [snip]
>>
>> So it is not asking just a /16 but also asking for reservation of a /12.
>>
>> Pretty big space.
>>
>> And in the list of reasons, I mainly read that it is "sufficiently large",
>> but not much about why it needs to be this big. Why would a smaller
>> allocation not be sufficient?
>>
>
> Well, to keep it short, the WG felt that /16 is the "right size", and that if the growth of LISP would be so important as to need a bigger space would be nice to have it contiguous (so implementations can just change the prefix length).
>
> Luigi
>
>> Bert
>
>

From dhc@dcrocker.net  Thu Nov 15 08:04:14 2012
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 193F021F8943 for <ietf@ietfa.amsl.com>; Thu, 15 Nov 2012 08:04:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.058
X-Spam-Level: 
X-Spam-Status: No, score=-5.058 tagged_above=-999 required=5 tests=[AWL=-0.102, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, RCVD_IN_NJABL_PROXY=1.643]
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 b+ZV-o83k9yl for <ietf@ietfa.amsl.com>; Thu, 15 Nov 2012 08:04:13 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 0306721F88EA for <ietf@ietf.org>; Thu, 15 Nov 2012 08:04:12 -0800 (PST)
Received: from [192.168.1.9] (adsl-67-127-56-94.dsl.pltn13.pacbell.net [67.127.56.94]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id qAFG4BQR001623 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 15 Nov 2012 08:04:12 -0800
Message-ID: <50A51274.2060308@dcrocker.net>
Date: Thu, 15 Nov 2012 08:04:04 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: Carsten Bormann <cabo@tzi.org>
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
References: <201211121745.qACHjiXS919660@shell01.TheWorld.com> <50A13B43.7000309@dcrocker.net> <72F0897C-D473-4F34-8D21-B9A60DDBBB09@tzi.org> <50A3F814.1030509@dcrocker.net> <3C8B46A8-1D7C-481F-883D-7CC7D4946BA1@tzi.org>
In-Reply-To: <3C8B46A8-1D7C-481F-883D-7CC7D4946BA1@tzi.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Thu, 15 Nov 2012 08:04:12 -0800 (PST)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Nov 2012 16:04:14 -0000

Carsten, et al,


On 11/14/2012 11:08 PM, Carsten Bormann wrote:
> My comment was not about getting work done, but about impact of this
> work.

OK.  So the choice of venue is supposed to serve two goals:

    *  Being useful for the workers developing IETF documents.

    *  Promoting that work to (potential) consumers of it.

The first bullet is the operational one of choosing venues that are 
convenient and useful for attendees doing the work.  It's important to 
note that it is difficult to service this one requirement.  Adding more 
increases the challenges and risks.

Concerning the second bullet an example would be that by showing up in 
South America, we will get more use of IETF work in South America.  Or 
is the view broader that our showing up in SA, we will get more use 
elsewhere also?


>>     I believe that it is better
>> accomplished by doing work that has more community involvement and
>> more operational relevance.
...
>> If we do that, it won't matter where we hold our meetings.
>
> And I was pointing out that this isn't true. It may not matter nearly
> as much as the quality of the work, but there is an effect.

The second bullet is about marketing the IETF brand.  Your position is 
that we will have better use of IETF output if we choose locations to 
increase awareness, mindshare, and the like.  The importance of brand 
awareness is well established in marketing.  The question is how much 
the particular choice of venue affects IETF brand awareness.

In terms of marketing theory, your premise is reasonable. 
Unfortunately, many marketing theories are reasonable but wrong.

So what I do not understand is its empirical basis for the specific case 
of the IETF.

The fact that we have been wandering around the globe for 20 years ought 
to have provided us with that empirical basis.  In addition, we should 
be able to compare our own history with that of standards groups that do 
/not/ wander around, or who wander less than we do, and we should see a 
history of better mindshare and better uptake of work for the IETF.

As popular as IETF work is, I don't see that less 'mobile' standards 
groups are suffering by comparison.  Or, at least, not due to their 
being less mobile.

To the extent that one disagrees with my assertion, I'll claim that any 
differences in mindshare are readily explained by the quality or 
relevance of the work, not the choice of meeting venue.

In other words, I appreciate your firm "this isn't true" but ask you to 
substantiate it empirically.  Otherwise, we are making an expensive, 
risky, strategic decision based on an unfounded belief.  It's a popular 
belief, I admit, but that doesn't make it valid.


> Increasing visibility and mindshare, in particular at level 9, can
> very much help enabling involvement.

So the fact that we haven't been showing up in South America or Africa 
or the Middle East should mean that the IETF's work has less mindshare 
there and less adoption, especially compared with other standards groups 
that do go to those regions.

Another example of an empirical test could be that that folk from such 
venues, who have shown up on our many mailing lists, choose not to 
continue working with the IETF because we don't go to their countries.


>> In other words, I would have that our relevance is determined more
>> by the quality and utility of our work than by the marketing
>> effects of meeting venue.
>
> I certainly subscribe to that.


>> Again, finding meeting venues that work well for an IETF venue is
>> quite difficult. When we add other goals, such as marketing the
>> IETF to the community, we make venue selection especially
>> difficult.
>
> Again, you are trying to argue against my point by saying your point
> is more important. That is certainly so, but doesn't make my point
> wrong or irrelevant.

I'm saying that your point lacks an empirical basis and, worse, that it 
can hurt the primary requirement for meeting venues.

There is a very real and cost to your point and only a theoretical 
benefit.  The real cost is that it increases the aggregate 
/in/convenience to /existing/ IETF workers and it /increases/ the 
barrier to participation for people from the regions that are already 
supplying workers.

Our current model is to distribute the travel pain.  One time, more 
convenient for North Americans.  Another time, more convenient for 
Eastern Asians.  That is, the goal is fairness among current workers.

The choice of the 3 regions we vary among has been based on actual 
participation.  We increased the desired proportion of meetings in East 
Asia as we saw a strong trend of increased participation from that 
region.  This was a /reactive/, not /proactive/, change.  (Our failure 
to maintain the model has been due to logistical problems, not a change 
in the model.)

To the extent that going elsewhere increases the pain, cost, operational 
risk, or the like for current workers, this theoretical marketing 
benefit hurts actual work.

Showing up in venues that already supply participants to IETF work also 
lowers the barrier for existing IETF workers who have less time and 
money for attending.  Note that the core of the IETF is workers with 
rather plush corporate funding and a pattern of extensive travel.  That 
creates an insensitivity to folk with more limited budget or time.


> Practically speaking, e.g., if we can get a reasonable venue in
> Brazil or in a Spanish-speaking country, we should go there.

And my point is that you are not speaking practically.  Your are 
speaking reasonably but entirely theoretically, absent an empirical basis.

And one of the hallmarks of behavioral analysis -- of which marketing is 
a sub-specialty -- most assertions of cause/effect turn out to be wrong, 
when actually tested.


d/

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From sander@steffann.nl  Thu Nov 15 01:43:36 2012
Return-Path: <sander@steffann.nl>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2549621F8585; Thu, 15 Nov 2012 01:43:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.126
X-Spam-Level: *
X-Spam-Status: No, score=1.126 tagged_above=-999 required=5 tests=[AWL=-0.150,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_EQ_IP_ADDR=1.119, MIME_8BIT_HEADER=0.3, RCVD_IN_PBL=0.905, RDNS_NONE=0.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 H5e10viNfNFL; Thu, 15 Nov 2012 01:43:35 -0800 (PST)
Received: from mail.sintact.nl (mail.sintact.nl [IPv6:2001:4038:0:16::7]) by ietfa.amsl.com (Postfix) with ESMTP id 293D921F85C8; Thu, 15 Nov 2012 01:43:34 -0800 (PST)
Received: from [172.20.10.3] (unknown [62.140.132.44]) by mail.sintact.nl (Postfix) with ESMTP id CD1722008; Thu, 15 Nov 2012 10:43:30 +0100 (CET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
From: Sander Steffann <sander@steffann.nl>
In-Reply-To: <CAKFn1SFy2+hXJLVtEpkdXfNuXA31ybmYnBFFPXj-73kb3tD+yw@mail.gmail.com>
Date: Thu, 15 Nov 2012 10:43:29 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <5FCB8A98-4984-427C-9468-1DFDEBD206FD@steffann.nl>
References: <20121113144545.12836.71935.idtracker@ietfa.amsl.com> <CAKFn1SFy2+hXJLVtEpkdXfNuXA31ybmYnBFFPXj-73kb3tD+yw@mail.gmail.com>
To: =?iso-8859-1?Q?Roger_J=F8rgensen?= <rogerj@gmail.com>
X-Mailer: Apple Mail (2.1499)
X-Mailman-Approved-At: Thu, 15 Nov 2012 09:09:12 -0800
Cc: ietf@ietf.org, lisp@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Nov 2012 09:43:36 -0000

Hi,

> I have to ask, who can request an netblock from this address space and
> from where?
> I might be blind but I couldn't find it mentioned anywhere.

Good question. Will there be a central registry, or will parts of the =
space be delegated to i.e. LISP based ISPs?

- Sander


From sander@steffann.nl  Thu Nov 15 06:45:35 2012
Return-Path: <sander@steffann.nl>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1012121F8451; Thu, 15 Nov 2012 06:45:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.189
X-Spam-Level: *
X-Spam-Status: No, score=1.189 tagged_above=-999 required=5 tests=[AWL=-0.064,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, MIME_QP_LONG_LINE=1.396,  RCVD_IN_PBL=0.905, RDNS_NONE=0.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 L2THYOFBopQN; Thu, 15 Nov 2012 06:45:34 -0800 (PST)
Received: from mail.sintact.nl (mail.sintact.nl [IPv6:2001:4038:0:16::7]) by ietfa.amsl.com (Postfix) with ESMTP id 21D2321F846E; Thu, 15 Nov 2012 06:45:34 -0800 (PST)
Received: from [10.13.121.140] (unknown [62.140.132.44]) by mail.sintact.nl (Postfix) with ESMTP id 4EC5C200C; Thu, 15 Nov 2012 15:45:33 +0100 (CET)
References: <20121113144545.12836.71935.idtracker@ietfa.amsl.com> <CAKFn1SFy2+hXJLVtEpkdXfNuXA31ybmYnBFFPXj-73kb3tD+yw@mail.gmail.com> <5FCB8A98-4984-427C-9468-1DFDEBD206FD@steffann.nl> <87676878-B077-4B4C-96DC-9F755F78018A@gigix.net>
Mime-Version: 1.0 (1.0)
In-Reply-To: <87676878-B077-4B4C-96DC-9F755F78018A@gigix.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <471ADB67-9BAB-44FC-BA9E-9D75DA011503@steffann.nl>
X-Mailer: iPhone Mail (10A523)
From: Sander Steffann <sander@steffann.nl>
Subject: Re: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
Date: Thu, 15 Nov 2012 15:45:30 +0100
To: Luigi Iannone <ggx@gigix.net>
X-Mailman-Approved-At: Thu, 15 Nov 2012 09:09:12 -0800
Cc: "ietf@ietf.org" <ietf@ietf.org>, "lisp@ietf.org" <lisp@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Nov 2012 14:45:35 -0000

Hi,

> no central registry has been ever discussed, was more about delegated the s=
pace to LISP ISPs.

Glad to hear that!
Sander


From pvinci@VinciConsulting.com  Thu Nov 15 07:10:00 2012
Return-Path: <pvinci@VinciConsulting.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 82D9721F893A; Thu, 15 Nov 2012 07:10:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.413
X-Spam-Level: 
X-Spam-Status: No, score=-2.413 tagged_above=-999 required=5 tests=[AWL=0.186,  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 OjgDRFxlyIFt; Thu, 15 Nov 2012 07:10:00 -0800 (PST)
Received: from exchange.vinci-consulting-corp.com (exchange.vinci-consulting-corp.com [38.125.5.16]) by ietfa.amsl.com (Postfix) with ESMTP id C461821F8932; Thu, 15 Nov 2012 07:09:59 -0800 (PST)
Received: from NYDC-EXCH01.vinci-consulting-corp.local ([::1]) by NYDC-EXCH01.vinci-consulting-corp.local ([::1]) with mapi id 14.02.0318.001; Thu, 15 Nov 2012 10:09:58 -0500
From: Paul Vinciguerra <pvinci@VinciConsulting.com>
To: Luigi Iannone <ggx@gigix.net>, Sander Steffann <sander@steffann.nl>
Subject: RE: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
Thread-Topic: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
Thread-Index: Ac3DQXxYSz//3jgbSSusYJBGpYtnCg==
Date: Thu, 15 Nov 2012 15:09:57 +0000
Message-ID: <6E5736BD68F770449C74FBAD975F807C94AA2C60@NYDC-EXCH01.vinci-consulting-corp.local>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.10.14]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Thu, 15 Nov 2012 09:09:12 -0800
Cc: "ietf@ietf.org" <ietf@ietf.org>, "lisp@ietf.org" <lisp@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Nov 2012 15:10:00 -0000

> On 15 Nov. 2012, at 10:43 , Sander Steffann <sander@steffann.nl> wrote:
>=20
> > Hi,
> >
> >> I have to ask, who can request an netblock from this address space
> >> and from where?
> >> I might be blind but I couldn't find it mentioned anywhere.
> >
> > Good question. Will there be a central registry, or will parts of the s=
pace be
> delegated to i.e. LISP based ISPs?
> >
>=20
> Hi Sander,
>=20
> no central registry has been ever discussed, was more about delegated the
> space to LISP ISPs.

So there will be a pool of addresses that the RIR's can allocate out of for=
 EIDs?  If that's the case, what is the additional value to an ISP who woul=
d conceivably have to pay the RIR for another block of V6 addresses specifi=
cally for use as EIDs, when most likely they are already paying for a block=
 that can be used for either purpose?=20
=20
Paul


From johnl@taugh.com  Thu Nov 15 09:16:01 2012
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 25F2D21F8623 for <ietf@ietfa.amsl.com>; Thu, 15 Nov 2012 09:16:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.253
X-Spam-Level: 
X-Spam-Status: No, score=-2.253 tagged_above=-999 required=5 tests=[AWL=0.047,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, NO_RELAYS=-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 Nsei1CzlCnfW for <ietf@ietfa.amsl.com>; Thu, 15 Nov 2012 09:16:00 -0800 (PST)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 9A74521F8618 for <ietf@ietf.org>; Thu, 15 Nov 2012 09:15:54 -0800 (PST)
Received: (qmail 40643 invoked from network); 15 Nov 2012 17:15:52 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:vbr-info:user-agent:cleverness; s=9ec2.50a52348.k1211; bh=uJ74EJIm4ogtfqnb6AJsFH+5GaEZMmOaHjUGo2zDjnE=; b=DOx/xTVjlGb+vl9oecPYtTzSFVHVvipw5pQX/W69ErHI8gxPrf9UeTmf5lQXUgdBfEfwHm8tQxIKylwaZe7oC0shJjT4QgrlQYCnbOJ3ACdeI3/PVAaa4tAgpNhXQAr5GuilIGT83pu2t95FeZZrM0c/pcOmy8RBv4NHniADbEk=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:vbr-info:user-agent:cleverness; s=9ec2.50a52348.k1211; bh=uJ74EJIm4ogtfqnb6AJsFH+5GaEZMmOaHjUGo2zDjnE=; b=OoJEFqkVqexJiknczr86yik4OF1/fNrHk50haXkIpVKQNSW5MJalkP3R5KbGW3N3zgoC6b/BtgwjJMBMis04RgjCHsGAMl3YBYz2CRicjNbhUCKQAdusVAL+e6kKzrINryg/MnAy5FrSZ2+ybup7qkCn5uXPNOg6AjeE3u+FHiw=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Received: (ofmipd 127.0.0.1); 15 Nov 2012 17:15:30 -0000
Date: 15 Nov 2012 12:15:51 -0500
Message-ID: <alpine.BSF.2.00.1211151215100.30183@joyce.lan>
From: "John R Levine" <johnl@taugh.com>
To: "=?UTF-8?Q?Patrik_F=C3=A4ltstr=C3=B6m?=" <paf@frobbit.se>
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
In-Reply-To: <103721F2-BA44-4EA5-BA9D-A7941EA4D5ED@frobbit.se>
References: <20121115050813.4158.qmail@joyce.lan> <103721F2-BA44-4EA5-BA9D-A7941EA4D5ED@frobbit.se>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Nov 2012 17:16:01 -0000

> As Arturo says, having people that traditionally go to an IETF meeting travel to (for them) far away places and (for them) new cultures, do definitely open their eyes to how large our world is.

I think that learning about other parts of the world is swell, but I don't 
think the IETF should be a travel agent.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
"I dropped the toothpaste", said Tom, crestfallenly.

From sm@resistor.net  Thu Nov 15 09:25:57 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 896AF21F8996; Thu, 15 Nov 2012 09:25:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.492
X-Spam-Level: 
X-Spam-Status: No, score=-102.492 tagged_above=-999 required=5 tests=[AWL=0.107, 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 b3yhQcMhShsK; Thu, 15 Nov 2012 09:25:54 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id C6C3E21F8549; Thu, 15 Nov 2012 09:25:40 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id qAFHPQk7021137; Thu, 15 Nov 2012 09:25:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1353000337; bh=k3eONktwbbqFfREu22oKAe+/aOxsbkY3Q2/j0emFr2c=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=x8LI7nMarJH5Pct5gESm+4huYtdaa/UW8iK7jKCGQ+HSMQNmZNcVfN7TWMH2NzSQa R0imqnfNXtLaU8x4ykm+YvsDqPyDceTiNj1d2T6ReaukuJFu8pAxZnN38ZZZmaD7ST LIM7YfgkrZ4g1VnverpSUzzpzE/zSaA0F6jjYMYs=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1353000337; i=@resistor.net; bh=k3eONktwbbqFfREu22oKAe+/aOxsbkY3Q2/j0emFr2c=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=Grn0pO8VWH7WvjZi8dZUh5FS45eT35AO4zgOEKxLUHHR8uvJfZwURAPgY3jJok8fp t0kpg3vaGkb5gi5DPintig/zgUH2kCx3K6J6oWqFIR5cRnI0r6u4pDjCSQaSrI6BXq uJ/n39L8dN5ErGgudzGZBizW4uJbhrc2y2/eVQlQ=
Message-Id: <6.2.5.6.2.20121115075935.0a4c3298@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 15 Nov 2012 09:08:08 -0800
To: Luigi Iannone <ggx@gigix.net>
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
In-Reply-To: <63359CE6-0009-45D1-B2AE-3F2B4384D5D4@gigix.net>
References: <20121113144545.12836.71935.idtracker@ietfa.amsl.com> <6.2.5.6.2.20121114030352.0da0e888@resistor.net> <63359CE6-0009-45D1-B2AE-3F2B4384D5D4@gigix.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org, lisp@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Nov 2012 17:25:57 -0000

Hi Luigi,
At 06:32 15-11-2012, Luigi Iannone wrote:
>  thanks for the comments. Few answers inline.

Thanks for the response.

>Well, if we go along that road we should put the whole document in a 
>single "IANA Considerations" Section. ;-)

Yes. :-)

>Actually the current IANA Considerations section states the same 
>request but does not specify "/12".
>You are right that it should be clearly stated, to make the document 
>coherent. Will fix.

Ok.

>It refers to the IANA allocation policies. May be it could be 
>changed in the following way:
>
>         If in the future there will be need for a larger EID Block the
>         address space adjacent the EID Block could be allocate by IANA
>         according to its current allocation policies."
>
>Would that work?

Not yet. :-)  You did not answer my question about which IANA 
allocation policies the draft is referring to.

>I agree that this point has been not discussed thoroughly, the idea 
>is not to create any new "manager", rather to make ISPs (or whoever 
>interested in deploying LISP) to request an EID address 
>sub-block  as they do with usual prefixes.

I'll comment below.

>Well, this is standard, to have a reserved space we have to go 
>through the (now called) "IETF Review", which is what we are doing ;-)

What the draft is doing is reserving address space.  According to 
Section 10 address blocks from that reserved address space (the /16) 
will be assigned through IETF review.  I read the previous comment as 
meaning that the EID address block will be assigned to ISPs by 
RIRs.  There isn't any mention of that in the draft.  Even if it was 
mentioned it is doubtful that ISPs would be able to get that address 
space assigned through RIRs at present.  The issue was mentioned in 
the AD review [1].  I didn't find any discussion of that in the LISP 
mailing list archives.

According to the LISP Charter the document is to request "address 
space to be used for the LISP experiment as identifier space".  The 
draft is reserving a /16 and there is scope to have that extended to 
a /12 in future.  This goes beyond the usual experiments.  There 
isn't any discussion of how the ip6.arpa delegation will be 
handled.  There isn't any discussion of how long the experiment will 
last.  I understand that IPv6 is not a scare resource.  However, that 
is not a reason for handing out address space and leaving it to 
someone in future to figure out what to do if this becomes a problem.

I haven't seen anyone asking why the document is not a BCP.  If the 
aim is to have:

   "Routers in the Legacy Internet must treat announcements of prefixes
    from the IPv6 EID Block as normal announcements, applying best
    current practice for traffic engineering and security."

I think that the document might have to be a BCP.  It would be good 
to be clear about whether the address space should be listed in the 
IANA IPv6 Special Purpose Address Registry.

Section 5 mentions that "The working group reached consensus on an 
initial allocation".  Could the document shepherd upload the write-up 
and provide some details about that?

Regards,
-sm

1. http://www.ietf.org/mail-archive/web/lisp/current/msg03848.html 


From cabo@tzi.org  Thu Nov 15 09:27:40 2012
Return-Path: <cabo@tzi.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB85821F89AE for <ietf@ietfa.amsl.com>; Thu, 15 Nov 2012 09:27:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.43
X-Spam-Level: 
X-Spam-Status: No, score=-106.43 tagged_above=-999 required=5 tests=[AWL=-0.181, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, 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 FoRf+Fcu1nbV for <ietf@ietfa.amsl.com>; Thu, 15 Nov 2012 09:27:40 -0800 (PST)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id 437B121F8549 for <ietf@ietf.org>; Thu, 15 Nov 2012 09:27:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.3/8.14.3) with ESMTP id qAFHROFB024842; Thu, 15 Nov 2012 18:27:24 +0100 (CET)
Received: from [192.168.217.117] (p54892240.dip.t-dialin.net [84.137.34.64]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 20FB5123; Thu, 15 Nov 2012 18:27:24 +0100 (CET)
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Content-Type: text/plain; charset=iso-8859-1
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <50A51274.2060308@dcrocker.net>
Date: Thu, 15 Nov 2012 18:27:23 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <2A1E0AF1-98CB-4212-8AF5-3AB38E0EED1A@tzi.org>
References: <201211121745.qACHjiXS919660@shell01.TheWorld.com> <50A13B43.7000309@dcrocker.net> <72F0897C-D473-4F34-8D21-B9A60DDBBB09@tzi.org> <50A3F814.1030509@dcrocker.net> <3C8B46A8-1D7C-481F-883D-7CC7D4946BA1@tzi.org> <50A51274.2060308@dcrocker.net>
To: dcrocker@bbiw.net
X-Mailer: Apple Mail (2.1499)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Nov 2012 17:27:40 -0000

On Nov 15, 2012, at 17:04, Dave Crocker <dhc@dcrocker.net> wrote:

> I'm saying that your point lacks an empirical basis

Yes.
I'm not even arguing that the IETF spend effort on obtaining that =
empirical basis (hint: there is probably a great PhD thesis in =
organizational marketing waiting to be written).

My hypothesis is mainly based on my perceptions of changes in reception =
of the IETF in the German corporate technology and research environments =
right after both Amsterdam (1993) and Munich (1997).  I'm well aware =
that perception of mine may, of course, be all based on confirmation =
bias.  I still strongly believe I have seen the effect.  I'm also quite =
skeptical that this experience will reliably transfer to any other =
market.  I still believe that the potential benefits from repeating the =
experiment in some of them would be worth a *small* increase in =
inconvenience for IETF's regular attendees.  I trust the IAOC to choose =
a reasonable value of "small".

I probably don't need to point out that we regularly meet in venues that =
are ridiculously inconvenient to completely inaccessible for a sizable =
fraction of our regular contributors.  I don't think we have very good =
numbers on this effect, either (I don't think we track citizenship or =
blacklist name matches).  Just to throw another unfounded hypothesis in =
the air: in the working groups where I'm active, this might block access =
to 10 to 15 % of the contributors, and it cools down the potential =
interest of some more.  We make a lot of our decisions on bad data like =
this.

> and, worse, that it can hurt the primary requirement for meeting =
venues.

Which, again, is not a useful way to falsify my hypothesis.

I don't think that there is any danger to the IAOC's "prime directive" =
in site selection (convenience for regulars) from bringing a couple of =
important, but secondary concerns to the table.

Gr=FC=DFe, Carsten


From carlosm3011@gmail.com  Thu Nov 15 09:43:53 2012
Return-Path: <carlosm3011@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 062E121F86CE for <ietf@ietfa.amsl.com>; Thu, 15 Nov 2012 09:43:53 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RTv+csz4C+tD for <ietf@ietfa.amsl.com>; Thu, 15 Nov 2012 09:43:52 -0800 (PST)
Received: from mail-gh0-f181.google.com (mail-gh0-f181.google.com [209.85.160.181]) by ietfa.amsl.com (Postfix) with ESMTP id 1A57B21F88D4 for <ietf@ietf.org>; Thu, 15 Nov 2012 09:43:51 -0800 (PST)
Received: by mail-gh0-f181.google.com with SMTP id z22so444794ghb.26 for <ietf@ietf.org>; Thu, 15 Nov 2012 09:43:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=XCDzwHGCwDOBocv7fnExL58obxF6mPZnLOF1v84nsF4=; b=XnUvLWfEbTRKpQgT69NfbKpU+yWpb1hRL34NOZPGUw1bM3Iu8o/v7phwa01pyi3Bit Xky4cXixHdWnJB2SKdeBTIxd5zUPY3atGZZV8Hc/tY9/skUtZV3GIihgSBZmW/pJt33Y dEBvW8+4TrX91YlPfNX91M1WzvtV3po6GCkeAx/6ROGzhZq2donBqxS5Aljok+fTmMM4 XZoBJCv41+QiD31V19p3IPVAOcR+H+BANF0rsr7x79sOgdwjsiGlGlLP2G/iWin0xoni 4H7nf9vcfngdyQsdiTfjUUy2bmbTsQ/0beJxhCBZ8mW40rV1xhHed401Cw2+4z3ffdBR OrDg==
Received: by 10.236.73.198 with SMTP id v46mr1701158yhd.80.1353001431582; Thu, 15 Nov 2012 09:43:51 -0800 (PST)
Received: from europa.local ([2001:13c7:7001:5128:68bb:4b3d:ecb6:a7be]) by mx.google.com with ESMTPS id z65sm16407732yhe.22.2012.11.15.09.43.49 (version=SSLv3 cipher=OTHER); Thu, 15 Nov 2012 09:43:50 -0800 (PST)
Message-ID: <50A529D2.5050808@gmail.com>
Date: Thu, 15 Nov 2012 15:43:46 -0200
From: "Carlos M. Martinez" <carlosm3011@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: John R Levine <johnl@taugh.com>
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
References: <20121115050813.4158.qmail@joyce.lan> <103721F2-BA44-4EA5-BA9D-A7941EA4D5ED@frobbit.se> <alpine.BSF.2.00.1211151215100.30183@joyce.lan>
In-Reply-To: <alpine.BSF.2.00.1211151215100.30183@joyce.lan>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org, =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Nov 2012 17:43:53 -0000

On 11/15/12 3:15 PM, John R Levine wrote:
>> As Arturo says, having people that traditionally go to an IETF meeting
>> travel to (for them) far away places and (for them) new cultures, do
>> definitely open their eyes to how large our world is.
> 
> I think that learning about other parts of the world is swell, but I
> don't think the IETF should be a travel agent.
> 

Comparing with the ITU who does tour the world, organizing workshops in
far away places, I really think we should be trying a little harder to
be more open.

So far this entire thread would provide a nice argument for those
proposing more government involvement as clearly the multistakeholder
approach is failing the less developed economies. Given that WCIT is
starting in a few days, and that every country has one vote in that
thing, I think this kind of attitude is not helping us.

This is not my personal view, but that is how some may read it: the IETF
attendees are a bunch of 'ivory tower' engineers who can't be bothered
to fly routes with more than one connection or who firmly believe that
the business district in Sao Paulo is more dangerous/menacing than the
area around the Atlanta Hilton.

I want the IETF and the governance model it represents to succeed, I
firmly believe in it. However I'm not that blind and I seriously believe
we need to fix some things at home, or we are going to be easy prey for
those seeking to control the Internet.

regards

~Carlos

> Regards,
> John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
> "I dropped the toothpaste", said Tom, crestfallenly.

From carlosm3011@gmail.com  Thu Nov 15 09:47:54 2012
Return-Path: <carlosm3011@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F7E121F89C2 for <ietf@ietfa.amsl.com>; Thu, 15 Nov 2012 09:47:54 -0800 (PST)
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.000,  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 nMOmqpZ0DfK5 for <ietf@ietfa.amsl.com>; Thu, 15 Nov 2012 09:47:53 -0800 (PST)
Received: from mail-ye0-f172.google.com (mail-ye0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id 695D321F89B5 for <ietf@ietf.org>; Thu, 15 Nov 2012 09:47:53 -0800 (PST)
Received: by mail-ye0-f172.google.com with SMTP id l13so380539yen.31 for <ietf@ietf.org>; Thu, 15 Nov 2012 09:47:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=IPXaXoJARbP5yCLA35pHmxd7CjnbKAI6ZFqujdoTRkc=; b=yBDrz7BQIXWuAlC65vMlDRtwZIR0ImmRhJOXct+cP8FIWSWbMxw69KpffWQK/Mq2hx fmnbJjUsDTal5od3Zr6cG8m7G+NerCTtWqIyD4nwmiNTiFt6aIHcNhl1pmQyBJ5MaRfL KCJRzU5dzkRdU1QL7t2yb7M2EVqjoTkyYXKqlLIow4GCr/zI+rLgFw1z68xTn7E0tnzc F/8WiIBGFuX5bMo9BH4TTlHWVl3ueadqoBApneHoleYrlOPeOSEVNsf1iuvGBafdUS8s CtFjCBkCpSfwJlRcQSkzboQAj3papLBpPHn9okVCrKwwLkqhx0qSLtq6q5VVOjaLxwIB UNPA==
Received: by 10.236.83.103 with SMTP id p67mr1666413yhe.78.1353001672987; Thu, 15 Nov 2012 09:47:52 -0800 (PST)
Received: from europa.local ([2001:13c7:7001:5128:68bb:4b3d:ecb6:a7be]) by mx.google.com with ESMTPS id u15sm14817718anq.14.2012.11.15.09.47.50 (version=SSLv3 cipher=OTHER); Thu, 15 Nov 2012 09:47:51 -0800 (PST)
Message-ID: <50A52AC3.9060205@gmail.com>
Date: Thu, 15 Nov 2012 15:47:47 -0200
From: "Carlos M. Martinez" <carlosm3011@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
References: <201211121745.qACHjiXS919660@shell01.TheWorld.com>	<50A13B43.7000309@dcrocker.net>	<72F0897C-D473-4F34-8D21-B9A60DDBBB09@tzi.org>	<50A3F814.1030509@dcrocker.net> <50A44418.2010707@gmail.com>	<50A44B7C.10103@gmail.com> <50A4599A.8080507@lacnic.net>	<50A45A6F.70900@gmail.com> <50A4640D.1060800@lacnic.net> <50A464E5.5050104@gmail.com> <50A4A3AF.1060704@gmail.com>
In-Reply-To: <50A4A3AF.1060704@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Nov 2012 17:47:54 -0000

Hello,

On 11/15/12 6:11 AM, Brian E Carpenter wrote:
> On 15/11/2012 03:43, Melinda Shore wrote:
> 
> We'd reached 50 attendees from China at IETF 63 before we even
> started seriously negotiating the Beijing meeting. It seems to
> me that the causality is mainly in the opposite direction:
> participation causes meetings, not meetings cause participation.
> 

Having a metric for considering having a meeting in a give region would
be really nice, so we can stop arguing over smoke. If 50 is a magic
number, well, we Latin America are not that far, I'm confident we'll be
there in a few meetings.

I do believe that regions wanting to have an IETF meeting should also
give back in terms of active participation, I agree with that.

> (IMHO, there is some value to the IETF in having one-off
> attendees who don't subsequently participate: they learn what
> the IETF is and hopefully tell others about it. This can't be a
> bad thing, but it's definitely secondary.)
Agreed.
> 
>    Brian
> 

From gih@apnic.net  Thu Nov 15 09:59:04 2012
Return-Path: <gih@apnic.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5CFE821F8959; Thu, 15 Nov 2012 09:59:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.048
X-Spam-Level: 
X-Spam-Status: No, score=-101.048 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, RDNS_NONE=0.1, 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 hzV+4wsCHDg0; Thu, 15 Nov 2012 09:59:03 -0800 (PST)
Received: from asmtp.apnic.net (asmtp.apnic.net [IPv6:2001:dc0:2001:11::199]) by ietfa.amsl.com (Postfix) with ESMTP id 2EC2F21F896E; Thu, 15 Nov 2012 09:58:54 -0800 (PST)
Received: from [192.168.48.32] (unknown [87.213.29.58]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by asmtp.apnic.net (Postfix) with ESMTP id 67B2EB68BC; Fri, 16 Nov 2012 03:58:49 +1000 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
From: Geoff Huston <gih@apnic.net>
In-Reply-To: <63359CE6-0009-45D1-B2AE-3F2B4384D5D4@gigix.net>
Date: Fri, 16 Nov 2012 04:58:44 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <B2919A9C-5333-46E8-84BE-A302B75B73DE@apnic.net>
References: <20121113144545.12836.71935.idtracker@ietfa.amsl.com> <6.2.5.6.2.20121114030352.0da0e888@resistor.net> <63359CE6-0009-45D1-B2AE-3F2B4384D5D4@gigix.net>
To: Luigi Iannone <ggx@gigix.net>
X-Mailer: Apple Mail (2.1499)
Cc: "ietf@ietf.org Mailing List" <ietf@ietf.org>, lisp@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Nov 2012 17:59:04 -0000

>> In Section 6:
>>=20
>> "It is suggested to IANA to temporarily avoid allocating any
>>  other address block the same /12 prefix the EID /16 prefix
>>  belongs to.  This is to accommodate future requests of EID
>>  space without fragmenting the EID addressing space."
>>=20
>> Shouldn't that be under IANA Considerations?
>=20
> Well, if we go along that road we should put the whole document in a =
single "IANA Considerations" Section. ;-)
>=20
> Actually the current IANA Considerations section states the same =
request but does not specify "/12".
> You are right that it should be clearly stated, to make the document =
coherent. Will fix. thanks
>=20

it would be very helpful for the document to clearly show the basis for =
the calculation of a /12. Why a /12 and not any other size? What are the =
underlying estimates here? Why do they lead to the conclusion of a /12?

I am uncomfortable with the rather vague nature of the justification =
being shown here, and I don't think that this document as it stands is =
ready for publication.=20

Geoff


From sander@steffann.nl  Thu Nov 15 09:59:57 2012
Return-Path: <sander@steffann.nl>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D037221F88A9; Thu, 15 Nov 2012 09:59:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.072
X-Spam-Level: *
X-Spam-Status: No, score=1.072 tagged_above=-999 required=5 tests=[AWL=0.096,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_EQ_IP_ADDR=1.119, RCVD_IN_PBL=0.905, RDNS_NONE=0.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 nuJjMLj5-Ykx; Thu, 15 Nov 2012 09:59:56 -0800 (PST)
Received: from mail.sintact.nl (mail.sintact.nl [IPv6:2001:4038:0:16::7]) by ietfa.amsl.com (Postfix) with ESMTP id B802C21F8991; Thu, 15 Nov 2012 09:59:51 -0800 (PST)
Received: from [172.20.10.3] (unknown [62.140.132.44]) by mail.sintact.nl (Postfix) with ESMTP id 1B451200C; Thu, 15 Nov 2012 18:59:45 +0100 (CET)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
From: Sander Steffann <sander@steffann.nl>
In-Reply-To: <6E5736BD68F770449C74FBAD975F807C94AA2C60@NYDC-EXCH01.vinci-consulting-corp.local>
Date: Thu, 15 Nov 2012 18:59:41 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <85D1FE26-4299-454C-AE81-684B08934232@steffann.nl>
References: <6E5736BD68F770449C74FBAD975F807C94AA2C60@NYDC-EXCH01.vinci-consulting-corp.local>
To: Paul Vinciguerra <pvinci@VinciConsulting.com>
X-Mailer: Apple Mail (2.1499)
Cc: "ietf@ietf.org" <ietf@ietf.org>, "lisp@ietf.org" <lisp@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Nov 2012 17:59:57 -0000

Hi,

> So there will be a pool of addresses that the RIR's can allocate out =
of for EIDs?  If that's the case, what is the additional value to an ISP =
who would conceivably have to pay the RIR for another block of V6 =
addresses specifically for use as EIDs, when most likely they are =
already paying for a block that can be used for either purpose?=20


Good point.

I am currently using my whole /32 allocation from RIPE NCC as EID space. =
I run multiple PxTRs in an BGP based anycast setup to route to/from the =
non-LISP internet. What would be the use of requesting another prefix? I =
would have to put it in the global routing table to route traffic for it =
(unless other people start running PITRs for the whole /12, but then we =
get the 3rd party relay dependencies we know so well from 6to4...)

(PS: my PxTRs do map-requests for anything in ::/0 using DDT, so =
everything in DDT is already sent to a locator if possible, and they =
forward traffic natively otherwise)

Met vriendelijke groet,
Sander Steffann




From melinda.shore@gmail.com  Thu Nov 15 10:00:54 2012
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 732D421F8A37 for <ietf@ietfa.amsl.com>; Thu, 15 Nov 2012 10:00:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.661
X-Spam-Level: 
X-Spam-Status: No, score=-3.661 tagged_above=-999 required=5 tests=[AWL=-0.062, 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 Al1APPIt0rol for <ietf@ietfa.amsl.com>; Thu, 15 Nov 2012 10:00:53 -0800 (PST)
Received: from mail-pa0-f44.google.com (mail-pa0-f44.google.com [209.85.220.44]) by ietfa.amsl.com (Postfix) with ESMTP id B114721F850B for <ietf@ietf.org>; Thu, 15 Nov 2012 10:00:53 -0800 (PST)
Received: by mail-pa0-f44.google.com with SMTP id fb11so1262122pad.31 for <ietf@ietf.org>; Thu, 15 Nov 2012 10:00:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=Tr5ZzRWFEFdXfdfOelOVKSz8Ou3HSriNbAQCfK1Tb2A=; b=Di4+ALok7lVuE+d8niQd/qcuVFHawVd18UEeWrOYQrihewPl4a7KqLq3ZBmwBjFZkO 0tlPs3Cv9Ash9i4mu8y2dVl7eYFSuT3yuEP1JOjDnlEJ61dTHoADt9FmVjX6wGSlRRQQ gdNS2YHpEN8yOFiRs7OM0IJi2UepyTs+WtD0FSSCUatOM0PeUcZ0KqKHJPoxjG0mMYBV y7VqWAC3MRPU2AzDjo8VMxdy1BT8GNQOMoU2XJ/QgzDapoj7QMoFAvzDQPwalDPOlaOG 2zwEOHzeBzb0jGZEWK8GLnt3jjAvZojBudDvz5wu4DOyp6xElRaRVljPh3CrCAXUMcqO lWqA==
Received: by 10.66.79.167 with SMTP id k7mr5449649pax.24.1353002453467; Thu, 15 Nov 2012 10:00:53 -0800 (PST)
Received: from spandex.local (216-67-46-210-rb1.fai.dsl.dynamic.acsalaska.net. [216.67.46.210]) by mx.google.com with ESMTPS id gu5sm9842101pbc.10.2012.11.15.10.00.51 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 15 Nov 2012 10:00:52 -0800 (PST)
Message-ID: <50A52DD2.1030706@gmail.com>
Date: Thu, 15 Nov 2012 09:00:50 -0900
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: "Carlos M. Martinez" <carlosm3011@gmail.com>
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
References: <201211121745.qACHjiXS919660@shell01.TheWorld.com>	<50A13B43.7000309@dcrocker.net>	<72F0897C-D473-4F34-8D21-B9A60DDBBB09@tzi.org>	<50A3F814.1030509@dcrocker.net> <50A44418.2010707@gmail.com>	<50A44B7C.10103@gmail.com> <50A4599A.8080507@lacnic.net>	<50A45A6F.70900@gmail.com> <50A4640D.1060800@lacnic.net> <50A464E5.5050104@gmail.com> <50A4A3AF.1060704@gmail.com> <50A52AC3.9060205@gmail.com>
In-Reply-To: <50A52AC3.9060205@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Nov 2012 18:00:54 -0000

On 11/15/12 8:47 AM, Carlos M. Martinez wrote:
> I do believe that regions wanting to have an IETF meeting should also
> give back in terms of active participation, I agree with that.

I really think there's an enormous disconnect here.  I'm really unclear
on how this is supposed to work: if someone thinks they need to attend
a meeting in order to participate in the work and there's only one
meeting in their region in some large number of years, it's difficult
to see how that one meeting is going to lead to active participation.
Arguing that IETF openness is a function of meeting location is
totally missing the point.  Clearly we could be making that point
better, but it seems to me that privileging meetings as a more
important part of the process of producing documents very clearly works
against an open participation model.

The main benefit, it seems to me, is not geographic but that we
are woefully short on participation by operators and that many of the
folk in developing or less affluent countries work for operators,
registrars, regulators, etc., and we may benefit from one-off
participation from them.

Melinda


From aservin@lacnic.net  Thu Nov 15 10:14:07 2012
Return-Path: <aservin@lacnic.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 11C0921F88A9; Thu, 15 Nov 2012 10:14:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.434
X-Spam-Level: 
X-Spam-Status: No, score=-2.434 tagged_above=-999 required=5 tests=[AWL=0.166,  BAYES_00=-2.599, NO_RELAYS=-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 WY-r4PdfO3ql; Thu, 15 Nov 2012 10:14:06 -0800 (PST)
Received: from mail.lacnic.net.uy (mail.lacnic.net.uy [IPv6:2001:13c7:7001:4000::3]) by ietfa.amsl.com (Postfix) with ESMTP id 6E63821F888E; Thu, 15 Nov 2012 10:14:06 -0800 (PST)
Received: from 85-7-200.lacnic.net.uy (unknown [IPv6:2001:13c7:7001:5128:39f7:daf:f8fc:e39d]) by mail.lacnic.net.uy (Postfix) with ESMTP id 26C5530841C; Thu, 15 Nov 2012 16:14:01 -0200 (UYST)
Message-ID: <50A530E7.8@lacnic.net>
Date: Thu, 15 Nov 2012 16:13:59 -0200
From: Arturo Servin <aservin@lacnic.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: lisp@ietf.org
Subject: Re: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
References: <20121113144545.12836.71935.idtracker@ietfa.amsl.com> <CAKFn1SFy2+hXJLVtEpkdXfNuXA31ybmYnBFFPXj-73kb3tD+yw@mail.gmail.com> <5FCB8A98-4984-427C-9468-1DFDEBD206FD@steffann.nl> <87676878-B077-4B4C-96DC-9F755F78018A@gigix.net>
In-Reply-To: <87676878-B077-4B4C-96DC-9F755F78018A@gigix.net>
X-Enigmail-Version: 1.4.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-LACNIC.uy-MailScanner-Information: Please contact the ISP for more information
X-LACNIC.uy-MailScanner: Found to be clean
X-LACNIC.uy-MailScanner-SpamCheck: 
X-LACNIC.uy-MailScanner-From: aservin@lacnic.net
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Nov 2012 18:14:07 -0000

Luigi,

On 15/11/2012 12:33, Luigi Iannone wrote:
> 
> On 15 Nov. 2012, at 10:43 , Sander Steffann <sander@steffann.nl> wrote:
> 
>> Hi,
>>
>>> I have to ask, who can request an netblock from this address space and
>>> from where?
>>> I might be blind but I couldn't find it mentioned anywhere.
>>
>> Good question. Will there be a central registry, or will parts of the space be delegated to i.e. LISP based ISPs?
>>
> 
> Hi Sander,
> 
> no central registry has been ever discussed, was more about delegated the space to LISP ISPs.


	How are you going to allocate space to ISPs?

	Who is going to track the allocations made to ISPs, how are they going
to be published, what are the requirements to ask for space, what data
needs to be registered, where I can see allocations data?

	You asked George why the document is not ready to be published. Well,
the undocumented rules on how the space is going to be managed is one
important reason IMHO.

Regards,
as
	

> 
> Luigi
> 
> 
>> - Sander
>>
>> _______________________________________________
>> lisp mailing list
>> lisp@ietf.org
>> https://www.ietf.org/mailman/listinfo/lisp
> 
> _______________________________________________
> lisp mailing list
> lisp@ietf.org
> https://www.ietf.org/mailman/listinfo/lisp
> 

From aservin@lacnic.net  Thu Nov 15 10:47:23 2012
Return-Path: <aservin@lacnic.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7019521F871F; Thu, 15 Nov 2012 10:47:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.457
X-Spam-Level: 
X-Spam-Status: No, score=-2.457 tagged_above=-999 required=5 tests=[AWL=0.143,  BAYES_00=-2.599, NO_RELAYS=-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 XdVmrGmnGxzI; Thu, 15 Nov 2012 10:47:23 -0800 (PST)
Received: from mail.lacnic.net.uy (mail.lacnic.net.uy [IPv6:2001:13c7:7001:4000::3]) by ietfa.amsl.com (Postfix) with ESMTP id 76A0F21F869B; Thu, 15 Nov 2012 10:47:22 -0800 (PST)
Received: from 85-7-200.lacnic.net.uy (unknown [IPv6:2001:13c7:7001:5128:39f7:daf:f8fc:e39d]) by mail.lacnic.net.uy (Postfix) with ESMTP id 50EAB308436; Thu, 15 Nov 2012 16:47:22 -0200 (UYST)
Message-ID: <50A538B8.7080709@lacnic.net>
Date: Thu, 15 Nov 2012 16:47:20 -0200
From: Arturo Servin <aservin@lacnic.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: Dino Farinacci <farinacci@gmail.com>
Subject: Re: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
References: <20121113144545.12836.71935.idtracker@ietfa.amsl.com> <CAKFn1SFy2+hXJLVtEpkdXfNuXA31ybmYnBFFPXj-73kb3tD+yw@mail.gmail.com> <5FCB8A98-4984-427C-9468-1DFDEBD206FD@steffann.nl> <87676878-B077-4B4C-96DC-9F755F78018A@gigix.net> <50A530E7.8@lacnic.net> <B8132154-7260-43B4-B10D-E5B95924A15D@gmail.com>
In-Reply-To: <B8132154-7260-43B4-B10D-E5B95924A15D@gmail.com>
X-Enigmail-Version: 1.4.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-LACNIC.uy-MailScanner-Information: Please contact the ISP for more information
X-LACNIC.uy-MailScanner: Found to be clean
X-LACNIC.uy-MailScanner-SpamCheck: 
X-LACNIC.uy-MailScanner-From: aservin@lacnic.net
Cc: lisp@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Nov 2012 18:47:23 -0000

Dino,

	But who are the registries? The RIRs? Large ISPs? IANA? I think you
should specify clearly either: what a registry is or that is not defined
yet.

	Point taken on "This draft is purely a draft to REQUEST space. There
will need to be a deployment guide on how to allocate EIDs, in general."
But then it should be written somewhere in the document.

	Although it could be enough only to clearly say that a deployment guide
would define allocation guides in the future; for the sake of clarity
and usefulness (now, after the space is allocated by IANA it will be
there left unused because there is not a clearly indication how is going
to be used) I would recommend to discuss how the space is going to be
allocated.

Regards
as

	
On 15/11/2012 16:25, Dino Farinacci wrote:
>> Luigi,
>>
>> On 15/11/2012 12:33, Luigi Iannone wrote:
>>>
>>> On 15 Nov. 2012, at 10:43 , Sander Steffann <sander@steffann.nl> wrote:
>>>
>>>> Hi,
>>>>
>>>>> I have to ask, who can request an netblock from this address space and
>>>>> from where?
>>>>> I might be blind but I couldn't find it mentioned anywhere.
>>>>
>>>> Good question. Will there be a central registry, or will parts of the space be delegated to i.e. LISP based ISPs?
>>>>
>>>
>>> Hi Sander,
>>>
>>> no central registry has been ever discussed, was more about delegated the space to LISP ISPs.
>>
>>
>> 	How are you going to allocate space to ISPs?
> 
> This is PI space. The registries will take portions of this space to allocate to end devices.  This is endpoint ID space. ISPs will continue to allocate addresses for LISP RLOCs. And they will have to allocate orders of magnitude less address space now.
> 
>> 	Who is going to track the allocations made to ISPs, how are they going
>> to be published, what are the requirements to ask for space, what data
>> needs to be registered, where I can see allocations data?
> 
> Registries will track allocations to end sites.
> 
>> 	You asked George why the document is not ready to be published. Well,
>> the undocumented rules on how the space is going to be managed is one
>> important reason IMHO.
> 
> This draft is purely a draft to REQUEST space. There will need to be a deployment guide on how to allocate EIDs, in general.
> 
> Dino
> 
>>
>> Regards,
>> as
>> 	
>>
>>>
>>> Luigi
>>>
>>>
>>>> - Sander
>>>>
>>>> _______________________________________________
>>>> lisp mailing list
>>>> lisp@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/lisp
>>>
>>> _______________________________________________
>>> lisp mailing list
>>> lisp@ietf.org
>>> https://www.ietf.org/mailman/listinfo/lisp
>>>
>> _______________________________________________
>> lisp mailing list
>> lisp@ietf.org
>> https://www.ietf.org/mailman/listinfo/lisp

From carlosm3011@gmail.com  Thu Nov 15 10:54:34 2012
Return-Path: <carlosm3011@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 333B921F8481 for <ietf@ietfa.amsl.com>; Thu, 15 Nov 2012 10:54:34 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X8rZoD1q9e1D for <ietf@ietfa.amsl.com>; Thu, 15 Nov 2012 10:54:33 -0800 (PST)
Received: from mail-gg0-f172.google.com (mail-gg0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 88A8F21F84F6 for <ietf@ietf.org>; Thu, 15 Nov 2012 10:54:33 -0800 (PST)
Received: by mail-gg0-f172.google.com with SMTP id i4so392656ggn.31 for <ietf@ietf.org>; Thu, 15 Nov 2012 10:54:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=xtuGeNapGkD7kGvSvntbEDBtxgSFYT1sNH6ZQ/a5LLg=; b=EUxOB/zF3SHIIiH0kaaf5eOXVdnvck/IlU0+h46kSEuq15z8sCnKxON3O/GoCm/djP iSUpXueMIdt52ypCw1Ayxz8ofJzCxGGSc/WWGuLVIzxXE8jEqCR7at7aXHT+qzmgmh5p Y3wGqbvgqxT+7+EdNm5fE/80JVOtUOH3CExRJK+TLEK+9hOYLX5OyPbWlgK9EcPtiT8t dXjk1bK3zld36P+V1nDaN6HEt3+nICa9++sUF8jZNPvsnTY6URjPTA0RcqKgKgn0NsRL QQ4HJy5GXegnL+ElmOn8STYHx6Tr9NEJ4R/83lyXO6pfPKB6tc3Kf7Ubp+Z9ujRu7GRi QfNg==
Received: by 10.236.131.138 with SMTP id m10mr1887352yhi.101.1353005673029; Thu, 15 Nov 2012 10:54:33 -0800 (PST)
Received: from europa.local ([200.7.85.162]) by mx.google.com with ESMTPS id z1sm14968487anj.2.2012.11.15.10.54.30 (version=SSLv3 cipher=OTHER); Thu, 15 Nov 2012 10:54:31 -0800 (PST)
Message-ID: <50A53A64.7030807@gmail.com>
Date: Thu, 15 Nov 2012 16:54:28 -0200
From: "Carlos M. Martinez" <carlosm3011@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: Melinda Shore <melinda.shore@gmail.com>
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
References: <201211121745.qACHjiXS919660@shell01.TheWorld.com>	<50A13B43.7000309@dcrocker.net>	<72F0897C-D473-4F34-8D21-B9A60DDBBB09@tzi.org>	<50A3F814.1030509@dcrocker.net> <50A44418.2010707@gmail.com>	<50A44B7C.10103@gmail.com> <50A4599A.8080507@lacnic.net>	<50A45A6F.70900@gmail.com> <50A4640D.1060800@lacnic.net> <50A464E5.5050104@gmail.com> <50A4A3AF.1060704@gmail.com> <50A52AC3.9060205@gmail.com> <50A52DD2.1030706@gmail.com>
In-Reply-To: <50A52DD2.1030706@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Nov 2012 18:54:34 -0000

Note that I didn't say 'give back in terms of attendees' , I wrote 'give
back in terms of participation', in my mind, participation *can* be
remote, although as I mentioned in an earlier email the IETF needs to
improve remote access facilities a lot.

However, the perception of almost everyone I've spoken with is that if
you really want to push a document (not being a reviewer, not being a
3rd or 4th co-author), you need to be there in person. I'm sure I will
be pointed to exceptions to this rule, but that seems to be the general
perception.

regards,

Carlos

On 11/15/12 4:00 PM, Melinda Shore wrote:
> On 11/15/12 8:47 AM, Carlos M. Martinez wrote:
>> I do believe that regions wanting to have an IETF meeting should also
>> give back in terms of active participation, I agree with that.
> 
> I really think there's an enormous disconnect here.  I'm really unclear
> on how this is supposed to work: if someone thinks they need to attend
> a meeting in order to participate in the work and there's only one
> meeting in their region in some large number of years, it's difficult
> to see how that one meeting is going to lead to active participation.
> Arguing that IETF openness is a function of meeting location is
> totally missing the point.  Clearly we could be making that point
> better, but it seems to me that privileging meetings as a more
> important part of the process of producing documents very clearly works
> against an open participation model.
> 
> The main benefit, it seems to me, is not geographic but that we
> are woefully short on participation by operators and that many of the
> folk in developing or less affluent countries work for operators,
> registrars, regulators, etc., and we may benefit from one-off
> participation from them.
> 
> Melinda
> 

From dhc@dcrocker.net  Thu Nov 15 11:19:54 2012
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AAF3421F8623 for <ietf@ietfa.amsl.com>; Thu, 15 Nov 2012 11:19:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.04
X-Spam-Level: 
X-Spam-Status: No, score=-5.04 tagged_above=-999 required=5 tests=[AWL=-0.084,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, RCVD_IN_NJABL_PROXY=1.643]
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 pcUEQJQYouLq for <ietf@ietfa.amsl.com>; Thu, 15 Nov 2012 11:19:54 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 1A3DE21F85E3 for <ietf@ietf.org>; Thu, 15 Nov 2012 11:19:54 -0800 (PST)
Received: from [192.168.1.6] (adsl-67-127-56-94.dsl.pltn13.pacbell.net [67.127.56.94]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id qAFJJkkE005404 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 15 Nov 2012 11:19:46 -0800
Message-ID: <50A54044.10305@dcrocker.net>
Date: Thu, 15 Nov 2012 11:19:32 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: "Carlos M. Martinez" <carlosm3011@gmail.com>
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
References: <20121115050813.4158.qmail@joyce.lan> <103721F2-BA44-4EA5-BA9D-A7941EA4D5ED@frobbit.se> <alpine.BSF.2.00.1211151215100.30183@joyce.lan> <50A529D2.5050808@gmail.com>
In-Reply-To: <50A529D2.5050808@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Thu, 15 Nov 2012 11:19:47 -0800 (PST)
Cc: ietf@ietf.org, =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Nov 2012 19:19:54 -0000

On 11/15/2012 9:43 AM, Carlos M. Martinez wrote:
> Comparing with the ITU who does tour the world, organizing workshops in
> far away places, I really think we should be trying a little harder to
> be more open.


It's important to distinguish between a 'workshop' and a 'working 
meeting' where decisions are made.

As I understand the ITU's operation, all of the ITU-T formal decisions 
are made in Geneva.  Any meetings held before that and seeming to make 
decisions can be reversed during a Geneva session, in my direct experience.

Also, ISOC actually seems to do a pretty good job of showing up in many 
places around the world, on the IETF's behalf, including events that can 
be called workshops.

d/
-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From sander@steffann.nl  Thu Nov 15 11:51:35 2012
Return-Path: <sander@steffann.nl>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6DF7C21F846C; Thu, 15 Nov 2012 11:51:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.504
X-Spam-Level: 
X-Spam-Status: No, score=-0.504 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545]
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 glExuFD0TICg; Thu, 15 Nov 2012 11:51:34 -0800 (PST)
Received: from mail.sintact.nl (mail.sintact.nl [IPv6:2001:4038:0:16::7]) by ietfa.amsl.com (Postfix) with ESMTP id A81B221F8417; Thu, 15 Nov 2012 11:51:32 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.sintact.nl (Postfix) with ESMTP id B80F02012; Thu, 15 Nov 2012 20:51:31 +0100 (CET)
X-Virus-Scanned: amavisd-new at mail.sintact.nl
Received: from mail.sintact.nl ([127.0.0.1]) by localhost (mail.sintact.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q7OLOxWt2GNc; Thu, 15 Nov 2012 20:51:31 +0100 (CET)
Received: from macpro.10ww.steffann.nl (macpro.10ww.steffann.nl [37.77.56.75]) by mail.sintact.nl (Postfix) with ESMTP id 0717D200C; Thu, 15 Nov 2012 20:51:30 +0100 (CET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
From: Sander Steffann <sander@steffann.nl>
In-Reply-To: <B8132154-7260-43B4-B10D-E5B95924A15D@gmail.com>
Date: Thu, 15 Nov 2012 20:51:30 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <00C0245E-59D7-4552-8BB4-1C0099513D1D@steffann.nl>
References: <20121113144545.12836.71935.idtracker@ietfa.amsl.com> <CAKFn1SFy2+hXJLVtEpkdXfNuXA31ybmYnBFFPXj-73kb3tD+yw@mail.gmail.com> <5FCB8A98-4984-427C-9468-1DFDEBD206FD@steffann.nl> <87676878-B077-4B4C-96DC-9F755F78018A@gigix.net> <50A530E7.8@lacnic.net> <B8132154-7260-43B4-B10D-E5B95924A15D@gmail.com>
To: Dino Farinacci <farinacci@gmail.com>
X-Mailer: Apple Mail (2.1499)
Cc: ietf@ietf.org, lisp@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Nov 2012 19:51:35 -0000

Hi,

>> How are you going to allocate space to ISPs?
>=20
> This is PI space. The registries will take portions of this space to =
allocate to end devices.

Are you thinking about the existing RIRs here? If so: it might be a good =
idea to notify them that this is coming.

> This draft is purely a draft to REQUEST space. There will need to be a =
deployment guide on how to allocate EIDs, in general.

And if the RIR system is used every RIR will develop its own policy for =
allocating EIDs independently (hopefully based on the recommendations in =
such a deployment guide). It will have to be very clear whose =
responsibility it is to allocate from this space, and when assigning =
responsibility it might be a good idea to make sure they accept that =
responsibility too.

Note that I am not opposing the idea. I'm just trying to make sure this =
address space doesn't disappear into a black hole because nobody takes =
the responsibility to manage it.

One thing we have to be very careful with here is that EIDs are not =
directly allocated/assigned to end sites from this block. That will =
cause everyone to independently find (different) PITRs for their space, =
which will make a mess of the global IPv6 routing table...

Thanks,
Sander


From tony@att.com  Thu Nov 15 11:59:42 2012
Return-Path: <tony@att.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 291D421F8319 for <ietf@ietfa.amsl.com>; Thu, 15 Nov 2012 11:59:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[AWL=0.001, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 d5miAJcA8cwL for <ietf@ietfa.amsl.com>; Thu, 15 Nov 2012 11:59:41 -0800 (PST)
Received: from nbfkord-smmo06.seg.att.com (nbfkord-smmo06.seg.att.com [209.65.160.94]) by ietfa.amsl.com (Postfix) with ESMTP id 9431F21F8A00 for <ietf@ietf.org>; Thu, 15 Nov 2012 11:59:40 -0800 (PST)
Received: from unknown [144.160.128.153] (EHLO flpi408.enaf.ffdc.sbc.com) by nbfkord-smmo06.seg.att.com(mxl_mta-6.11.0-12) over TLS secured channel with ESMTP id ca945a05.0.1629896.00-351.4507961.nbfkord-smmo06.seg.att.com (envelope-from <tony@att.com>);  Thu, 15 Nov 2012 19:59:40 +0000 (UTC)
X-MXL-Hash: 50a549ac540f64d1-d420a7b5a4efc314fcb65cd50d52374f5e504e8e
Received: from enaf.ffdc.sbc.com (localhost.localdomain [127.0.0.1]) by flpi408.enaf.ffdc.sbc.com (8.14.5/8.14.5) with ESMTP id qAFJxdPD023119 for <ietf@ietf.org>; Thu, 15 Nov 2012 11:59:39 -0800
Received: from fflint03.pst.cso.att.com (fflint03.pst.cso.att.com [150.234.39.63]) by flpi408.enaf.ffdc.sbc.com (8.14.5/8.14.5) with ESMTP id qAFJxVcb022950 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 15 Nov 2012 11:59:36 -0800
Received: from alpd052.aldc.att.com (alpd052.aldc.att.com [130.8.42.31]) by fflint03.pst.cso.att.com (RSA Interceptor) for <ietf@ietf.org>; Thu, 15 Nov 2012 11:59:22 -0800
Received: from aldc.att.com (localhost.localdomain [127.0.0.1]) by alpd052.aldc.att.com (8.14.4/8.14.4) with ESMTP id qAFJxLnc032040 for <ietf@ietf.org>; Thu, 15 Nov 2012 14:59:21 -0500
Received: from mailgw1.maillennium.att.com (maillennium.att.com [135.25.114.99]) by alpd052.aldc.att.com (8.14.4/8.14.4) with ESMTP id qAFJxF30031933 for <ietf@ietf.org>; Thu, 15 Nov 2012 14:59:16 -0500
Received: from [135.70.92.3] (vpn-135-70-92-3.vpn.swst.att.com[135.70.92.3]) by maillennium.att.com (mailgw1) with ESMTP id <20121115195921gw100632doe> (Authid: tony); Thu, 15 Nov 2012 19:59:30 +0000
X-Originating-IP: [135.70.92.3]
Message-ID: <50A54987.7020201@att.com>
Date: Thu, 15 Nov 2012 14:59:03 -0500
From: Tony Hansen <tony@att.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
References: <201211121745.qACHjiXS919660@shell01.TheWorld.com>	<50A13B43.7000309@dcrocker.net>	<72F0897C-D473-4F34-8D21-B9A60DDBBB09@tzi.org>	<50A3F814.1030509@dcrocker.net><50A44418.2010707@gmail.com>	<50A44B7C.10103@gmail.com><50A4599A.8080507@lacnic.net>	<50A45A6F.70900@gmail.com><50A4640D.1060800@lacnic.net> <50A464E5.5050104@gmail.com> <50A4A3AF.1060704@gmail.com> <003901cdc316$0d19bda0$4001a8c0@gateway.2wire.net>
In-Reply-To: <003901cdc316$0d19bda0$4001a8c0@gateway.2wire.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2010122901)]
X-MAIL-FROM: <tony@att.com>
X-SOURCE-IP: [144.160.128.153]
X-AnalysisOut: [v=2.0 cv=VI9qaazX c=1 sm=0 a=xwOvzTHDVLE4u4nGvK72ag==:17 a]
X-AnalysisOut: [=lYdQ7UQbJqUA:10 a=1I5aD5_xVbAA:10 a=nQfKJAFVzxkA:10 a=ofM]
X-AnalysisOut: [gfj31e3cA:10 a=BLceEmwcHowA:10 a=IkcTkHD0fZMA:10 a=zQP7CpK]
X-AnalysisOut: [OAAAA:8 a=7m9OY8SF6psA:10 a=Pe5QkJmDmkHQ76QkWmkA:9 a=QEXdD]
X-AnalysisOut: [O2ut3YA:10]
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Nov 2012 19:59:42 -0000

On 11/15/2012 4:45 AM, t.p. wrote:
> I started, some years ago, with a meeting, because the culture that I
> was used to was that conferences, be they annual or triannual, were
> where things really happened and that e-mail filled in the gaps in
> between (and I think that this remains the case in other, related,
> fora).  That attendance showed me that most of the IETF meeting was a
> waste of time, that it was e-mail that was the main vehicle for work,
> and I think that the IETF web site has it about right when it says
>
> "People interested in particular technical issues join the mailing list
> of a WG  and occasionally attend one or more of the three IETF meetings
> held every year."
> and
> "After participating by email for a while, it may be time to attend your
> first meeting."
>
> which is not exactly sellling the idea of attending meetings:-)  But as
> I say, I think that that is the nature of the IETF.

I've always felt that: between the meetings, four months worth of work 
gets done, and then during the meeting, another four months worth of 
work gets done.

I've found this to be true over and over.

     Tony Hansen

From sander@steffann.nl  Thu Nov 15 12:04:01 2012
Return-Path: <sander@steffann.nl>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CAC3921F842B; Thu, 15 Nov 2012 12:04:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.504
X-Spam-Level: 
X-Spam-Status: No, score=-0.504 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545]
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 2LXJ3PfSGdmd; Thu, 15 Nov 2012 12:04:01 -0800 (PST)
Received: from mail.sintact.nl (mail.sintact.nl [IPv6:2001:4038:0:16::7]) by ietfa.amsl.com (Postfix) with ESMTP id 1AF4B21F841D; Thu, 15 Nov 2012 12:04:01 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.sintact.nl (Postfix) with ESMTP id 70EA42012; Thu, 15 Nov 2012 21:04:00 +0100 (CET)
X-Virus-Scanned: amavisd-new at mail.sintact.nl
Received: from mail.sintact.nl ([127.0.0.1]) by localhost (mail.sintact.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IgHVGRECm+CO; Thu, 15 Nov 2012 21:03:59 +0100 (CET)
Received: from macpro.10ww.steffann.nl (macpro.10ww.steffann.nl [37.77.56.75]) by mail.sintact.nl (Postfix) with ESMTP id A603B200C; Thu, 15 Nov 2012 21:03:59 +0100 (CET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
From: Sander Steffann <sander@steffann.nl>
In-Reply-To: <D1AD4093-C3F7-4A35-8108-3E16639E5991@gmail.com>
Date: Thu, 15 Nov 2012 21:03:58 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <AB29213E-5381-4FCE-82ED-ABB9E473C83E@steffann.nl>
References: <20121113144545.12836.71935.idtracker@ietfa.amsl.com> <CAKFn1SFy2+hXJLVtEpkdXfNuXA31ybmYnBFFPXj-73kb3tD+yw@mail.gmail.com> <5FCB8A98-4984-427C-9468-1DFDEBD206FD@steffann.nl> <87676878-B077-4B4C-96DC-9F755F78018A@gigix.net> <50A530E7.8@lacnic.net> <B8132154-7260-43B4-B10D-E5B95924A15D@gmail.com> <50A538B8.7080709@lacnic.net> <D1AD4093-C3F7-4A35-8108-3E16639E5991@gmail.com>
To: Dino Farinacci <farinacci@gmail.com>
X-Mailer: Apple Mail (2.1499)
Cc: ietf@ietf.org, lisp@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Nov 2012 20:04:01 -0000

Hi Dino,

>> 	But who are the registries? The RIRs? Large ISPs? IANA? I think =
you
>> should specify clearly either: what a registry is or that is not =
defined
>> yet.
>=20
> Yes, nothing has to change in terms of who and how PI addresses are =
allocated.

Sorry, but if the RIRs are going to allocate from this space then that =
is not the IETFs decision to make. That responsibility lies with the =
policy-making community in the RIR's region. And in the RIPE region =
there is ongoing work to write a policy that removes the distinction =
between PA and PI for IPv6. So don't make any assumptions here.

Also: if they are handed out as PI addresses there is still the question =
of who is going to run the PxTRs for that space. No operator will route =
the whole /12 or /16 for free. Besides the cost, that would put us back =
to the 6to4 mess: being dependent on (possibly unknown) 3rd-party relays =
that you have no business relationship with. Assigning the addresses as =
PI would mean that every block has to be routed separately, which will =
fill up the routing table. PA would make aggregation possible but tie =
the end-user to one LISP-ISP, and that ISP might then just use their =
existing PA block anyway (without using up an extra BGP routing table =
slot).

I think it should be clear who is going to manage the address space =
before requesting it.
Sander


From petithug@acm.org  Thu Nov 15 12:34:31 2012
Return-Path: <petithug@acm.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 730E721F892B for <ietf@ietfa.amsl.com>; Thu, 15 Nov 2012 12:34:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.55
X-Spam-Level: 
X-Spam-Status: No, score=-102.55 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599, NO_RELAYS=-0.001, 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 DNa-h3gF++di for <ietf@ietfa.amsl.com>; Thu, 15 Nov 2012 12:34:30 -0800 (PST)
Received: from implementers.org (implementers.org [IPv6:2604:3400:dc1:41:216:3eff:fe5b:8240]) by ietfa.amsl.com (Postfix) with ESMTP id 01C1521F891B for <ietf@ietf.org>; Thu, 15 Nov 2012 12:34:29 -0800 (PST)
Received: from [IPv6:2601:9:4b80:32:4871:22be:d4c7:a88e] (unknown [IPv6:2601:9:4b80:32:4871:22be:d4c7:a88e]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client CN "Marc Petit-Huguenin", Issuer "implementers.org" (verified OK)) by implementers.org (Postfix) with ESMTPS id 0CCBF20550; Thu, 15 Nov 2012 20:34:27 +0000 (UTC)
Message-ID: <50A551D3.1070005@acm.org>
Date: Thu, 15 Nov 2012 12:34:27 -0800
From: Marc Petit-Huguenin <petithug@acm.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.10) Gecko/20121027 Icedove/10.0.10
MIME-Version: 1.0
To: Tony Hansen <tony@att.com>
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
References: <201211121745.qACHjiXS919660@shell01.TheWorld.com>	<50A13B43.7000309@dcrocker.net>	<72F0897C-D473-4F34-8D21-B9A60DDBBB09@tzi.org>	<50A3F814.1030509@dcrocker.net><50A44418.2010707@gmail.com>	<50A44B7C.10103@gmail.com><50A4599A.8080507@lacnic.net>	<50A45A6F.70900@gmail.com><50A4640D.1060800@lacnic.net> <50A464E5.5050104@gmail.com> <50A4A3AF.1060704@gmail.com> <003901cdc316$0d19bda0$4001a8c0@gateway.2wire.net> <50A54987.7020201@att.com>
In-Reply-To: <50A54987.7020201@att.com>
X-Enigmail-Version: 1.4.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Nov 2012 20:34:31 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 11/15/2012 11:59 AM, Tony Hansen wrote:
> On 11/15/2012 4:45 AM, t.p. wrote:
>> I started, some years ago, with a meeting, because the culture that I was
>> used to was that conferences, be they annual or triannual, were where
>> things really happened and that e-mail filled in the gaps in between (and
>> I think that this remains the case in other, related, fora).  That
>> attendance showed me that most of the IETF meeting was a waste of time,
>> that it was e-mail that was the main vehicle for work, and I think that
>> the IETF web site has it about right when it says
>> 
>> "People interested in particular technical issues join the mailing list 
>> of a WG  and occasionally attend one or more of the three IETF meetings 
>> held every year." and "After participating by email for a while, it may
>> be time to attend your first meeting."
>> 
>> which is not exactly sellling the idea of attending meetings:-)  But as I
>> say, I think that that is the nature of the IETF.
> 
> I've always felt that: between the meetings, four months worth of work
> gets done, and then during the meeting, another four months worth of work
> gets done.
> 
> I've found this to be true over and over.

My experience is that during the meeting, 2 hours of work gets done (per WG),
and then between the meetings, another 2 hours of work gets done.

- -- 
Marc Petit-Huguenin
Email: marc@petit-huguenin.org
Blog: http://blog.marc.petit-huguenin.org
Profile: http://www.linkedin.com/in/petithug
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBCAAGBQJQpVHPAAoJECnERZXWan7EJn0QAIZuJ2PX3d0U1EWtKoxDlz3k
Y0eShE+G4rMa82xBJ4RHdNnyNymXdebcvQlFeH6ecep8nm1++r9KQ8kWeo/FEPRN
eK+q8jEMABy4IVSTIgOjMJcA4834FdCnW+oFaP8t8J0ufCMenoKkRfz2pDx6VFOh
7mHmfU4lfFuYNVbVRHinkSZqtklGwLwrIaJ/zpjQX5dTJRpMeakeSRKiurSzIK9u
Nd2P8TY5V2M332g5TreEZAQh2+bS1Wuhvx4FV69SnpPGMpFqsMzcbRVyQfkFuMJ7
+Ol4evJL5DNfPNZSX7EENvyxK+lXNkok2vA4TEa3eQvb5c2PfEYx4xE39l3Jj9+H
XBw4swRLIfWKyJ50E8w9alEJYa4tAL2eCSZuMpSXNp37XbGPZ2glpWQUNZXFRhgY
oXjzflI84rzGPCNzGyg70JEYz3GJ5SS9K5kF4dqmVu1+OS9vfJKNSkce0IhNbc+I
Tl+fK6LEXnzCresRwnOP28Mw9QzbHih7nC+d2iQHUI5jq2II254VBddrEaHRfSFm
tCtNWIgDXDxuB5losK91+9IkU0IbUOZXmOpb5vqlXJujEbcxgnceb5+5zhsD/6Mp
pSTwyzs8Bz7xUrli2UTsQSEbT4DC8bPon7uy4dyzCe+x2Z/D+4BJVHAtMI/TVdfY
N8qSqkqp2PrCXLgr2qU2
=/ibP
-----END PGP SIGNATURE-----

From sander@steffann.nl  Thu Nov 15 13:27:01 2012
Return-Path: <sander@steffann.nl>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4580E21F89AA; Thu, 15 Nov 2012 13:27:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.504
X-Spam-Level: 
X-Spam-Status: No, score=-0.504 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545]
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 Q3V12zv+fFhr; Thu, 15 Nov 2012 13:27:00 -0800 (PST)
Received: from mail.sintact.nl (mail.sintact.nl [IPv6:2001:4038:0:16::7]) by ietfa.amsl.com (Postfix) with ESMTP id B6CDA21F871F; Thu, 15 Nov 2012 13:27:00 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.sintact.nl (Postfix) with ESMTP id 291202012; Thu, 15 Nov 2012 22:27:00 +0100 (CET)
X-Virus-Scanned: amavisd-new at mail.sintact.nl
Received: from mail.sintact.nl ([127.0.0.1]) by localhost (mail.sintact.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id INREHQvYeA3s; Thu, 15 Nov 2012 22:26:55 +0100 (CET)
Received: from macpro.10ww.steffann.nl (macpro.10ww.steffann.nl [37.77.56.75]) by mail.sintact.nl (Postfix) with ESMTP id 5377D200C; Thu, 15 Nov 2012 22:26:52 +0100 (CET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
From: Sander Steffann <sander@steffann.nl>
In-Reply-To: <6E5736BD68F770449C74FBAD975F807C94AA4F0C@NYDC-EXCH01.vinci-consulting-corp.local>
Date: Thu, 15 Nov 2012 22:26:52 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <A0F47CBF-393D-4639-84E4-FC7240949CBD@steffann.nl>
References: <20121113144545.12836.71935.idtracker@ietfa.amsl.com> <CAKFn1SFy2+hXJLVtEpkdXfNuXA31ybmYnBFFPXj-73kb3tD+yw@mail.gmail.com> <5FCB8A98-4984-427C-9468-1DFDEBD206FD@steffann.nl> <87676878-B077-4B4C-96DC-9F755F78018A@gigix.net>	<50A530E7.8@lacnic.net> <B8132154-7260-43B4-B10D-E5B95924A15D@gmail.com> <00C0245E-59D7-4552-8BB4-1C0099513D1D@steffann.nl> <6E5736BD68F770449C74FBAD975F807C94AA4F0C@NYDC-EXCH01.vinci-consulting-corp.local>
To: Paul Vinciguerra <pvinci@VinciConsulting.com>
X-Mailer: Apple Mail (2.1499)
Cc: "ietf@ietf.org" <ietf@ietf.org>, Dino Farinacci <farinacci@gmail.com>, "lisp@ietf.org" <lisp@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Nov 2012 21:27:01 -0000

Hi,

>> One thing we have to be very careful with here is that EIDs are not =
directly
>> allocated/assigned to end sites from this block. That will cause =
everyone to
>> independently find (different) PITRs for their space, which will make =
a mess
>> of the global IPv6 routing table...
>>=20
>> Thanks,
>> Sander
>=20
> I don't think that (by definition) there is any way to cleanly =
aggregate PI space.  Legacy advertisements are going to be done by their =
LISP provider and will have to match the endpoint's PI allocations.

Yeah, so RIR policy-making communities might want to allow for LISP-PA =
space for example. I don't think we can make assumptions about that =
here. The other side of this is then: why not use 'normal' address =
space? If it is going to be announced in the legacy global BGP table =
anyway by some LISP provider I can't see why an end-site would choose =
for the LISP block instead of the more flexible regular block (which can =
then also be used as EID space)...

Thanks,
Sander


From sander@steffann.nl  Thu Nov 15 13:32:01 2012
Return-Path: <sander@steffann.nl>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF90A21F89B0; Thu, 15 Nov 2012 13:32:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.504
X-Spam-Level: 
X-Spam-Status: No, score=-0.504 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545]
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 kg0ATs1jelyB; Thu, 15 Nov 2012 13:32:01 -0800 (PST)
Received: from mail.sintact.nl (mail.sintact.nl [IPv6:2001:4038:0:16::7]) by ietfa.amsl.com (Postfix) with ESMTP id 361EC21F89AC; Thu, 15 Nov 2012 13:32:01 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.sintact.nl (Postfix) with ESMTP id 89ECA2012; Thu, 15 Nov 2012 22:32:00 +0100 (CET)
X-Virus-Scanned: amavisd-new at mail.sintact.nl
Received: from mail.sintact.nl ([127.0.0.1]) by localhost (mail.sintact.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ikWVaMxgEMks; Thu, 15 Nov 2012 22:31:59 +0100 (CET)
Received: from macpro.10ww.steffann.nl (macpro.10ww.steffann.nl [37.77.56.75]) by mail.sintact.nl (Postfix) with ESMTP id BE23B200C; Thu, 15 Nov 2012 22:31:59 +0100 (CET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
From: Sander Steffann <sander@steffann.nl>
In-Reply-To: <D470B9D8-977F-4E8B-8EDF-7769D5773279@gmail.com>
Date: Thu, 15 Nov 2012 22:31:59 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <0BC58149-A314-4AD3-80A5-DC8BF5DB0E2D@steffann.nl>
References: <20121113144545.12836.71935.idtracker@ietfa.amsl.com> <CAKFn1SFy2+hXJLVtEpkdXfNuXA31ybmYnBFFPXj-73kb3tD+yw@mail.gmail.com> <5FCB8A98-4984-427C-9468-1DFDEBD206FD@steffann.nl> <87676878-B077-4B4C-96DC-9F755F78018A@gigix.net> <50A530E7.8@lacnic.net> <B8132154-7260-43B4-B10D-E5B95924A15D@gmail.com> <00C0245E-59D7-4552-8BB4-1C0099513D1D@steffann.nl> <D470B9D8-977F-4E8B-8EDF-7769D5773279@gmail.com>
To: Dino Farinacci <farinacci@gmail.com>
X-Mailer: Apple Mail (2.1499)
Cc: ietf@ietf.org, lisp@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Nov 2012 21:32:02 -0000

Hi Dino,

> Nothing is coming. Nothing really needs to change.
>=20
> But if there is anything written up to define allocation procedures, =
the RIRs can review such a document.
>=20
> The main motivation for this prefix is to optimize ITRs so they know =
that a destination is in a LISP site. This COULD eliminate a mapping =
database lookup for a destination not in this range. Meaning, if a =
packet is destined to a non-EID, you may know this by inspecting the =
address rather than asking the mapping system.

I don't agree. For example: I'm using regular space for LISP EIDs now, =
so you can't assume that if it's not in this block that it's not in the =
mapping system...

>>> This draft is purely a draft to REQUEST space. There will need to be =
a deployment guide on how to allocate EIDs, in general.
>>=20
>> And if the RIR system is used every RIR will develop its own policy =
for allocating EIDs independently (hopefully based on the =
recommendations in such a deployment guide). It will have to be very =
clear whose responsibility it is to allocate from this space, and when =
assigning responsibility it might be a good idea to make sure they =
accept that responsibility too.
>=20
> Right.
>=20
>> Note that I am not opposing the idea. I'm just trying to make sure =
this address space doesn't disappear into a black hole because nobody =
takes the responsibility to manage it.
>>=20
>> One thing we have to be very careful with here is that EIDs are not =
directly allocated/assigned to end sites from this block. That will =
cause everyone to independently find (different) PITRs for their space,
>=20
> Why not?

Because the RIR communities will probably just refuse to allocate from =
this space if it means that all those routes end up in the BGP table... =
They are already plenty of people that don't like regular PI policies...

>> which will make a mess of the global IPv6 routing table...
>=20
> And why do you think you need to assign PITRs per sub-block?

I hope that is not necessary, but if addresses are assigned to end-sites =
directly in a PI-like way then who is going to provide PITR services for =
the users? Someone has to pay the bandwidth cost for operating a PITR... =
And the users of that space want reliability, so they are not going to =
rely on the goodwill of some unknown 3rd parties. There is too much bad =
experience with 2002::/16 for that.

If you see another way that I am missing please let me know! I want this =
to work, I just don't see how...
- Sander


From sander@steffann.nl  Thu Nov 15 13:34:36 2012
Return-Path: <sander@steffann.nl>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8DB8F21F89B0; Thu, 15 Nov 2012 13:34:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.504
X-Spam-Level: 
X-Spam-Status: No, score=-0.504 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545]
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 lG6RX4GLeHsB; Thu, 15 Nov 2012 13:34:36 -0800 (PST)
Received: from mail.sintact.nl (mail.sintact.nl [IPv6:2001:4038:0:16::7]) by ietfa.amsl.com (Postfix) with ESMTP id 1262421F89AA; Thu, 15 Nov 2012 13:34:36 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.sintact.nl (Postfix) with ESMTP id 6C4B52012; Thu, 15 Nov 2012 22:34:35 +0100 (CET)
X-Virus-Scanned: amavisd-new at mail.sintact.nl
Received: from mail.sintact.nl ([127.0.0.1]) by localhost (mail.sintact.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dHXh5z9TzBoe; Thu, 15 Nov 2012 22:34:35 +0100 (CET)
Received: from macpro.10ww.steffann.nl (macpro.10ww.steffann.nl [37.77.56.75]) by mail.sintact.nl (Postfix) with ESMTP id DCE77200C; Thu, 15 Nov 2012 22:34:34 +0100 (CET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
From: Sander Steffann <sander@steffann.nl>
In-Reply-To: <5958FE99-2975-490A-9F51-E56CFD9D384B@gmail.com>
Date: Thu, 15 Nov 2012 22:34:34 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <78C68165-E984-4974-B2D4-12A9A008A25E@steffann.nl>
References: <20121113144545.12836.71935.idtracker@ietfa.amsl.com> <CAKFn1SFy2+hXJLVtEpkdXfNuXA31ybmYnBFFPXj-73kb3tD+yw@mail.gmail.com> <5FCB8A98-4984-427C-9468-1DFDEBD206FD@steffann.nl> <87676878-B077-4B4C-96DC-9F755F78018A@gigix.net>	<50A530E7.8@lacnic.net> <B8132154-7260-43B4-B10D-E5B95924A15D@gmail.com> <00C0245E-59D7-4552-8BB4-1C0099513D1D@steffann.nl> <6E5736BD68F770449C74FBAD975F807C94AA4F0C@NYDC-EXCH01.vinci-consulting-corp.local> <5958FE99-2975-490A-9F51-E56CFD9D384B@gmail.com>
To: Dino Farinacci <farinacci@gmail.com>
X-Mailer: Apple Mail (2.1499)
Cc: "lisp@ietf.org" <lisp@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, Paul Vinciguerra <pvinci@VinciConsulting.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Nov 2012 21:34:36 -0000

Hi,

> And you do not want to tie addresses to topological entities. Or you =
will lose the mobility capabilities that Locator/ID separation can =
bring.

Well, it is a business model. I am providing exactly such a service to a =
few test users now. I now hand out EID space from my PA block. If =
someone wants to be provider independent I'll route their PI space for =
them as well. I'm just hoping that we can avoid any BGP routing table =
mess...

Sander


From sander@steffann.nl  Thu Nov 15 13:48:51 2012
Return-Path: <sander@steffann.nl>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B3C4A21F8A40; Thu, 15 Nov 2012 13:48:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.504
X-Spam-Level: 
X-Spam-Status: No, score=-0.504 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545]
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 oRNAywDRicEE; Thu, 15 Nov 2012 13:48:51 -0800 (PST)
Received: from mail.sintact.nl (mail.sintact.nl [IPv6:2001:4038:0:16::7]) by ietfa.amsl.com (Postfix) with ESMTP id E620321F8A3E; Thu, 15 Nov 2012 13:48:50 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.sintact.nl (Postfix) with ESMTP id 479FB2012; Thu, 15 Nov 2012 22:48:50 +0100 (CET)
X-Virus-Scanned: amavisd-new at mail.sintact.nl
Received: from mail.sintact.nl ([127.0.0.1]) by localhost (mail.sintact.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3Vuyvuo7-wcr; Thu, 15 Nov 2012 22:48:45 +0100 (CET)
Received: from macpro.10ww.steffann.nl (macpro.10ww.steffann.nl [37.77.56.75]) by mail.sintact.nl (Postfix) with ESMTP id 53248200C; Thu, 15 Nov 2012 22:48:43 +0100 (CET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
From: Sander Steffann <sander@steffann.nl>
In-Reply-To: <2007FD20-0EA4-4204-81A5-D9AE0201419D@gmail.com>
Date: Thu, 15 Nov 2012 22:48:42 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <D40BD502-1E3A-4AAA-A040-E2E4EE83141D@steffann.nl>
References: <20121113144545.12836.71935.idtracker@ietfa.amsl.com> <CAKFn1SFy2+hXJLVtEpkdXfNuXA31ybmYnBFFPXj-73kb3tD+yw@mail.gmail.com> <5FCB8A98-4984-427C-9468-1DFDEBD206FD@steffann.nl> <87676878-B077-4B4C-96DC-9F755F78018A@gigix.net> <50A530E7.8@lacnic.net> <B8132154-7260-43B4-B10D-E5B95924A15D@gmail.com> <00C0245E-59D7-4552-8BB4-1C0099513D1D@steffann.nl> <D470B9D8-977F-4E8B-8EDF-7769D5773279@gmail.com> <0BC58149-A314-4AD3-80A5-DC8BF5DB0E2D@steffann.nl> <2007FD20-0EA4-4204-81A5-D9AE0201419D@gmail.com>
To: Dino Farinacci <farinacci@gmail.com>
X-Mailer: Apple Mail (2.1499)
Cc: ietf@ietf.org, lisp@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Nov 2012 21:48:51 -0000

Hi,

>>> The main motivation for this prefix is to optimize ITRs so they know =
that a destination is in a LISP site. This COULD eliminate a mapping =
database lookup for a destination not in this range. Meaning, if a =
packet is destined to a non-EID, you may know this by inspecting the =
address rather than asking the mapping system.
>>=20
>> I don't agree. For example: I'm using regular space for LISP EIDs =
now, so you can't assume that if it's not in this block that it's not in =
the mapping system...
>=20
> That is why I capitalized "COULD".

Ok :-)

But I think it comes down to
  COULD ignore that certain EIDs are in the mapping system and always =
route them legacy-style

I wouldn't agree with
  COULD know if certain addresses are EIDs or not by looking at the =
prefix
because any address space can be used as EIDs now. Or are you proposing =
to deprecate the use of all other address space as EIDs?

>> Because the RIR communities will probably just refuse to allocate =
from this space if it means that all those routes end up in the BGP =
table... They are already plenty of people that don't like regular PI =
policies...
>=20
> You have all the PITRs in the world advertise only the one /12 into =
underlying routing.

ROFL. No sorry, that's not going to work
a) they would have to pay all the bandwidth cost for users of that EID =
space that they have no business relation with
b) as a user of that EID space I would be at the mercy of PITR operators =
that I don't even know
c) See all the arguments about why 6to4 is unreliable. They'll apply =
here too

>>>> which will make a mess of the global IPv6 routing table...
>>>=20
>>> And why do you think you need to assign PITRs per sub-block?
>>=20
>> I hope that is not necessary, but if addresses are assigned to =
end-sites directly in a PI-like way then who is going to provide PITR =
services for the users? Someone has to pay the bandwidth cost for =
operating=20
>=20
> PITR services are provide for non-LISP sources to send to these sites. =
If you have a well-known defined /12 that all PITRs advertise, then when =
you allocate sub-blocks, you don't have to change, reconfigure, or touch =
the 1000s of PITRs deployed.

What makes you think that all those PITRs will pay the cost for routing =
all that traffic?

>> a PITR... And the users of that space want reliability, so they are =
not going to rely on the goodwill of some unknown 3rd parties. There is =
too much bad experience with 2002::/16 for that.
>=20
> We do that all the time on the Internet unless you sent this email on =
a source-route to me. ;-)

No, sorry. I now pay my ISP to make sure my connectivity works. In your =
example I'm going to rely on some unknown PETR for outbound traffic and =
on whatever PITR is closest to the other side for my inbound traffic. I =
might be able to control the PETR, but not the PITR because that depends =
on the routing from the other side. We have been here before with =
2002::/16. Don't repeat that huge mistake!

- Sander


From arturo.servin@gmail.com  Thu Nov 15 13:51:45 2012
Return-Path: <arturo.servin@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 30BFB21F85FC for <ietf@ietfa.amsl.com>; Thu, 15 Nov 2012 13:51:45 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lBS40-mEKK6O for <ietf@ietfa.amsl.com>; Thu, 15 Nov 2012 13:51:44 -0800 (PST)
Received: from mail-gh0-f181.google.com (mail-gh0-f181.google.com [209.85.160.181]) by ietfa.amsl.com (Postfix) with ESMTP id A2E1421F8A51 for <ietf@ietf.org>; Thu, 15 Nov 2012 13:51:44 -0800 (PST)
Received: by mail-gh0-f181.google.com with SMTP id z22so512922ghb.26 for <ietf@ietf.org>; Thu, 15 Nov 2012 13:51:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=hRadi4B3XGUX5tiBaYjKMAkTkc9hJTzHvXVe1gpoj5E=; b=mC2X6418Gp3KsOyByEP8hE6UfYpCCoXKnH561yiVjc9gURdqVf61EOmxi4sYiHpAHi sIFaYoynC+Zj8FhHTNYSNJ3QM6nbbmCbYlwnzrtH+whEtm0nTSimw8q0BkqC/rv87NVf gswzRIpNEbRXG7akwrhaME5dF+edTujI71jyjz4QkyLHOkD+VHJqtzMGa68FLn+mIuvY 9IdU6VjJXoAYYZIqaowGTPU+/bDG4VrEvU27CQEu6C6N5lncThgdDjwOeKQiJaz4YjJR wDHJUZCAU4O0ytRzPeLQlvOr30Mp9OtP4kDNNhV5/NPoy3VhmayhQkgRWdIPNKb+NHVq ttRA==
Received: by 10.236.131.69 with SMTP id l45mr2406846yhi.46.1353016304167; Thu, 15 Nov 2012 13:51:44 -0800 (PST)
Received: from [192.168.1.133] (r186-48-250-100.dialup.adsl.anteldata.net.uy. [186.48.250.100]) by mx.google.com with ESMTPS id o66sm17010946yhi.19.2012.11.15.13.51.41 (version=SSLv3 cipher=OTHER); Thu, 15 Nov 2012 13:51:42 -0800 (PST)
Message-ID: <50A563EA.8010003@gmail.com>
Date: Thu, 15 Nov 2012 19:51:38 -0200
From: Arturo Servin <arturo.servin@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
References: <20121115050813.4158.qmail@joyce.lan> <103721F2-BA44-4EA5-BA9D-A7941EA4D5ED@frobbit.se> <alpine.BSF.2.00.1211151215100.30183@joyce.lan> <50A529D2.5050808@gmail.com> <50A54044.10305@dcrocker.net>
In-Reply-To: <50A54044.10305@dcrocker.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Nov 2012 21:51:45 -0000

	They are doing a great job, but I wouldn't said that all of that is on
IETF behalf. They are there because that is ISOC's mission, not to
represent us in the majority of their work.

	If we want representation, we need to do it ourselves. ISOC would
support us, I am sure, but we need to at least show up.

Regards
as



On 15/11/2012 17:19, Dave Crocker wrote:
> 
> Also, ISOC actually seems to do a pretty good job of showing up in many
> places around the world, on the IETF's behalf, including events that can
> be called workshops.

From carlosm3011@gmail.com  Thu Nov 15 13:53:27 2012
Return-Path: <carlosm3011@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1BE1C21F8C14 for <ietf@ietfa.amsl.com>; Thu, 15 Nov 2012 13:53:27 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oEbtMKK0Mcsn for <ietf@ietfa.amsl.com>; Thu, 15 Nov 2012 13:53:26 -0800 (PST)
Received: from mail-ye0-f172.google.com (mail-ye0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id 88EEA21F8BC2 for <ietf@ietf.org>; Thu, 15 Nov 2012 13:53:26 -0800 (PST)
Received: by mail-ye0-f172.google.com with SMTP id l13so437941yen.31 for <ietf@ietf.org>; Thu, 15 Nov 2012 13:53:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=amg5emJJg/QacIQdyf9xcSxljhy2ZcMXr5sIsZ9qH/M=; b=QVHeCVO5TEXdyp2LyczlHpGopfgkNOPG73+8OsW20lM3QjWLgyMxmjYfH3bb3OWrh0 67dzM8WHwkMngmbvy/EeS9SfIr/Wb7xe9xSCrGVlM92Vfeqm8ARGin6TiG/Mb1swofvv r6TngKTaT9gs/U4OjOL4Lpz5EX6hjdJAzqEKHaCrmT8vmWZL5XVAn8KKNOTQq/UclxK8 onrHn3ShfDad9iuo41uDfnOTnFeSqK/KES8xhBGKuqM5V4ybaLfGyiqHZsD0ybznCJ0A VgzW+gSfCWGoc2DCfRWHF0oudNpnAHDqWwwv17IqPyezFeyJEukE9mxh48WYCnSGxkN9 qjcQ==
Received: by 10.101.136.14 with SMTP id o14mr684769ann.22.1353016406065; Thu, 15 Nov 2012 13:53:26 -0800 (PST)
Received: from ?IPv6:2001:470:d815:fe0:357f:a121:9cbc:19c4? ([2001:470:d815:fe0:357f:a121:9cbc:19c4]) by mx.google.com with ESMTPS id m51sm17018290yhh.16.2012.11.15.13.53.23 (version=SSLv3 cipher=OTHER); Thu, 15 Nov 2012 13:53:25 -0800 (PST)
Message-ID: <50A56452.2040406@gmail.com>
Date: Thu, 15 Nov 2012 19:53:22 -0200
From: "Carlos M. Martinez" <carlosm3011@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: dcrocker@bbiw.net
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
References: <20121115050813.4158.qmail@joyce.lan> <103721F2-BA44-4EA5-BA9D-A7941EA4D5ED@frobbit.se> <alpine.BSF.2.00.1211151215100.30183@joyce.lan> <50A529D2.5050808@gmail.com> <50A54044.10305@dcrocker.net>
In-Reply-To: <50A54044.10305@dcrocker.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Cc: ietf@ietf.org, =?ISO-8859-1?Q?Patrik?= =?ISO-8859-1?Q?_F=E4ltstr=F6m?= <paf@frobbit.se>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Nov 2012 21:53:27 -0000

Hi,
On 11/15/2012 5:19 PM, Dave Crocker wrote:
>
> On 11/15/2012 9:43 AM, Carlos M. Martinez wrote:
>> Comparing with the ITU who does tour the world, organizing workshops in
>> far away places, I really think we should be trying a little harder to
>> be more open.
>
>
> It's important to distinguish between a 'workshop' and a 'working
> meeting' where decisions are made.
>
> As I understand the ITU's operation, all of the ITU-T formal decisions
> are made in Geneva.  Any meetings held before that and seeming to make
> decisions can be reversed during a Geneva session, in my direct
> experience.
>
> Also, ISOC actually seems to do a pretty good job of showing up in
> many places around the world, on the IETF's behalf, including events
> that can be called workshops.
>
I agree, but I´m talking about perceptions and how these things can be
manipulated against us. If we don´t care, that´s fine, but we shouldn´t
be surprised afterwards if something we do not like comes out of WCIT.


> d/


From ggm+ietf@apnic.net  Thu Nov 15 14:25:04 2012
Return-Path: <ggm+ietf@apnic.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B47FB21F8A3A; Thu, 15 Nov 2012 14:25:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.048
X-Spam-Level: 
X-Spam-Status: No, score=-1.048 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, RDNS_NONE=0.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 cP8B5a3K1KCx; Thu, 15 Nov 2012 14:25:04 -0800 (PST)
Received: from asmtp.apnic.net (asmtp.apnic.net [IPv6:2001:dc0:2001:11::199]) by ietfa.amsl.com (Postfix) with ESMTP id 3132D21F8A38; Thu, 15 Nov 2012 14:25:04 -0800 (PST)
Received: from [192.168.55.108] (unknown [87.213.29.58]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by asmtp.apnic.net (Postfix) with ESMTP id DC87BB684D; Fri, 16 Nov 2012 08:25:01 +1000 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
From: George Michaelson <ggm+ietf@apnic.net>
In-Reply-To: <8F781829-457B-4B32-B91A-46C22BC5D570@gmail.com>
Date: Thu, 15 Nov 2012 23:24:57 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <551B2C05-2E30-4B6F-8D35-8CA0482A8D82@apnic.net>
References: <20121113144545.12836.71935.idtracker@ietfa.amsl.com> <CAKFn1SFy2+hXJLVtEpkdXfNuXA31ybmYnBFFPXj-73kb3tD+yw@mail.gmail.com> <5FCB8A98-4984-427C-9468-1DFDEBD206FD@steffann.nl> <87676878-B077-4B4C-96DC-9F755F78018A@gigix.net> <50A530E7.8@lacnic.net> <B8132154-7260-43B4-B10D-E5B95924A15D@gmail.com> <00C0245E-59D7-4552-8BB4-1C0099513D1D@steffann.nl> <D470B9D8-977F-4E8B-8EDF-7769D5773279@gmail.com> <0BC58149-A314-4AD3-80A5-DC8BF5DB0E2D@steffann.nl> <2007FD20-0EA4-4204-81A5-D9AE0201419D@gmail.com> <D40BD502-1E3A-4AAA-A040-E2E4EE83141D@steffann.nl> <8F781829-457B-4B32-B91A-46C22BC5D570@gmail.com>
To: Dino Farinacci <farinacci@gmail.com>
X-Mailer: Apple Mail (2.1499)
Cc: "ietf@ietf.org list" <ietf@ietf.org>, lisp@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Nov 2012 22:25:04 -0000

Dino, to come back on topic. I understand the drafts purpose is to =
request a block of IPv6 address be delegated for this specific purpose, =
from IANA. The request is to the IAB. So, its a request for =
architectural aspects of addressing, facing an experiment.

a /12 is a very large amount of space. This demands rigour in the =
process to apply, even a reservation requires a sense of why, and =
justification. "we think its about right" isn't appropriate and the =
document needs more work to specify why a 16, and why a /12, and what =
the implications are of eg a smaller allocation under a /16 reservation, =
or some other size (a /32 even, for which there are both precedents, in =
experimental allocations, and an existing process inside the RIR address =
management framework).

Secondly, you appear to assume these allocations to EID can simply use =
current RIR practices. The problem is that you need to understand what =
needs-based and justification means in process terms: Hostmasters in the =
RIR system try very hard not to be placed in a position of making =
arbitrary subjective decisions: they have processes which are designed =
to ask for objective justifications to specify why an allocation should =
take place, and at what scale. Those objective criteria face addresses =
as addresses. not EID.

For an example: IPv6 address allocation process currently is implemented =
using sparse allocation (binary chop with some modifications) in the =
APNIC region. This maximises space around allocations to equalise the =
distribution of free blocks such that the commons, the unallocated =
space, remains as usefully large as possible and when the next binary =
stride is entered, there is some understanding its going to be applied =
in common to all occupants of that region of space (in terms of the size =
of hole around them, which is not a reservation per se, but provides for =
risk-management of future growth to the largest extent).

We're really quite proud of sparse: its extended the life of the /12 we =
occupy quite markedly. What impact will EID have on this? Is sparse an =
appropriate allocation engine to use for EID? What if eg you have =
expectations of almost-geographic aspects of address management in EID. =
Doesn't that require documentation as a process? And, you may be =
specifying a cost on the RIR system, to engineer support for the new =
allocation logic. If it doesn't logically fit in sparse allocation, we =
need to know. And we need to know why.

EID are not going to be used like 'normal' addresses. So, the normal =
justifications don't look entirely appropriate to me from 10,000ft. The =
document needs to say "maybe we need to understand the allocation =
processes that the RIR should objectively apply" or maybe you need to =
step outside of draft space and engage inside the RIR policy process and =
seek a global policy which can document the process.

To ask for an IANA allocation without having undertaken this process =
looks wrong to me. So, I stand by my concern the document isn't ready =
for IETF last call: it hasn't addressed substantive issues around the =
process and expectations of address/registry function, to manage the =
/16, and it hasn't documented the basis of asking for a /16 in the first =
place, or a /12 reservation.

cheers

-George=

From jmh@joelhalpern.com  Thu Nov 15 14:39:51 2012
Return-Path: <jmh@joelhalpern.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1664721F89F6; Thu, 15 Nov 2012 14:39:51 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 50uYF8zC9quK; Thu, 15 Nov 2012 14:39:50 -0800 (PST)
Received: from morbo.mail.tigertech.net (morbo.mail.tigertech.net [67.131.251.54]) by ietfa.amsl.com (Postfix) with ESMTP id 2487C21F896C; Thu, 15 Nov 2012 14:39:45 -0800 (PST)
Received: from mailc2.tigertech.net (mailc2.tigertech.net [208.80.4.156]) by morbo.tigertech.net (Postfix) with ESMTP id 0706D5593C0; Thu, 15 Nov 2012 14:39:44 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailc2.tigertech.net (Postfix) with ESMTP id 43BFD1BDB2E6; Thu, 15 Nov 2012 14:39:42 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at c2.tigertech.net
Received: from [10.10.10.104] (pool-71-161-50-174.clppva.btas.verizon.net [71.161.50.174]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailc2.tigertech.net (Postfix) with ESMTPSA id 527D71BDAD44; Thu, 15 Nov 2012 14:39:39 -0800 (PST)
Message-ID: <50A56F23.7020903@joelhalpern.com>
Date: Thu, 15 Nov 2012 17:39:31 -0500
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: George Michaelson <ggm+ietf@apnic.net>
Subject: Re: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
References: <20121113144545.12836.71935.idtracker@ietfa.amsl.com> <CAKFn1SFy2+hXJLVtEpkdXfNuXA31ybmYnBFFPXj-73kb3tD+yw@mail.gmail.com> <5FCB8A98-4984-427C-9468-1DFDEBD206FD@steffann.nl> <87676878-B077-4B4C-96DC-9F755F78018A@gigix.net> <50A530E7.8@lacnic.net> <B8132154-7260-43B4-B10D-E5B95924A15D@gmail.com> <00C0245E-59D7-4552-8BB4-1C0099513D1D@steffann.nl> <D470B9D8-977F-4E8B-8EDF-7769D5773279@gmail.com> <0BC58149-A314-4AD3-80A5-DC8BF5DB0E2D@steffann.nl> <2007FD20-0EA4-4204-81A5-D9AE0201419D@gmail.com> <D40BD502-1E3A-4AAA-A040-E2E4EE83141D@steffann.nl> <8F781829-457B-4B32-B91A-46C22BC5D570@gmail.com> <551B2C05-2E30-4B6F-8D35-8CA0482A8D82@apnic.net>
In-Reply-To: <551B2C05-2E30-4B6F-8D35-8CA0482A8D82@apnic.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "ietf@ietf.org list" <ietf@ietf.org>, Dino Farinacci <farinacci@gmail.com>, lisp@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Nov 2012 22:39:51 -0000

Whatever else is going on, LISP EIDs do not have geographic 
significance.  They do not have IP Routing topological significance. 
The are not aggregateable.

They are intended to beused by a site as a single prefix.  Hence, the 
desired behavior (within the /16) is exactly the same as that needed to 
respond to a PI request.

Yours,
Joel

On 11/15/2012 5:24 PM, George Michaelson wrote:
>
> Dino, to come back on topic. I understand the drafts purpose is to request a block of IPv6 address be delegated for this specific purpose, from IANA. The request is to the IAB. So, its a request for architectural aspects of addressing, facing an experiment.
>
> a /12 is a very large amount of space. This demands rigour in the process to apply, even a reservation requires a sense of why, and justification. "we think its about right" isn't appropriate and the document needs more work to specify why a 16, and why a /12, and what the implications are of eg a smaller allocation under a /16 reservation, or some other size (a /32 even, for which there are both precedents, in experimental allocations, and an existing process inside the RIR address management framework).
>
> Secondly, you appear to assume these allocations to EID can simply use current RIR practices. The problem is that you need to understand what needs-based and justification means in process terms: Hostmasters in the RIR system try very hard not to be placed in a position of making arbitrary subjective decisions: they have processes which are designed to ask for objective justifications to specify why an allocation should take place, and at what scale. Those objective criteria face addresses as addresses. not EID.
>
> For an example: IPv6 address allocation process currently is implemented using sparse allocation (binary chop with some modifications) in the APNIC region. This maximises space around allocations to equalise the distribution of free blocks such that the commons, the unallocated space, remains as usefully large as possible and when the next binary stride is entered, there is some understanding its going to be applied in common to all occupants of that region of space (in terms of the size of hole around them, which is not a reservation per se, but provides for risk-management of future growth to the largest extent).
>
> We're really quite proud of sparse: its extended the life of the /12 we occupy quite markedly. What impact will EID have on this? Is sparse an appropriate allocation engine to use for EID? What if eg you have expectations of almost-geographic aspects of address management in EID. Doesn't that require documentation as a process? And, you may be specifying a cost on the RIR system, to engineer support for the new allocation logic. If it doesn't logically fit in sparse allocation, we need to know. And we need to know why.
>
> EID are not going to be used like 'normal' addresses. So, the normal justifications don't look entirely appropriate to me from 10,000ft. The document needs to say "maybe we need to understand the allocation processes that the RIR should objectively apply" or maybe you need to step outside of draft space and engage inside the RIR policy process and seek a global policy which can document the process.
>
> To ask for an IANA allocation without having undertaken this process looks wrong to me. So, I stand by my concern the document isn't ready for IETF last call: it hasn't addressed substantive issues around the process and expectations of address/registry function, to manage the /16, and it hasn't documented the basis of asking for a /16 in the first place, or a /12 reservation.
>
> cheers
>
> -George
> _______________________________________________
> lisp mailing list
> lisp@ietf.org
> https://www.ietf.org/mailman/listinfo/lisp
>

From sander@steffann.nl  Thu Nov 15 14:41:50 2012
Return-Path: <sander@steffann.nl>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5578321F8A72; Thu, 15 Nov 2012 14:41:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.504
X-Spam-Level: 
X-Spam-Status: No, score=-0.504 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545]
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 MZSe2S4K8fjK; Thu, 15 Nov 2012 14:41:49 -0800 (PST)
Received: from mail.sintact.nl (mail.sintact.nl [IPv6:2001:4038:0:16::7]) by ietfa.amsl.com (Postfix) with ESMTP id 556CA21F852D; Thu, 15 Nov 2012 14:41:48 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.sintact.nl (Postfix) with ESMTP id 089302012; Thu, 15 Nov 2012 23:41:48 +0100 (CET)
X-Virus-Scanned: amavisd-new at mail.sintact.nl
Received: from mail.sintact.nl ([127.0.0.1]) by localhost (mail.sintact.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ftoPN+nb53pn; Thu, 15 Nov 2012 23:41:45 +0100 (CET)
Received: from macpro.10ww.steffann.nl (macpro.10ww.steffann.nl [37.77.56.75]) by mail.sintact.nl (Postfix) with ESMTP id 7DEC7200C; Thu, 15 Nov 2012 23:41:45 +0100 (CET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
From: Sander Steffann <sander@steffann.nl>
In-Reply-To: <8F781829-457B-4B32-B91A-46C22BC5D570@gmail.com>
Date: Thu, 15 Nov 2012 23:41:43 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <22AD9545-DDC9-4FE9-A984-1D0E3987D02D@steffann.nl>
References: <20121113144545.12836.71935.idtracker@ietfa.amsl.com> <CAKFn1SFy2+hXJLVtEpkdXfNuXA31ybmYnBFFPXj-73kb3tD+yw@mail.gmail.com> <5FCB8A98-4984-427C-9468-1DFDEBD206FD@steffann.nl> <87676878-B077-4B4C-96DC-9F755F78018A@gigix.net> <50A530E7.8@lacnic.net> <B8132154-7260-43B4-B10D-E5B95924A15D@gmail.com> <00C0245E-59D7-4552-8BB4-1C0099513D1D@steffann.nl> <D470B9D8-977F-4E8B-8EDF-7769D5773279@gmail.com> <0BC58149-A314-4AD3-80A5-DC8BF5DB0E2D@steffann.nl> <2007FD20-0EA4-4204-81A5-D9AE0201419D@gmail.com> <D40BD502-1E3A-4AAA-A040-E2E4EE83141D@steffann.nl> <8F781829-457B-4B32-B91A-46C22BC5D570@gmail.com>
To: Dino Farinacci <farinacci@gmail.com>
X-Mailer: Apple Mail (2.1499)
Cc: ietf@ietf.org, lisp@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Nov 2012 22:41:50 -0000

Hi,

>> But I think it comes down to
>> COULD ignore that certain EIDs are in the mapping system and always =
route them legacy-style
>=20
> No, I don't think so. You just avoided doing LISP to the destination =
site that wants multi-homing.

That's what I said (or at least meant :) )

>> I wouldn't agree with
>> COULD know if certain addresses are EIDs or not by looking at the =
prefix
>> because any address space can be used as EIDs now. Or are you =
proposing to deprecate the use of all other address space as EIDs?
>=20
> You can configure a device to be more restrictive. And this would be =
the case in the non-capital I internet.

Ok

>>>> Because the RIR communities will probably just refuse to allocate =
from this space if it means that all those routes end up in the BGP =
table... They are already plenty of people that don't like regular PI =
policies...
>>>=20
>>> You have all the PITRs in the world advertise only the one /12 into =
underlying routing.
>>=20
>> ROFL. No sorry, that's not going to work
>=20
> I'm sorry, it can work and people will WANT to do this. Infrastructure =
providers do want to attract traffic.
>=20
>> a) they would have to pay all the bandwidth cost for users of that =
EID space that they have no business relation with
>=20
> If you have enough PITRs spread around the Internet, it works no =
differently than a set of boxes at a public inter-connect that =
advertises the same prefix (to say google).

Yes, but there is a big financial incentive for Google to maintain that.

>> b) as a user of that EID space I would be at the mercy of PITR =
operators that I don't even know
>=20
> You are at the mercy of a lot of infrastructure components today. This =
is no different.

Yes it is. *please*please*please* study what happened to 6to4 and the =
2002::/16 prefix before continuing this discussion.

> You are at the mercy of your DNS server, are you not? It is the same =
thing. So let's not make things more complicated.
>=20
>> c) See all the arguments about why 6to4 is unreliable. They'll apply =
here too
>=20
> Then you deploy an ITR at your site. You will want to for other =
reasons, so you kill the problem you think you have.
>=20
>>>>>> which will make a mess of the global IPv6 routing table...
>>>>>=20
>>>>> And why do you think you need to assign PITRs per sub-block?
>>>>=20
>>>> I hope that is not necessary, but if addresses are assigned to =
end-sites directly in a PI-like way then who is going to provide PITR =
services for the users? Someone has to pay the bandwidth cost for =
operating=20
>>>=20
>>> PITR services are provide for non-LISP sources to send to these =
sites. If you have a well-known defined /12 that all PITRs advertise, =
then when you allocate sub-blocks, you don't have to change, =
reconfigure, or touch the 1000s of PITRs deployed.
>>=20
>> What makes you think that all those PITRs will pay the cost for =
routing all that traffic?
>=20
> Pay the cost? The cost is the bandwidth that is already provision to =
come into those boxes. And infrastructure providers do want to attract =
traffic.

That assumes that *everybody* runs such a PITR... Otherwise the company =
running the PITR will attract traffic from other's and pay for the =
bandwidth.

>>>> a PITR... And the users of that space want reliability, so they are =
not going to rely on the goodwill of some unknown 3rd parties. There is =
too much bad experience with 2002::/16 for that.
>>>=20
>>> We do that all the time on the Internet unless you sent this email =
on a source-route to me. ;-)
>>=20
>> No, sorry. I now pay my ISP to make sure my connectivity works. In =
your example I'm going to rely on some unknown PETR for outbound traffic =
and on whatever PITR is closest to the other side for my inbound
>=20
> Don't change the context of this discussion. We are talking PITRs. =
PETRs are something completely different.

Yes, and I explicitly mention below that you *can* control those.

>> traffic. I might be able to control the PETR, but not the PITR =
because that depends on the routing from the other side. We have been =
here before with 2002::/16. Don't repeat that huge mistake!
>>=20
>> - Sander
>=20
> This is now off topic. The draft has nothing to do with PITR =
deployment.

*you* are the one suggesting that PITRs will be deployed that handle the =
/12 or /16 that is being proposed in this draft. Getting this EID =
address accessible from non-LISP sites needs PITRs, so it is very much =
on topic.

Please read up on the mess that RFC 3056 caused. There is a good reason =
that RFC 6724 depreferenced 2002::/16. It explicitly says (although it =
contains an error, it says 2002::/32 when 2002::/16 is meant): =
"Depreferenced 6to4 (2002::/32) below native IPv4 since 6to4 =
connectivity is less reliable today (and is expected to be phased out =
over time, rather than becoming more reliable)." The EID prefix has the =
same problems as the 6to4 prefix.

Before requesting address space for EIDs I think we need to know how =
it's going to be distributed (RIRs, separate registry (actually doesn't =
have to be a bad idea!)) and how it's going to be routed (like PI space =
is today with every end-site a separate entry in the global BGP table, =
like, PA space where a LISP-ISP provides aggregation, like 6to4 is with =
the whole prefix anycast by open relays, ...)

Please understand that I am u huge fan of LISP (my home network and lab =
networks are all using LISP). I am just not very sure if we really need =
this EID prefix. I am afraid it will do a lot of harm if defined, =
distributed and routed badly.

- Sander


From aservin@lacnic.net  Thu Nov 15 14:49:15 2012
Return-Path: <aservin@lacnic.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB4EC21F8AA4; Thu, 15 Nov 2012 14:49:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.475
X-Spam-Level: 
X-Spam-Status: No, score=-2.475 tagged_above=-999 required=5 tests=[AWL=0.125,  BAYES_00=-2.599, NO_RELAYS=-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 ers2UDZi0LZX; Thu, 15 Nov 2012 14:49:14 -0800 (PST)
Received: from mail.lacnic.net.uy (mail.lacnic.net.uy [IPv6:2001:13c7:7001:4000::3]) by ietfa.amsl.com (Postfix) with ESMTP id 07C1B21F8A92; Thu, 15 Nov 2012 14:49:04 -0800 (PST)
Received: from [IPv6:2800:af:ba30:fa64:4d61:e232:817c:d402] (unknown [IPv6:2800:af:ba30:fa64:4d61:e232:817c:d402]) by mail.lacnic.net.uy (Postfix) with ESMTP id 2715A308454; Thu, 15 Nov 2012 20:48:54 -0200 (UYST)
Message-ID: <50A57153.70000@lacnic.net>
Date: Thu, 15 Nov 2012 20:48:51 -0200
From: Arturo Servin <aservin@lacnic.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: "Joel M. Halpern" <jmh@joelhalpern.com>
Subject: Re: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
References: <20121113144545.12836.71935.idtracker@ietfa.amsl.com> <CAKFn1SFy2+hXJLVtEpkdXfNuXA31ybmYnBFFPXj-73kb3tD+yw@mail.gmail.com> <5FCB8A98-4984-427C-9468-1DFDEBD206FD@steffann.nl> <87676878-B077-4B4C-96DC-9F755F78018A@gigix.net> <50A530E7.8@lacnic.net> <B8132154-7260-43B4-B10D-E5B95924A15D@gmail.com> <00C0245E-59D7-4552-8BB4-1C0099513D1D@steffann.nl> <D470B9D8-977F-4E8B-8EDF-7769D5773279@gmail.com> <0BC58149-A314-4AD3-80A5-DC8BF5DB0E2D@steffann.nl> <2007FD20-0EA4-4204-81A5-D9AE0201419D@gmail.com> <D40BD502-1E3A-4AAA-A040-E2E4EE83141D@steffann.nl> <8F781829-457B-4B32-B91A-46C22BC5D570@gmail.com> <551B2C05-2E30-4B6F-8D35-8CA0482A8D82@apnic.net> <50A56F23.7020903@joelhalpern.com>
In-Reply-To: <50A56F23.7020903@joelhalpern.com>
X-Enigmail-Version: 1.4.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-LACNIC.uy-MailScanner-Information: Please contact the ISP for more information
X-LACNIC.uy-MailScanner: Found to be clean
X-LACNIC.uy-MailScanner-SpamCheck: 
X-LACNIC.uy-MailScanner-From: aservin@lacnic.net
Cc: George Michaelson <ggm+ietf@apnic.net>, "ietf@ietf.org list" <ietf@ietf.org>, lisp@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Nov 2012 22:49:16 -0000

Joel,

	I think that George raised a very valid concern and he explained very
well the RIR machinery to perform address allocation.

	Saying that "it is just PI" simple does not help.

	As an example of our concerns (or at least mine), the policy to
allocate PI in lacnic is:

"
4.5.4.1. Direct assignment of portable IPv6 addresses to End Sites
having portable IPv4 addresses previously assigned by LACNIC
LACNIC will assign portable IPv6 address blocks directly to end sites if
they hold portable IPv4 addresses previously assigned by LACNIC.
In case of announcing the assignment on the Internet inter-domain
routing system, the receiving organization shall announce the block
maintaining de-aggregation to a minimum in accordance with the
announcing organization's needs.
Assignments will be made in blocks smaller than or equal to a /32 but
always greater than or equal to a /48.
Where possible, subsequent allocations will be made from an adjacent
address block, but only if duly documented and justified.

4.5.4.2. Direct assignment of portable IPv6 addresses to End sites not
having portable IPv4 addresses previously assigned by LACNIC
LACNIC will assign portable IPv6 address blocks directly to end sites
that satisfy the following requirements:
Not be an LIR or ISP.
In case of announcing the assignment on the Internet inter-domain
routing system, the receiving organization shall announce the block
maintaining de-aggregation to a minimum in accordance with the
announcing organization's needs.
Provide detailed information showing how the requested block will be
used within the following three, six and twelve months.
Submit addressing plans for at least a year, and host numbers on each
subnet.
Submit a detailed description of the network topology.
Prepare a detailed description of the network routing plans, including
the routing protocols to be used as well as any existing limitations.
Assignments will be made in blocks smaller than or equal to a /32 but
always greater than or equal to a /48.
Where possible, subsequent allocations will be made from an adjacent
address block, but only if duly documented and justified.
"

	So, are you expecting these to be the rules over the /16 that you are
requesting?

	As I said to Dino, you are free to leave the rules for later
definition, but that IMHO would demerit the request making the space
basically useless.

Regards,
as

On 15/11/2012 20:39, Joel M. Halpern wrote:
> Whatever else is going on, LISP EIDs do not have geographic
> significance.  They do not have IP Routing topological significance. The
> are not aggregateable.
> 
> They are intended to beused by a site as a single prefix.  Hence, the
> desired behavior (within the /16) is exactly the same as that needed to
> respond to a PI request.
> 
> Yours,
> Joel
> 
> On 11/15/2012 5:24 PM, George Michaelson wrote:
>>
>> Dino, to come back on topic. I understand the drafts purpose is to
>> request a block of IPv6 address be delegated for this specific
>> purpose, from IANA. The request is to the IAB. So, its a request for
>> architectural aspects of addressing, facing an experiment.
>>
>> a /12 is a very large amount of space. This demands rigour in the
>> process to apply, even a reservation requires a sense of why, and
>> justification. "we think its about right" isn't appropriate and the
>> document needs more work to specify why a 16, and why a /12, and what
>> the implications are of eg a smaller allocation under a /16
>> reservation, or some other size (a /32 even, for which there are both
>> precedents, in experimental allocations, and an existing process
>> inside the RIR address management framework).
>>
>> Secondly, you appear to assume these allocations to EID can simply use
>> current RIR practices. The problem is that you need to understand what
>> needs-based and justification means in process terms: Hostmasters in
>> the RIR system try very hard not to be placed in a position of making
>> arbitrary subjective decisions: they have processes which are designed
>> to ask for objective justifications to specify why an allocation
>> should take place, and at what scale. Those objective criteria face
>> addresses as addresses. not EID.
>>
>> For an example: IPv6 address allocation process currently is
>> implemented using sparse allocation (binary chop with some
>> modifications) in the APNIC region. This maximises space around
>> allocations to equalise the distribution of free blocks such that the
>> commons, the unallocated space, remains as usefully large as possible
>> and when the next binary stride is entered, there is some
>> understanding its going to be applied in common to all occupants of
>> that region of space (in terms of the size of hole around them, which
>> is not a reservation per se, but provides for risk-management of
>> future growth to the largest extent).
>>
>> We're really quite proud of sparse: its extended the life of the /12
>> we occupy quite markedly. What impact will EID have on this? Is sparse
>> an appropriate allocation engine to use for EID? What if eg you have
>> expectations of almost-geographic aspects of address management in
>> EID. Doesn't that require documentation as a process? And, you may be
>> specifying a cost on the RIR system, to engineer support for the new
>> allocation logic. If it doesn't logically fit in sparse allocation, we
>> need to know. And we need to know why.
>>
>> EID are not going to be used like 'normal' addresses. So, the normal
>> justifications don't look entirely appropriate to me from 10,000ft.
>> The document needs to say "maybe we need to understand the allocation
>> processes that the RIR should objectively apply" or maybe you need to
>> step outside of draft space and engage inside the RIR policy process
>> and seek a global policy which can document the process.
>>
>> To ask for an IANA allocation without having undertaken this process
>> looks wrong to me. So, I stand by my concern the document isn't ready
>> for IETF last call: it hasn't addressed substantive issues around the
>> process and expectations of address/registry function, to manage the
>> /16, and it hasn't documented the basis of asking for a /16 in the
>> first place, or a /12 reservation.
>>
>> cheers
>>
>> -George
>> _______________________________________________
>> lisp mailing list
>> lisp@ietf.org
>> https://www.ietf.org/mailman/listinfo/lisp
>>
> _______________________________________________
> lisp mailing list
> lisp@ietf.org
> https://www.ietf.org/mailman/listinfo/lisp

From johnl@taugh.com  Thu Nov 15 15:01:47 2012
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E9B1721F8522 for <ietf@ietfa.amsl.com>; Thu, 15 Nov 2012 15:01:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.409
X-Spam-Level: 
X-Spam-Status: No, score=-2.409 tagged_above=-999 required=5 tests=[AWL=0.191,  BAYES_00=-2.599, NO_RELAYS=-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 orA64mP3fcva for <ietf@ietfa.amsl.com>; Thu, 15 Nov 2012 15:01:46 -0800 (PST)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 867C321F84FB for <ietf@ietf.org>; Thu, 15 Nov 2012 15:01:46 -0800 (PST)
Received: (qmail 18430 invoked from network); 15 Nov 2012 23:01:45 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:vbr-info:user-agent:cleverness; s=47fd.50a57459.k1211; bh=K2fs7TENngPdOsrFfpi9yciV4BOwHaO2qEB23ROQh1Q=; b=lmsdR/GqquGAtHqUAucTrCsO3Ay6X2l3RSFD1E3lL9GZHhsp+br92+pMrPMHn0ExJItkOdbE69Iy7cO4SdLFFUdMoWNyaWqMBCfQxsz0kpY10iwWr6s/S3sjCZCaTxk/YSenrdSPvQCQ/+RN85XNAkSX8qbIg/PwPaosTtjZEb8=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:vbr-info:user-agent:cleverness; s=47fd.50a57459.k1211; bh=K2fs7TENngPdOsrFfpi9yciV4BOwHaO2qEB23ROQh1Q=; b=gPd+NSjSEtVv7BL8hEFs90ghHPRdmhom30nB1DFy01ickWeGMV5y8mhMsiJnMKRuDSKsbrJBs8mFqm1ir8dQn3WYm/zVcTxePm0I+5gv9tb/E3jyrS6L+/HPt5lkZnuiHZOzSmvb6wo5ZR44Og+Jf08ZC6CDSId6Oe1uBxb3YDw=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Received: (ofmipd 127.0.0.1); 15 Nov 2012 23:01:23 -0000
Date: 15 Nov 2012 18:01:45 -0500
Message-ID: <alpine.BSF.2.00.1211151757000.2981@joyce.lan>
From: "John R Levine" <johnl@taugh.com>
To: "Carlos M. Martinez" <carlosm3011@gmail.com>
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
In-Reply-To: <50A529D2.5050808@gmail.com>
References: <20121115050813.4158.qmail@joyce.lan> <103721F2-BA44-4EA5-BA9D-A7941EA4D5ED@frobbit.se> <alpine.BSF.2.00.1211151215100.30183@joyce.lan> <50A529D2.5050808@gmail.com>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Nov 2012 23:01:48 -0000

> Comparing with the ITU who does tour the world, organizing workshops in
> far away places, I really think we should be trying a little harder to
> be more open.

The IAOC has often noted that holding meetings in more exotic places is 
considerably more expensive, the hotels and other services just charge 
more.

Keeping in mind that the IETF is paid for by a combination of conference 
fees and an annual grant from ISOC, not governments, who were you 
expecting to pay the increased costs?

Also, why do you believe that people people need to go to meetings in 
person rather than joining the mailing lists where the bulk of the IETF's 
work gets done?

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
"I dropped the toothpaste", said Tom, crestfallenly.

From aservin@lacnic.net  Thu Nov 15 16:51:51 2012
Return-Path: <aservin@lacnic.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB94C1F0C8B for <ietf@ietfa.amsl.com>; Thu, 15 Nov 2012 16:51:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.489
X-Spam-Level: 
X-Spam-Status: No, score=-2.489 tagged_above=-999 required=5 tests=[AWL=0.111,  BAYES_00=-2.599, NO_RELAYS=-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 n6AJpljsjg0a for <ietf@ietfa.amsl.com>; Thu, 15 Nov 2012 16:51:51 -0800 (PST)
Received: from mail.lacnic.net.uy (mail.lacnic.net.uy [IPv6:2001:13c7:7001:4000::3]) by ietfa.amsl.com (Postfix) with ESMTP id 337081F0C82 for <ietf@ietf.org>; Thu, 15 Nov 2012 16:51:51 -0800 (PST)
Received: from [IPv6:2800:af:ba30:fa64:911a:8e41:9b5b:6a2e] (unknown [IPv6:2800:af:ba30:fa64:911a:8e41:9b5b:6a2e]) by mail.lacnic.net.uy (Postfix) with ESMTP id 1D3C4308465 for <ietf@ietf.org>; Thu, 15 Nov 2012 22:51:43 -0200 (UYST)
Message-ID: <50A58E1B.3010901@lacnic.net>
Date: Thu, 15 Nov 2012 22:51:39 -0200
From: Arturo Servin <aservin@lacnic.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
References: <20121115050813.4158.qmail@joyce.lan> <103721F2-BA44-4EA5-BA9D-A7941EA4D5ED@frobbit.se> <alpine.BSF.2.00.1211151215100.30183@joyce.lan> <50A529D2.5050808@gmail.com> <alpine.BSF.2.00.1211151757000.2981@joyce.lan>
In-Reply-To: <alpine.BSF.2.00.1211151757000.2981@joyce.lan>
X-Enigmail-Version: 1.4.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-LACNIC.uy-MailScanner-Information: Please contact the ISP for more information
X-LACNIC.uy-MailScanner: Found to be clean
X-LACNIC.uy-MailScanner-SpamCheck: 
X-LACNIC.uy-MailScanner-From: aservin@lacnic.net
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Nov 2012 00:51:52 -0000

	

On 15/11/2012 21:01, John R Levine wrote:
>> Comparing with the ITU who does tour the world, organizing workshops in
>> far away places, I really think we should be trying a little harder to
>> be more open.
> 
> The IAOC has often noted that holding meetings in more exotic places is
> considerably more expensive, the hotels and other services just charge
> more.
> 
> Keeping in mind that the IETF is paid for by a combination of conference
> fees and an annual grant from ISOC, not governments, who were you
> expecting to pay the increased costs?
> 
> Also, why do you believe that people people need to go to meetings in
> person rather than joining the mailing lists where the bulk of the
> IETF's work gets done?
> 

	That has been answered:

http://www.ietf.org/mail-archive/web/ietf/current/msg75890.html

	Shall we move on?

> Regards,
> John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
> "I dropped the toothpaste", said Tom, crestfallenly.

Regards,
as

From johnl@iecc.com  Thu Nov 15 19:28:05 2012
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 13A3921F857D for <ietf@ietfa.amsl.com>; Thu, 15 Nov 2012 19:28:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.634
X-Spam-Level: 
X-Spam-Status: No, score=-106.634 tagged_above=-999 required=5 tests=[AWL=-4.035, 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 bEUOrimvf-g4 for <ietf@ietfa.amsl.com>; Thu, 15 Nov 2012 19:28:04 -0800 (PST)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 27E8721F8577 for <ietf@ietf.org>; Thu, 15 Nov 2012 19:28:02 -0800 (PST)
Received: (qmail 71303 invoked from network); 16 Nov 2012 03:28:00 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 16 Nov 2012 03:28:00 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=50a5b2c0.xn--30v786c.k1211; i=johnl@user.iecc.com; bh=rDq5lEbm7gH7DpxcUxALpqY5IGbsKZMfkd9Cx/Gs6Eg=; b=DtQQOQylUMBtHSTDPW9yqprerNBGw0yTbgF/Kxjtlv+MtIe7Nhu81HJWziAp6mTMIXYeBLFkwo4vD0zv8YUrtfYFRaS1v2uOnnT93tKrWuCA6bWWW/3Zl7A/FXTvVIVJtiTqJQLOC/sw+l6RxraY13568jKMeRjRuSsNo9lLR/0=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=50a5b2c0.xn--30v786c.k1211; olt=johnl@user.iecc.com; bh=rDq5lEbm7gH7DpxcUxALpqY5IGbsKZMfkd9Cx/Gs6Eg=; b=Dnw+MkuTzjF4DkDzYGItjyunqcpIrWW2JM7vma46LjbsmsuQq0Rli+HK92q4KtinxKSeU6+d2ISRGNNbiALAuUozhFOdpOmIhfADf5Jc8ZyOAg8XsWo++ujfIyoAisu08iLPlmqa3mF/WuI5c4mMF+fEM3tiP8GzyQ600kIYgI0=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 16 Nov 2012 03:27:38 -0000
Message-ID: <20121116032738.11495.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
In-Reply-To: <50A58E1B.3010901@lacnic.net>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Nov 2012 03:28:05 -0000

>	Shall we move on?

Sure.  Since we agree that there is no way to pay for the extra costs
involved in meeting in places where there are insignificant numbers of
IETF participants, it won't happen, and we're done.

That was simple, wasn't it?


From narten@us.ibm.com  Thu Nov 15 21:53:08 2012
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B34B21F85E3 for <ietf@ietfa.amsl.com>; Thu, 15 Nov 2012 21:53:08 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CZjmJvnaTjR6 for <ietf@ietfa.amsl.com>; Thu, 15 Nov 2012 21:53:07 -0800 (PST)
Received: from e3.ny.us.ibm.com (e3.ny.us.ibm.com [32.97.182.143]) by ietfa.amsl.com (Postfix) with ESMTP id 3D15321F8531 for <ietf@ietf.org>; Thu, 15 Nov 2012 21:53:07 -0800 (PST)
Received: from /spool/local by e3.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Fri, 16 Nov 2012 00:53:06 -0500
Received: from d01dlp02.pok.ibm.com (9.56.250.167) by e3.ny.us.ibm.com (192.168.1.103) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Fri, 16 Nov 2012 00:53:05 -0500
Received: from d01relay05.pok.ibm.com (d01relay05.pok.ibm.com [9.56.227.237]) by d01dlp02.pok.ibm.com (Postfix) with ESMTP id 6957B6E803A for <ietf@ietf.org>; Fri, 16 Nov 2012 00:53:04 -0500 (EST)
Received: from d01av03.pok.ibm.com (d01av03.pok.ibm.com [9.56.224.217]) by d01relay05.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id qAG5r4fq157472 for <ietf@ietf.org>; Fri, 16 Nov 2012 00:53:04 -0500
Received: from d01av03.pok.ibm.com (loopback [127.0.0.1]) by d01av03.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id qAG5r4A9025285 for <ietf@ietf.org>; Fri, 16 Nov 2012 03:53:04 -0200
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.44.115.148]) by d01av03.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id qAG5r4DQ025277 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Fri, 16 Nov 2012 03:53:04 -0200
Received: from rotala.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.5/8.12.5) with ESMTP id qAG5r3co006240 for <ietf@ietf.org>; Fri, 16 Nov 2012 00:53:03 -0500
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.5/8.14.5/Submit) id qAG5r3Nc006195 for ietf@ietf.org; Fri, 16 Nov 2012 00:53:03 -0500
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201211160553.qAG5r3Nc006195@rotala.raleigh.ibm.com>
Date: Fri, 16 Nov 2012 00:53:02 -0500
To: ietf@ietf.org
Subject: Weekly posting summary for ietf@ietf.org
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 12111605-8974-0000-0000-0000113907E2
X-IBM-ISS-SpamDetectors: 
X-IBM-ISS-DetailInfo: BY=3.00000295; HX=3.00000198; KW=3.00000007; PH=3.00000001; SC=3.00000008; SDB=6.00191722; UDB=6.00043414; UTC=2012-11-16 05:53:06
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Nov 2012 05:53:08 -0000

Total of 148 messages in the last 7 days.
 
script run at: Fri Nov 16 00:53:02 EST 2012
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  6.76% |   10 |  5.99% |    68144 | sander@steffann.nl
  6.08% |    9 |  5.97% |    67932 | arturo.servin@gmail.com
  5.41% |    8 |  4.72% |    53729 | melinda.shore@gmail.com
  4.73% |    7 |  4.75% |    54068 | sm@resistor.net
  4.73% |    7 |  4.44% |    50498 | aservin@lacnic.net
  4.73% |    7 |  4.32% |    49148 | dhc@dcrocker.net
  4.73% |    7 |  4.21% |    47897 | carlosm3011@gmail.com
  0.68% |    1 |  7.67% |    87301 | fred@cisco.com
  3.38% |    5 |  3.88% |    44170 | brian.e.carpenter@gmail.com
  4.05% |    6 |  3.05% |    34682 | johnl@taugh.com
  3.38% |    5 |  3.13% |    35659 | ggx@gigix.net
  2.70% |    4 |  3.45% |    39268 | daedulus@btconnect.com
  2.70% |    4 |  2.93% |    33343 | abdussalambaryun@gmail.com
  2.03% |    3 |  2.19% |    24972 | ynir@checkpoint.com
  2.03% |    3 |  2.02% |    22964 | ben@nostrum.com
  2.03% |    3 |  1.92% |    21896 | joelja@bogus.com
  2.03% |    3 |  1.85% |    21067 | cabo@tzi.org
  2.03% |    3 |  1.83% |    20850 | tglassey@earthlink.net
  2.03% |    3 |  1.68% |    19071 | bertietf@bwijnen.net
  1.35% |    2 |  1.68% |    19087 | framefritti@gmail.com
  1.35% |    2 |  1.68% |    19083 | wesley.george@twcable.com
  1.35% |    2 |  1.22% |    13919 | ggm+ietf@apnic.net
  1.35% |    2 |  1.21% |    13808 | vinayakh@gmail.com
  1.35% |    2 |  1.14% |    13021 | worley@ariadne.com
  1.35% |    2 |  1.13% |    12811 | bob.hinden@gmail.com
  1.35% |    2 |  1.04% |    11795 | ajs@anvilwalrusden.com
  1.35% |    2 |  1.02% |    11623 | adrian@olddog.co.uk
  1.35% |    2 |  1.01% |    11479 | swmike@swm.pp.se
  1.35% |    2 |  0.97% |    11069 | nick@inex.ie
  1.35% |    2 |  0.96% |    10973 | stephen.farrell@cs.tcd.ie
  1.35% |    2 |  0.88% |    10021 | randy@psg.com
  0.68% |    1 |  1.00% |    11430 | swb@internet2.edu
  0.68% |    1 |  0.90% |    10225 | narten@us.ibm.com
  0.68% |    1 |  0.83% |     9502 | jmh@joelhalpern.com
  0.68% |    1 |  0.75% |     8559 | hsantos@isdg.net
  0.68% |    1 |  0.74% |     8480 | ted.ietf@gmail.com
  0.68% |    1 |  0.72% |     8251 | mary.ietf.barnes@gmail.com
  0.68% |    1 |  0.70% |     7989 | iad@ietf.org
  0.68% |    1 |  0.70% |     7931 | tony@att.com
  0.68% |    1 |  0.66% |     7466 | gmail.sant9442@winserver.com
  0.68% |    1 |  0.65% |     7440 | spencer@wonderhamster.org
  0.68% |    1 |  0.65% |     7413 | petithug@acm.org
  0.68% |    1 |  0.60% |     6874 | d3e3e3@gmail.com
  0.68% |    1 |  0.59% |     6754 | randy_presuhn@mindspring.com
  0.68% |    1 |  0.58% |     6598 | mcr+ietf@sandelman.ca
  0.68% |    1 |  0.55% |     6307 | rogerj@gmail.com
  0.68% |    1 |  0.54% |     6183 | azuremesa@gmail.com
  0.68% |    1 |  0.53% |     6013 | dwm@xpasc.com
  0.68% |    1 |  0.52% |     5943 | paf@frobbit.se
  0.68% |    1 |  0.51% |     5856 | lear@cisco.com
  0.68% |    1 |  0.51% |     5830 | gih@apnic.net
  0.68% |    1 |  0.50% |     5725 | rsk@gsp.org
  0.68% |    1 |  0.50% |     5673 | hartmans-ietf@mit.edu
  0.68% |    1 |  0.50% |     5646 | pvinci@vinciconsulting.com
  0.68% |    1 |  0.47% |     5317 | dcrocker@bbiw.net
  0.68% |    1 |  0.44% |     4960 | bortzmeyer@nic.fr
  0.68% |    1 |  0.41% |     4661 | ietf@meetecho.com
--------+------+--------+----------+------------------------
100.00% |  148 |100.00% |  1138374 | Total


From ggm+ietf@apnic.net  Fri Nov 16 00:38:24 2012
Return-Path: <ggm+ietf@apnic.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B084321F86D2; Fri, 16 Nov 2012 00:38:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.3
X-Spam-Level: 
X-Spam-Status: No, score=-102.3 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_66=0.6, NO_RELAYS=-0.001, 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 268bKqoqKP3A; Fri, 16 Nov 2012 00:38:23 -0800 (PST)
Received: from asmtp.apnic.net (asmtp.apnic.net [IPv6:2001:dc0:2001:11::199]) by ietfa.amsl.com (Postfix) with ESMTP id 0C1AB21F8668; Fri, 16 Nov 2012 00:38:21 -0800 (PST)
Received: from [IPv6:2001:67c:2e8:13:3490:ce58:7e8b:5eb0] (unknown [IPv6:2001:67c:2e8:13:3490:ce58:7e8b:5eb0]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by asmtp.apnic.net (Postfix) with ESMTP id 65F57B68D2; Fri, 16 Nov 2012 18:38:18 +1000 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
From: George Michaelson <ggm+ietf@apnic.net>
In-Reply-To: <766205F6-48FB-4962-9F43-EDCACC73D1DA@gmail.com>
Date: Fri, 16 Nov 2012 09:38:13 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <149720A8-FC8D-4BD0-9A7A-0EB42E8CCE75@apnic.net>
References: <20121113144545.12836.71935.idtracker@ietfa.amsl.com> <CAKFn1SFy2+hXJLVtEpkdXfNuXA31ybmYnBFFPXj-73kb3tD+yw@mail.gmail.com> <5FCB8A98-4984-427C-9468-1DFDEBD206FD@steffann.nl> <87676878-B077-4B4C-96DC-9F755F78018A@gigix.net> <50A530E7.8@lacnic.net> <B8132154-7260-43B4-B10D-E5B95924A15D@gmail.com> <00C0245E-59D7-4552-8BB4-1C0099513D1D@steffann.nl> <D470B9D8-977F-4E8B-8EDF-7769D5773279@gmail.com> <0BC58149-A314-4AD3-80A5-DC8BF5DB0E2D@steffann.nl> <2007FD20-0EA4-4204-81A5-D9AE0201419D@gmail.com> <D40BD502-1E3A-4AAA-A040-E2E4EE83141D@steffann.nl> <8F781829-457B-4B32-B91A-46C22BC5D570@gmail.com> <37436188-2E53-40DC-839F-AC52E5CA8188@apnic.net> <766205F6-48FB-4962-9F43-EDCACC73D1DA@gmail.com>
To: Dino Farinacci <farinacci@gmail.com>
X-Mailer: Apple Mail (2.1499)
Cc: "ietf@ietf.org list" <ietf@ietf.org>, lisp@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Nov 2012 08:38:24 -0000

On 16/11/2012, at 7:24 AM, Dino Farinacci <farinacci@gmail.com> wrote:
>=20
>> Secondly, you appear to assume these allocations to EID can simply =
use current RIR practices. The problem is that you need to understand =
what needs-based and justification means in process terms: Hostmasters =
in the RIR system try very hard not to be placed in a position of making =
arbitrary subjective decisions: they have processes which are designed =
to ask for objective justifications to specify why an allocation should =
take place, and at what scale. Those objective criteria face addresses =
as addresses. not EID.
>=20
> No, I am not making any assumptions either way. How allocation gets =
done is subject to more work.

Maybe this is something you could come to an RIR meeting and present on =
or discuss? We've got an APNIC/APRICOT coming up early in 2013 and I am =
sure you'd be welcomed to submit some content. Its good to talk about =
these things.


>=20
>> For an example: IPv6 address allocation process currently is =
implemented using sparse allocation (binary chop with some =
modifications) in the APNIC region. This maximises space around =
allocations to equalise the distribution of free blocks such that the =
commons, the unallocated space, remains as usefully large as possible =
and when the next binary stride is entered, there is some understanding =
its going to be applied in common to all occupants of that region of =
space (in terms of the size of hole around them, which is not a =
reservation per se, but provides for risk-management of future growth to =
the largest extent).
>=20
> There is no special semantics of EIDs that require you to change this. =
EIDs are just addresses that do not get injected into the underlying =
routing system. Other than that, they are just like any other address an =
RIR allocates.

But by not being injected in the routing system they've already got a =
qualification against normal allocations, which are for globally routed =
addresses. So if under current criteria, somebody fronts to the RIR =
system and asks for a unique address assignment NOT to be globally =
routed, what do you think happens?

We try not to 'just make it up on the fly' -If there is going to be an =
EID space, shared footprint, with this behaviour, it will need to be =
documented in RIR policy.

>=20
>> We're really quite proud of sparse: its extended the life of the /12 =
we occupy quite markedly. What impact will EID have on this? Is sparse =
an appropriate allocation engine to use for EID? What if eg you have =
expectations of almost-geographic aspects of address management in EID. =
Doesn't that require documentation as a process? And, you may be =
specifying a cost on the RIR system, to engineer support for the new =
allocation logic. If it doesn't logically fit in sparse allocation, we =
need to know. And we need to know why.
>=20
> What Joel said.

4.  Expected use


   Sites planning to deploy LISP may request a prefix in the IPv6 EID
   Block.  Such prefix will be used for routing and endpoint
   identification inside the site requesting it.  Mappings related to
   such prefix, or part of it, will be made available through the
   mapping system in use or registered to one or more Map Server(s).
   Too guarantee reachability from the Legacy Internet the prefix could
   be announced in the BGP routing infrastructure by one or more
   PITR(s), possibly as part of a larger prefix, AGGREGATING several
   prefixes of several sites.

[my emphasis]


>=20
7.  Routing Considerations


   In order to provide connectivity between the Legacy Internet and LISP
   sites, PITRs announcing large AGGREGATES of the IPv6 EID Block could
   be deployed.  By doing so, PITRs will attract traffic destined to
   LISP sites in order to encapsulate and forward it toward the specific
   destination LISP site.  Routers in the Legacy Internet must treat
   announcements of prefixes from the IPv6 EID Block as normal
   announcements, applying best current practice for traffic engineering
   and security.

[my emphasis]

thats in the 03 draft. So, naievely, I read that as meaning global =
unicast Aggregation. If it refers inside LISP only and is not implying =
aggregatable assignment to end entities holding EID, if EID are unique =
only and can be sparse and disjoint, Thats good to know.


>> EID are not going to be used like 'normal' addresses. So, the normal =
justifications don't look entirely
>=20
> Define how a 'normal address" is used.

globally routable (normally) for starters. With assignment dynamics =
which relate an end-site to a customer, so with some scaling which =
reflects demand and the depth of network complexity to achieve it. Which =
is specified at time of assignment and tracked for subsequent =
reallocation/growth.=20

Address management has costs btw. I expect many people in this community =
are concerned by that and there are times quite unpleasant language is =
used about the RIR process and its cost recovery needs, but it can't be =
avoided. So in that context, did you expect EID allocation and address =
management to be free? Its got to reflect its societal costs like other =
addresses is a possible position.

>=20
>> appropriate to me from 10,000ft. The document needs to say "maybe we =
need to understand the allocation processes that the RIR should =
objectively apply" or maybe you need to step outside of draft space and =
engage inside the RIR policy process and seek a global policy which can =
document the process.
>=20
> The working decided that this draft is solely for request purposes. We =
could use help from RIRs to write a document on how to allocate EIDs. =
But I am pretty sure it would look like documents that already exist.

Yes, but the conversation would be useful. So why not come into RIR =
policy development process and kick off a conversation about global =
address policy (which this clearly is)

Seriously: this could be talked about.

>=20
> I don't understand why you think they look different or need to be =
treated differently. So you have to do the explaining.  ;-)

Cute. I'd like this document to explore the need for work in the area =
and say its for further study, and observe the IAB/IANA instruction =
might be pending that further work, because assigning a block without =
objective criteria and a global policy in RIR Process is not a good =
idea.

I really don't think the IAB should simply give the /12 on the basis of =
this document. If another document needs to be spun then this one can =
sit at IETF last call and share fate.


>=20
>> To ask for an IANA allocation without having undertaken this process =
looks wrong to me. So, I stand by my concern the document isn't ready =
for IETF last call: it hasn't addressed substantive issues around the =
process and expectations of address/registry function, to manage the =
/16, and it hasn't documented the basis of asking for a /16 in the first =
place, or a /12 reservation.
>=20
> Here is a real world example we have been using on the LISP beta =
network. It is so simple that it really needs no more explanation than =
what I am going to explain below:
>=20
> (1) We have 2610:00d0::/32 allocated for EIDs.
> (2) Each site on the LISP beta network gets a /48 out of that.
> (3) Each site xTRs register their /48 with the mapping system using =
RLOCs that are PA addresses they use to attach to the Internet.
>=20
> That is it. So I am not getting why there are so many issues. Can't we =
keep this simple and experiment please?

Ok. So work with me on this a bit Dino. I realize you are very busy, but =
I want to understand.

1) how many /48 have been allocated thus far from this experimental /32? =
it has 65,000 of them. The dynamics of the rollout would be very =
interesting.

I'm really interested in this number. Its pretty fundamental to an =
address application/reservation facing the IAB/IANA and I expect you =
will be asked it more formally anyway (not by me. I dont do this stuff, =
but its forseeable). Bearing in mind that Sander Steffan has already =
shown global-unicast can be used for EID, I don't expect it to be =
equivalent to the count of EID visible in LISP routing.
t
Anyway, even with that caveat 65,000 is quite a lot. If you've achieved =
high density, the experiment has very interesting scaling and we need to =
know. In particular, I would suggest that its possibly less an =
experiment, and more a product. If its in production, then applying =
under experimental criteria is a bit of a concern for me.

2) how many /48 do you foresee being allocated in a 1,2,5 year footprint =
heading to the /16 horizon? There are 4 billion /48 in a /16=20

3) how many /48 do you foresee being allocated in the 5,10,20 year =
footprint heading to the /12 horizon?=20

I have to say that to achieve 2) I do not believe this could be in any =
real sense "an experiment" except to the extent the entire IPv4 network =
we have is an 'experiment' because 2^32 is looking like a very large =
amount of EID, equivalent to the entire IPv4 space.

So from here, I can't grasp the /16, let alone the /12. If this is an =
experiment, then I think we should be having a conversation about what =
size above a /32 achieves your goals. If there is to be a reservation, =
we should understand the scoping it can grow to, which begins to look =
more like the /16 than the /12, although I suspect its a lot smaller =
than the /16 and more like a /22

[I am not a hostmaster and this is most definitely not an APNIC =
position: its my personal view]

BTW, comparisons to the /12 of 2002: are very unhelpful to your case. =
Firstly, it was a transition technology, in the main an automatic =
tunnelling mechanism and not structured, and the sub assigns in the =
space reflected their global routing via the IPv4 label embedded.

Secondly, there were very real administrative issues facing 2002: in =
terms of reverse-DNS, and the over-reach of an ISPs routing footprint =
and intrusion of services.

I think the /12 reflected the needs of the format to embed the =
server,client pairs into the footprint of address. Since you have =
demonstrated your EID is in /48, the size of the parent above that in =
global routing does not need to be the same as 2002 which depended on =
totally ad-hoc server IPs and the anycast cloud instance as fallback.=20

I may be wrong, but I suspect if the 2002 protocol spec had been written =
not to need the /12 it would not have been assigned a /12.

I think in hindsight the Teredo footprint of a single /32 in 2001:0: is =
equally instructive. Microsoft deployed this into their core technology =
worldwide. clearly, a single /32 can scale to an entire global Internet =
for this class of tunnel. I appreciate that EID is a different kind of =
tunnel, but the difference tends to less EID doesn't it?

cheers

-george


>=20
> Dino
>=20
>>=20
>> cheers
>>=20
>> -George
>=20
> _______________________________________________
> lisp mailing list
> lisp@ietf.org
> https://www.ietf.org/mailman/listinfo/lisp


From ggm+ietf@apnic.net  Fri Nov 16 00:42:07 2012
Return-Path: <ggm+ietf@apnic.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4AF3A21F86DE; Fri, 16 Nov 2012 00:42:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.45
X-Spam-Level: 
X-Spam-Status: No, score=-102.45 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, NO_RELAYS=-0.001, 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 kJAb8wYqlc-H; Fri, 16 Nov 2012 00:42:07 -0800 (PST)
Received: from asmtp.apnic.net (asmtp.apnic.net [IPv6:2001:dc0:2001:11::199]) by ietfa.amsl.com (Postfix) with ESMTP id B88B821F8504; Fri, 16 Nov 2012 00:42:06 -0800 (PST)
Received: from [IPv6:2001:67c:2e8:13:3490:ce58:7e8b:5eb0] (unknown [IPv6:2001:67c:2e8:13:3490:ce58:7e8b:5eb0]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by asmtp.apnic.net (Postfix) with ESMTP id C22D6B684D; Fri, 16 Nov 2012 18:42:04 +1000 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
From: George Michaelson <ggm+ietf@apnic.net>
In-Reply-To: <149720A8-FC8D-4BD0-9A7A-0EB42E8CCE75@apnic.net>
Date: Fri, 16 Nov 2012 09:42:00 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <951612FB-F1A5-4EBE-8792-57CC9BDC71A2@apnic.net>
References: <20121113144545.12836.71935.idtracker@ietfa.amsl.com> <CAKFn1SFy2+hXJLVtEpkdXfNuXA31ybmYnBFFPXj-73kb3tD+yw@mail.gmail.com> <5FCB8A98-4984-427C-9468-1DFDEBD206FD@steffann.nl> <87676878-B077-4B4C-96DC-9F755F78018A@gigix.net> <50A530E7.8@lacnic.net> <B8132154-7260-43B4-B10D-E5B95924A15D@gmail.com> <00C0245E-59D7-4552-8BB4-1C0099513D1D@steffann.nl> <D470B9D8-977F-4E8B-8EDF-7769D5773279@gmail.com> <0BC58149-A314-4AD3-80A5-DC8BF5DB0E2D@steffann.nl> <2007FD20-0EA4-4204-81A5-D9AE0201419D@gmail.com> <D40BD502-1E3A-4AAA-A040-E2E4EE83141D@steffann.nl> <8F781829-457B-4B32-B91A-46C22BC5D570@gmail.com> <37436188-2E53-40DC-839F-AC52E5CA8188@apnic.net> <766205F6-48FB-4962-9F43-EDCACC73D1DA@gmail.com> <149720A8-FC8D-4BD0-9A7A-0EB42E8CCE75@apnic.net>
To: Dino Farinacci <farinacci@gmail.com>
X-Mailer: Apple Mail (2.1499)
Cc: "ietf@ietf.org list" <ietf@ietf.org>, lisp@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Nov 2012 08:42:07 -0000

s/12/16/ wrt 2002: doh. the principle stands. 2002://16 did not imply a =
reservation to a /12 and would have been given less than a /16 if the =
technology had allowed it.

-G=

From brian.e.carpenter@gmail.com  Fri Nov 16 01:05:16 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 48A6D21F8477; Fri, 16 Nov 2012 01:05:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.557
X-Spam-Level: 
X-Spam-Status: No, score=-101.557 tagged_above=-999 required=5 tests=[AWL=0.134, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, 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 5vjgoUzD86s0; Fri, 16 Nov 2012 01:05:15 -0800 (PST)
Received: from mail-wg0-f44.google.com (mail-wg0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id 48D9821F845A; Fri, 16 Nov 2012 01:05:15 -0800 (PST)
Received: by mail-wg0-f44.google.com with SMTP id dr13so977044wgb.13 for <multiple recipients>; Fri, 16 Nov 2012 01:05:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=H8F9Psv3wh+2N96lmDrohYem/whPh6va7BSXpAA+F3w=; b=tSvLeayaX550ZBUDDBGHEBdHSRJWGe1mnXbRYNJLvyPkV1pn1na5u+wkLnzqF2ZXEh CsWE6mz1k6Dsas8REmXG0wpisWvKO0pSf4iB9MUk+KOxy7OLmtsn8jb0Y2qHGpODAyBh dqcJ6ApRkNnewH75TtL+zamemPUdsT3qfoBQ6NEC5MA6CmvKnWZ/4xov0AsUUCTB4nE4 dZzyw6MDTs+2IaT0E71wbCJTkLANt7Q/3yNTRBv3cNTqc6lhyzi2QQj0FTR0/7AJA4ul rYmzCNzBqpopEF0ks2kuOaxo8O12U7E08ch8fMDS7XG/l03bAGv9ZYx1uvMJkoqfjvSL yYdg==
Received: by 10.216.140.87 with SMTP id d65mr1653927wej.131.1353056714314; Fri, 16 Nov 2012 01:05:14 -0800 (PST)
Received: from [192.168.1.65] (host-2-102-216-111.as13285.net. [2.102.216.111]) by mx.google.com with ESMTPS id d16sm14433728wiw.8.2012.11.16.01.05.12 (version=SSLv3 cipher=OTHER); Fri, 16 Nov 2012 01:05:13 -0800 (PST)
Message-ID: <50A601D6.6080701@gmail.com>
Date: Fri, 16 Nov 2012 09:05:26 +0000
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Sander Steffann <sander@steffann.nl>
Subject: Re: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
References: <20121113144545.12836.71935.idtracker@ietfa.amsl.com>	<CAKFn1SFy2+hXJLVtEpkdXfNuXA31ybmYnBFFPXj-73kb3tD+yw@mail.gmail.com>	<5FCB8A98-4984-427C-9468-1DFDEBD206FD@steffann.nl>	<87676878-B077-4B4C-96DC-9F755F78018A@gigix.net>	<50A530E7.8@lacnic.net>	<B8132154-7260-43B4-B10D-E5B95924A15D@gmail.com>	<00C0245E-59D7-4552-8BB4-1C0099513D1D@steffann.nl>	<D470B9D8-977F-4E8B-8EDF-7769D5773279@gmail.com>	<0BC58149-A314-4AD3-80A5-DC8BF5DB0E2D@steffann.nl>	<2007FD20-0EA4-4204-81A5-D9AE0201419D@gmail.com>	<D40BD502-1E3A-4AAA-A040-E2E4EE83141D@steffann.nl>	<8F781829-457B-4B32-B91A-46C22BC5D570@gmail.com> <22AD9545-DDC9-4FE9-A984-1D0E3987D02D@steffann.nl>
In-Reply-To: <22AD9545-DDC9-4FE9-A984-1D0E3987D02D@steffann.nl>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org, Dino Farinacci <farinacci@gmail.com>, lisp@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Nov 2012 09:05:16 -0000

On 15/11/2012 22:41, Sander Steffann wrote:
...
>>> b) as a user of that EID space I would be at the mercy of
>>> PITR operators that I don't even know
>> You are at the mercy of a lot of infrastructure components
>> today. This is no different.
> 
> Yes it is. *please*please*please* study what happened to 6to4
> and the 2002::/16 prefix before continuing this discussion.

The problem there was that the design of 6to4 assumed, and
relied on, altruistic cooperation between operators, to ensure
that there was a useable route to 2002::/16 *everywhere* in the
IPv6 network. That assumption was naive and led to black holes.

My main concern with LISP deployment is whether there will be
a useable route to EID space *everywhere* in the (non-LISP)
network. If that also relies on altruism, I would share Sander's
concern.

     Brian

From sander@steffann.nl  Fri Nov 16 02:18:17 2012
Return-Path: <sander@steffann.nl>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C6C521F868A; Fri, 16 Nov 2012 02:18:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.048
X-Spam-Level: 
X-Spam-Status: No, score=-1.048 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, RDNS_NONE=0.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 HcraAW0+4tC6; Fri, 16 Nov 2012 02:18:17 -0800 (PST)
Received: from mail.sintact.nl (mail.sintact.nl [IPv6:2001:4038:0:16::7]) by ietfa.amsl.com (Postfix) with ESMTP id 1F5BE21F867F; Fri, 16 Nov 2012 02:18:16 -0800 (PST)
Received: from [192.168.222.59] (unknown [87.249.115.10]) by mail.sintact.nl (Postfix) with ESMTP id A827B2011; Fri, 16 Nov 2012 11:18:15 +0100 (CET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
From: Sander Steffann <sander@steffann.nl>
In-Reply-To: <149720A8-FC8D-4BD0-9A7A-0EB42E8CCE75@apnic.net>
Date: Fri, 16 Nov 2012 11:18:15 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <EE0CED54-D440-434C-8804-05EF6419B1AD@steffann.nl>
References: <20121113144545.12836.71935.idtracker@ietfa.amsl.com> <CAKFn1SFy2+hXJLVtEpkdXfNuXA31ybmYnBFFPXj-73kb3tD+yw@mail.gmail.com> <5FCB8A98-4984-427C-9468-1DFDEBD206FD@steffann.nl> <87676878-B077-4B4C-96DC-9F755F78018A@gigix.net> <50A530E7.8@lacnic.net> <B8132154-7260-43B4-B10D-E5B95924A15D@gmail.com> <00C0245E-59D7-4552-8BB4-1C0099513D1D@steffann.nl> <D470B9D8-977F-4E8B-8EDF-7769D5773279@gmail.com> <0BC58149-A314-4AD3-80A5-DC8BF5DB0E2D@steffann.nl> <2007FD20-0EA4-4204-81A5-D9AE0201419D@gmail.com> <D40BD502-1E3A-4AAA-A040-E2E4EE83141D@steffann.nl> <8F781829-457B-4B32-B91A-46C22BC5D570@gmail.com> <37436188-2E53-40DC-839F-AC52E5CA8188@apnic.net> <766205F6-48FB-4962-9F43-EDCACC73D1DA@gmail.com> <149720A8-FC8D-4BD0-9A7A-0EB42E8CCE75@apnic.net>
To: Dino Farinacci <farinacci@gmail.com>
X-Mailer: Apple Mail (2.1499)
Cc: George Michaelson <ggm+ietf@apnic.net>, "ietf@ietf.org list" <ietf@ietf.org>, "lisp@ietf.org list" <lisp@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Nov 2012 10:18:17 -0000

Hi Dino,

> George:
>> Maybe this is something you could come to an RIR meeting and present =
on or discuss? We've got an APNIC/APRICOT coming up early in 2013 and I =
am sure you'd be welcomed to submit some content. Its good to talk about =
these things.

+1

Let's make it official :-)

It would be very good to discuss this idea in the RIR communities. I =
think both the LISP community and the RIR communities can learn from =
each other. As co-chair of the RIPE Address Policy Working Group I would =
really appreciate it if you could come to the next RIPE meeting to =
discuss this. I'll make sure that there is a slot on the working group =
agenda. RIPE 66 will take place from 13-17 May 2013 at the Burlington =
Hotel in Dublin.

Thanks,
Sander


From aservin@lacnic.net  Fri Nov 16 02:51:12 2012
Return-Path: <aservin@lacnic.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B6D6E21F852D; Fri, 16 Nov 2012 02:51:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.745
X-Spam-Level: 
X-Spam-Status: No, score=-0.745 tagged_above=-999 required=5 tests=[AWL=-1.655, BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, HOST_EQ_DIALUP=0.862, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RDNS_DYNAMIC=0.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 L843Wz7MXWfZ; Fri, 16 Nov 2012 02:51:11 -0800 (PST)
Received: from mail.lacnic.net.uy (mail.lacnic.net.uy [IPv6:2001:13c7:7001:4000::3]) by ietfa.amsl.com (Postfix) with ESMTP id 0DA8921F862D; Fri, 16 Nov 2012 02:51:10 -0800 (PST)
Received: from [192.168.1.133] (r186-48-193-143.dialup.adsl.anteldata.net.uy [186.48.193.143]) by mail.lacnic.net.uy (Postfix) with ESMTP id 68764308455; Fri, 16 Nov 2012 08:51:06 -0200 (UYST)
Message-ID: <50A61A97.9060005@lacnic.net>
Date: Fri, 16 Nov 2012 08:51:03 -0200
From: Arturo Servin <aservin@lacnic.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: Dino Farinacci <farinacci@gmail.com>
Subject: Re: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
References: <20121113144545.12836.71935.idtracker@ietfa.amsl.com> <CAKFn1SFy2+hXJLVtEpkdXfNuXA31ybmYnBFFPXj-73kb3tD+yw@mail.gmail.com> <5FCB8A98-4984-427C-9468-1DFDEBD206FD@steffann.nl> <87676878-B077-4B4C-96DC-9F755F78018A@gigix.net> <50A530E7.8@lacnic.net> <B8132154-7260-43B4-B10D-E5B95924A15D@gmail.com> <00C0245E-59D7-4552-8BB4-1C0099513D1D@steffann.nl> <D470B9D8-977F-4E8B-8EDF-7769D5773279@gmail.com> <0BC58149-A314-4AD3-80A5-DC8BF5DB0E2D@steffann.nl> <2007FD20-0EA4-4204-81A5-D9AE0201419D@gmail.com> <D40BD502-1E3A-4AAA-A040-E2E4EE83141D@steffann.nl> <8F781829-457B-4B32-B91A-46C22BC5D570@gmail.com> <37436188-2E53-40DC-839F-AC52E5CA8188@apnic.net> <766205F6-48FB-4962-9F43-EDCACC73D1DA@gmail.com> <149720A8-FC8D-4BD0-9A7A-0EB42E8CCE75@apnic.net> <EE0CED54-D440-434C-8804-05EF6419B1AD@steffann.nl>
In-Reply-To: <EE0CED54-D440-434C-8804-05EF6419B1AD@steffann.nl>
X-Enigmail-Version: 1.4.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-LACNIC.uy-MailScanner-Information: Please contact the ISP for more information
X-LACNIC.uy-MailScanner: Found to be clean
X-LACNIC.uy-MailScanner-SpamCheck: 
X-LACNIC.uy-MailScanner-From: aservin@lacnic.net
Cc: "ietf@ietf.org list" <ietf@ietf.org>, "lisp@ietf.org list" <lisp@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Nov 2012 10:51:12 -0000

Dino,

	+1 In LACNIC, may 6th to 10th 2013 in Medellin Colombia.

	I am not the policiy guy but I can get you time in the technical and
policy plenaries and assit you in the discussion.

	Also, if you plan to write some text about the allocation mechanics let
me know, I will be happy to help to review, comment and even write some
text if that is useful for lisp.

Regards,
as

On 16/11/2012 08:18, Sander Steffann wrote:
> Hi Dino,
> 
>> George:
>>> Maybe this is something you could come to an RIR meeting and present on or discuss? We've got an APNIC/APRICOT coming up early in 2013 and I am sure you'd be welcomed to submit some content. Its good to talk about these things.
> 
> +1
> 
> Let's make it official :-)
> 
> It would be very good to discuss this idea in the RIR communities. I think both the LISP community and the RIR communities can learn from each other. As co-chair of the RIPE Address Policy Working Group I would really appreciate it if you could come to the next RIPE meeting to discuss this. I'll make sure that there is a slot on the working group agenda. RIPE 66 will take place from 13-17 May 2013 at the Burlington Hotel in Dublin.
> 
> Thanks,
> Sander
> 

From aservin@lacnic.net  Fri Nov 16 02:54:20 2012
Return-Path: <aservin@lacnic.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D29321F857C for <ietf@ietfa.amsl.com>; Fri, 16 Nov 2012 02:54:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.595
X-Spam-Level: 
X-Spam-Status: No, score=-0.595 tagged_above=-999 required=5 tests=[AWL=-1.505, BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, HOST_EQ_DIALUP=0.862, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RDNS_DYNAMIC=0.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 w-6kdIoZ0b0t for <ietf@ietfa.amsl.com>; Fri, 16 Nov 2012 02:54:19 -0800 (PST)
Received: from mail.lacnic.net.uy (mail.lacnic.net.uy [IPv6:2001:13c7:7001:4000::3]) by ietfa.amsl.com (Postfix) with ESMTP id 9D85A21F8575 for <ietf@ietf.org>; Fri, 16 Nov 2012 02:54:19 -0800 (PST)
Received: from [192.168.1.133] (r186-48-193-143.dialup.adsl.anteldata.net.uy [186.48.193.143]) by mail.lacnic.net.uy (Postfix) with ESMTP id 1F83A30849C; Fri, 16 Nov 2012 08:54:20 -0200 (UYST)
Message-ID: <50A61B59.60205@lacnic.net>
Date: Fri, 16 Nov 2012 08:54:17 -0200
From: Arturo Servin <aservin@lacnic.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: John Levine <johnl@taugh.com>
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
References: <20121116032738.11495.qmail@joyce.lan>
In-Reply-To: <20121116032738.11495.qmail@joyce.lan>
X-Enigmail-Version: 1.4.5
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-LACNIC.uy-MailScanner-Information: Please contact the ISP for more information
X-LACNIC.uy-MailScanner: Found to be clean
X-LACNIC.uy-MailScanner-SpamCheck: 
X-LACNIC.uy-MailScanner-From: aservin@lacnic.net
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Nov 2012 10:54:20 -0000

On 16/11/2012 01:27, John Levine wrote:
>> 	Shall we move on?
> 
> Sure.  Since we agree that there is no way to pay for the extra costs

	I wouldn't say that we agreed on that.

	We do not want to look how to pay the extra cost, we are simply not
interested. We agree on this.


> involved in meeting in places where there are insignificant numbers of
> IETF participants, it won't happen, and we're done.
> 
> That was simple, wasn't it?
> 

	Yes, disappointing but simple.

Regards,
as

From rogerj@gmail.com  Fri Nov 16 03:57:35 2012
Return-Path: <rogerj@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1EA6921F893C; Fri, 16 Nov 2012 03:57:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.299
X-Spam-Level: 
X-Spam-Status: No, score=-3.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, 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 JPovIDKDwfLf; Fri, 16 Nov 2012 03:57:34 -0800 (PST)
Received: from mail-wi0-f178.google.com (mail-wi0-f178.google.com [209.85.212.178]) by ietfa.amsl.com (Postfix) with ESMTP id A197721F8524; Fri, 16 Nov 2012 03:57:33 -0800 (PST)
Received: by mail-wi0-f178.google.com with SMTP id hm14so1494388wib.13 for <multiple recipients>; Fri, 16 Nov 2012 03:57:32 -0800 (PST)
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 :cc:content-type; bh=HlfwgW+KVPE5fz7Uo97DepTITgjWfd8Ld9aMCN/+ZHM=; b=AoMzRppe3xOO5UunmuE9HtlRzQ9mIvA48CDrsrBMh1vOO31PyY7b3gI0a+VbBiSSED yTKzAOVKX8MuHX/ZuieDMGSIPemEq9l+KPT1JoLwa77CTZgeeH6MdVzfibp8Fofw2xPN bbIdhB1eOBF52/tAhf9MgVuykUujRVNYtV5GA+Cc1Y6t4iCDTDlW5qFaFOMTB03yR05r zz08tKv7qQBt/DEBw0WkZ696K/5IAnlyNXrvj+xIHl0F5BPmnJmcrW9ibrSiQ7ExXcFr xhuGuNugfFapjQQ5gdhLnHFK9isu8m3zKrjehd9T9WvX0F3fspL/LR+Ry5sgRLxZMVAo oDjQ==
MIME-Version: 1.0
Received: by 10.180.19.197 with SMTP id h5mr4698792wie.22.1353067052713; Fri, 16 Nov 2012 03:57:32 -0800 (PST)
Received: by 10.217.83.4 with HTTP; Fri, 16 Nov 2012 03:57:32 -0800 (PST)
In-Reply-To: <20121113144545.12836.71935.idtracker@ietfa.amsl.com>
References: <20121113144545.12836.71935.idtracker@ietfa.amsl.com>
Date: Fri, 16 Nov 2012 12:57:32 +0100
Message-ID: <CAKFn1SF4+k5gWip-WBNfbjt-qAafPbTSY8L_EBLA9Pqvbw4=kQ@mail.gmail.com>
Subject: Re: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
From: =?ISO-8859-1?Q?Roger_J=F8rgensen?= <rogerj@gmail.com>
To: ietf@ietf.org, lisp@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Nov 2012 11:57:35 -0000

On Tue, Nov 13, 2012 at 3:45 PM, The IESG <iesg-secretary@ietf.org> wrote:
>
> The IESG has received a request from the Locator/ID Separation Protocol
> WG (lisp) to consider the following document:
> - 'LISP EID Block'
>   <draft-ietf-lisp-eid-block-03.txt> as Informational RFC
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2012-11-27. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.


I think LISP is an important factor in the future of Internet and I do
support the idea of having different IP block for LISP based network.

However, I can not support the publication of this document, it has
some unclear issues that need good answers first.



Anyhow, I see two issues that need to be addressed better

1.) How should the address space be administrated, RIR structure or
something else closer to 6bone? I support the suggested idea of
discussing this part with the different RIRs to look more into how
this are going to work in practice.
And as Dino said, "No, I am not making any assumptions either way. How
allocation gets done is subject to more work." the document should
state this.




2.) The interaction between none-LISP and LISP Internet. This problem
has two sub-problems within it

a.) Why is there a need for a special LISP block. This is partly
answered in section 3.  Rationale and Intent. Is this the entire
reason?

<start copy'n'paste>
   With the current specifications, if an ITR is sending to all types of
   destinations (i.e., non-LISP destinations, LISP destinations not in
   the IPv6 EID Block, and LISP destinations in the IPv6 EID Block) the
   only way to understand whether or not to encapsulate the traffic is
   to perform a cache lookup and, in case of cache-miss, send a Map-
   Request to the mapping system.  In the meanwhile, packets can be
   dropped.
<end copy'n'paste>



b.) the routing integration between none-LISP and LISP internet, how
are that going to work?
The current document isn't clear enough on that as I see it. Are there
an assumption that some ISPs will announce the entire LISP space (/16
are mention) for free ?
If each and every EID space holder (/32 or similiar) each have to
connect to Internet and get their address space routed, then it's
nothing different than regular RIR allocated /32's.



Address these thing somehow in the document, even just mention that
it's subject for other document and I'm happy... :-)



-- 

Roger Jorgensen           | ROJO9-RIPE
rogerj@gmail.com          | - IPv6 is The Key!
http://www.jorgensen.no   | roger@jorgensen.no

From roberta.maglione@telecomitalia.it  Fri Nov 16 05:13:03 2012
Return-Path: <roberta.maglione@telecomitalia.it>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DB16121F8D0A; Fri, 16 Nov 2012 05:13:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.26
X-Spam-Level: 
X-Spam-Status: No, score=-1.26 tagged_above=-999 required=5 tests=[AWL=0.459,  BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, 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 EMP3KZ3+zAFn; Fri, 16 Nov 2012 05:13:03 -0800 (PST)
Received: from GRFEDG702BA020.telecomitalia.it (grfedg702ba020.telecomitalia.it [156.54.233.201]) by ietfa.amsl.com (Postfix) with ESMTP id AA36121F8C71; Fri, 16 Nov 2012 05:13:02 -0800 (PST)
Received: from grfhub704ba020.griffon.local (10.188.101.117) by GRFEDG702BA020.telecomitalia.it (10.188.45.101) with Microsoft SMTP Server (TLS) id 8.3.279.5; Fri, 16 Nov 2012 14:13:01 +0100
Received: from GRFMBX704BA020.griffon.local ([10.188.101.15]) by grfhub704ba020.griffon.local ([10.188.101.117]) with mapi; Fri, 16 Nov 2012 14:13:01 +0100
From: Maglione Roberta <roberta.maglione@telecomitalia.it>
To: 'Leaf Yeh' <leaf.yeh.sdo@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>
Date: Fri, 16 Nov 2012 14:13:00 +0100
Subject: RE: [Softwires] Last	Call: <draft-ietf-softwire-6rd-radius-attrib-07.txt>	(RADIUS	Attribute	for 6rd) to Proposed Standard
Thread-Topic: [Softwires] Last	Call: <draft-ietf-softwire-6rd-radius-attrib-07.txt>	(RADIUS	Attribute	for 6rd) to Proposed Standard
Thread-Index: Ac3Dea+1vtvDT4NuRzq0ZZgefRaMjQAfhzhgAADf3CA=
Message-ID: <282BBE8A501E1F4DA9C775F964BB21FE519AC44BEA@GRFMBX704BA020.griffon.local>
References: <20121115213918.3949.85119.idtracker@ietfa.amsl.com> <50a63503.848f440a.6460.6ac1@mx.google.com>
In-Reply-To: <50a63503.848f440a.6460.6ac1@mx.google.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
x-ti-disclaimer: Disclaimer1
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "softwires@ietf.org" <softwires@ietf.org>, "<dhcwg@ietf.org> WG" <dhcwg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Nov 2012 13:13:04 -0000

Hi Leaf,
> Section 3 - If the DHCP server to which the DHCP Request message was sent=
 > at time  T1 has not responded, the DHCP client enters the REBINDING stat=
e > and  attempts to contact any server.

> Per the Figure 5 in RFC2131, the above 'T1' sounds 'T2'.
(http://www.rfc-editor.org/rfc/rfc2131.txt)

Why T2?
According to section 4.4.5 of RFC 2131:
" At time T1 the client moves to RENEWING state and sends (via unicast)
   a DHCPREQUEST message to the server to extend its lease."
[..]

" If no DHCPACK arrives before time T2, the client moves to REBINDING
   state and sends (via broadcast) a DHCPREQUEST message to extend its
   lease."

The DHCPREQUEST is sent at T1, in my opinion the current text is correct.
Thanks
Regards,
Roberta

-----Original Message-----
From: softwires-bounces@ietf.org [mailto:softwires-bounces@ietf.org] On Beh=
alf Of Leaf Yeh
Sent: Friday, November 16, 2012 1:44 PM
To: ietf@ietf.org
Cc: softwires@ietf.org
Subject: Re: [Softwires] Last Call: <draft-ietf-softwire-6rd-radius-attrib-=
07.txt> (RADIUS Attribute for 6rd) to Proposed Standard

Section 3 - After the BNG responds to the user with
   an Advertise message, the user requests for a DHCP 6rd Option by
   carrying a Parameter Request option (55) [RFC2132].

Per the Figure 1 in Section 3, the above 'Advertise message' sounds the
DHCPv4 message of 'DHCPOFFER (2)'.
(http://www.iana.org/assignments/bootp-dhcp-parameters/bootp-dhcp-parameter=
s
.xml)


Section 3 - If the DHCP server to which the DHCP Request message was sent a=
t
time
   T1 has not responded, the DHCP client enters the REBINDING state and
   attempts to contact any server.

Per the Figure 5 in RFC2131, the above 'T1' sounds 'T2'.
(http://www.rfc-editor.org/rfc/rfc2131.txt)


Best Regards,
Leaf





-----Original Message-----
From: softwires-bounces@ietf.org [mailto:softwires-bounces@ietf.org] On
Behalf Of The IESG
Sent: Friday, November 16, 2012 5:39 AM
To: IETF-Announce
Cc: softwires@ietf.org
Subject: [Softwires] Last Call:
<draft-ietf-softwire-6rd-radius-attrib-07.txt> (RADIUS Attribute for 6rd) t=
o
Proposed Standard


The IESG has received a request from the Softwires WG (softwire) to conside=
r
the following document:
- 'RADIUS Attribute for 6rd'
  <draft-ietf-softwire-6rd-radius-attrib-07.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2012-11-29. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.

Abstract


   IPv6 Rapid Deployment (6rd) is one of the most popular methods to
   provide both IPv4 and IPv6 connectivity services simultaneously
   during the IPv4/IPv6 co-existing period. The Dynamic Host
   Configuration Protocol (DHCP) 6rd option has been defined to
   configure 6rd Customer Edge (CE). However, in many networks, the
   configuration information may be stored in Authentication
   Authorization and Accounting (AAA) servers while user configuration
   is mainly from Broadband Network Gateway (BNG) through DHCP protocol.
   This document defines a Remote Authentication Dial In User Service
   (RADIUS) attribute that carries 6rd configuration information from
   AAA server to BNG.






The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-softwire-6rd-radius-attrib/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-softwire-6rd-radius-attrib/ballo=
t
/


No IPR declarations have been submitted directly on this I-D.


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

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

Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle per=
sone indicate. La diffusione, copia o qualsiasi altra azione derivante dall=
a conoscenza di queste informazioni sono rigorosamente vietate. Qualora abb=
iate ricevuto questo documento per errore siete cortesemente pregati di dar=
ne immediata comunicazione al mittente e di provvedere alla sua distruzione=
, Grazie.

This e-mail and any attachments is confidential and may contain privileged =
information intended for the addressee(s) only. Dissemination, copying, pri=
nting or use by anybody else is unauthorised. If you are not the intended r=
ecipient, please delete this message and any attachments and advise the sen=
der by return e-mail, Thanks.


From carlosm3011@gmail.com  Fri Nov 16 05:25:47 2012
Return-Path: <carlosm3011@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F3AB21F8613 for <ietf@ietfa.amsl.com>; Fri, 16 Nov 2012 05:25:47 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jGrEKGJi+yfv for <ietf@ietfa.amsl.com>; Fri, 16 Nov 2012 05:25:46 -0800 (PST)
Received: from mail-yh0-f44.google.com (mail-yh0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 6684B21F860E for <ietf@ietf.org>; Fri, 16 Nov 2012 05:25:46 -0800 (PST)
Received: by mail-yh0-f44.google.com with SMTP id 56so531617yhq.31 for <ietf@ietf.org>; Fri, 16 Nov 2012 05:25:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=BaWEfIIXdCETfPMoYfyNO9OLp+8qjioV9mtdHpop2Lw=; b=0IhFMv7yJMzgWEd5L1BSNwjgKYCdvK3lpC5/WSY4uPWfAD15nsD6EGpHY+jm5PANxr Qq1kpn3d16v73j5oxJ8H+1GsconjB4+sWuFiSbWwxancvKV3qP/eeY+83/uR5rV8cqM4 w0e5KoCmUCh9osL7BIRtbUs2T3Ccd/gxLecNUoCOs9cVtCvw2UhSyxl0FkyLrIFIXPC1 qvXXpXrdNUlsldw8YPFl7uk4iVWvkps7x0zcFFFYSheOEvpehvgEExP0u9oW/u/twL98 YK/sbDnymOm+qTSXQFjNJUNZ9KV7Ina5gUENP7qRrHR9D58hwi+vRXYDl2TsMmKdugiH yz0Q==
Received: by 10.236.134.18 with SMTP id r18mr4187898yhi.45.1353072345934; Fri, 16 Nov 2012 05:25:45 -0800 (PST)
Received: from europa.local ([200.7.85.162]) by mx.google.com with ESMTPS id u21sm1451711yhl.6.2012.11.16.05.25.43 (version=SSLv3 cipher=OTHER); Fri, 16 Nov 2012 05:25:44 -0800 (PST)
Message-ID: <50A63ED8.5060802@gmail.com>
Date: Fri, 16 Nov 2012 11:25:44 -0200
From: "Carlos M. Martinez" <carlosm3011@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: John Levine <johnl@taugh.com>
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
References: <20121116032738.11495.qmail@joyce.lan>
In-Reply-To: <20121116032738.11495.qmail@joyce.lan>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Nov 2012 13:25:47 -0000

Hello,

On 11/16/12 1:27 AM, John Levine wrote:
>> 	Shall we move on?
> 
> Sure.  Since we agree that there is no way to pay for the extra costs
> involved in meeting in places where there are insignificant numbers of
> IETF participants, it won't happen, and we're done.
> 

I don't remember when I agreed with that. In fact I believe quite the
opposite holds. If there was a will there would be ways. However, what I
read here is a lot of refusal, denial and roadblocking.

I can't speak for other regions, but from ours, there are at least four
organizations which manage significant budgets, have been in the
conference organization business for more than 10 years, and which would
be very interested in having an IETF in Latin America.

The feeling I kept receiving here is that there is a kernel of IETFers
who still believe that IETF is some kind of ivory tower that exists by
itself, for itself and is self-sufficient.

Big news: this is no longer the case. For bad but, IMO, mostly for good.

The IETF is one more component of the complex ecosystem of Internet
governance. A critical one, but not the only one. If you reach out to
the balcony of the ivory tower, you will see that the IETF has plenty of
enemies, but, also plenty of friends and allies.

Moving the IETF forward will involve reaching out to other peoples,
other regions, and yes, travel farther away once in a while. I also
understand that we need to do our part in terms of fostering and
increasing the contribution of our region. I said this in an earlier
email and I stand by it.

Reach out to your friends and allies. We all want the whole
multi-stakeholder approach to succeed, we are all on the same boat and
we definitely need to move the IETF forward in order to do that.

Don't get me wrong: I get where most of this resistance is coming from,
and I sort of agree that newcomers need to prove themselves. But instead
of roadblocking and refusal I would have hoped to see something along
the lines of:

- What is a reasonable goal in terms of participation, so that having a
meeting in Latin America is actually meaningful?: "X attendees from the
region and Y people actively participating in mailing lists and
contributing text"

- After that, set the goal: "The IETF will hold a meeting in Latin
America in the next four to five years"

- What does the IETF to do that?: "The IETF needs partners to pledge X $
in sponsorship funds", or whatever else.

- Reach out to your allies in the region.

If we could agree on a basis set of participation principles, on metrics
and on development goals, we will be a much stronger organization.

regards,

~Carlos

> That was simple, wasn't it?
> 

From wesley.george@twcable.com  Fri Nov 16 05:27:08 2012
Return-Path: <wesley.george@twcable.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA48E21F8641; Fri, 16 Nov 2012 05:27:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.996
X-Spam-Level: 
X-Spam-Status: No, score=-0.996 tagged_above=-999 required=5 tests=[AWL=0.467,  BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, 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 JWoLXFhG29W1; Fri, 16 Nov 2012 05:27:08 -0800 (PST)
Received: from cdpipgw01.twcable.com (cdpipgw01.twcable.com [165.237.59.22]) by ietfa.amsl.com (Postfix) with ESMTP id DAE4621F852D; Fri, 16 Nov 2012 05:27:02 -0800 (PST)
X-SENDER-IP: 10.136.163.12
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.83,264,1352091600"; d="scan'208";a="471923801"
Received: from unknown (HELO PRVPEXHUB03.corp.twcable.com) ([10.136.163.12]) by cdpipgw01.twcable.com with ESMTP/TLS/RC4-MD5; 16 Nov 2012 08:26:42 -0500
Received: from PRVPEXVS15.corp.twcable.com ([10.136.163.78]) by PRVPEXHUB03.corp.twcable.com ([10.136.163.12]) with mapi; Fri, 16 Nov 2012 08:26:52 -0500
From: "George, Wes" <wesley.george@twcable.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Sander Steffann <sander@steffann.nl>
Date: Fri, 16 Nov 2012 08:26:50 -0500
Subject: RE: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
Thread-Topic: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
Thread-Index: Ac3D2ZB7DjJwipvuSwOSIMmOy4m4IwAIWyTA
Message-ID: <2671C6CDFBB59E47B64C10B3E0BD592303373BDF01@PRVPEXVS15.corp.twcable.com>
References: <20121113144545.12836.71935.idtracker@ietfa.amsl.com> <CAKFn1SFy2+hXJLVtEpkdXfNuXA31ybmYnBFFPXj-73kb3tD+yw@mail.gmail.com> <5FCB8A98-4984-427C-9468-1DFDEBD206FD@steffann.nl> <87676878-B077-4B4C-96DC-9F755F78018A@gigix.net>	<50A530E7.8@lacnic.net> <B8132154-7260-43B4-B10D-E5B95924A15D@gmail.com> <00C0245E-59D7-4552-8BB4-1C0099513D1D@steffann.nl> <D470B9D8-977F-4E8B-8EDF-7769D5773279@gmail.com> <0BC58149-A314-4AD3-80A5-DC8BF5DB0E2D@steffann.nl> <2007FD20-0EA4-4204-81A5-D9AE0201419D@gmail.com> <D40BD502-1E3A-4AAA-A040-E2E4EE83141D@steffann.nl> <8F781829-457B-4B32-B91A-46C22BC5D570@gmail.com> <22AD9545-DDC9-4FE9-A984-1D0E3987D02D@steffann.nl> <50A601D6.6080701@gmail.com>
In-Reply-To: <50A601D6.6080701@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: "ietf@ietf.org" <ietf@ietf.org>, Dino Farinacci <farinacci@gmail.com>, "lisp@ietf.org" <lisp@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Nov 2012 13:27:08 -0000

PiBGcm9tOiBpZXRmLWJvdW5jZXNAaWV0Zi5vcmcgW21haWx0bzppZXRmLWJvdW5jZXNAaWV0Zi5v
cmddIE9uIEJlaGFsZiBPZg0KPiBCcmlhbiBFIENhcnBlbnRlcg0KDQo+ID4gKnBsZWFzZSpwbGVh
c2UqcGxlYXNlKiBzdHVkeSB3aGF0IGhhcHBlbmVkIHRvIDZ0bzQgYW5kIHRoZQ0KPiA+IDIwMDI6
Oi8xNiBwcmVmaXggYmVmb3JlIGNvbnRpbnVpbmcgdGhpcyBkaXNjdXNzaW9uLg0KPg0KPiBUaGUg
cHJvYmxlbSB0aGVyZSB3YXMgdGhhdCB0aGUgZGVzaWduIG9mIDZ0bzQgYXNzdW1lZCwgYW5kIHJl
bGllZCBvbiwNCj4gYWx0cnVpc3RpYyBjb29wZXJhdGlvbiBiZXR3ZWVuIG9wZXJhdG9ycywgdG8g
ZW5zdXJlIHRoYXQgdGhlcmUgd2FzIGENCj4gdXNlYWJsZSByb3V0ZSB0byAyMDAyOjovMTYgKmV2
ZXJ5d2hlcmUqIGluIHRoZQ0KPiBJUHY2IG5ldHdvcmsuIFRoYXQgYXNzdW1wdGlvbiB3YXMgbmFp
dmUgYW5kIGxlZCB0byBibGFjayBob2xlcy4NCg0KW1dFR10gVGhlIG90aGVyIHByb2JsZW0gd2l0
aCA2dG80IGlzIHRoYXQgYnkgdGhlIHRpbWUgd2UgdHJpZWQgdG8gc2h1dCBpdCBkb3duIGJlY2F1
c2Ugd2UgZGV0ZXJtaW5lZCB0aGF0IGl0IHdhc24ndCB3b3JraW5nIGFjY2VwdGFibHkgYW5kL29y
IGhhZCBmYXRhbCBmbGF3cyBpbiBpdHMgZGVzaWduLCB0aGVyZSB3YXMgYSBzbWFsbCAoYnV0IGV4
dHJlbWVseSB2b2NhbCkgZ3JvdXAgb2YgcGVvcGxlIHdobyBiYXNpY2FsbHkgc2FpZCAieW91IGNh
biBoYXZlIDZ0bzQgYmFjayB3aGVuIHlvdSBwcnkgaXQgZnJvbSBteSBjb2xkLCBkZWFkIGZpbmdl
cnMhISIgLS0gcGVyaGFwcyB3ZSBjYW4ga2lsbCB0d28gYmlyZHMgd2l0aCBvbmUgc3RvbmUgaWYg
eW91IGNhbiBjb252aW5jZSB0aG9zZSBzYW1lIHBlb3BsZSB0byBsZXQgeW91IHJlcHVycG9zZSB0
aGUgMjAwMjo6LzE2IHNwYWNlIGZvciBMSVNQPw0KDQoqZHVja3MqIDotKQ0KDQpNb3JlIHNlcmlv
dXNseToNCg0KSSBlY2hvIHRoZSBjb25jZXJucyB0aGF0IG90aGVycyBoYXZlIHJhaXNlZCBhYm91
dCB0aGUgcXVlc3Rpb25hYmxlIGp1c3RpZmljYXRpb24gZm9yIGEgLzEyIG9yIC8xNiwgdGhlIGxp
bWl0ZWQgZGV0YWlscyBhcm91bmQgaG93IGFsbG9jYXRpb24gYW5kIG1hbmFnZW1lbnQgbWlnaHQg
d29yaywgYW5kIHRoZSByZWNvbW1lbmRhdGlvbiB0byBnbyB0YWxrIHRvIHRoZSBSSVJzIGFuZCBs
ZWFybiBob3cgYWRkcmVzcyBhbGxvY2F0aW9uIG1pZ2h0IHdvcmsgc28gdGhhdCB5b3UgY2FuIGdp
dmUgdGhlbSBoZWxwZnVsIHJlY29tbWVuZGF0aW9ucyB3aGVuIChhbmQgaWYpIGl0IGNvbWVzIHRp
bWUgdG8gd3JpdGUgUklSIHBvbGljeSB0byBtYW5hZ2UgdGhpcyBzcGFjZS4gSSdkIHJhdGhlciB0
aGlzIG5vdCBiZSBkZWZlcnJlZCB0byBhIGxhdGVyIGRvY3VtZW50LCBiZWNhdXNlIHRoZXJlIGlz
IGxpdHRsZSBpbmNlbnRpdmUgdG8gY29tcGxldGUgc3VjaCBhIGRvY3VtZW50IG9uY2UgdGhlIGFs
bG9jYXRpb24gaXMgYWxyZWFkeSBtYWRlLiBFaXRoZXIgeW91IGtub3cgaG93IHRoaXMgd2lsbCBi
ZSB1c2VkIGFuZCBjYW4gYXJ0aWN1bGF0ZSBpdCwgb3IgeW91IGRvbid0LiBJZiB5b3UgZG9uJ3Qs
IHlvdSBhcmVuJ3QgcmVhZHkgdG8gcmVxdWVzdCBpdC4NCg0KQWRkaXRpb25hbGx5OiBUaGUgTElT
UCBkb2N1bWVudHMgYXJlIGNsYXNzaWZpZWQgYXMgZXhwZXJpbWVudGFsICh0aG91Z2ggdGhpcyBv
bmUgaXMgbm90Li4uKS4gVGhlcmVmb3JlIEkgc2VlIHR3byBwb3NzaWJsZSBzb2x1dGlvbnMgdGhh
dCBkb24ndCBhcHBlYXIgdG8gaGF2ZSBiZWVuIGRpc2N1c3NlZCB5ZXQ6DQoxKSB0aGUgUklScyBo
YXZlIGV4aXN0aW5nIHBvbGljeSByZWdhcmRpbmcgZXhwZXJpbWVudHMgKGUuZy4gaHR0cHM6Ly93
d3cuYXJpbi5uZXQvcG9saWN5L25ycG0uaHRtbCNlbGV2ZW4gKS4gWW91IG1pZ2h0IGNvbnNpZGVy
IGxvb2tpbmcgYXQgdGhvc2UgcG9saWNpZXMgdG8gc2VlIGlmIGdldHRpbmcgYSBkaXJlY3QgYWxs
b2NhdGlvbiBmcm9tIG9uZSBvciBtb3JlIFJJUnMgZm9yIHlvdXIgZXhwZXJpbWVudCB3b3VsZCBi
ZSBhIHdvcmthYmxlIHNvbHV0aW9uLCByYXRoZXIgdGhhbiBsb2NraW5nIHNwYWNlIGludG8gdGhp
cyB2aWEgSUFOQS4NCjIpIFJlcXVlc3QgdGhlIHNwYWNlICh3aXRoIGltcHJvdmVtZW50cyB0byB0
aGUgcmVxdWVzdCBhcyBzdGF0ZWQgYWJvdmUgYW5kIGVsc2V3aGVyZSBpbiB0aGlzIHRocmVhZCkg
YnV0IGluY2x1ZGUgYSBzdW5zZXQgZGF0ZSBmb3IgdGhlIGFsbG9jYXRpb24gZnJvbSBJQU5BLiBJ
ZiB0aGUgZXhwZXJpbWVudCBpcyBzdWNjZXNzZnVsLCB0aGUgZXhwZWN0YXRpb24gaXMgdGhhdCB5
b3Ugd2lsbCB3cml0ZSBwcm9wb3NlZCBzdGFuZGFyZCBkcmFmdHMgcmVmaW5lIHRoZSBpbXBsZW1l
bnRhdGlvbiBhbmQgdG8gbWFrZSBpdCBub3QgZXhwZXJpbWVudGFsLCBhbmQgeW91IGNhbiBtYWtl
IHRoZSBJQU5BIGFsbG9jYXRpb24gcGVybWFuZW50IGF0IHRoZSBzYW1lIHRpbWUuIElmIHRoZSBl
eHBlcmltZW50IGlzIG5vdCBzdWNjZXNzZnVsIGFuZCB0aGlzIHNwYWNlIGlzIG5vIGxvbmdlciBu
ZWVkZWQgaW4gYSBmZXcgeWVhcnMsIHdlIGRvbid0IGhhdmUgdG8gZmlnaHQgYSBzbWFsbCB2b2Nh
bCBtaW5vcml0eSB0byBzaHV0IGl0IGRvd24uIChjLmYuIFJGQzM3MDEpLiBXaGlsZSBJJ20gKmxl
c3MqIHdvcnJpZWQgYWJvdXQgdXMgIndhc3RpbmciIElQdjYgc3BhY2UsIGl0J3Mgbm90IGluZmlu
aXRlLCBhbmQgSSdtIGhhdmluZyB2aXNpb25zIG9mIHRoZSBJUHY0IENsYXNzIEUgc3BhY2UsIHdo
ZXJlIHdlIGhhdmUgdGhpcyBzaXphYmxlIGNodW5rIG9mIGFkZHJlc3NlcyBhbGxvY2F0ZWQgZm9y
IGEgc3BlY2lhbCBwdXJwb3NlIHRoYXQgMTAgeWVhcnMgZnJvbSBub3cgY291bGQgKGFuZCBzaG91
bGQpIGJlIHVzZWQgZm9yIHNvbWV0aGluZyBlbHNlLCBhbmQgaW5lcnRpYSBtZWFucyB0aGF0IHRo
ZXkgbmV2ZXIgZG8sIGZpbGVkIHVuZGVyICJpdCBzZWVtZWQgbGlrZSBhIGdvb2QgaWRlYSBhdCB0
aGUgdGltZS4uLiINCg0KV2VzIEdlb3JnZQ0KDQpUaGlzIEUtbWFpbCBhbmQgYW55IG9mIGl0cyBh
dHRhY2htZW50cyBtYXkgY29udGFpbiBUaW1lIFdhcm5lciBDYWJsZSBwcm9wcmlldGFyeSBpbmZv
cm1hdGlvbiwgd2hpY2ggaXMgcHJpdmlsZWdlZCwgY29uZmlkZW50aWFsLCBvciBzdWJqZWN0IHRv
IGNvcHlyaWdodCBiZWxvbmdpbmcgdG8gVGltZSBXYXJuZXIgQ2FibGUuIFRoaXMgRS1tYWlsIGlz
IGludGVuZGVkIHNvbGVseSBmb3IgdGhlIHVzZSBvZiB0aGUgaW5kaXZpZHVhbCBvciBlbnRpdHkg
dG8gd2hpY2ggaXQgaXMgYWRkcmVzc2VkLiBJZiB5b3UgYXJlIG5vdCB0aGUgaW50ZW5kZWQgcmVj
aXBpZW50IG9mIHRoaXMgRS1tYWlsLCB5b3UgYXJlIGhlcmVieSBub3RpZmllZCB0aGF0IGFueSBk
aXNzZW1pbmF0aW9uLCBkaXN0cmlidXRpb24sIGNvcHlpbmcsIG9yIGFjdGlvbiB0YWtlbiBpbiBy
ZWxhdGlvbiB0byB0aGUgY29udGVudHMgb2YgYW5kIGF0dGFjaG1lbnRzIHRvIHRoaXMgRS1tYWls
IGlzIHN0cmljdGx5IHByb2hpYml0ZWQgYW5kIG1heSBiZSB1bmxhd2Z1bC4gSWYgeW91IGhhdmUg
cmVjZWl2ZWQgdGhpcyBFLW1haWwgaW4gZXJyb3IsIHBsZWFzZSBub3RpZnkgdGhlIHNlbmRlciBp
bW1lZGlhdGVseSBhbmQgcGVybWFuZW50bHkgZGVsZXRlIHRoZSBvcmlnaW5hbCBhbmQgYW55IGNv
cHkgb2YgdGhpcyBFLW1haWwgYW5kIGFueSBwcmludG91dC4NCg==

From jnc@mercury.lcs.mit.edu  Fri Nov 16 06:00:23 2012
Return-Path: <jnc@mercury.lcs.mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B941C21F8485; Fri, 16 Nov 2012 06:00:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.603
X-Spam-Level: 
X-Spam-Status: No, score=-6.603 tagged_above=-999 required=5 tests=[AWL=-0.004, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 NkCNJ-GrOjcD; Fri, 16 Nov 2012 06:00:23 -0800 (PST)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 3ED9921F847F; Fri, 16 Nov 2012 06:00:23 -0800 (PST)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id F2C2618C095; Fri, 16 Nov 2012 09:00:21 -0500 (EST)
To: ietf@ietf.org, lisp@ietf.org
Subject: Re: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
Message-Id: <20121116140021.F2C2618C095@mercury.lcs.mit.edu>
Date: Fri, 16 Nov 2012 09:00:21 -0500 (EST)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Nov 2012 14:00:23 -0000

    > From: <rogerj@gmail.com>

    > the routing integration between none-LISP and LISP internet, how are
    > that going to work? The current document isn't clear enough on that as
    > I see it.

The way the routing will work would take a couple of PhD theses to fully
cover (I know of one that's already underway). So it's not really a topic
that can be covered in this ID.

Adding to the complexity is that if LISP becomes widely deployed, how the
routing works will likely change over time; in the early stages, when there
are small islands of LISP, it'll be one thing; later on, when there are
islands of legacy stuff, it'll be totally different. Etc, etc.

    > Address these thing somehow in the document, even just mention that
    > it's subject for other document and I'm happy... :-)

The IETF used to have this concept of 'rough consensus and _running code_';
i.e. we tried stuff out to see if it works. When did we change into an
organization that had to have every 'i' dotted, and every 't' crossed, before
we could move an inch? (Saying 'just refer to the document where it is
covered' doesn't help, if the other document isn't written yet.)

All this ID is trying to do is allocate a rather modest chunk (~ one quarter
of one tenth of one percent - .025% - if I've done the math right) of address
space for an experiment; exactly how it will be best used, and what the best
allocation process is, is to some degree part of that experiment.

	Noel

From roberta.maglione@telecomitalia.it  Fri Nov 16 06:09:18 2012
Return-Path: <roberta.maglione@telecomitalia.it>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 03B3921F8590; Fri, 16 Nov 2012 06:09:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.336
X-Spam-Level: 
X-Spam-Status: No, score=-1.336 tagged_above=-999 required=5 tests=[AWL=0.383,  BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, 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 G+Boe+t0GLHe; Fri, 16 Nov 2012 06:09:17 -0800 (PST)
Received: from GRFEDG701BA020.telecomitalia.it (grfedg701ba020.telecomitalia.it [156.54.233.200]) by ietfa.amsl.com (Postfix) with ESMTP id 43DA221F8521; Fri, 16 Nov 2012 06:09:16 -0800 (PST)
Received: from GRFHUB702BA020.griffon.local (10.188.101.112) by GRFEDG701BA020.telecomitalia.it (10.188.45.100) with Microsoft SMTP Server (TLS) id 8.3.279.5; Fri, 16 Nov 2012 15:09:13 +0100
Received: from GRFMBX704BA020.griffon.local ([10.188.101.15]) by GRFHUB702BA020.griffon.local ([10.188.101.112]) with mapi; Fri, 16 Nov 2012 15:09:11 +0100
From: Maglione Roberta <roberta.maglione@telecomitalia.it>
To: 'Leaf Yeh' <leaf.yeh.sdo@gmail.com>, 'Sheng Jiang' <jiangsheng@huawei.com>
Date: Fri, 16 Nov 2012 15:09:11 +0100
Subject: RE: [Softwires] Last	Call: <draft-ietf-softwire-6rd-radius-attrib-07.txt>	(RADIUS	Attribute	for 6rd) to Proposed Standard
Thread-Topic: [Softwires] Last	Call: <draft-ietf-softwire-6rd-radius-attrib-07.txt>	(RADIUS	Attribute	for 6rd) to Proposed Standard
Thread-Index: Ac3Dea+1vtvDT4NuRzq0ZZgefRaMjQAfhzhgAADf3CAAARUoIAAA6biw
Message-ID: <282BBE8A501E1F4DA9C775F964BB21FE519AC44BEB@GRFMBX704BA020.griffon.local>
References: <20121115213918.3949.85119.idtracker@ietfa.amsl.com> <50a63503.848f440a.6460.6ac1@mx.google.com> <282BBE8A501E1F4DA9C775F964BB21FE519AC44BEA@GRFMBX704BA020.griffon.local> <50a6465d.4b53440a.7e28.73cc@mx.google.com>
In-Reply-To: <50a6465d.4b53440a.7e28.73cc@mx.google.com>
Accept-Language: en-US, it-IT
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, it-IT
x-ti-disclaimer: Disclaimer1
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "softwires@ietf.org" <softwires@ietf.org>, "dhcwg@ietf.org" <dhcwg@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Nov 2012 14:09:18 -0000

Leaf,
In my opinion current text is fine and inline with RFC2131, while the text =
you are proposing is not completely accurate because it does not clarify "w=
hich DHCP Server" has not replied.

'If the DHCP server has not replied the
DHCPREQUEST message till T2, the DHCP client enters into the REBINDING stat=
e
and attempts to contact any possible server. '

Sheng,
 As original author of this text, what do you think?

Thanks,
Roberta

-----Original Message-----
From: Leaf Yeh [mailto:leaf.yeh.sdo@gmail.com]
Sent: Friday, November 16, 2012 2:58 PM
To: Maglione Roberta; ietf@ietf.org
Cc: softwires@ietf.org; dhcwg@ietf.org
Subject: RE: [Softwires] Last Call: <draft-ietf-softwire-6rd-radius-attrib-=
07.txt> (RADIUS Attribute for 6rd) to Proposed Standard

<Roberta> According to section 4.4.5 of RFC 2131:
" At time T1 the client moves to RENEWING state and sends (via unicast)
   a DHCPREQUEST message to the server to extend its lease."
[..]
" If no DHCPACK arrives before time T2, the client moves to REBINDING
   state and sends (via broadcast) a DHCPREQUEST message to extend its
   lease."
The DHCPREQUEST is sent at T1, in my opinion the current text is correct.
</Roberta>


Correct but not accurate. The client enters the rebinding state after T2
expired.

How about to update the text to be 'If the DHCP server has not replied the
DHCPREQUEST message till T2, the DHCP client enters into the REBINDING stat=
e
and attempts to contact any possible server. '?


Best Regards,
Leaf



-----Original Message-----
From: Maglione Roberta [mailto:roberta.maglione@telecomitalia.it]
Sent: Friday, November 16, 2012 9:13 PM
To: 'Leaf Yeh'; ietf@ietf.org
Cc: softwires@ietf.org; <dhcwg@ietf.org> WG
Subject: RE: [Softwires] Last Call:
<draft-ietf-softwire-6rd-radius-attrib-07.txt> (RADIUS Attribute for 6rd) t=
o
Proposed Standard

Hi Leaf,
> Section 3 - If the DHCP server to which the DHCP Request message was sent
> at time  T1 has not responded, the DHCP client enters the REBINDING state
> and  attempts to contact any server.

> Per the Figure 5 in RFC2131, the above 'T1' sounds 'T2'.
(http://www.rfc-editor.org/rfc/rfc2131.txt)

Why T2?
According to section 4.4.5 of RFC 2131:
" At time T1 the client moves to RENEWING state and sends (via unicast)
   a DHCPREQUEST message to the server to extend its lease."
[..]

" If no DHCPACK arrives before time T2, the client moves to REBINDING
   state and sends (via broadcast) a DHCPREQUEST message to extend its
   lease."

The DHCPREQUEST is sent at T1, in my opinion the current text is correct.
Thanks
Regards,
Roberta

-----Original Message-----
From: softwires-bounces@ietf.org [mailto:softwires-bounces@ietf.org] On
Behalf Of Leaf Yeh
Sent: Friday, November 16, 2012 1:44 PM
To: ietf@ietf.org
Cc: softwires@ietf.org
Subject: Re: [Softwires] Last Call:
<draft-ietf-softwire-6rd-radius-attrib-07.txt> (RADIUS Attribute for 6rd) t=
o
Proposed Standard

Section 3 - After the BNG responds to the user with
   an Advertise message, the user requests for a DHCP 6rd Option by
   carrying a Parameter Request option (55) [RFC2132].

Per the Figure 1 in Section 3, the above 'Advertise message' sounds the
DHCPv4 message of 'DHCPOFFER (2)'.
(http://www.iana.org/assignments/bootp-dhcp-parameters/bootp-dhcp-parameter=
s
.xml)


Section 3 - If the DHCP server to which the DHCP Request message was sent a=
t
time
   T1 has not responded, the DHCP client enters the REBINDING state and
   attempts to contact any server.

Per the Figure 5 in RFC2131, the above 'T1' sounds 'T2'.
(http://www.rfc-editor.org/rfc/rfc2131.txt)


Best Regards,
Leaf





-----Original Message-----
From: softwires-bounces@ietf.org [mailto:softwires-bounces@ietf.org] On
Behalf Of The IESG
Sent: Friday, November 16, 2012 5:39 AM
To: IETF-Announce
Cc: softwires@ietf.org
Subject: [Softwires] Last Call:
<draft-ietf-softwire-6rd-radius-attrib-07.txt> (RADIUS Attribute for 6rd) t=
o
Proposed Standard


The IESG has received a request from the Softwires WG (softwire) to conside=
r
the following document:
- 'RADIUS Attribute for 6rd'
  <draft-ietf-softwire-6rd-radius-attrib-07.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2012-11-29. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.

Abstract


   IPv6 Rapid Deployment (6rd) is one of the most popular methods to
   provide both IPv4 and IPv6 connectivity services simultaneously
   during the IPv4/IPv6 co-existing period. The Dynamic Host
   Configuration Protocol (DHCP) 6rd option has been defined to
   configure 6rd Customer Edge (CE). However, in many networks, the
   configuration information may be stored in Authentication
   Authorization and Accounting (AAA) servers while user configuration
   is mainly from Broadband Network Gateway (BNG) through DHCP protocol.
   This document defines a Remote Authentication Dial In User Service
   (RADIUS) attribute that carries 6rd configuration information from
   AAA server to BNG.






The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-softwire-6rd-radius-attrib/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-softwire-6rd-radius-attrib/ballo=
t
/


No IPR declarations have been submitted directly on this I-D.


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

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

Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle
persone indicate. La diffusione, copia o qualsiasi altra azione derivante
dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora
abbiate ricevuto questo documento per errore siete cortesemente pregati di
darne immediata comunicazione al mittente e di provvedere alla sua
distruzione, Grazie.

This e-mail and any attachments is confidential and may contain privileged
information intended for the addressee(s) only. Dissemination, copying,
printing or use by anybody else is unauthorised. If you are not the intende=
d
recipient, please delete this message and any attachments and advise the
sender by return e-mail, Thanks.


Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle per=
sone indicate. La diffusione, copia o qualsiasi altra azione derivante dall=
a conoscenza di queste informazioni sono rigorosamente vietate. Qualora abb=
iate ricevuto questo documento per errore siete cortesemente pregati di dar=
ne immediata comunicazione al mittente e di provvedere alla sua distruzione=
, Grazie.

This e-mail and any attachments is confidential and may contain privileged =
information intended for the addressee(s) only. Dissemination, copying, pri=
nting or use by anybody else is unauthorised. If you are not the intended r=
ecipient, please delete this message and any attachments and advise the sen=
der by return e-mail, Thanks.


From jmh@joelhalpern.com  Fri Nov 16 08:00:29 2012
Return-Path: <jmh@joelhalpern.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5BC7521F84DE; Fri, 16 Nov 2012 08:00:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.115
X-Spam-Level: 
X-Spam-Status: No, score=-102.115 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, MIME_8BIT_HEADER=0.3, 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 EkuQfvisapT9; Fri, 16 Nov 2012 08:00:28 -0800 (PST)
Received: from morbo.mail.tigertech.net (morbo.mail.tigertech.net [67.131.251.54]) by ietfa.amsl.com (Postfix) with ESMTP id BE1A021F8459; Fri, 16 Nov 2012 08:00:28 -0800 (PST)
Received: from mailc2.tigertech.net (mailc2.tigertech.net [208.80.4.156]) by morbo.tigertech.net (Postfix) with ESMTP id 7FC7255995C; Fri, 16 Nov 2012 08:00:28 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailc2.tigertech.net (Postfix) with ESMTP id 086D41BD1FBC; Fri, 16 Nov 2012 08:00:26 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at c2.tigertech.net
Received: from [10.10.10.104] (pool-71-161-50-174.clppva.btas.verizon.net [71.161.50.174]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailc2.tigertech.net (Postfix) with ESMTPSA id 126351BD1FCC; Fri, 16 Nov 2012 08:00:24 -0800 (PST)
Message-ID: <50A66313.9090002@joelhalpern.com>
Date: Fri, 16 Nov 2012 11:00:19 -0500
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: =?ISO-8859-1?Q?Roger_J=F8rgensen?= <rogerj@gmail.com>
Subject: Re: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
References: <20121113144545.12836.71935.idtracker@ietfa.amsl.com> <CAKFn1SF4+k5gWip-WBNfbjt-qAafPbTSY8L_EBLA9Pqvbw4=kQ@mail.gmail.com>
In-Reply-To: <CAKFn1SF4+k5gWip-WBNfbjt-qAafPbTSY8L_EBLA9Pqvbw4=kQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: ietf@ietf.org, lisp@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Nov 2012 16:00:29 -0000

It is a fair question to ask whether the allocation strategy and polices 
need to be spelled out at the time of the reservation.  Possibly we made 
the wrong call on keeping them separate.  Part of the issue is that fo 
current experimentation having the block is more important, but for 
longer term experiments, and for implications on other parties, the 
allocation policies matter more.

With regard to interworking and deployment, there are a number of 
documents that deal with that.  They discuss what the currently 
understood deployment incentives are, and what paths are currently seen. 
   (As Noel noted, this is an experiment, and one should expect that the 
actual path will be different from the expectation.)  Given that 
interworkng dives are data plane devices, altruism is clearly not a 
sufficient incentive to get this to scale, and the models do not depend 
upon that.

Yours,
Joel

On 11/16/2012 6:57 AM, Roger Jørgensen wrote:
> On Tue, Nov 13, 2012 at 3:45 PM, The IESG <iesg-secretary@ietf.org> wrote:
>>
>> The IESG has received a request from the Locator/ID Separation Protocol
>> WG (lisp) to consider the following document:
>> - 'LISP EID Block'
>>    <draft-ietf-lisp-eid-block-03.txt> as Informational RFC
>>
>> The IESG plans to make a decision in the next few weeks, and solicits
>> final comments on this action. Please send substantive comments to the
>> ietf@ietf.org mailing lists by 2012-11-27. Exceptionally, comments may be
>> sent to iesg@ietf.org instead. In either case, please retain the
>> beginning of the Subject line to allow automated sorting.
>
>
> I think LISP is an important factor in the future of Internet and I do
> support the idea of having different IP block for LISP based network.
>
> However, I can not support the publication of this document, it has
> some unclear issues that need good answers first.
>
>
>
> Anyhow, I see two issues that need to be addressed better
>
> 1.) How should the address space be administrated, RIR structure or
> something else closer to 6bone? I support the suggested idea of
> discussing this part with the different RIRs to look more into how
> this are going to work in practice.
> And as Dino said, "No, I am not making any assumptions either way. How
> allocation gets done is subject to more work." the document should
> state this.
>
>
>
>
> 2.) The interaction between none-LISP and LISP Internet. This problem
> has two sub-problems within it
>
> a.) Why is there a need for a special LISP block. This is partly
> answered in section 3.  Rationale and Intent. Is this the entire
> reason?
>
> <start copy'n'paste>
>     With the current specifications, if an ITR is sending to all types of
>     destinations (i.e., non-LISP destinations, LISP destinations not in
>     the IPv6 EID Block, and LISP destinations in the IPv6 EID Block) the
>     only way to understand whether or not to encapsulate the traffic is
>     to perform a cache lookup and, in case of cache-miss, send a Map-
>     Request to the mapping system.  In the meanwhile, packets can be
>     dropped.
> <end copy'n'paste>
>
>
>
> b.) the routing integration between none-LISP and LISP internet, how
> are that going to work?
> The current document isn't clear enough on that as I see it. Are there
> an assumption that some ISPs will announce the entire LISP space (/16
> are mention) for free ?
> If each and every EID space holder (/32 or similiar) each have to
> connect to Internet and get their address space routed, then it's
> nothing different than regular RIR allocated /32's.
>
>
>
> Address these thing somehow in the document, even just mention that
> it's subject for other document and I'm happy... :-)
>
>
>

From brian.e.carpenter@gmail.com  Fri Nov 16 08:35:41 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1127D21F8779; Fri, 16 Nov 2012 08:35:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.566
X-Spam-Level: 
X-Spam-Status: No, score=-101.566 tagged_above=-999 required=5 tests=[AWL=0.125, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, 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 kcNQjVjMWTZ3; Fri, 16 Nov 2012 08:35:40 -0800 (PST)
Received: from mail-wi0-f172.google.com (mail-wi0-f172.google.com [209.85.212.172]) by ietfa.amsl.com (Postfix) with ESMTP id AE9D721F8777; Fri, 16 Nov 2012 08:35:39 -0800 (PST)
Received: by mail-wi0-f172.google.com with SMTP id hj6so1873655wib.13 for <multiple recipients>; Fri, 16 Nov 2012 08:35:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=TU1V+kSxTg6fj4LjO+FotVvXmrHWlwXUkHjUr4Asr3g=; b=Pe+O7GY4nJB0/oHTA9NqmQj/evjOjnlGJ5d+DJvEQAB8Gy4MptE3wgEglYsyhetsPw DjJHFwGkT+2F+juilKCkHBR512beVUVYsAjc6WmRcAm3eEkbhk6FpGjk82TzdEzz3Tfv +CAE1yDAN0RVSU4+2xDByma8GQaXZ0JXEoS/Ocjn280e/eZFMypa6MOdGSQHFQKbDw26 veYeynxklgBih9OrDfHoc2VaqTtoWYI/PTp411cyopY4VUWrH9NDBDmfWOLHdMCh/IPc tUkSErCuNIoYc0XiHP6q3hzwPBF1I6eyeviciovnzSlXpDclOA7D28kBxDOtKfmuzufv i3cg==
Received: by 10.180.101.231 with SMTP id fj7mr3282247wib.4.1353083738698; Fri, 16 Nov 2012 08:35:38 -0800 (PST)
Received: from [192.168.1.65] (host-2-102-216-111.as13285.net. [2.102.216.111]) by mx.google.com with ESMTPS id gz3sm1447499wib.2.2012.11.16.08.35.36 (version=SSLv3 cipher=OTHER); Fri, 16 Nov 2012 08:35:37 -0800 (PST)
Message-ID: <50A66B67.5000609@gmail.com>
Date: Fri, 16 Nov 2012 16:35:51 +0000
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: "Joel M. Halpern" <jmh@joelhalpern.com>
Subject: Re: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
References: <20121113144545.12836.71935.idtracker@ietfa.amsl.com>	<CAKFn1SF4+k5gWip-WBNfbjt-qAafPbTSY8L_EBLA9Pqvbw4=kQ@mail.gmail.com> <50A66313.9090002@joelhalpern.com>
In-Reply-To: <50A66313.9090002@joelhalpern.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org, lisp@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Nov 2012 16:35:41 -0000

Joel,

On 16/11/2012 16:00, Joel M. Halpern wrote:
...
> With regard to interworking and deployment, there are a number of
> documents that deal with that.  They discuss what the currently
> understood deployment incentives are, and what paths are currently seen.
>   (As Noel noted, this is an experiment, and one should expect that the
> actual path will be different from the expectation.)  Given that
> interworkng dives are data plane devices, altruism is clearly not a
> sufficient incentive to get this to scale, and the models do not depend
> upon that.

My concern with this allocation request was not about scaling
but about black holes. What are the incentives for operators not
very interested in LISP to carry the routes that make it work?
That's the root of many of the problems with 6to4 (and, I think,
many of the problems of the MBONE, for those with long memories).

Regards
    Brian

From farinacci@gmail.com  Thu Nov 15 10:26:06 2012
Return-Path: <farinacci@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 76A3421F8467; Thu, 15 Nov 2012 10:26:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.449
X-Spam-Level: 
X-Spam-Status: No, score=-3.449 tagged_above=-999 required=5 tests=[AWL=0.150,  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 A01A0wl7kCYF; Thu, 15 Nov 2012 10:26:04 -0800 (PST)
Received: from mail-pa0-f44.google.com (mail-pa0-f44.google.com [209.85.220.44]) by ietfa.amsl.com (Postfix) with ESMTP id 3E9A721F8428; Thu, 15 Nov 2012 10:26:04 -0800 (PST)
Received: by mail-pa0-f44.google.com with SMTP id fb11so1278033pad.31 for <multiple recipients>; Thu, 15 Nov 2012 10:25:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=rf0IPjmMHLRM/S6zNnDAfmV7Ac+E30fN0kMcL0M4x5Q=; b=OWnr3Q2V7EdpVXUmtmM/7OmssLBUdqLOFPYpPaLvOzdoJusvN9fB6VJ/9keyjNomCU FNlzbLb4GL02afObRaVnSgooNH/X0z4P6xuTNbU19KyMO+t50wAtd2cyFJXHpA2NzpbD jTTGOrKNFHPIzp6jcHKB6WxaltgwrnkXHsB5mgRZQ1JobI4WoGKDY0pY5ViYa2ursCWI +JMoe+/GduNyGoFaZC8nUMQq1WTHZQN8AoN1A/oeRsGP/j4YNV0uGwaA1Lrh6+bOGCy4 i1gwn+I/yXqPymc21iPvQDzCbBocxC7Z5R9I+DgtXjDyfp9cxvw42Lm/Le+XG7/ji6OO /TQg==
Received: by 10.66.73.102 with SMTP id k6mr5610000pav.22.1353003959927; Thu, 15 Nov 2012 10:25:59 -0800 (PST)
Received: from sjc-vpn5-1054.cisco.com (128-107-239-233.cisco.com. [128.107.239.233]) by mx.google.com with ESMTPS id g10sm10091212pav.9.2012.11.15.10.25.56 (version=SSLv3 cipher=OTHER); Thu, 15 Nov 2012 10:25:58 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
From: Dino Farinacci <farinacci@gmail.com>
In-Reply-To: <50A530E7.8@lacnic.net>
Date: Thu, 15 Nov 2012 10:25:56 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <B8132154-7260-43B4-B10D-E5B95924A15D@gmail.com>
References: <20121113144545.12836.71935.idtracker@ietfa.amsl.com> <CAKFn1SFy2+hXJLVtEpkdXfNuXA31ybmYnBFFPXj-73kb3tD+yw@mail.gmail.com> <5FCB8A98-4984-427C-9468-1DFDEBD206FD@steffann.nl> <87676878-B077-4B4C-96DC-9F755F78018A@gigix.net> <50A530E7.8@lacnic.net>
To: Arturo Servin <aservin@lacnic.net>
X-Mailer: Apple Mail (2.1499)
X-Mailman-Approved-At: Fri, 16 Nov 2012 08:43:07 -0800
Cc: lisp@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Nov 2012 18:26:06 -0000

> Luigi,
>=20
> On 15/11/2012 12:33, Luigi Iannone wrote:
>>=20
>> On 15 Nov. 2012, at 10:43 , Sander Steffann <sander@steffann.nl> =
wrote:
>>=20
>>> Hi,
>>>=20
>>>> I have to ask, who can request an netblock from this address space =
and
>>>> from where?
>>>> I might be blind but I couldn't find it mentioned anywhere.
>>>=20
>>> Good question. Will there be a central registry, or will parts of =
the space be delegated to i.e. LISP based ISPs?
>>>=20
>>=20
>> Hi Sander,
>>=20
>> no central registry has been ever discussed, was more about delegated =
the space to LISP ISPs.
>=20
>=20
> 	How are you going to allocate space to ISPs?

This is PI space. The registries will take portions of this space to =
allocate to end devices.  This is endpoint ID space. ISPs will continue =
to allocate addresses for LISP RLOCs. And they will have to allocate =
orders of magnitude less address space now.

> 	Who is going to track the allocations made to ISPs, how are they =
going
> to be published, what are the requirements to ask for space, what data
> needs to be registered, where I can see allocations data?

Registries will track allocations to end sites.

> 	You asked George why the document is not ready to be published. =
Well,
> the undocumented rules on how the space is going to be managed is one
> important reason IMHO.

This draft is purely a draft to REQUEST space. There will need to be a =
deployment guide on how to allocate EIDs, in general.

Dino

>=20
> Regards,
> as
> =09
>=20
>>=20
>> Luigi
>>=20
>>=20
>>> - Sander
>>>=20
>>> _______________________________________________
>>> lisp mailing list
>>> lisp@ietf.org
>>> https://www.ietf.org/mailman/listinfo/lisp
>>=20
>> _______________________________________________
>> lisp mailing list
>> lisp@ietf.org
>> https://www.ietf.org/mailman/listinfo/lisp
>>=20
> _______________________________________________
> lisp mailing list
> lisp@ietf.org
> https://www.ietf.org/mailman/listinfo/lisp


From farinacci@gmail.com  Thu Nov 15 11:27:24 2012
Return-Path: <farinacci@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B5B0C21F892B; Thu, 15 Nov 2012 11:27:24 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E5RmVd2Cn-xh; Thu, 15 Nov 2012 11:27:24 -0800 (PST)
Received: from mail-pa0-f44.google.com (mail-pa0-f44.google.com [209.85.220.44]) by ietfa.amsl.com (Postfix) with ESMTP id 1E3A721F8487; Thu, 15 Nov 2012 11:27:24 -0800 (PST)
Received: by mail-pa0-f44.google.com with SMTP id fb11so1316534pad.31 for <multiple recipients>; Thu, 15 Nov 2012 11:27:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=f7gX3VV3hpum0JQntxgjbd/BUjqCnR1htVY0RGxJxgo=; b=HGzbpjWsIQ+NHgNap/EhH5PpMhokdVs2j5ti9ov6/n+aPFDz4bCMLKiZnXaIpaXr3d 1NB/dsGMtz0rfTwL1GVclMDZA1gqr+l3RuB+5G17co6Hog1Kbk8jzsAqXv0RdRX5KX4b ZYkx4B0hAnL0/0+Dl4eZ4aARNUDNLNN4njteuXxwJf6R3SC5x6Uot3U44GfkoV+rsXpp /rsAhiqTrlKGZLc2CGmY59rKY7MmMQ7yqwCrEQwYC9gNNWh5kbL/xlBp5/5jwYlkrpI8 7kBJFbC7duxIrD5z69dKfwpc+Q2ZKg8v40tBy4xpz398xtT5BNe9qJxTQX2x1YrzVpp6 v4Vw==
Received: by 10.66.88.133 with SMTP id bg5mr5830092pab.80.1353007643819; Thu, 15 Nov 2012 11:27:23 -0800 (PST)
Received: from [192.168.1.4] (173-8-188-29-SFBA.hfc.comcastbusiness.net. [173.8.188.29]) by mx.google.com with ESMTPS id ph7sm9937211pbb.9.2012.11.15.11.27.21 (version=SSLv3 cipher=OTHER); Thu, 15 Nov 2012 11:27:23 -0800 (PST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
From: Dino Farinacci <farinacci@gmail.com>
In-Reply-To: <50A538B8.7080709@lacnic.net>
Date: Thu, 15 Nov 2012 11:27:21 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <D1AD4093-C3F7-4A35-8108-3E16639E5991@gmail.com>
References: <20121113144545.12836.71935.idtracker@ietfa.amsl.com> <CAKFn1SFy2+hXJLVtEpkdXfNuXA31ybmYnBFFPXj-73kb3tD+yw@mail.gmail.com> <5FCB8A98-4984-427C-9468-1DFDEBD206FD@steffann.nl> <87676878-B077-4B4C-96DC-9F755F78018A@gigix.net> <50A530E7.8@lacnic.net> <B8132154-7260-43B4-B10D-E5B95924A15D@gmail.com> <50A538B8.7080709@lacnic.net>
To: Arturo Servin <aservin@lacnic.net>
X-Mailer: Apple Mail (2.1499)
X-Mailman-Approved-At: Fri, 16 Nov 2012 08:43:07 -0800
Cc: lisp@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Nov 2012 19:27:24 -0000

> Dino,
>=20
> 	But who are the registries? The RIRs? Large ISPs? IANA? I think =
you
> should specify clearly either: what a registry is or that is not =
defined
> yet.

Yes, nothing has to change in terms of who and how PI addresses are =
allocated.

> 	Point taken on "This draft is purely a draft to REQUEST space. =
There
> will need to be a deployment guide on how to allocate EIDs, in =
general."
> But then it should be written somewhere in the document.

I agree the wording in the abstract and introduction should be a bit =
stronger and/or more direct.

> 	Although it could be enough only to clearly say that a =
deployment guide
> would define allocation guides in the future; for the sake of clarity
> and usefulness (now, after the space is allocated by IANA it will be
> there left unused because there is not a clearly indication how is =
going
> to be used) I would recommend to discuss how the space is going to be
> allocated.

Sure, good comment.

Dino

>=20
> Regards
> as
>=20
> =09
> On 15/11/2012 16:25, Dino Farinacci wrote:
>>> Luigi,
>>>=20
>>> On 15/11/2012 12:33, Luigi Iannone wrote:
>>>>=20
>>>> On 15 Nov. 2012, at 10:43 , Sander Steffann <sander@steffann.nl> =
wrote:
>>>>=20
>>>>> Hi,
>>>>>=20
>>>>>> I have to ask, who can request an netblock from this address =
space and
>>>>>> from where?
>>>>>> I might be blind but I couldn't find it mentioned anywhere.
>>>>>=20
>>>>> Good question. Will there be a central registry, or will parts of =
the space be delegated to i.e. LISP based ISPs?
>>>>>=20
>>>>=20
>>>> Hi Sander,
>>>>=20
>>>> no central registry has been ever discussed, was more about =
delegated the space to LISP ISPs.
>>>=20
>>>=20
>>> 	How are you going to allocate space to ISPs?
>>=20
>> This is PI space. The registries will take portions of this space to =
allocate to end devices.  This is endpoint ID space. ISPs will continue =
to allocate addresses for LISP RLOCs. And they will have to allocate =
orders of magnitude less address space now.
>>=20
>>> 	Who is going to track the allocations made to ISPs, how are they =
going
>>> to be published, what are the requirements to ask for space, what =
data
>>> needs to be registered, where I can see allocations data?
>>=20
>> Registries will track allocations to end sites.
>>=20
>>> 	You asked George why the document is not ready to be published. =
Well,
>>> the undocumented rules on how the space is going to be managed is =
one
>>> important reason IMHO.
>>=20
>> This draft is purely a draft to REQUEST space. There will need to be =
a deployment guide on how to allocate EIDs, in general.
>>=20
>> Dino
>>=20
>>>=20
>>> Regards,
>>> as
>>> =09
>>>=20
>>>>=20
>>>> Luigi
>>>>=20
>>>>=20
>>>>> - Sander
>>>>>=20
>>>>> _______________________________________________
>>>>> lisp mailing list
>>>>> lisp@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/lisp
>>>>=20
>>>> _______________________________________________
>>>> lisp mailing list
>>>> lisp@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/lisp
>>>>=20
>>> _______________________________________________
>>> lisp mailing list
>>> lisp@ietf.org
>>> https://www.ietf.org/mailman/listinfo/lisp


From pvinci@VinciConsulting.com  Thu Nov 15 12:22:04 2012
Return-Path: <pvinci@VinciConsulting.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7CAD321F8604; Thu, 15 Nov 2012 12:22:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.436
X-Spam-Level: 
X-Spam-Status: No, score=-2.436 tagged_above=-999 required=5 tests=[AWL=0.163,  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 tF8zbv894Qz8; Thu, 15 Nov 2012 12:22:00 -0800 (PST)
Received: from exchange.vinci-consulting-corp.com (exchange.vinci-consulting-corp.com [38.125.5.16]) by ietfa.amsl.com (Postfix) with ESMTP id AAA8321F85FA; Thu, 15 Nov 2012 12:21:59 -0800 (PST)
Received: from NYDC-EXCH01.vinci-consulting-corp.local ([::1]) by NYDC-EXCH01.vinci-consulting-corp.local ([::1]) with mapi id 14.02.0318.001; Thu, 15 Nov 2012 15:21:58 -0500
From: Paul Vinciguerra <pvinci@VinciConsulting.com>
To: Sander Steffann <sander@steffann.nl>, Dino Farinacci <farinacci@gmail.com>
Subject: RE: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
Thread-Topic: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
Thread-Index: AQHNw16z6nPAFQBGGECg4Vbwr2D40pfrokoA//+tu1A=
Date: Thu, 15 Nov 2012 20:21:56 +0000
Message-ID: <6E5736BD68F770449C74FBAD975F807C94AA4F0C@NYDC-EXCH01.vinci-consulting-corp.local>
References: <20121113144545.12836.71935.idtracker@ietfa.amsl.com> <CAKFn1SFy2+hXJLVtEpkdXfNuXA31ybmYnBFFPXj-73kb3tD+yw@mail.gmail.com> <5FCB8A98-4984-427C-9468-1DFDEBD206FD@steffann.nl> <87676878-B077-4B4C-96DC-9F755F78018A@gigix.net>	<50A530E7.8@lacnic.net> <B8132154-7260-43B4-B10D-E5B95924A15D@gmail.com> <00C0245E-59D7-4552-8BB4-1C0099513D1D@steffann.nl>
In-Reply-To: <00C0245E-59D7-4552-8BB4-1C0099513D1D@steffann.nl>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.10.14]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Fri, 16 Nov 2012 08:43:07 -0800
Cc: "ietf@ietf.org" <ietf@ietf.org>, "lisp@ietf.org" <lisp@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Nov 2012 20:22:04 -0000

> One thing we have to be very careful with here is that EIDs are not direc=
tly
> allocated/assigned to end sites from this block. That will cause everyone=
 to
> independently find (different) PITRs for their space, which will make a m=
ess
> of the global IPv6 routing table...
>=20
> Thanks,
> Sander
=20
I don't think that (by definition) there is any way to cleanly aggregate PI=
 space.  Legacy advertisements are going to be done by their LISP provider =
and will have to match the endpoint's PI allocations.

From farinacci@gmail.com  Thu Nov 15 13:24:20 2012
Return-Path: <farinacci@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B526121F84C4; Thu, 15 Nov 2012 13:24:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.47
X-Spam-Level: 
X-Spam-Status: No, score=-3.47 tagged_above=-999 required=5 tests=[AWL=0.129,  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 vOedzSx6UjkA; Thu, 15 Nov 2012 13:24:20 -0800 (PST)
Received: from mail-pa0-f44.google.com (mail-pa0-f44.google.com [209.85.220.44]) by ietfa.amsl.com (Postfix) with ESMTP id 2CF9121F84BA; Thu, 15 Nov 2012 13:24:20 -0800 (PST)
Received: by mail-pa0-f44.google.com with SMTP id fb11so1381767pad.31 for <multiple recipients>; Thu, 15 Nov 2012 13:24:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=kYmcTdpLPsEfAPHYGzr2ANvg1WHU/HT6u+8U4+Pxtzs=; b=uJOqAE475ibKzFyh4LEH+KGy/5ORC7Y+PqythaUmN+ljwjzUhe9NDhsloC/4K7QTlQ uEzGTyZT3NkIpO9j36N/pZTCkPWpN/wwD3IaEGAvp1pv1/0RWVQgmxF9QLEgts3uFaTp mlh5xfQVOdopug3eWRHiO+4qbZsx3VeBn8r2PpfRh1sB6Bn2lmR9XLHm8NyZfSrIZs7/ 1zrRsdoOmD1V3/20x5Iq/sgN2IfWwCXFbRX4kLe2WC0teNMTpb+fqyCrrSwf7Botm8Pn sqbRwzZT+X4NT/FfVgTtSTmkyvLzC3qAGYfnhbHk13oWvc8DTWJKsmkRXc0bht5N3Gxz DyKQ==
Received: by 10.68.248.1 with SMTP id yi1mr2869788pbc.93.1353014659904; Thu, 15 Nov 2012 13:24:19 -0800 (PST)
Received: from dhcp-10-155-59-220.cisco.com (128-107-239-234.cisco.com. [128.107.239.234]) by mx.google.com with ESMTPS id is6sm10054834pbc.55.2012.11.15.13.24.18 (version=SSLv3 cipher=OTHER); Thu, 15 Nov 2012 13:24:19 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
From: Dino Farinacci <farinacci@gmail.com>
In-Reply-To: <00C0245E-59D7-4552-8BB4-1C0099513D1D@steffann.nl>
Date: Thu, 15 Nov 2012 13:24:18 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <D470B9D8-977F-4E8B-8EDF-7769D5773279@gmail.com>
References: <20121113144545.12836.71935.idtracker@ietfa.amsl.com> <CAKFn1SFy2+hXJLVtEpkdXfNuXA31ybmYnBFFPXj-73kb3tD+yw@mail.gmail.com> <5FCB8A98-4984-427C-9468-1DFDEBD206FD@steffann.nl> <87676878-B077-4B4C-96DC-9F755F78018A@gigix.net> <50A530E7.8@lacnic.net> <B8132154-7260-43B4-B10D-E5B95924A15D@gmail.com> <00C0245E-59D7-4552-8BB4-1C0099513D1D@steffann.nl>
To: Sander Steffann <sander@steffann.nl>
X-Mailer: Apple Mail (2.1499)
X-Mailman-Approved-At: Fri, 16 Nov 2012 08:43:07 -0800
Cc: ietf@ietf.org, lisp@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Nov 2012 21:24:20 -0000

> Hi,
>=20
>>> How are you going to allocate space to ISPs?
>>=20
>> This is PI space. The registries will take portions of this space to =
allocate to end devices.
>=20
> Are you thinking about the existing RIRs here? If so: it might be a =
good idea to notify them that this is coming.

Nothing is coming. Nothing really needs to change.

But if there is anything written up to define allocation procedures, the =
RIRs can review such a document.

The main motivation for this prefix is to optimize ITRs so they know =
that a destination is in a LISP site. This COULD eliminate a mapping =
database lookup for a destination not in this range. Meaning, if a =
packet is destined to a non-EID, you may know this by inspecting the =
address rather than asking the mapping system.

>> This draft is purely a draft to REQUEST space. There will need to be =
a deployment guide on how to allocate EIDs, in general.
>=20
> And if the RIR system is used every RIR will develop its own policy =
for allocating EIDs independently (hopefully based on the =
recommendations in such a deployment guide). It will have to be very =
clear whose responsibility it is to allocate from this space, and when =
assigning responsibility it might be a good idea to make sure they =
accept that responsibility too.

Right.

> Note that I am not opposing the idea. I'm just trying to make sure =
this address space doesn't disappear into a black hole because nobody =
takes the responsibility to manage it.
>=20
> One thing we have to be very careful with here is that EIDs are not =
directly allocated/assigned to end sites from this block. That will =
cause everyone to independently find (different) PITRs for their space,

Why not?

> which will make a mess of the global IPv6 routing table...

And why do you think you need to assign PITRs per sub-block?

Dino

>=20
> Thanks,
> Sander
>=20


From farinacci@gmail.com  Thu Nov 15 13:25:40 2012
Return-Path: <farinacci@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F283E21F896C; Thu, 15 Nov 2012 13:25:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.487
X-Spam-Level: 
X-Spam-Status: No, score=-3.487 tagged_above=-999 required=5 tests=[AWL=0.113,  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 zLwXTv5ZKvVj; Thu, 15 Nov 2012 13:25:39 -0800 (PST)
Received: from mail-da0-f44.google.com (mail-da0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id 812EB21F8947; Thu, 15 Nov 2012 13:25:39 -0800 (PST)
Received: by mail-da0-f44.google.com with SMTP id h15so849384dan.31 for <multiple recipients>; Thu, 15 Nov 2012 13:25:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=oBFS7tz/G6QqiQoKH7YZ6EBcKZXZlYCChCgmv7AcgCg=; b=vbDKVXSYuku3KOSEyoQU/mkwzSS7IMtFDy8tTjQIfgQb3OnEEHbZNxlGRWUmaYceYI sZrxJW9kBZ1RCHYmHEt5OnyRZV5SF6zPHJhJWprp83EnJYnyR0ie9E4CnMPwYdUgVgoj 1YYAVSmiR/4hNN5Vgb69SJhP9pXD43GfFY9qujwSGUZnxKcn2DS5UtpV1o7fBeRNAo6l XHflhTuIjMVz3Pnc8hj9+3Yy3l3toEZVHAvrfMyYovLYV9vLIwOkE4FQkBu9xnprLXXg JLb1r2Y7rVQ2BU2Kb/+ma+0vxP0NBOEzCTcFU37kW/S2ZJTrxOyQb51H0GiJPTwXXUXS +Dlg==
Received: by 10.66.74.40 with SMTP id q8mr6877478pav.29.1353014738896; Thu, 15 Nov 2012 13:25:38 -0800 (PST)
Received: from dhcp-10-155-59-220.cisco.com (128-107-239-234.cisco.com. [128.107.239.234]) by mx.google.com with ESMTPS id pv8sm10062749pbc.26.2012.11.15.13.25.36 (version=SSLv3 cipher=OTHER); Thu, 15 Nov 2012 13:25:37 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
From: Dino Farinacci <farinacci@gmail.com>
In-Reply-To: <6E5736BD68F770449C74FBAD975F807C94AA4F0C@NYDC-EXCH01.vinci-consulting-corp.local>
Date: Thu, 15 Nov 2012 13:25:35 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <5958FE99-2975-490A-9F51-E56CFD9D384B@gmail.com>
References: <20121113144545.12836.71935.idtracker@ietfa.amsl.com> <CAKFn1SFy2+hXJLVtEpkdXfNuXA31ybmYnBFFPXj-73kb3tD+yw@mail.gmail.com> <5FCB8A98-4984-427C-9468-1DFDEBD206FD@steffann.nl> <87676878-B077-4B4C-96DC-9F755F78018A@gigix.net>	<50A530E7.8@lacnic.net> <B8132154-7260-43B4-B10D-E5B95924A15D@gmail.com> <00C0245E-59D7-4552-8BB4-1C0099513D1D@steffann.nl> <6E5736BD68F770449C74FBAD975F807C94AA4F0C@NYDC-EXCH01.vinci-consulting-corp.local>
To: Paul Vinciguerra <pvinci@VinciConsulting.com>
X-Mailer: Apple Mail (2.1499)
X-Mailman-Approved-At: Fri, 16 Nov 2012 08:43:07 -0800
Cc: Sander Steffann <sander@steffann.nl>, "ietf@ietf.org" <ietf@ietf.org>, "lisp@ietf.org" <lisp@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Nov 2012 21:25:40 -0000

And you do not want to tie addresses to topological entities. Or you =
will lose the mobility capabilities that Locator/ID separation can =
bring.

Dino

On Nov 15, 2012, at 12:21 PM, Paul Vinciguerra =
<pvinci@VinciConsulting.com> wrote:

>> One thing we have to be very careful with here is that EIDs are not =
directly
>> allocated/assigned to end sites from this block. That will cause =
everyone to
>> independently find (different) PITRs for their space, which will make =
a mess
>> of the global IPv6 routing table...
>>=20
>> Thanks,
>> Sander
>=20
> I don't think that (by definition) there is any way to cleanly =
aggregate PI space.  Legacy advertisements are going to be done by their =
LISP provider and will have to match the endpoint's PI allocations.


From farinacci@gmail.com  Thu Nov 15 13:36:44 2012
Return-Path: <farinacci@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 968D621F89C7; Thu, 15 Nov 2012 13:36:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.499
X-Spam-Level: 
X-Spam-Status: No, score=-3.499 tagged_above=-999 required=5 tests=[AWL=0.100,  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 G1QevkXJL9Me; Thu, 15 Nov 2012 13:36:43 -0800 (PST)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id CAA4421F89AC; Thu, 15 Nov 2012 13:36:43 -0800 (PST)
Received: by mail-pb0-f44.google.com with SMTP id uo1so1461375pbc.31 for <multiple recipients>; Thu, 15 Nov 2012 13:36:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=kt8KG1sCA0zCl0XqVj8kuWUC/8V/bxmBKXC4N31GIpM=; b=wSb7FY6WQdOBzx0d40kVDCsHzpD3ebvZMEnb/OydWWgxlKQBX5YocxfBjZ/Tgusqvo KAsIIP4nx8sOl4TEZHUGyBahnKJZhE15/KWKxRKdGDfuLnOU8xXohdlKuF7xUvYq79XP Y3fj811poW3hPSTlde4rOtOdp65VIkuIPVFAFCAduHqEi71uK1nE7gNJtK8uvZDKRUQi KfojqFg/pMMdaJbDjeSMyUOxoQ4DhlSDpYWpQ7ooBNjb/D4XMaK7cEhaz4gKSBUW54UM On2rAS/Dp3MFxFD3f/sdX7zPMhPpCp+M1vqW7tfkqpAdqTLH9WT+Tzu1mE9Wy1VfpooL 08/A==
Received: by 10.66.87.34 with SMTP id u2mr6686117paz.82.1353015400161; Thu, 15 Nov 2012 13:36:40 -0800 (PST)
Received: from dhcp-10-155-59-220.cisco.com (128-107-239-234.cisco.com. [128.107.239.234]) by mx.google.com with ESMTPS id m7sm10307372paz.3.2012.11.15.13.36.39 (version=SSLv3 cipher=OTHER); Thu, 15 Nov 2012 13:36:39 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
From: Dino Farinacci <farinacci@gmail.com>
In-Reply-To: <0BC58149-A314-4AD3-80A5-DC8BF5DB0E2D@steffann.nl>
Date: Thu, 15 Nov 2012 13:36:38 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <2007FD20-0EA4-4204-81A5-D9AE0201419D@gmail.com>
References: <20121113144545.12836.71935.idtracker@ietfa.amsl.com> <CAKFn1SFy2+hXJLVtEpkdXfNuXA31ybmYnBFFPXj-73kb3tD+yw@mail.gmail.com> <5FCB8A98-4984-427C-9468-1DFDEBD206FD@steffann.nl> <87676878-B077-4B4C-96DC-9F755F78018A@gigix.net> <50A530E7.8@lacnic.net> <B8132154-7260-43B4-B10D-E5B95924A15D@gmail.com> <00C0245E-59D7-4552-8BB4-1C0099513D1D@steffann.nl> <D470B9D8-977F-4E8B-8EDF-7769D5773279@gmail.com> <0BC58149-A314-4AD3-80A5-DC8BF5DB0E2D@steffann.nl>
To: Sander Steffann <sander@steffann.nl>
X-Mailer: Apple Mail (2.1499)
X-Mailman-Approved-At: Fri, 16 Nov 2012 08:43:07 -0800
Cc: ietf@ietf.org, lisp@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Nov 2012 21:36:44 -0000

> Hi Dino,
>=20
>> Nothing is coming. Nothing really needs to change.
>>=20
>> But if there is anything written up to define allocation procedures, =
the RIRs can review such a document.
>>=20
>> The main motivation for this prefix is to optimize ITRs so they know =
that a destination is in a LISP site. This COULD eliminate a mapping =
database lookup for a destination not in this range. Meaning, if a =
packet is destined to a non-EID, you may know this by inspecting the =
address rather than asking the mapping system.
>=20
> I don't agree. For example: I'm using regular space for LISP EIDs now, =
so you can't assume that if it's not in this block that it's not in the =
mapping system...

That is why I capitalized "COULD".

>>>> This draft is purely a draft to REQUEST space. There will need to =
be a deployment guide on how to allocate EIDs, in general.
>>>=20
>>> And if the RIR system is used every RIR will develop its own policy =
for allocating EIDs independently (hopefully based on the =
recommendations in such a deployment guide). It will have to be very =
clear whose responsibility it is to allocate from this space, and when =
assigning responsibility it might be a good idea to make sure they =
accept that responsibility too.
>>=20
>> Right.
>>=20
>>> Note that I am not opposing the idea. I'm just trying to make sure =
this address space doesn't disappear into a black hole because nobody =
takes the responsibility to manage it.
>>>=20
>>> One thing we have to be very careful with here is that EIDs are not =
directly allocated/assigned to end sites from this block. That will =
cause everyone to independently find (different) PITRs for their space,
>>=20
>> Why not?
>=20
> Because the RIR communities will probably just refuse to allocate from =
this space if it means that all those routes end up in the BGP table... =
They are already plenty of people that don't like regular PI policies...

You have all the PITRs in the world advertise only the one /12 into =
underlying routing.

>>> which will make a mess of the global IPv6 routing table...
>>=20
>> And why do you think you need to assign PITRs per sub-block?
>=20
> I hope that is not necessary, but if addresses are assigned to =
end-sites directly in a PI-like way then who is going to provide PITR =
services for the users? Someone has to pay the bandwidth cost for =
operating=20

PITR services are provide for non-LISP sources to send to these sites. =
If you have a well-known defined /12 that all PITRs advertise, then when =
you allocate sub-blocks, you don't have to change, reconfigure, or touch =
the 1000s of PITRs deployed.

> a PITR... And the users of that space want reliability, so they are =
not going to rely on the goodwill of some unknown 3rd parties. There is =
too much bad experience with 2002::/16 for that.

We do that all the time on the Internet unless you sent this email on a =
source-route to me. ;-)

> If you see another way that I am missing please let me know! I want =
this to work, I just don't see how...
> - Sander

Dino



From farinacci@gmail.com  Thu Nov 15 14:04:26 2012
Return-Path: <farinacci@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C2AF21F8A01; Thu, 15 Nov 2012 14:04:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.509
X-Spam-Level: 
X-Spam-Status: No, score=-3.509 tagged_above=-999 required=5 tests=[AWL=0.090,  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 CnrDYFXGqkxz; Thu, 15 Nov 2012 14:04:25 -0800 (PST)
Received: from mail-pa0-f44.google.com (mail-pa0-f44.google.com [209.85.220.44]) by ietfa.amsl.com (Postfix) with ESMTP id 9B97521F8A00; Thu, 15 Nov 2012 14:04:24 -0800 (PST)
Received: by mail-pa0-f44.google.com with SMTP id fb11so1403017pad.31 for <multiple recipients>; Thu, 15 Nov 2012 14:04:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=g7EI6xNgiJc2oLUr3sPpaj4LLvny9ThftO7XV0utpcY=; b=KjwpzrOIWBs4wy1Ag+l+o1IEqzZNc91e6NaLS/62FjP+QWHW9858nF6VewUBlLXoOj iiZpHUGnrgd4noj3bRFmMUKZ7BNlw5XeYsxMzOtq8cTyyz31OvT1x4tec9QDhI56u1Ux JCZIKwqQXd5znv4AJV8Fo/i5ROMPuE1Fme9xt8ZFU+bU6MLYe5vR92ck4I8mYUSwW6II ckVNsWgBm3pGlN3r1GONSM/e+F5ass0rsF2sUb6ke7ZqiVmj3U5ZzerrR04L0UR1UBue XCEzlJWJcL1UcCt+8SNKOTzaDlGmFZ3xJecUxRcCL9PArsuahQzDexkMNDcNtguufTTg +kaA==
Received: by 10.68.200.10 with SMTP id jo10mr9005881pbc.45.1353017064305; Thu, 15 Nov 2012 14:04:24 -0800 (PST)
Received: from dhcp-10-155-59-220.cisco.com (128-107-239-233.cisco.com. [128.107.239.233]) by mx.google.com with ESMTPS id b6sm10325433pav.33.2012.11.15.14.04.22 (version=SSLv3 cipher=OTHER); Thu, 15 Nov 2012 14:04:23 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
From: Dino Farinacci <farinacci@gmail.com>
In-Reply-To: <D40BD502-1E3A-4AAA-A040-E2E4EE83141D@steffann.nl>
Date: Thu, 15 Nov 2012 14:04:22 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <8F781829-457B-4B32-B91A-46C22BC5D570@gmail.com>
References: <20121113144545.12836.71935.idtracker@ietfa.amsl.com> <CAKFn1SFy2+hXJLVtEpkdXfNuXA31ybmYnBFFPXj-73kb3tD+yw@mail.gmail.com> <5FCB8A98-4984-427C-9468-1DFDEBD206FD@steffann.nl> <87676878-B077-4B4C-96DC-9F755F78018A@gigix.net> <50A530E7.8@lacnic.net> <B8132154-7260-43B4-B10D-E5B95924A15D@gmail.com> <00C0245E-59D7-4552-8BB4-1C0099513D1D@steffann.nl> <D470B9D8-977F-4E8B-8EDF-7769D5773279@gmail.com> <0BC58149-A314-4AD3-80A5-DC8BF5DB0E2D@steffann.nl> <2007FD20-0EA4-4204-81A5-D9AE0201419D@gmail.com> <D40BD502-1E3A-4AAA-A040-E2E4EE83141D@steffann.nl>
To: Sander Steffann <sander@steffann.nl>
X-Mailer: Apple Mail (2.1499)
X-Mailman-Approved-At: Fri, 16 Nov 2012 08:43:07 -0800
Cc: ietf@ietf.org, lisp@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Nov 2012 22:04:26 -0000

> Hi,
>=20
>>>> The main motivation for this prefix is to optimize ITRs so they =
know that a destination is in a LISP site. This COULD eliminate a =
mapping database lookup for a destination not in this range. Meaning, if =
a packet is destined to a non-EID, you may know this by inspecting the =
address rather than asking the mapping system.
>>>=20
>>> I don't agree. For example: I'm using regular space for LISP EIDs =
now, so you can't assume that if it's not in this block that it's not in =
the mapping system...
>>=20
>> That is why I capitalized "COULD".
>=20
> Ok :-)
>=20
> But I think it comes down to
>  COULD ignore that certain EIDs are in the mapping system and always =
route them legacy-style

No, I don't think so. You just avoided doing LISP to the destination =
site that wants multi-homing.

> I wouldn't agree with
>  COULD know if certain addresses are EIDs or not by looking at the =
prefix
> because any address space can be used as EIDs now. Or are you =
proposing to deprecate the use of all other address space as EIDs?

You can configure a device to be more restrictive. And this would be the =
case in the non-capital I internet.

>>> Because the RIR communities will probably just refuse to allocate =
from this space if it means that all those routes end up in the BGP =
table... They are already plenty of people that don't like regular PI =
policies...
>>=20
>> You have all the PITRs in the world advertise only the one /12 into =
underlying routing.
>=20
> ROFL. No sorry, that's not going to work

I'm sorry, it can work and people will WANT to do this. Infrastructure =
providers do want to attract traffic.

> a) they would have to pay all the bandwidth cost for users of that EID =
space that they have no business relation with

If you have enough PITRs spread around the Internet, it works no =
differently than a set of boxes at a public inter-connect that =
advertises the same prefix (to say google).

> b) as a user of that EID space I would be at the mercy of PITR =
operators that I don't even know

You are at the mercy of a lot of infrastructure components today. This =
is no different. You are at the mercy of your DNS server, are you not? =
It is the same thing. So let's not make things more complicated.

> c) See all the arguments about why 6to4 is unreliable. They'll apply =
here too

Then you deploy an ITR at your site. You will want to for other reasons, =
so you kill the problem you think you have.

>>>>> which will make a mess of the global IPv6 routing table...
>>>>=20
>>>> And why do you think you need to assign PITRs per sub-block?
>>>=20
>>> I hope that is not necessary, but if addresses are assigned to =
end-sites directly in a PI-like way then who is going to provide PITR =
services for the users? Someone has to pay the bandwidth cost for =
operating=20
>>=20
>> PITR services are provide for non-LISP sources to send to these =
sites. If you have a well-known defined /12 that all PITRs advertise, =
then when you allocate sub-blocks, you don't have to change, =
reconfigure, or touch the 1000s of PITRs deployed.
>=20
> What makes you think that all those PITRs will pay the cost for =
routing all that traffic?

Pay the cost? The cost is the bandwidth that is already provision to =
come into those boxes. And infrastructure providers do want to attract =
traffic.

>>> a PITR... And the users of that space want reliability, so they are =
not going to rely on the goodwill of some unknown 3rd parties. There is =
too much bad experience with 2002::/16 for that.
>>=20
>> We do that all the time on the Internet unless you sent this email on =
a source-route to me. ;-)
>=20
> No, sorry. I now pay my ISP to make sure my connectivity works. In =
your example I'm going to rely on some unknown PETR for outbound traffic =
and on whatever PITR is closest to the other side for my inbound

Don't change the context of this discussion. We are talking PITRs. PETRs =
are something completely different.

> traffic. I might be able to control the PETR, but not the PITR because =
that depends on the routing from the other side. We have been here =
before with 2002::/16. Don't repeat that huge mistake!
>=20
> - Sander

This is now off topic. The draft has nothing to do with PITR deployment.

Dino


From farinacci@gmail.com  Thu Nov 15 22:24:13 2012
Return-Path: <farinacci@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6984421F84DD; Thu, 15 Nov 2012 22:24:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.517
X-Spam-Level: 
X-Spam-Status: No, score=-3.517 tagged_above=-999 required=5 tests=[AWL=0.082,  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 F3OnXuaejydj; Thu, 15 Nov 2012 22:24:12 -0800 (PST)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id 4E5C821F8522; Thu, 15 Nov 2012 22:24:12 -0800 (PST)
Received: by mail-pb0-f44.google.com with SMTP id uo1so1724833pbc.31 for <multiple recipients>; Thu, 15 Nov 2012 22:24:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=Cf0mDqTfJxuYXvRwAsKszpjDa7N75lUwPrtiRResaI8=; b=NDuFq07PW3jhOq473zCMWXcrNPmYR5dRLTgUSuiJE+Kk7VB7F9Va+QiDWFBgrrJXyA zt33SWf2Cs12HJdRGa02PN8+yQ3OaiWzhAdobMoNqTnTF2qaB3YEe7JYmlZthAJShyyx BPNDkq1eRj6gaQba/ycme588iq82Jhrwjk4EHxJstivG+AYWbL/EbjbLw7GXuiXuDVmy O2yeA8HkSw6RpcON5/0v87vvRrz3PrKWpI4NoBLRceyLAaYYpg0pMBH5GIZ4RF9GR/Nv 4ZxmfkVWYmZj5Yg0joww0sfFumK1bios40cEpSc3EGY85Dl20gWe0Lw6NKrczLhUULyj D2Ng==
Received: by 10.66.85.134 with SMTP id h6mr10052689paz.36.1353047051916; Thu, 15 Nov 2012 22:24:11 -0800 (PST)
Received: from sjc-vpn5-144.cisco.com (128-107-239-233.cisco.com. [128.107.239.233]) by mx.google.com with ESMTPS id c1sm545245pav.23.2012.11.15.22.24.08 (version=SSLv3 cipher=OTHER); Thu, 15 Nov 2012 22:24:09 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
From: Dino Farinacci <farinacci@gmail.com>
In-Reply-To: <37436188-2E53-40DC-839F-AC52E5CA8188@apnic.net>
Date: Thu, 15 Nov 2012 22:24:08 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <766205F6-48FB-4962-9F43-EDCACC73D1DA@gmail.com>
References: <20121113144545.12836.71935.idtracker@ietfa.amsl.com> <CAKFn1SFy2+hXJLVtEpkdXfNuXA31ybmYnBFFPXj-73kb3tD+yw@mail.gmail.com> <5FCB8A98-4984-427C-9468-1DFDEBD206FD@steffann.nl> <87676878-B077-4B4C-96DC-9F755F78018A@gigix.net> <50A530E7.8@lacnic.net> <B8132154-7260-43B4-B10D-E5B95924A15D@gmail.com> <00C0245E-59D7-4552-8BB4-1C0099513D1D@steffann.nl> <D470B9D8-977F-4E8B-8EDF-7769D5773279@gmail.com> <0BC58149-A314-4AD3-80A5-DC8BF5DB0E2D@steffann.nl> <2007FD20-0EA4-4204-81A5-D9AE0201419D@gmail.com> <D40BD502-1E3A-4AAA-A040-E2E4EE83141D@steffann.nl> <8F781829-457B-4B32-B91A-46C22BC5D570@gmail.com> <37436188-2E53-40DC-839F-AC52E5CA8188@apnic.net>
To: George Michaelson <ggm+ap-lists@apnic.net>
X-Mailer: Apple Mail (2.1499)
X-Mailman-Approved-At: Fri, 16 Nov 2012 08:43:07 -0800
Cc: "ietf@ietf.org list" <ietf@ietf.org>, lisp@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Nov 2012 06:24:13 -0000

> Dino, to come back on topic. I understand the drafts purpose is to =
request a block of IPv6 address be delegated for this specific purpose, =
from IANA. The request is to the IAB. So, its a request for =
architectural aspects of addressing, facing an experiment.

Sure.

> a /12 is a very large amount of space. This demands rigour in the =
process to apply, even a reservation requires a sense of why, and =
justification. "we think its about right" isn't appropriate and the =
document needs more work to specify why a 16, and why a /12, and what =
the implications are of eg a smaller allocation under a /16 reservation, =
or some other size (a /32 even, for which there are both precedents, in =
experimental allocations, and an existing process inside the RIR address =
management framework).

Okay.

> Secondly, you appear to assume these allocations to EID can simply use =
current RIR practices. The problem is that you need to understand what =
needs-based and justification means in process terms: Hostmasters in the =
RIR system try very hard not to be placed in a position of making =
arbitrary subjective decisions: they have processes which are designed =
to ask for objective justifications to specify why an allocation should =
take place, and at what scale. Those objective criteria face addresses =
as addresses. not EID.

No, I am not making any assumptions either way. How allocation gets done =
is subject to more work.

> For an example: IPv6 address allocation process currently is =
implemented using sparse allocation (binary chop with some =
modifications) in the APNIC region. This maximises space around =
allocations to equalise the distribution of free blocks such that the =
commons, the unallocated space, remains as usefully large as possible =
and when the next binary stride is entered, there is some understanding =
its going to be applied in common to all occupants of that region of =
space (in terms of the size of hole around them, which is not a =
reservation per se, but provides for risk-management of future growth to =
the largest extent).

There is no special semantics of EIDs that require you to change this. =
EIDs are just addresses that do not get injected into the underlying =
routing system. Other than that, they are just like any other address an =
RIR allocates.

> We're really quite proud of sparse: its extended the life of the /12 =
we occupy quite markedly. What impact will EID have on this? Is sparse =
an appropriate allocation engine to use for EID? What if eg you have =
expectations of almost-geographic aspects of address management in EID. =
Doesn't that require documentation as a process? And, you may be =
specifying a cost on the RIR system, to engineer support for the new =
allocation logic. If it doesn't logically fit in sparse allocation, we =
need to know. And we need to know why.

What Joel said.

> EID are not going to be used like 'normal' addresses. So, the normal =
justifications don't look entirely

Define how a 'normal address" is used.

> appropriate to me from 10,000ft. The document needs to say "maybe we =
need to understand the allocation processes that the RIR should =
objectively apply" or maybe you need to step outside of draft space and =
engage inside the RIR policy process and seek a global policy which can =
document the process.

The working decided that this draft is solely for request purposes. We =
could use help from RIRs to write a document on how to allocate EIDs. =
But I am pretty sure it would look like documents that already exist.

I don't understand why you think they look different or need to be =
treated differently. So you have to do the explaining.  ;-)

> To ask for an IANA allocation without having undertaken this process =
looks wrong to me. So, I stand by my concern the document isn't ready =
for IETF last call: it hasn't addressed substantive issues around the =
process and expectations of address/registry function, to manage the =
/16, and it hasn't documented the basis of asking for a /16 in the first =
place, or a /12 reservation.

Here is a real world example we have been using on the LISP beta =
network. It is so simple that it really needs no more explanation than =
what I am going to explain below:

(1) We have 2610:00d0::/32 allocated for EIDs.
(2) Each site on the LISP beta network gets a /48 out of that.
(3) Each site xTRs register their /48 with the mapping system using =
RLOCs that are PA addresses they use to attach to the Internet.

That is it. So I am not getting why there are so many issues. Can't we =
keep this simple and experiment please?

Dino

>=20
> cheers
>=20
> -George


From leaf.yeh.sdo@gmail.com  Fri Nov 16 04:43:49 2012
Return-Path: <leaf.yeh.sdo@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E70821F8779; Fri, 16 Nov 2012 04:43:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.556
X-Spam-Level: 
X-Spam-Status: No, score=-3.556 tagged_above=-999 required=5 tests=[AWL=0.043,  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 jJpq3Sv7aklO; Fri, 16 Nov 2012 04:43:48 -0800 (PST)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id 6C22F21F84BB; Fri, 16 Nov 2012 04:43:48 -0800 (PST)
Received: by mail-pb0-f44.google.com with SMTP id uo1so1937142pbc.31 for <multiple recipients>; Fri, 16 Nov 2012 04:43:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type:content-transfer-encoding:x-mailer :thread-index:content-language; bh=DnwKaKxPA9f354wAEa8c2nwqqvB83iXnCK4UyXeBCTY=; b=CkUypkZ+cufflVacXnauI1JtHab/QTUWsgWakm5hj/nqZ7sJXn09WtONYCsso7RaPd gUzbKtFtSG3LrA+x5/Sw0ViGxJFi0TP6q+9PgtXWjgWCttn42bqgHIMAkqkU9/W+vHAh qRDK9eqpzMXa6A5Bu+OCodM+MjYXzRiDSO5KXGvHlefPaNaoDY/DL479WJ9AJ6S7crVZ jveX1eD4c2zf8ljsSZH5+95K3NIv2fwpit/pWZik2/7rOchxgUpxkL0iQXAgzZZ0c6NE CK0z+SWz0aI3kNMcd/H5t9NvvgqYAzMxQNAxCCi1Fo057aFXqsfJtDufXas7L734BRqL Evvg==
Received: by 10.68.216.234 with SMTP id ot10mr8913771pbc.26.1353069828152; Fri, 16 Nov 2012 04:43:48 -0800 (PST)
Received: from lst9242355d22a ([14.153.105.155]) by mx.google.com with ESMTPS id se4sm1195770pbb.13.2012.11.16.04.43.43 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 16 Nov 2012 04:43:47 -0800 (PST)
From: "Leaf Yeh" <leaf.yeh.sdo@gmail.com>
To: <ietf@ietf.org>
References: <20121115213918.3949.85119.idtracker@ietfa.amsl.com>
In-Reply-To: <20121115213918.3949.85119.idtracker@ietfa.amsl.com>
Subject: RE: [Softwires] Last Call:	<draft-ietf-softwire-6rd-radius-attrib-07.txt>	(RADIUS	Attribute for 6rd) to Proposed Standard
Date: Fri, 16 Nov 2012 20:43:47 +0800
Message-ID: <50a63503.848f440a.6460.6ac1@mx.google.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac3Dea+1vtvDT4NuRzq0ZZgefRaMjQAfhzhg
Content-Language: zh-cn
X-Mailman-Approved-At: Fri, 16 Nov 2012 08:43:07 -0800
Cc: softwires@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Nov 2012 12:43:49 -0000

Section 3 - After the BNG responds to the user with 
   an Advertise message, the user requests for a DHCP 6rd Option by 
   carrying a Parameter Request option (55) [RFC2132].

Per the Figure 1 in Section 3, the above 'Advertise message' sounds the
DHCPv4 message of 'DHCPOFFER (2)'.
(http://www.iana.org/assignments/bootp-dhcp-parameters/bootp-dhcp-parameters
.xml)


Section 3 - If the DHCP server to which the DHCP Request message was sent at
time 
   T1 has not responded, the DHCP client enters the REBINDING state and 
   attempts to contact any server.

Per the Figure 5 in RFC2131, the above 'T1' sounds 'T2'.
(http://www.rfc-editor.org/rfc/rfc2131.txt)


Best Regards,
Leaf





-----Original Message-----
From: softwires-bounces@ietf.org [mailto:softwires-bounces@ietf.org] On
Behalf Of The IESG
Sent: Friday, November 16, 2012 5:39 AM
To: IETF-Announce
Cc: softwires@ietf.org
Subject: [Softwires] Last Call:
<draft-ietf-softwire-6rd-radius-attrib-07.txt> (RADIUS Attribute for 6rd) to
Proposed Standard


The IESG has received a request from the Softwires WG (softwire) to consider
the following document:
- 'RADIUS Attribute for 6rd'
  <draft-ietf-softwire-6rd-radius-attrib-07.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2012-11-29. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.

Abstract


   IPv6 Rapid Deployment (6rd) is one of the most popular methods to
   provide both IPv4 and IPv6 connectivity services simultaneously
   during the IPv4/IPv6 co-existing period. The Dynamic Host
   Configuration Protocol (DHCP) 6rd option has been defined to
   configure 6rd Customer Edge (CE). However, in many networks, the
   configuration information may be stored in Authentication
   Authorization and Accounting (AAA) servers while user configuration
   is mainly from Broadband Network Gateway (BNG) through DHCP protocol.
   This document defines a Remote Authentication Dial In User Service
   (RADIUS) attribute that carries 6rd configuration information from
   AAA server to BNG.






The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-softwire-6rd-radius-attrib/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-softwire-6rd-radius-attrib/ballot
/


No IPR declarations have been submitted directly on this I-D.


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


From pvinci@VinciConsulting.com  Fri Nov 16 05:06:05 2012
Return-Path: <pvinci@VinciConsulting.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 915AD21F850D; Fri, 16 Nov 2012 05:06:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.304
X-Spam-Level: 
X-Spam-Status: No, score=-2.304 tagged_above=-999 required=5 tests=[AWL=-0.005, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
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 tCfX7ih0gDHS; Fri, 16 Nov 2012 05:06:05 -0800 (PST)
Received: from exchange.vinci-consulting-corp.com (exchange.vinci-consulting-corp.com [38.125.5.16]) by ietfa.amsl.com (Postfix) with ESMTP id D69DC21F84E4; Fri, 16 Nov 2012 05:06:04 -0800 (PST)
Received: from NYDC-EXCH01.vinci-consulting-corp.local ([::1]) by NYDC-EXCH01.vinci-consulting-corp.local ([::1]) with mapi id 14.02.0318.001; Fri, 16 Nov 2012 08:06:03 -0500
From: Paul Vinciguerra <pvinci@VinciConsulting.com>
To: =?iso-8859-1?Q?Roger_J=F8rgensen?= <rogerj@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>, "lisp@ietf.org" <lisp@ietf.org>
Subject: RE: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
Thread-Topic: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
Thread-Index: AQHNw/GsxGi1EUnc4EWrahCjLHXJF5fsY22w
Date: Fri, 16 Nov 2012 13:06:02 +0000
Message-ID: <6E5736BD68F770449C74FBAD975F807C94AA6DA4@NYDC-EXCH01.vinci-consulting-corp.local>
References: <20121113144545.12836.71935.idtracker@ietfa.amsl.com> <CAKFn1SF4+k5gWip-WBNfbjt-qAafPbTSY8L_EBLA9Pqvbw4=kQ@mail.gmail.com>
In-Reply-To: <CAKFn1SF4+k5gWip-WBNfbjt-qAafPbTSY8L_EBLA9Pqvbw4=kQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.10.14]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Fri, 16 Nov 2012 08:43:07 -0800
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Nov 2012 13:06:05 -0000

So, I had originally thought that the reason for this was to change the cha=
racteristics of a new flow with a cache-hit from the ..!!! that we see to a=
 !!!!!

But even if you know that the destination is an EID, you still need to look=
up the RLOCs, so how does this help?  If the destination is a non-LISP endp=
oint, and there is a cache-miss, isn't the packet forwarded to the destinat=
ion, hoping that the packet can be delivered unencapsulated because it is n=
ot and EID, or that there is a legacy aggregate being announced that knows =
the destination to deliver the encapsulated packet until the xTR's cache po=
pulates?=20

Section 3 states:

By defining an IPv6 EID Block [, it] is possible to configure the router so
   to natively forward all packets that have not a destination address
   in the block, without performing any lookup whatsoever.

This reads as if the intent is to set a policy that would only allow LISP e=
ncapsulation to IPv6 destinations within this new block and to remove the e=
xisting ability to encapsulate to existing v6 EID's in the DDT.  The implic=
ation to me is that if I have existing v6 space, I must provide legacy tran=
sit through my own PxTR's, almost as a second class citizen as I will be as=
sured a suboptimal path.

Do I have this wrong?   =20


From johnl@iecc.com  Fri Nov 16 05:17:38 2012
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1002521F8628 for <ietf@ietfa.amsl.com>; Fri, 16 Nov 2012 05:17:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, 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 42JMthXsdek7 for <ietf@ietfa.amsl.com>; Fri, 16 Nov 2012 05:17:37 -0800 (PST)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id DC74E21F8613 for <ietf@ietf.org>; Fri, 16 Nov 2012 05:17:36 -0800 (PST)
Received: (qmail 74680 invoked from network); 16 Nov 2012 13:17:34 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:vbr-info:user-agent:cleverness; s=123b7.50a63cee.k1211; bh=9GVIlGpSwbnRXjkksHQEuFouG9i0Tg2EKHq0Or+N60g=; b=dwHsci+qJofWk4Mtb8dmRGc2rtpiGXlpXVnh2XUQUogYSDG5vXG0RHA82KzK8ztVWUo01BW6UrUZL1tINiEMhzU0anTE0NNYrYLgJ2F62o55Bo8/zxuTpoTIyisNJ8KIZtOk1+KhQa8zvZHYCOOK01XrcjG8iidB8Nyj9WseII8=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Received: (ofmipd 127.0.0.1); 16 Nov 2012 13:17:12 -0000
Date: 16 Nov 2012 08:17:33 -0500
Message-ID: <alpine.BSF.2.00.1211160817110.33123@joyce.lan>
From: "John R. Levine" <johnl@iecc.com>
To: "Arturo Servin" <aservin@lacnic.net>
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
In-Reply-To: <50A61B59.60205@lacnic.net>
References: <20121116032738.11495.qmail@joyce.lan> <50A61B59.60205@lacnic.net>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Mailman-Approved-At: Fri, 16 Nov 2012 08:43:06 -0800
Cc: John Levine <johnl@taugh.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Nov 2012 13:17:38 -0000

>> Sure.  Since we agree that there is no way to pay for the extra costs
>
> 	I wouldn't say that we agreed on that.
>
> 	We do not want to look how to pay the extra cost, we are simply not
> interested. We agree on this.

Oh, sorry, I didn't realize this was a purely hypothetical argument. 
Never mind.

Regards,
John Levine, johnl@iecc.com, Primary Perpetrator of "The Internet for Dummies",
Please consider the environment before reading this e-mail. http://jl.ly

From leaf.yeh.sdo@gmail.com  Fri Nov 16 05:57:52 2012
Return-Path: <leaf.yeh.sdo@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E555321F8769; Fri, 16 Nov 2012 05:57:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.669
X-Spam-Level: 
X-Spam-Status: No, score=-3.669 tagged_above=-999 required=5 tests=[AWL=-0.070, 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 bEiJ3z0p3ASn; Fri, 16 Nov 2012 05:57:51 -0800 (PST)
Received: from mail-pa0-f44.google.com (mail-pa0-f44.google.com [209.85.220.44]) by ietfa.amsl.com (Postfix) with ESMTP id B30CF21F8661; Fri, 16 Nov 2012 05:57:51 -0800 (PST)
Received: by mail-pa0-f44.google.com with SMTP id fb11so1900640pad.31 for <multiple recipients>; Fri, 16 Nov 2012 05:57:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type:content-transfer-encoding:x-mailer :thread-index:content-language; bh=s9DkzeQ7c91TGu2rh5aAyXdJlulnUeUzz1AhpAk6ZyA=; b=RCZB5hJoNF6HwfKBXjoGjk9yzES1e0nGFtCEmq8zByF8k/D/dzjslvNAd698U83DqJ FZInyR2IqOdgYYZC/ZIxy8PHJimwscGmppIwBuFbfKXaYMIZ5gaRuqcZJPh036lTW6dS yjMuiSon8pe9L0KGt/I8d6eLtpZw3A+TV8set/5HvfIRuwrP1V3/xCryQBYDHssvzfK4 wD3X/EAGxjpxkREhJSq4E2Cg4vrRBGJHb+rw0cH2FlwkLtD+Gzv4i+YjDTIjokX1tEXr P00rhEqttFvQT+e06VYvajob73fiF9AenE6Rx4tbFIHczHRNJjOpCzIpJTEXc8gmSEnW gVqA==
Received: by 10.68.234.201 with SMTP id ug9mr9438910pbc.63.1353074270985; Fri, 16 Nov 2012 05:57:50 -0800 (PST)
Received: from lst9242355d22a ([14.153.105.155]) by mx.google.com with ESMTPS id o11sm1280720pby.8.2012.11.16.05.57.41 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 16 Nov 2012 05:57:49 -0800 (PST)
From: "Leaf Yeh" <leaf.yeh.sdo@gmail.com>
To: "'Maglione Roberta'" <roberta.maglione@telecomitalia.it>, <ietf@ietf.org>
References: <20121115213918.3949.85119.idtracker@ietfa.amsl.com> <50a63503.848f440a.6460.6ac1@mx.google.com> <282BBE8A501E1F4DA9C775F964BB21FE519AC44BEA@GRFMBX704BA020.griffon.local>
In-Reply-To: <282BBE8A501E1F4DA9C775F964BB21FE519AC44BEA@GRFMBX704BA020.griffon.local>
Subject: RE: [Softwires] Last	Call:	<draft-ietf-softwire-6rd-radius-attrib-07.txt>	(RADIUS	Attribute	for 6rd) to Proposed Standard
Date: Fri, 16 Nov 2012 21:57:43 +0800
Message-ID: <50a6465d.4b53440a.7e28.73cc@mx.google.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac3Dea+1vtvDT4NuRzq0ZZgefRaMjQAfhzhgAADf3CAAARUoIA==
Content-Language: zh-cn
X-Mailman-Approved-At: Fri, 16 Nov 2012 08:43:07 -0800
Cc: softwires@ietf.org, dhcwg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Nov 2012 13:57:53 -0000

<Roberta> According to section 4.4.5 of RFC 2131:
" At time T1 the client moves to RENEWING state and sends (via unicast)
   a DHCPREQUEST message to the server to extend its lease."
[..]
" If no DHCPACK arrives before time T2, the client moves to REBINDING
   state and sends (via broadcast) a DHCPREQUEST message to extend its
   lease."
The DHCPREQUEST is sent at T1, in my opinion the current text is correct.
</Roberta>


Correct but not accurate. The client enters the rebinding state after T2
expired. 

How about to update the text to be 'If the DHCP server has not replied the
DHCPREQUEST message till T2, the DHCP client enters into the REBINDING state
and attempts to contact any possible server. '?


Best Regards,
Leaf



-----Original Message-----
From: Maglione Roberta [mailto:roberta.maglione@telecomitalia.it] 
Sent: Friday, November 16, 2012 9:13 PM
To: 'Leaf Yeh'; ietf@ietf.org
Cc: softwires@ietf.org; <dhcwg@ietf.org> WG
Subject: RE: [Softwires] Last Call:
<draft-ietf-softwire-6rd-radius-attrib-07.txt> (RADIUS Attribute for 6rd) to
Proposed Standard

Hi Leaf,
> Section 3 - If the DHCP server to which the DHCP Request message was sent
> at time  T1 has not responded, the DHCP client enters the REBINDING state
> and  attempts to contact any server.

> Per the Figure 5 in RFC2131, the above 'T1' sounds 'T2'.
(http://www.rfc-editor.org/rfc/rfc2131.txt)

Why T2?
According to section 4.4.5 of RFC 2131:
" At time T1 the client moves to RENEWING state and sends (via unicast)
   a DHCPREQUEST message to the server to extend its lease."
[..]

" If no DHCPACK arrives before time T2, the client moves to REBINDING
   state and sends (via broadcast) a DHCPREQUEST message to extend its
   lease."

The DHCPREQUEST is sent at T1, in my opinion the current text is correct.
Thanks
Regards,
Roberta

-----Original Message-----
From: softwires-bounces@ietf.org [mailto:softwires-bounces@ietf.org] On
Behalf Of Leaf Yeh
Sent: Friday, November 16, 2012 1:44 PM
To: ietf@ietf.org
Cc: softwires@ietf.org
Subject: Re: [Softwires] Last Call:
<draft-ietf-softwire-6rd-radius-attrib-07.txt> (RADIUS Attribute for 6rd) to
Proposed Standard

Section 3 - After the BNG responds to the user with
   an Advertise message, the user requests for a DHCP 6rd Option by
   carrying a Parameter Request option (55) [RFC2132].

Per the Figure 1 in Section 3, the above 'Advertise message' sounds the
DHCPv4 message of 'DHCPOFFER (2)'.
(http://www.iana.org/assignments/bootp-dhcp-parameters/bootp-dhcp-parameters
.xml)


Section 3 - If the DHCP server to which the DHCP Request message was sent at
time
   T1 has not responded, the DHCP client enters the REBINDING state and
   attempts to contact any server.

Per the Figure 5 in RFC2131, the above 'T1' sounds 'T2'.
(http://www.rfc-editor.org/rfc/rfc2131.txt)


Best Regards,
Leaf





-----Original Message-----
From: softwires-bounces@ietf.org [mailto:softwires-bounces@ietf.org] On
Behalf Of The IESG
Sent: Friday, November 16, 2012 5:39 AM
To: IETF-Announce
Cc: softwires@ietf.org
Subject: [Softwires] Last Call:
<draft-ietf-softwire-6rd-radius-attrib-07.txt> (RADIUS Attribute for 6rd) to
Proposed Standard


The IESG has received a request from the Softwires WG (softwire) to consider
the following document:
- 'RADIUS Attribute for 6rd'
  <draft-ietf-softwire-6rd-radius-attrib-07.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2012-11-29. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.

Abstract


   IPv6 Rapid Deployment (6rd) is one of the most popular methods to
   provide both IPv4 and IPv6 connectivity services simultaneously
   during the IPv4/IPv6 co-existing period. The Dynamic Host
   Configuration Protocol (DHCP) 6rd option has been defined to
   configure 6rd Customer Edge (CE). However, in many networks, the
   configuration information may be stored in Authentication
   Authorization and Accounting (AAA) servers while user configuration
   is mainly from Broadband Network Gateway (BNG) through DHCP protocol.
   This document defines a Remote Authentication Dial In User Service
   (RADIUS) attribute that carries 6rd configuration information from
   AAA server to BNG.






The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-softwire-6rd-radius-attrib/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-softwire-6rd-radius-attrib/ballot
/


No IPR declarations have been submitted directly on this I-D.


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

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

Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle
persone indicate. La diffusione, copia o qualsiasi altra azione derivante
dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora
abbiate ricevuto questo documento per errore siete cortesemente pregati di
darne immediata comunicazione al mittente e di provvedere alla sua
distruzione, Grazie.

This e-mail and any attachments is confidential and may contain privileged
information intended for the addressee(s) only. Dissemination, copying,
printing or use by anybody else is unauthorised. If you are not the intended
recipient, please delete this message and any attachments and advise the
sender by return e-mail, Thanks.


From jmh@joelhalpern.com  Fri Nov 16 09:26:57 2012
Return-Path: <jmh@joelhalpern.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 697EC21F858E; Fri, 16 Nov 2012 09:26:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.253
X-Spam-Level: 
X-Spam-Status: No, score=-102.253 tagged_above=-999 required=5 tests=[AWL=0.012, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, 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 ty1RC+ay3Lw4; Fri, 16 Nov 2012 09:26:57 -0800 (PST)
Received: from morbo.mail.tigertech.net (morbo.mail.tigertech.net [67.131.251.54]) by ietfa.amsl.com (Postfix) with ESMTP id 01AFF21F84FF; Fri, 16 Nov 2012 09:26:57 -0800 (PST)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) by morbo.tigertech.net (Postfix) with ESMTP id E734A558350; Fri, 16 Nov 2012 09:26:55 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id AC0EB1C0928; Fri, 16 Nov 2012 09:26:54 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [10.10.10.104] (pool-71-161-50-174.clppva.btas.verizon.net [71.161.50.174]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id E78291C0751; Fri, 16 Nov 2012 09:26:53 -0800 (PST)
Message-ID: <50A67758.8000001@joelhalpern.com>
Date: Fri, 16 Nov 2012 12:26:48 -0500
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
References: <20121113144545.12836.71935.idtracker@ietfa.amsl.com>	<CAKFn1SF4+k5gWip-WBNfbjt-qAafPbTSY8L_EBLA9Pqvbw4=kQ@mail.gmail.com> <50A66313.9090002@joelhalpern.com> <50A66B67.5000609@gmail.com>
In-Reply-To: <50A66B67.5000609@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org, lisp@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Nov 2012 17:26:57 -0000

Why does any operator have a reason to carr any routes other than their 
paying customers?  Because it provides connectivity for their customers.
If we get this block allocaed, then it results in 1 extra routing entry 
in the global routing table to support LISP inter-working.
An entry that some of their customers may use, whether the operator 
carrying it knows that or not.

In fact, it would take significant extra work for the operator to 
somehow block this aggregate.

If LISP fails, this is a small cost to find out.
If LISP succeeds, this results in significant reduction in core tabl 
sizes for everyone.

Yours,
Joel

On 11/16/2012 11:35 AM, Brian E Carpenter wrote:
> Joel,
>
> On 16/11/2012 16:00, Joel M. Halpern wrote:
> ...
>> With regard to interworking and deployment, there are a number of
>> documents that deal with that.  They discuss what the currently
>> understood deployment incentives are, and what paths are currently seen.
>>    (As Noel noted, this is an experiment, and one should expect that the
>> actual path will be different from the expectation.)  Given that
>> interworkng dives are data plane devices, altruism is clearly not a
>> sufficient incentive to get this to scale, and the models do not depend
>> upon that.
>
> My concern with this allocation request was not about scaling
> but about black holes. What are the incentives for operators not
> very interested in LISP to carry the routes that make it work?
> That's the root of many of the problems with 6to4 (and, I think,
> many of the problems of the MBONE, for those with long memories).
>
> Regards
>      Brian
>

From sm@resistor.net  Fri Nov 16 09:37:19 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 32A3521F8956 for <ietf@ietfa.amsl.com>; Fri, 16 Nov 2012 09:37:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.503
X-Spam-Level: 
X-Spam-Status: No, score=-102.503 tagged_above=-999 required=5 tests=[AWL=0.096, 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 I6bEaue7NBM9 for <ietf@ietfa.amsl.com>; Fri, 16 Nov 2012 09:37:13 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 31B8C21F8872 for <ietf@ietf.org>; Fri, 16 Nov 2012 09:37:13 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id qAGHakgZ013119; Fri, 16 Nov 2012 09:36:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1353087411; bh=F8x6cfrIToi4IeJFaIWUyPUACG6XeQFQFqwHu5ANPjM=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=FzwYLDcCyrU3Ocbm523wEIrc3AE3G2/LxLgDwq8vH7H7rwsCd3yhwlMwz2qnMMxxo 0C148mNeIGV99/QU6RgYPx70dP7xiyRV4uZXL6/UwkUUEL9kNzkMwWXwVD1FQ4JVZy l4vrI4yLo5HqXvD/UdqBz8J3NV/v9YwkgDQqgOyk=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1353087411; i=@resistor.net; bh=F8x6cfrIToi4IeJFaIWUyPUACG6XeQFQFqwHu5ANPjM=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=dWVPTSCpaJPEZoKCNDzKJdk4+8EoLGM8wrnsy6pktPCVNMwlIeeYs8MhF5QGrBvEq 2tsqsoq6gX9fk8IfScIAeuOhaYfAn+q6xEqR842c1VVOoS/OPgWb+EzYRNJsJmRGrK /WtUDvlwm+B/4VuXgP5j7UGLDMvvLUp5vKroKKtY=
Message-Id: <6.2.5.6.2.20121116091244.0adda3a0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 16 Nov 2012 09:36:02 -0800
To: Terry Manderson <terry.manderson@icann.org>
From: SM <sm@resistor.net>
Subject: Re: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
In-Reply-To: <50A66B67.5000609@gmail.com>
References: <20121113144545.12836.71935.idtracker@ietfa.amsl.com> <CAKFn1SF4+k5gWip-WBNfbjt-qAafPbTSY8L_EBLA9Pqvbw4=kQ@mail.gmail.com> <50A66313.9090002@joelhalpern.com> <50A66B67.5000609@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Nov 2012 17:37:19 -0000

Hi Terry,

I posted a message [1] about draft-ietf-lisp-eid-block-03 and asked 
about the write-up.  Is there a write-up for 
draft-ietf-lisp-eid-block, and if so, where can I find it?

BTW, I don't see my comments being addressed.  Would it be possible 
to add a note for the Area Director about discontent? :-)

Regards,
-sm

1. http://www.ietf.org/mail-archive/web/ietf/current/msg75881.html


From sander@steffann.nl  Fri Nov 16 13:13:15 2012
Return-Path: <sander@steffann.nl>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1410621F8B3B; Fri, 16 Nov 2012 13:13:15 -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 6zXFBpV9So6y; Fri, 16 Nov 2012 13:13:14 -0800 (PST)
Received: from mail.sintact.nl (mail.sintact.nl [IPv6:2001:4038:0:16::7]) by ietfa.amsl.com (Postfix) with ESMTP id C11D221F8AF0; Fri, 16 Nov 2012 13:13:12 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.sintact.nl (Postfix) with ESMTP id 0477F2043; Fri, 16 Nov 2012 22:13:12 +0100 (CET)
X-Virus-Scanned: amavisd-new at mail.sintact.nl
Received: from mail.sintact.nl ([127.0.0.1]) by localhost (mail.sintact.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EvMxcuNnQb8n; Fri, 16 Nov 2012 22:12:55 +0100 (CET)
Received: from [IPv6:2a00:8640:1::ac6c:1708:e194:c8c0] (unknown [IPv6:2a00:8640:1:0:ac6c:1708:e194:c8c0]) by mail.sintact.nl (Postfix) with ESMTP id E27362013; Fri, 16 Nov 2012 22:12:54 +0100 (CET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
From: Sander Steffann <sander@steffann.nl>
In-Reply-To: <50A67758.8000001@joelhalpern.com>
Date: Fri, 16 Nov 2012 22:12:53 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <33C6C196-B881-4BAA-8E57-082B266C831A@steffann.nl>
References: <20121113144545.12836.71935.idtracker@ietfa.amsl.com>	<CAKFn1SF4+k5gWip-WBNfbjt-qAafPbTSY8L_EBLA9Pqvbw4=kQ@mail.gmail.com> <50A66313.9090002@joelhalpern.com> <50A66B67.5000609@gmail.com> <50A67758.8000001@joelhalpern.com>
To: Joel M. Halpern <jmh@joelhalpern.com>
X-Mailer: Apple Mail (2.1499)
Cc: lisp@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Nov 2012 21:13:15 -0000

Hi Joel,

> Why does any operator have a reason to carr any routes other than =
their paying customers?  Because it provides connectivity for their =
customers.
> If we get this block allocaed, then it results in 1 extra routing =
entry in the global routing table to support LISP inter-working.
> An entry that some of their customers may use, whether the operator =
carrying it knows that or not.
>=20
> In fact, it would take significant extra work for the operator to =
somehow block this aggregate.
>=20
> If LISP fails, this is a small cost to find out.
> If LISP succeeds, this results in significant reduction in core tabl =
sizes for everyone.

That still assumes the altruistic routing of the prefix. And I am afraid =
that if the usage of this block gets a bad reputation that all LISP =
usage will share that reputation. I really like LISP but I am still not =
convinced that it's a good idea. If we can find a way to get the EID =
prefix routed in a reliable way then I would love it!

I really care about LISP and I am afraid that: people see unreliable =
routing for EID /16 =3D> assume LISP is unreliable. That is why I am =
pushing so hard to get this sorted out.

Hmmm. What about the following strategy:
- Start with the EID prefix being handed out like PI
  - Either through the RIRs if they are willing to take the =
responsibility
  - Or from a separate registry
- Some altruistic /16 PITRs might show up in the global BGP table
- A holders of a (assume) /48 from the EID prefix can arrange PITRs for =
their own space
  - And announce it as a separate route in the global BGP table (for =
now)
  - Keep the routing and reliability under their own control
- If the experiment is a success we advise ISPs to:
  - Install their own PITRs for the /16
  - Filter out the /48s at their border

The filtering of the more-specifics once they have their own PITRs will =
make sure that they use those PITRs and that they will use the most =
optimal path to the locators as soon as possible. It will also keep =
their routing table smaller. If enough big transit providers offer /16 =
PITRs to their customers then the more-specifics might be filtered on a =
larger scale.

So, summary:

The ways to reach a PITR would be
a) Run your own PITR (big networks, LISP users)
b) Use one from your transit(s) (smaller networks that don't have their =
own)
c) Use an altruistic one as last resort

As long as (a) and (b) aren't a reality the LISP users who don't want to =
rely on (c) can run/rent/etc a PITR for their own space. I think the =
routing community would really appreciate it if all those more-specific =
routes would be temporary until wide deployment of (a) and (b) make them =
unnecessary.

And if this doesn't become a success we have a bunch of /48 prefixes to =
the separate PITRs in the BGP table. It won't be much, otherwise we =
would have declared success. So the risk of messing the BGP table up is =
very limited. And when can tell people: if you are bothered by those =
more-specifics in your routing table you can always deploy your own =
PITRs and filter the more-specifics at your border. That might keep =
everyone happy.

What do you think?

Thanks,
Sander


From cb.list6@gmail.com  Fri Nov 16 13:33:20 2012
Return-Path: <cb.list6@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1CEE121F852B; Fri, 16 Nov 2012 13:33:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.199
X-Spam-Level: 
X-Spam-Status: No, score=-3.199 tagged_above=-999 required=5 tests=[AWL=0.399,  BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 0yxGYFKcMb1g; Fri, 16 Nov 2012 13:33:15 -0800 (PST)
Received: from mail-la0-f44.google.com (mail-la0-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id 3E80221F84BC; Fri, 16 Nov 2012 13:33:14 -0800 (PST)
Received: by mail-la0-f44.google.com with SMTP id d3so2595260lah.31 for <multiple recipients>; Fri, 16 Nov 2012 13:33:13 -0800 (PST)
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 :cc:content-type; bh=YzbCvrcext7rdVZtAjfQBi//dQ65PoWop9at0zUSR/c=; b=JmPQ7VUdRYPmo7OWb8jyB/fZ6RbehbOYfwOXwio2rzxBVXfiyjJFWiHy7ov/QYJLCJ KrYtyWSpxAZ+CmA0YbE2OyvciYR5ozeETMq0mg5QbYHOhwzSpF/a7nc+LZBLIoT68B2C D+tANt5VsdOheb+1Bp3gZFSDwZWaGXevQ5wzt+uBgEkVG7ZkCyF+2/ZBWujwHsIZgNFj 1RkV7MWVqTOZj1lA7NSX4W5lJc75QOlEB7DN2HVcHBYh+My1y5FQHeZOR6l8XOJJVw5h xNrPtTF3S26iZRGSJyToSQ1vfoidvvuLruQjTGm5A+Wz0rTDgvExxTcArzEsTQQYeHLs oQnA==
MIME-Version: 1.0
Received: by 10.112.29.102 with SMTP id j6mr342970lbh.21.1353101593097; Fri, 16 Nov 2012 13:33:13 -0800 (PST)
Received: by 10.112.81.167 with HTTP; Fri, 16 Nov 2012 13:33:12 -0800 (PST)
Received: by 10.112.81.167 with HTTP; Fri, 16 Nov 2012 13:33:12 -0800 (PST)
In-Reply-To: <50A67758.8000001@joelhalpern.com>
References: <20121113144545.12836.71935.idtracker@ietfa.amsl.com> <CAKFn1SF4+k5gWip-WBNfbjt-qAafPbTSY8L_EBLA9Pqvbw4=kQ@mail.gmail.com> <50A66313.9090002@joelhalpern.com> <50A66B67.5000609@gmail.com> <50A67758.8000001@joelhalpern.com>
Date: Fri, 16 Nov 2012 13:33:12 -0800
Message-ID: <CAD6AjGSouE8XG5J9Xg1KBwcL7r2Nary4bVk9A4mcvJdtUp4Z6A@mail.gmail.com>
Subject: Re: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
From: Cameron Byrne <cb.list6@gmail.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
Content-Type: multipart/alternative; boundary=f46d04016815cd363804cea383c9
Cc: ietf@ietf.org, lisp@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Nov 2012 21:33:20 -0000

--f46d04016815cd363804cea383c9
Content-Type: text/plain; charset=ISO-8859-1

On Nov 16, 2012 9:27 AM, "Joel M. Halpern" <jmh@joelhalpern.com> wrote:
>
> Why does any operator have a reason to carr any routes other than their
paying customers?  Because it provides connectivity for their customers.
> If we get this block allocaed, then it results in 1 extra routing entry
in the global routing table to support LISP inter-working.
> An entry that some of their customers may use, whether the operator
carrying it knows that or not.
>
> In fact, it would take significant extra work for the operator to somehow
block this aggregate.
>
> If LISP fails, this is a small cost to find out.
> If LISP succeeds, this results in significant reduction in core tabl
sizes for everyone.
>

Not everyone. Only people who carry core tables.  That is LISP twist, it
transfers cost from a few cores to many edges. Associated pros and cons
exist.

CB
> Yours,
> Joel
>
>
> On 11/16/2012 11:35 AM, Brian E Carpenter wrote:
>>
>> Joel,
>>
>> On 16/11/2012 16:00, Joel M. Halpern wrote:
>> ...
>>>
>>> With regard to interworking and deployment, there are a number of
>>> documents that deal with that.  They discuss what the currently
>>> understood deployment incentives are, and what paths are currently seen.
>>>    (As Noel noted, this is an experiment, and one should expect that the
>>> actual path will be different from the expectation.)  Given that
>>> interworkng dives are data plane devices, altruism is clearly not a
>>> sufficient incentive to get this to scale, and the models do not depend
>>> upon that.
>>
>>
>> My concern with this allocation request was not about scaling
>> but about black holes. What are the incentives for operators not
>> very interested in LISP to carry the routes that make it work?
>> That's the root of many of the problems with 6to4 (and, I think,
>> many of the problems of the MBONE, for those with long memories).
>>
>> Regards
>>      Brian
>>

--f46d04016815cd363804cea383c9
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<p dir=3D"ltr"><br>
On Nov 16, 2012 9:27 AM, &quot;Joel M. Halpern&quot; &lt;<a href=3D"mailto:=
jmh@joelhalpern.com">jmh@joelhalpern.com</a>&gt; wrote:<br>
&gt;<br>
&gt; Why does any operator have a reason to carr any routes other than thei=
r paying customers? =A0Because it provides connectivity for their customers=
.<br>
&gt; If we get this block allocaed, then it results in 1 extra routing entr=
y in the global routing table to support LISP inter-working.<br>
&gt; An entry that some of their customers may use, whether the operator ca=
rrying it knows that or not.<br>
&gt;<br>
&gt; In fact, it would take significant extra work for the operator to some=
how block this aggregate.<br>
&gt;<br>
&gt; If LISP fails, this is a small cost to find out.<br>
&gt; If LISP succeeds, this results in significant reduction in core tabl s=
izes for everyone.<br>
&gt;</p>
<p dir=3D"ltr">Not everyone. Only people who carry core tables.=A0 That is =
LISP twist, it transfers cost from a few cores to many edges. Associated pr=
os and cons exist. </p>
<p dir=3D"ltr">CB<br>
&gt; Yours,<br>
&gt; Joel<br>
&gt;<br>
&gt;<br>
&gt; On 11/16/2012 11:35 AM, Brian E Carpenter wrote:<br>
&gt;&gt;<br>
&gt;&gt; Joel,<br>
&gt;&gt;<br>
&gt;&gt; On 16/11/2012 16:00, Joel M. Halpern wrote:<br>
&gt;&gt; ...<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; With regard to interworking and deployment, there are a number=
 of<br>
&gt;&gt;&gt; documents that deal with that. =A0They discuss what the curren=
tly<br>
&gt;&gt;&gt; understood deployment incentives are, and what paths are curre=
ntly seen.<br>
&gt;&gt;&gt; =A0 =A0(As Noel noted, this is an experiment, and one should e=
xpect that the<br>
&gt;&gt;&gt; actual path will be different from the expectation.) =A0Given =
that<br>
&gt;&gt;&gt; interworkng dives are data plane devices, altruism is clearly =
not a<br>
&gt;&gt;&gt; sufficient incentive to get this to scale, and the models do n=
ot depend<br>
&gt;&gt;&gt; upon that.<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; My concern with this allocation request was not about scaling<br>
&gt;&gt; but about black holes. What are the incentives for operators not<b=
r>
&gt;&gt; very interested in LISP to carry the routes that make it work?<br>
&gt;&gt; That&#39;s the root of many of the problems with 6to4 (and, I thin=
k,<br>
&gt;&gt; many of the problems of the MBONE, for those with long memories).<=
br>
&gt;&gt;<br>
&gt;&gt; Regards<br>
&gt;&gt; =A0 =A0 =A0Brian<br>
&gt;&gt;<br>
</p>

--f46d04016815cd363804cea383c9--

From ynir@checkpoint.com  Fri Nov 16 13:35:21 2012
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ACE5621F84D0 for <ietf@ietfa.amsl.com>; Fri, 16 Nov 2012 13:35:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.579
X-Spam-Level: 
X-Spam-Status: No, score=-10.579 tagged_above=-999 required=5 tests=[AWL=0.020, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 1h5UZi5P+p5Q for <ietf@ietfa.amsl.com>; Fri, 16 Nov 2012 13:35:21 -0800 (PST)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id A89D921F84BC for <ietf@ietf.org>; Fri, 16 Nov 2012 13:35:20 -0800 (PST)
Received: from IL-EX10.ad.checkpoint.com ([194.29.34.147]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id qAGLZG3R032067; Fri, 16 Nov 2012 23:35:16 +0200
X-CheckPoint: {50A6AE72-1-1B221DC2-1FFFF}
Received: from IL-EX10.ad.checkpoint.com ([169.254.2.194]) by IL-EX10.ad.checkpoint.com ([169.254.2.194]) with mapi id 14.02.0318.004; Fri, 16 Nov 2012 23:35:16 +0200
From: Yoav Nir <ynir@checkpoint.com>
To: "Carlos M. Martinez" <carlosm3011@gmail.com>
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
Thread-Topic: Newcomers [Was: Evolutionizing the IETF]
Thread-Index: AQHNwP2KazFBUP+KSLOLrbDo1lYx/JfmXhqAgAMa9wCAACh5AIAAWp4AgAAI0ACAABDUAIAAAP6AgAALd4CAABipgIAADw4AgAC8P4CAAAfMAIAAWNiAgAAetYCAACuVAIAApxsAgACIxYA=
Date: Fri, 16 Nov 2012 21:35:15 +0000
Message-ID: <4613980CFC78314ABFD7F85CC3027721018D34@IL-EX10.ad.checkpoint.com>
References: <20121116032738.11495.qmail@joyce.lan> <50A63ED8.5060802@gmail.com>
In-Reply-To: <50A63ED8.5060802@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.31.20.244]
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
x-cpdlp: 11da3cb91c6fa1476bd23497617c81577c33622282
Content-Type: text/plain; charset="us-ascii"
Content-ID: <83155A34FB1BC241B5B28E99C937CA41@ad.checkpoint.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: John Levine <johnl@taugh.com>, "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Nov 2012 21:35:21 -0000

Hi Carlos.

On Nov 16, 2012, at 3:25 PM, Carlos M. Martinez wrote:

> Hello,
>=20
> On 11/16/12 1:27 AM, John Levine wrote:
>>> 	Shall we move on?
>>=20
>> Sure.  Since we agree that there is no way to pay for the extra costs
>> involved in meeting in places where there are insignificant numbers of
>> IETF participants, it won't happen, and we're done.
>>=20
>=20
> I don't remember when I agreed with that. In fact I believe quite the
> opposite holds. If there was a will there would be ways. However, what I
> read here is a lot of refusal, denial and roadblocking.

There may be ways. But what you are suggesting requires more money. The way=
 the IETF is run now, it's a very frugal organization. Read the budget slid=
es from any meeting, those numbers are small when compared with many of the=
 organizations that participants come from. One of the great aspects of the=
 IETF's openness is that anyone can participate for the cost of an Internet=
 connection (I had my first RFC published before ever attending a meeting),=
 and for a relatively small amount (when compared to other bodies) they can=
 also attend meetings. This makes it possible for small companies and even =
individual consultants to attend, participate, and even chair working group=
s. We even have some people who are salaried employees, but for whatever re=
asons, their companies are not interested in funding them, and they pay the=
ir own way.

With increased meeting fees and/or travel budget this goes away, and the IE=
TF becomes the domain of large companies and governments. At least the meet=
ings.

> I can't speak for other regions, but from ours, there are at least four
> organizations which manage significant budgets, have been in the
> conference organization business for more than 10 years, and which would
> be very interested in having an IETF in Latin America.

Then they should propose to host a meeting. I don't think the IAOC would de=
ny them. There is the question or airfare and flight availability, but as l=
ong as the meeting is at or near a big enough hub, such as Mexico City, Rio=
 de Janeiro, Buenos Aires, or Sao Paolo, the IETF is not exactly choosy.

> Moving the IETF forward will involve reaching out to other peoples,
> other regions, and yes, travel farther away once in a while. I also
> understand that we need to do our part in terms of fostering and
> increasing the contribution of our region. I said this in an earlier
> email and I stand by it.

Yes, there are people the IETF should reach out to, people who are missing =
from our meetings and our mailing lists. But I don't think that group is de=
fined geographically. There are segments of our industry that are not repre=
sented or not represented enough in the IETF, like web developers and big w=
ebsite operators. We need some of those, regardless of where in the world t=
hey live.

Yoav


From farinacci@gmail.com  Fri Nov 16 18:19:45 2012
Return-Path: <farinacci@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC26B21F87E1; Fri, 16 Nov 2012 18:19:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.901
X-Spam-Level: 
X-Spam-Status: No, score=-2.901 tagged_above=-999 required=5 tests=[AWL=-0.698, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, 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 HR76zudq53G7; Fri, 16 Nov 2012 18:19:45 -0800 (PST)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id 69B0821F85ED; Fri, 16 Nov 2012 18:19:45 -0800 (PST)
Received: by mail-pb0-f44.google.com with SMTP id uo1so2322103pbc.31 for <multiple recipients>; Fri, 16 Nov 2012 18:19:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:x-mailer:from:subject:date :to; bh=nxqD2DppsvtAUYqVmLLkhk5b6A9YS99+ESasvATviXk=; b=ObDYvjQ/B6AnsC3Ub4A1wZUZlnrdombMj2BEbdC6BvicUA2Z7FDvnjwV1H+xGOu0W0 7IJT6PEmVhQdSi8ZVQMrgapcr4rOx1/mHONvYpLukxKFAsKjryFzmim9Yc0pwvLKYGCG ldZXTxsr+NsNX4QLk2CDOn3Rr8NwJLs80NKNmGUj3Svb+zPj5FRTlZAiJPJhTtKxxw9U AbtneqMP5sWZjMLsINI1tEiZUVKng4rRvQRCEMmfCG/wbiSlrxqmoKCt5mxrPqGMkVGG tGAaAUSSYzhvzajjiiNok7xLV/lL+SEtFm5oCDj5Jo6MaYEwFs8veNSowloeCIdZQZ+i SzCA==
Received: by 10.66.88.136 with SMTP id bg8mr17983155pab.54.1353118785170; Fri, 16 Nov 2012 18:19:45 -0800 (PST)
Received: from [192.168.1.6] (173-8-188-29-SFBA.hfc.comcastbusiness.net. [173.8.188.29]) by mx.google.com with ESMTPS id se4sm2125554pbb.13.2012.11.16.18.19.43 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 16 Nov 2012 18:19:43 -0800 (PST)
References: <20121113144545.12836.71935.idtracker@ietfa.amsl.com> <CAKFn1SF4+k5gWip-WBNfbjt-qAafPbTSY8L_EBLA9Pqvbw4=kQ@mail.gmail.com> <50A66313.9090002@joelhalpern.com> <50A66B67.5000609@gmail.com> <50A67758.8000001@joelhalpern.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <50A67758.8000001@joelhalpern.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <29234776-5E6B-4B21-9FB4-F7FA0989A6B0@gmail.com>
X-Mailer: iPhone Mail (10A525)
From: Dino Farinacci <farinacci@gmail.com>
Subject: Re: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
Date: Fri, 16 Nov 2012 18:19:42 -0800
To: "Joel M. Halpern" <jmh@joelhalpern.com>
Cc: "lisp@ietf.org" <lisp@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 17 Nov 2012 02:19:46 -0000

Good points Joel. I completely agree.=20

Dino

On Nov 16, 2012, at 9:26 AM, "Joel M. Halpern" <jmh@joelhalpern.com> wrote:

> Why does any operator have a reason to carr any routes other than their pa=
ying customers?  Because it provides connectivity for their customers.
> If we get this block allocaed, then it results in 1 extra routing entry in=
 the global routing table to support LISP inter-working.
> An entry that some of their customers may use, whether the operator carryi=
ng it knows that or not.
>=20
> In fact, it would take significant extra work for the operator to somehow b=
lock this aggregate.
>=20
> If LISP fails, this is a small cost to find out.
> If LISP succeeds, this results in significant reduction in core tabl sizes=
 for everyone.
>=20
> Yours,
> Joel
>=20
> On 11/16/2012 11:35 AM, Brian E Carpenter wrote:
>> Joel,
>>=20
>> On 16/11/2012 16:00, Joel M. Halpern wrote:
>> ...
>>> With regard to interworking and deployment, there are a number of
>>> documents that deal with that.  They discuss what the currently
>>> understood deployment incentives are, and what paths are currently seen.=

>>>   (As Noel noted, this is an experiment, and one should expect that the
>>> actual path will be different from the expectation.)  Given that
>>> interworkng dives are data plane devices, altruism is clearly not a
>>> sufficient incentive to get this to scale, and the models do not depend
>>> upon that.
>>=20
>> My concern with this allocation request was not about scaling
>> but about black holes. What are the incentives for operators not
>> very interested in LISP to carry the routes that make it work?
>> That's the root of many of the problems with 6to4 (and, I think,
>> many of the problems of the MBONE, for those with long memories).
>>=20
>> Regards
>>     Brian
>>=20
> _______________________________________________
> lisp mailing list
> lisp@ietf.org
> https://www.ietf.org/mailman/listinfo/lisp

From tjc@ecs.soton.ac.uk  Sat Nov 17 05:00:50 2012
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6520521F87D0 for <ietf@ietfa.amsl.com>; Sat, 17 Nov 2012 05:00:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.381
X-Spam-Level: 
X-Spam-Status: No, score=-2.381 tagged_above=-999 required=5 tests=[AWL=0.218,  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 tF5aS388jx4l for <ietf@ietfa.amsl.com>; Sat, 17 Nov 2012 05:00:49 -0800 (PST)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by ietfa.amsl.com (Postfix) with ESMTP id 56C6C21F8421 for <ietf@ietf.org>; Sat, 17 Nov 2012 05:00:49 -0800 (PST)
Received: from falcon.ecs.soton.ac.uk (localhost.ecs.soton.ac.uk [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id qAHD0ltp017334 for <ietf@ietf.org>; Sat, 17 Nov 2012 13:00:47 GMT
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk qAHD0ltp017334
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=200903; t=1353157247; bh=R0CDPo8sTsRgDY5AGx+yoellaDY=; h=Mime-Version:Subject:From:In-Reply-To:Date:References:To; b=eGslHOGiKKZ5N2smBVfodbSZEinPGhzTtmQ8pLqpTmRTe0zorJgDp1PqNlENsGB5v Aid8C9FewnpJgfn0NYd6889hLefHTpNJl5yfoTHKnegxiNBO7oh6PSrblQ3WDgk3xU tf3Ba7Ft4Tz+t3fOKJCVlVehmi/7ntbV7ZwkfCTo=
Received: from gander.ecs.soton.ac.uk (gander.ecs.soton.ac.uk [2001:630:d0:f102::25d]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102::25e]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id oAGD0l0430632207H0 ret-id none; Sat, 17 Nov 2012 13:00:47 +0000
Received: from [192.168.1.102] (host213-123-213-183.in-addr.btopenworld.com [213.123.213.183]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id qAHD0MHU003746 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <ietf@ietf.org>; Sat, 17 Nov 2012 13:00:22 GMT
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <50A63ED8.5060802@gmail.com>
Date: Sat, 17 Nov 2012 13:00:21 +0000
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|dc43f8e8167822ec7ee7484c8ecb584boAGD0l03tjc|ecs.soton.ac.uk|6B4ED9EC-A3BE-45F7-84F0-376E61506A3F@ecs.soton.ac.uk>
References: <20121116032738.11495.qmail@joyce.lan> <50A63ED8.5060802@gmail.com> <6B4ED9EC-A3BE-45F7-84F0-376E61506A3F@ecs.soton.ac.uk>
To: ietf@ietf.org
X-Mailer: Apple Mail (2.1499)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=oAGD0l043063220700; tid=oAGD0l0430632207H0; client=relay,ipv6; mail=; rcpt=; nrcpt=1:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: qAHD0ltp017334
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 17 Nov 2012 13:00:50 -0000

On 16 Nov 2012, at 13:25, Carlos M. Martinez <carlosm3011@gmail.com> =
wrote:

> Moving the IETF forward will involve reaching out to other peoples,
> other regions, and yes, travel farther away once in a while. I also
> understand that we need to do our part in terms of fostering and
> increasing the contribution of our region. I said this in an earlier
> email and I stand by it.


A strength of the IETF is that to participate you can simply join =
discussions on mailing lists and participate remotely when physical =
meetings are held. This may mean that for the majority of IETF =
contributors, the location of the meetings isn't critical, because =
attendance at every physical meeting isn't required.

However, when planning where meetings are held I hope organisers take =
into account the chairs of the 100+ working groups in the IETF, for whom =
attendance may not be compulsory but it's certainly highly desirable. If =
the cost of attending meetings and the complexity of travel goes up, it =
may become harder to find volunteers willing to take on WG chair and =
other similar responsibilities for the benefit of the IETF community as =
a whole.

Tim=20=

From jnc@mercury.lcs.mit.edu  Sat Nov 17 09:12:40 2012
Return-Path: <jnc@mercury.lcs.mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E54DB21F84E7; Sat, 17 Nov 2012 09:12:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.603
X-Spam-Level: 
X-Spam-Status: No, score=-6.603 tagged_above=-999 required=5 tests=[AWL=-0.004, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 JWhOpIoqGT9c; Sat, 17 Nov 2012 09:12:40 -0800 (PST)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 5292E21F84DF; Sat, 17 Nov 2012 09:12:39 -0800 (PST)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id E4A4118C08F; Sat, 17 Nov 2012 12:12:38 -0500 (EST)
To: ietf@ietf.org, lisp@ietf.org
Subject: Re: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
Message-Id: <20121117171238.E4A4118C08F@mercury.lcs.mit.edu>
Date: Sat, 17 Nov 2012 12:12:38 -0500 (EST)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 17 Nov 2012 17:12:41 -0000

    > From: Cameron Byrne <cb.list6@gmail.com>

    >> If LISP succeeds, this results in significant reduction in core table
    >> sizes for everyone.

    > Not everyone. Only people who carry core tables.

'this results in significant reduction in core table sizes for everyone who
has core tables' sounds a bit tautological, no?

    > That is LISP twist, it transfers cost from a few cores to many edges.

If you define 'many' is 'people who are actually trying to communicate with a
given site', yes. So it has transferred costs for communicating with site X
from 'everyone with a core table, everywhere in the entire network' to 'just
the people who are actually trying to communicate with site X'. This is
bad... how?

(When I first quickly read your message, I thought you were making a point
about the routing overhead of EIDs being carried in the global routing tables
for use by legacy sites, which is an interesting point, but not the one that
you make here.)

	Noel

From farinacci@gmail.com  Sat Nov 17 09:51:56 2012
Return-Path: <farinacci@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C95521F84EE; Sat, 17 Nov 2012 09:51:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.524
X-Spam-Level: 
X-Spam-Status: No, score=-3.524 tagged_above=-999 required=5 tests=[AWL=0.075,  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 HthN7hc+plVK; Sat, 17 Nov 2012 09:51:55 -0800 (PST)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id B932721F86B9; Sat, 17 Nov 2012 09:51:55 -0800 (PST)
Received: by mail-pb0-f44.google.com with SMTP id uo1so2601168pbc.31 for <multiple recipients>; Sat, 17 Nov 2012 09:51:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=1r6u/ovuhbgwRDZaS1zKYKBjTjl97TZy2DS94W8WfrA=; b=RRPEhYkBTWVZ2ptZ6ueW0sAv7RbcQTZyNTtDlkEKQGtn+h24Aq0InQWNFqtZHxjHT0 BZ1wzFYuxbrgAwXqloGkO3QNAJsTIQgrds/34a/71FYPKWCT3plMsSluLB2ZecaT250A HYS06SXmhMqUeUTpfRk9l6z6eVWNLeZSOCyDFmOdn+vy3I5aasVBuf4ouB6eOtaWZ0IQ 1+Hir62nXglETeD9GgSWcwZ5w5WKfsEW/ww827QzECxKeaaZjZgmbkPqioTPzasAJYmG SwQD4q6xJrVBWR61zRQ8xqtLHMHeUlKmYSZE1puGm5pIhGdqn8xcSnHEfL9DS8PrWobA 8Pjg==
Received: by 10.68.253.4 with SMTP id zw4mr20069978pbc.143.1353174715243; Sat, 17 Nov 2012 09:51:55 -0800 (PST)
Received: from [10.21.72.78] (128-107-239-233.cisco.com. [128.107.239.233]) by mx.google.com with ESMTPS id gu5sm3219792pbc.10.2012.11.17.09.51.52 (version=SSLv3 cipher=OTHER); Sat, 17 Nov 2012 09:51:54 -0800 (PST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
From: Dino Farinacci <farinacci@gmail.com>
In-Reply-To: <50A61A97.9060005@lacnic.net>
Date: Sat, 17 Nov 2012 09:51:54 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <7999F86A-5842-4BAE-A68D-8F783F50CA2C@gmail.com>
References: <20121113144545.12836.71935.idtracker@ietfa.amsl.com> <CAKFn1SFy2+hXJLVtEpkdXfNuXA31ybmYnBFFPXj-73kb3tD+yw@mail.gmail.com> <5FCB8A98-4984-427C-9468-1DFDEBD206FD@steffann.nl> <87676878-B077-4B4C-96DC-9F755F78018A@gigix.net> <50A530E7.8@lacnic.net> <B8132154-7260-43B4-B10D-E5B95924A15D@gmail.com> <00C0245E-59D7-4552-8BB4-1C0099513D1D@steffann.nl> <D470B9D8-977F-4E8B-8EDF-7769D5773279@gmail.com> <0BC58149-A314-4AD3-80A5-DC8BF5DB0E2D@steffann.nl> <2007FD20-0EA4-4204-81A5-D9AE0201419D@gmail.com> <D40BD502-1E3A-4AAA-A040-E2E4EE83141D@steffann.nl> <8F781829-457B-4B32-B91A-46C22BC5D570@gmail.com> <37436188-2E53-40DC-839F-AC52E5CA8188@apnic.net> <766205F6-48FB-4962-9F43-EDCACC73D1DA@gmail.com> <149720A8-FC8D-4BD0-9A7A-0EB42E8CCE75@apnic.net> <EE0CED54-D440-434C-8804-05EF6419B1AD@steffann.nl> <50A61A97.9060005@lacnic.net>
To: Arturo Servin <aservin@lacnic.net>
X-Mailer: Apple Mail (2.1499)
Cc: "ietf@ietf.org list" <ietf@ietf.org>, "lisp@ietf.org list" <lisp@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 17 Nov 2012 17:51:56 -0000

> Dino,
>=20
> 	+1 In LACNIC, may 6th to 10th 2013 in Medellin Colombia.

Will consider Singapore and Medellin.

> 	I am not the policiy guy but I can get you time in the technical =
and
> policy plenaries and assit you in the discussion.
>=20
> 	Also, if you plan to write some text about the allocation =
mechanics let
> me know, I will be happy to help to review, comment and even write =
some
> text if that is useful for lisp.

Thanks for the offer.

Dino

>=20
> Regards,
> as
>=20
> On 16/11/2012 08:18, Sander Steffann wrote:
>> Hi Dino,
>>=20
>>> George:
>>>> Maybe this is something you could come to an RIR meeting and =
present on or discuss? We've got an APNIC/APRICOT coming up early in =
2013 and I am sure you'd be welcomed to submit some content. Its good to =
talk about these things.
>>=20
>> +1
>>=20
>> Let's make it official :-)
>>=20
>> It would be very good to discuss this idea in the RIR communities. I =
think both the LISP community and the RIR communities can learn from =
each other. As co-chair of the RIPE Address Policy Working Group I would =
really appreciate it if you could come to the next RIPE meeting to =
discuss this. I'll make sure that there is a slot on the working group =
agenda. RIPE 66 will take place from 13-17 May 2013 at the Burlington =
Hotel in Dublin.
>>=20
>> Thanks,
>> Sander
>>=20


From cb.list6@gmail.com  Sat Nov 17 10:27:02 2012
Return-Path: <cb.list6@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E0BA21F84CA for <ietf@ietfa.amsl.com>; Sat, 17 Nov 2012 10:27:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.278
X-Spam-Level: 
X-Spam-Status: No, score=-3.278 tagged_above=-999 required=5 tests=[AWL=0.320,  BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 Ntlrcr68BL-u for <ietf@ietfa.amsl.com>; Sat, 17 Nov 2012 10:27:01 -0800 (PST)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id 0843921F84C6 for <ietf@ietf.org>; Sat, 17 Nov 2012 10:27:00 -0800 (PST)
Received: by mail-lb0-f172.google.com with SMTP id y2so3086082lbk.31 for <ietf@ietf.org>; Sat, 17 Nov 2012 10:26:59 -0800 (PST)
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 :cc:content-type; bh=j2Dq6MR3w5VKyDcvkrxHFbG7M44vCuePiNThTvbM9nQ=; b=GZ9ymlj0yvQTCpq2rAjoFw1WCsCc7XEDQO22t0NFQGN5c2IZSnceHa9VSxgYuyeYuy q60haewCPF6/AWu4tZWUy3Y9o9T542w8c+ctQLwYgwPlq/Ukv8BT/N8N+9haY7eUfoj/ CK+w1wbqSYjqoOd5cEpzaTve8tbcXwXCvD7Q5aNk9+/QaeBJ3nY4TShWgL8emia9vc35 yG3CsZ8v76VQKPmqQE+VwbI+eFbdpW8bsPv81IyBCa/4f03Dxbjtu7paQkal2Xz2CsUe ddJz7CTfRodVi2BIOMtjFsOHMEVq4wZLytfr67D6j81lMIG16kL5gXEAi/jm/20gh1ze 5Slw==
MIME-Version: 1.0
Received: by 10.152.135.41 with SMTP id pp9mr7547206lab.7.1353176819691; Sat, 17 Nov 2012 10:26:59 -0800 (PST)
Received: by 10.112.81.167 with HTTP; Sat, 17 Nov 2012 10:26:59 -0800 (PST)
Received: by 10.112.81.167 with HTTP; Sat, 17 Nov 2012 10:26:59 -0800 (PST)
In-Reply-To: <20121117171238.E4A4118C08F@mercury.lcs.mit.edu>
References: <20121117171238.E4A4118C08F@mercury.lcs.mit.edu>
Date: Sat, 17 Nov 2012 10:26:59 -0800
Message-ID: <CAD6AjGQkWwu95Eq7seJEbiJKk5zfBD_8Gw8SOZkDiciajytjYw@mail.gmail.com>
Subject: Re: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
From: Cameron Byrne <cb.list6@gmail.com>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Content-Type: multipart/alternative; boundary=f46d044270caa7eeeb04ceb507da
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 17 Nov 2012 18:27:02 -0000

--f46d044270caa7eeeb04ceb507da
Content-Type: text/plain; charset=ISO-8859-1

Sent from ipv6-only Android
On Nov 17, 2012 9:12 AM, "Noel Chiappa" <jnc@mercury.lcs.mit.edu> wrote:
>
>     > From: Cameron Byrne <cb.list6@gmail.com>
>
>     >> If LISP succeeds, this results in significant reduction in core
table
>     >> sizes for everyone.
>
>     > Not everyone. Only people who carry core tables.
>
> 'this results in significant reduction in core table sizes for everyone
who
> has core tables' sounds a bit tautological, no?
>

No. Most networks dont carry full bgp routes. "Most networks" is an odd
definition. So, I will say my network does not carry full bgp routes.

>     > That is LISP twist, it transfers cost from a few cores to many
edges.
>
> If you define 'many' is 'people who are actually trying to communicate
with a
> given site', yes. So it has transferred costs for communicating with site
X
> from 'everyone with a core table, everywhere in the entire network' to
'just
> the people who are actually trying to communicate with site X'. This is
> bad... how?
>

I am not a LISP expert (ILNP sounds better to me, but we are already way
OT), LISP has never passed my smell test. But the only thing I have gleaned
of it is that dfz caps in size while edge sites have to buy more routers
with newer functions. Which sounds good for "tier 1" operators who are on
the hook for dfz scaling and for router vendors who are on the hook for
selling more routers.   There might even be something in it for folks who
who are nostalgic for ATM SVCs.

There are a lot of ways to shrink the dfz. LISP, imho, is unlikely to
succeed due to the economic incentives not being aligned. It requires
action at edge sites for problems edge sites don't have (dfz scaling).

CB

> (When I first quickly read your message, I thought you were making a point
> about the routing overhead of EIDs being carried in the global routing
tables
> for use by legacy sites, which is an interesting point, but not the one
that
> you make here.)
>
>         Noel

--f46d044270caa7eeeb04ceb507da
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<p dir=3D"ltr"></p>
<p dir=3D"ltr">Sent from ipv6-only Android<br>
On Nov 17, 2012 9:12 AM, &quot;Noel Chiappa&quot; &lt;<a href=3D"mailto:jnc=
@mercury.lcs.mit.edu">jnc@mercury.lcs.mit.edu</a>&gt; wrote:<br>
&gt;<br>
&gt; =A0 =A0 &gt; From: Cameron Byrne &lt;<a href=3D"mailto:cb.list6@gmail.=
com">cb.list6@gmail.com</a>&gt;<br>
&gt;<br>
&gt; =A0 =A0 &gt;&gt; If LISP succeeds, this results in significant reducti=
on in core table<br>
&gt; =A0 =A0 &gt;&gt; sizes for everyone.<br>
&gt;<br>
&gt; =A0 =A0 &gt; Not everyone. Only people who carry core tables.<br>
&gt;<br>
&gt; &#39;this results in significant reduction in core table sizes for eve=
ryone who<br>
&gt; has core tables&#39; sounds a bit tautological, no?<br>
&gt;</p>
<p dir=3D"ltr">No. Most networks dont carry full bgp routes. &quot;Most net=
works&quot; is an odd definition. So, I will say my network does not carry =
full bgp routes.<br></p>
<p dir=3D"ltr">&gt; =A0 =A0 &gt; That is LISP twist, it transfers cost from=
 a few cores to many edges.<br>
&gt;<br>
&gt; If you define &#39;many&#39; is &#39;people who are actually trying to=
 communicate with a<br>
&gt; given site&#39;, yes. So it has transferred costs for communicating wi=
th site X<br>
&gt; from &#39;everyone with a core table, everywhere in the entire network=
&#39; to &#39;just<br>
&gt; the people who are actually trying to communicate with site X&#39;. Th=
is is<br>
&gt; bad... how?<br>
&gt;</p>
<p dir=3D"ltr">I am not a LISP expert (ILNP sounds better to me, but we are=
 already way OT), LISP has never passed my smell test. But the only thing I=
 have gleaned of it is that dfz caps in size while edge sites have to buy m=
ore routers with newer functions. Which sounds good for &quot;tier 1&quot; =
operators who are on the hook for dfz scaling and for router vendors who ar=
e on the hook for selling more routers.=A0=A0 There might even be something=
 in it for folks who who are nostalgic for ATM SVCs.</p>

<p dir=3D"ltr">There are a lot of ways to shrink the dfz. LISP, imho, is un=
likely to succeed due to the economic incentives not being aligned. It requ=
ires action at edge sites for problems edge sites don&#39;t have (dfz scali=
ng).<br>
</p>
<p dir=3D"ltr">CB<br><br></p>
<p dir=3D"ltr">&gt; (When I first quickly read your message, I thought you =
were making a point<br>
&gt; about the routing overhead of EIDs being carried in the global routing=
 tables<br>
&gt; for use by legacy sites, which is an interesting point, but not the on=
e that<br>
&gt; you make here.)<br>
&gt;<br>
&gt; =A0 =A0 =A0 =A0 Noel<br>
</p>

--f46d044270caa7eeeb04ceb507da--

From jnc@mercury.lcs.mit.edu  Sat Nov 17 11:36:33 2012
Return-Path: <jnc@mercury.lcs.mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D619221F851F for <ietf@ietfa.amsl.com>; Sat, 17 Nov 2012 11:36:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.603
X-Spam-Level: 
X-Spam-Status: No, score=-6.603 tagged_above=-999 required=5 tests=[AWL=-0.004, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 zcZlal8PJbRg for <ietf@ietfa.amsl.com>; Sat, 17 Nov 2012 11:36:33 -0800 (PST)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 46BE121F8532 for <ietf@ietf.org>; Sat, 17 Nov 2012 11:36:33 -0800 (PST)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 8792F18C08D; Sat, 17 Nov 2012 14:36:32 -0500 (EST)
To: ietf@ietf.org
Subject: Re: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
Message-Id: <20121117193632.8792F18C08D@mercury.lcs.mit.edu>
Date: Sat, 17 Nov 2012 14:36:32 -0500 (EST)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 17 Nov 2012 19:36:33 -0000

    > From: Cameron Byrne <cb.list6@gmail.com>

    >> So it has transferred costs for communicating with site X from
    >> 'everyone with a core table, everywhere in the entire network' to
    >> 'just the people who are actually trying to communicate with site X'.
    >> This is bad... how?

I didn't see an answer to this question (which is not at all LISP-specific -
rather, it's a general observation about the allocation of overhead costs in
a network). Why should site B, which _never_ talks to X, have to pay, so that
site A can talk to X?

    > edge sites have to buy more routers with newer functions.

???? Each vendor will have its own answer to this question, but the LISP
software suites I know of are new loads for existing router hardware. Do you
know of a LISP package which only comes with new hardware?

	Noel

From gih@apnic.net  Sat Nov 17 22:21:14 2012
Return-Path: <gih@apnic.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9CC7621F850D; Sat, 17 Nov 2012 22:21:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.891
X-Spam-Level: 
X-Spam-Status: No, score=-100.891 tagged_above=-999 required=5 tests=[AWL=-0.158, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, RDNS_NONE=0.1, SARE_MILLIONSOF=0.315, 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 r-oLm7xr8+vl; Sat, 17 Nov 2012 22:21:11 -0800 (PST)
Received: from asmtp.apnic.net (asmtp.apnic.net [IPv6:2001:dc0:2001:11::199]) by ietfa.amsl.com (Postfix) with ESMTP id 0283721F8501; Sat, 17 Nov 2012 22:21:09 -0800 (PST)
Received: from [192.168.51.200] (unknown [87.213.29.58]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by asmtp.apnic.net (Postfix) with ESMTP id 3CA39B684D; Sun, 18 Nov 2012 16:21:03 +1000 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
From: Geoff Huston <gih@apnic.net>
In-Reply-To: <50A6ADD0.3040000@joelhalpern.com>
Date: Sun, 18 Nov 2012 17:20:58 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <45813A84-7BE9-4D21-AE3E-F3401D6E1B50@apnic.net>
References: <20121113144545.12836.71935.idtracker@ietfa.amsl.com>	<CAKFn1SF4+k5gWip-WBNfbjt-qAafPbTSY8L_EBLA9Pqvbw4=kQ@mail.gmail.com> <50A66313.9090002@joelhalpern.com> <50A66B67.5000609@gmail.com> <50A67758.8000001@joelhalpern.com> <33C6C196-B881-4BAA-8E57-082B266C831A@steffann.nl> <50A6ADD0.3040000@joelhalpern.com>
To: Joel Halpern Direct <jmh.direct@joelhalpern.com>
X-Mailer: Apple Mail (2.1499)
Cc: ietf@ietf.org, Sander Steffann <sander@steffann.nl>, lisp@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 18 Nov 2012 06:21:14 -0000

But why request the reservation of a /12? Or even a /16 for that matter?

If the LISP experimental deployers have filled a /32 with /48 prefixes =
then should this imply that the experiment is all over over and its time =
to recast  this not as an experiment but as an application which =
requires global unicast address allocations, and proceed along those =
grounds?

Indeed if the entire point of this experimental use allocation request =
is on the basis that at the time when deployment numbers are =
sufficiently large (orders of millions of end sites presumably) then =
this block allocation will have some beneficial effects. But thats NOT =
an experimental justification.

So what is this request? Experimental? Planning for large scale =
deployment?

If its the latter than I do not understand how this draft, calling for a =
allocation from the IANA special purpose address registry on the grounds =
of supporting an IETF experimental activity, can be supported by the =
existing processes. The IANA Special purpose address registry and RFC =
4773 do not encompass the allocation of address blocks for use in a =
global unicast address context in the context of large scale deployment =
activities.

If its the former then the scale of the allocation is unwarranted. The =
broad characterisation of the experiment allocation is to test concepts, =
and if that's the case then once the "test" is over what are the plans =
to migrate OUT of the "test" allocation and support unicast global =
address allocations in the context of LISP under the general framework =
of RFC2860 and RFC 2050? What is the scale of this "test"? When would =
the "test" be completed?

I think this draft is not well thought through and the draft's proposals =
for address allocation from the IANA Special Purpose Address Registry  =
is inconsistent with the processes we use for management of addresses in =
the IETF. I do not support the publication of this draft.

regards,

   Geoff




On 17/11/2012, at 8:19 AM, Joel Halpern Direct =
<jmh.direct@joelhalpern.com> wrote:

> Most of what you describe Sander sounds reasonable, and sounds aligned =
with what is i the deployment documents.
>=20
> The WG debated the EID allocation extensively.  One could argue that =
there is no need for it, that we could merely request that PI =
allocations be granted for LISP EID usage individually.  The WG felt =
that if we could get all IPv6 LISP EID allocations from a single block =
that was not used for anything else, that would simplify avoiding =
lookups in the mapping system that were inevitably going to fail.  Thus =
the allocations request.
>=20
> Yours,
> Joel
>=20
> On 11/16/2012 4:12 PM, Sander Steffann wrote:
>> Hi Joel,
>>=20
>>> Why does any operator have a reason to carr any routes other than =
their paying customers?  Because it provides connectivity for their =
customers.
>>> If we get this block allocaed, then it results in 1 extra routing =
entry in the global routing table to support LISP inter-working.
>>> An entry that some of their customers may use, whether the operator =
carrying it knows that or not.
>>>=20
>>> In fact, it would take significant extra work for the operator to =
somehow block this aggregate.
>>>=20
>>> If LISP fails, this is a small cost to find out.
>>> If LISP succeeds, this results in significant reduction in core tabl =
sizes for everyone.
>>=20
>> That still assumes the altruistic routing of the prefix. And I am =
afraid that if the usage of this block gets a bad reputation that all =
LISP usage will share that reputation. I really like LISP but I am still =
not convinced that it's a good idea. If we can find a way to get the EID =
prefix routed in a reliable way then I would love it!
>>=20
>> I really care about LISP and I am afraid that: people see unreliable =
routing for EID /16 =3D> assume LISP is unreliable. That is why I am =
pushing so hard to get this sorted out.
>>=20
>> Hmmm. What about the following strategy:
>> - Start with the EID prefix being handed out like PI
>>   - Either through the RIRs if they are willing to take the =
responsibility
>>   - Or from a separate registry
>> - Some altruistic /16 PITRs might show up in the global BGP table
>> - A holders of a (assume) /48 from the EID prefix can arrange PITRs =
for their own space
>>   - And announce it as a separate route in the global BGP table (for =
now)
>>   - Keep the routing and reliability under their own control
>> - If the experiment is a success we advise ISPs to:
>>   - Install their own PITRs for the /16
>>   - Filter out the /48s at their border
>>=20
>> The filtering of the more-specifics once they have their own PITRs =
will make sure that they use those PITRs and that they will use the most =
optimal path to the locators as soon as possible. It will also keep =
their routing table smaller. If enough big transit providers offer /16 =
PITRs to their customers then the more-specifics might be filtered on a =
larger scale.
>>=20
>> So, summary:
>>=20
>> The ways to reach a PITR would be
>> a) Run your own PITR (big networks, LISP users)
>> b) Use one from your transit(s) (smaller networks that don't have =
their own)
>> c) Use an altruistic one as last resort
>>=20
>> As long as (a) and (b) aren't a reality the LISP users who don't want =
to rely on (c) can run/rent/etc a PITR for their own space. I think the =
routing community would really appreciate it if all those more-specific =
routes would be temporary until wide deployment of (a) and (b) make them =
unnecessary.
>>=20
>> And if this doesn't become a success we have a bunch of /48 prefixes =
to the separate PITRs in the BGP table. It won't be much, otherwise we =
would have declared success. So the risk of messing the BGP table up is =
very limited. And when can tell people: if you are bothered by those =
more-specifics in your routing table you can always deploy your own =
PITRs and filter the more-specifics at your border. That might keep =
everyone happy.
>>=20
>> What do you think?
>>=20
>> Thanks,
>> Sander
>>=20
> _______________________________________________
> lisp mailing list
> lisp@ietf.org
> https://www.ietf.org/mailman/listinfo/lisp

--

Geoff Huston
Chief Scientist, APNIC

+61 7 3858 3100
gih@apnic.net





From jmh.direct@joelhalpern.com  Fri Nov 16 13:19:21 2012
Return-Path: <jmh.direct@joelhalpern.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5BD5821F8B01; Fri, 16 Nov 2012 13:19:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.265
X-Spam-Level: 
X-Spam-Status: No, score=-2.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334]
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 aDH9wqlfuOq2; Fri, 16 Nov 2012 13:19:20 -0800 (PST)
Received: from morbo.mail.tigertech.net (morbo.mail.tigertech.net [67.131.251.54]) by ietfa.amsl.com (Postfix) with ESMTP id C0AAD21F8AED; Fri, 16 Nov 2012 13:19:20 -0800 (PST)
Received: from mailc2.tigertech.net (mailc2.tigertech.net [208.80.4.156]) by morbo.tigertech.net (Postfix) with ESMTP id 4BA6B559828; Fri, 16 Nov 2012 13:19:20 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailc2.tigertech.net (Postfix) with ESMTP id CDE5D1607E8; Fri, 16 Nov 2012 13:19:18 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at c2.tigertech.net
Received: from [10.10.10.104] (pool-71-161-50-174.clppva.btas.verizon.net [71.161.50.174]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailc2.tigertech.net (Postfix) with ESMTPSA id 96A841607E5; Fri, 16 Nov 2012 13:19:17 -0800 (PST)
Message-ID: <50A6ADD0.3040000@joelhalpern.com>
Date: Fri, 16 Nov 2012 16:19:12 -0500
From: Joel Halpern Direct <jmh.direct@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: Sander Steffann <sander@steffann.nl>
Subject: Re: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
References: <20121113144545.12836.71935.idtracker@ietfa.amsl.com>	<CAKFn1SF4+k5gWip-WBNfbjt-qAafPbTSY8L_EBLA9Pqvbw4=kQ@mail.gmail.com> <50A66313.9090002@joelhalpern.com> <50A66B67.5000609@gmail.com> <50A67758.8000001@joelhalpern.com> <33C6C196-B881-4BAA-8E57-082B266C831A@steffann.nl>
In-Reply-To: <33C6C196-B881-4BAA-8E57-082B266C831A@steffann.nl>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Sun, 18 Nov 2012 08:01:42 -0800
Cc: lisp@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Nov 2012 21:19:21 -0000

Most of what you describe Sander sounds reasonable, and sounds aligned 
with what is i the deployment documents.

The WG debated the EID allocation extensively.  One could argue that 
there is no need for it, that we could merely request that PI 
allocations be granted for LISP EID usage individually.  The WG felt 
that if we could get all IPv6 LISP EID allocations from a single block 
that was not used for anything else, that would simplify avoiding 
lookups in the mapping system that were inevitably going to fail.  Thus 
the allocations request.

Yours,
Joel

On 11/16/2012 4:12 PM, Sander Steffann wrote:
> Hi Joel,
>
>> Why does any operator have a reason to carr any routes other than their paying customers?  Because it provides connectivity for their customers.
>> If we get this block allocaed, then it results in 1 extra routing entry in the global routing table to support LISP inter-working.
>> An entry that some of their customers may use, whether the operator carrying it knows that or not.
>>
>> In fact, it would take significant extra work for the operator to somehow block this aggregate.
>>
>> If LISP fails, this is a small cost to find out.
>> If LISP succeeds, this results in significant reduction in core tabl sizes for everyone.
>
> That still assumes the altruistic routing of the prefix. And I am afraid that if the usage of this block gets a bad reputation that all LISP usage will share that reputation. I really like LISP but I am still not convinced that it's a good idea. If we can find a way to get the EID prefix routed in a reliable way then I would love it!
>
> I really care about LISP and I am afraid that: people see unreliable routing for EID /16 => assume LISP is unreliable. That is why I am pushing so hard to get this sorted out.
>
> Hmmm. What about the following strategy:
> - Start with the EID prefix being handed out like PI
>    - Either through the RIRs if they are willing to take the responsibility
>    - Or from a separate registry
> - Some altruistic /16 PITRs might show up in the global BGP table
> - A holders of a (assume) /48 from the EID prefix can arrange PITRs for their own space
>    - And announce it as a separate route in the global BGP table (for now)
>    - Keep the routing and reliability under their own control
> - If the experiment is a success we advise ISPs to:
>    - Install their own PITRs for the /16
>    - Filter out the /48s at their border
>
> The filtering of the more-specifics once they have their own PITRs will make sure that they use those PITRs and that they will use the most optimal path to the locators as soon as possible. It will also keep their routing table smaller. If enough big transit providers offer /16 PITRs to their customers then the more-specifics might be filtered on a larger scale.
>
> So, summary:
>
> The ways to reach a PITR would be
> a) Run your own PITR (big networks, LISP users)
> b) Use one from your transit(s) (smaller networks that don't have their own)
> c) Use an altruistic one as last resort
>
> As long as (a) and (b) aren't a reality the LISP users who don't want to rely on (c) can run/rent/etc a PITR for their own space. I think the routing community would really appreciate it if all those more-specific routes would be temporary until wide deployment of (a) and (b) make them unnecessary.
>
> And if this doesn't become a success we have a bunch of /48 prefixes to the separate PITRs in the BGP table. It won't be much, otherwise we would have declared success. So the risk of messing the BGP table up is very limited. And when can tell people: if you are bothered by those more-specifics in your routing table you can always deploy your own PITRs and filter the more-specifics at your border. That might keep everyone happy.
>
> What do you think?
>
> Thanks,
> Sander
>

From heinerhummel@aol.com  Sun Nov 18 00:40:19 2012
Return-Path: <heinerhummel@aol.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F94C21F84C6 for <ietf@ietfa.amsl.com>; Sun, 18 Nov 2012 00:40:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.481
X-Spam-Level: 
X-Spam-Status: No, score=-1.481 tagged_above=-999 required=5 tests=[AWL=0.802,  BAYES_00=-2.599, HTML_MESSAGE=0.001, SARE_MILLIONSOF=0.315]
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 ucoY6CNQQCNB for <ietf@ietfa.amsl.com>; Sun, 18 Nov 2012 00:40:15 -0800 (PST)
Received: from imr-ma03.mx.aol.com (imr-ma03.mx.aol.com [64.12.206.41]) by ietfa.amsl.com (Postfix) with ESMTP id A8E4C21F84B9 for <ietf@ietf.org>; Sun, 18 Nov 2012 00:40:14 -0800 (PST)
Received: from mtaomg-mb05.r1000.mx.aol.com (mtaomg-mb05.r1000.mx.aol.com [172.29.41.76]) by imr-ma03.mx.aol.com (8.14.1/8.14.1) with ESMTP id qAI8e0wp009889; Sun, 18 Nov 2012 03:40:00 -0500
Received: from core-dqd004c.r1000.mail.aol.com (core-dqd004.r1000.mail.aol.com [172.29.162.13]) by mtaomg-mb05.r1000.mx.aol.com (OMAG/Core Interface) with ESMTP id E9A9AE000081; Sun, 18 Nov 2012 03:39:59 -0500 (EST)
References: <20121113144545.12836.71935.idtracker@ietfa.amsl.com>	<CAKFn1SF4+k5gWip-WBNfbjt-qAafPbTSY8L_EBLA9Pqvbw4=kQ@mail.gmail.com> <50A66313.9090002@joelhalpern.com> <50A66B67.5000609@gmail.com> <50A67758.8000001@joelhalpern.com> <33C6C196-B881-4BAA-8E57-082B266C831A@steffann.nl> <50A6ADD0.3040000@joelhalpern.com> <45813A84-7BE9-4D21-AE3E-F3401D6E1B50@apnic.net>
To: gih@apnic.net, jmh.direct@joelhalpern.com
Subject: Re: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
In-Reply-To: <45813A84-7BE9-4D21-AE3E-F3401D6E1B50@apnic.net>
X-MB-Message-Source: WebUI
Received: from 178.27.21.1 by webmail-d037.sysops.aol.com (205.188.181.88) with HTTP (WebMailUI); Sun, 18 Nov 2012 03:39:59 -0500
MIME-Version: 1.0
From: heinerhummel@aol.com
X-MB-Message-Type: User
Content-Type: multipart/alternative;  boundary="--------MB_8CF937F6DE25FD2_D74_822A9_webmail-d037.sysops.aol.com"
X-Mailer: Webmail 37185-STANDARD
Message-Id: <8CF937F6DCF54D2-D74-23EDD@webmail-d037.sysops.aol.com>
X-Originating-IP: [178.27.21.1]
Date: Sun, 18 Nov 2012 03:39:59 -0500 (EST)
x-aol-global-disposition: G
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mx.aol.com; s=20110426; t=1353228000; bh=jEKxeI5A8nXZ5F6d6vtqG79Nt1EFk3MSroTdlK4ADBU=; h=From:To:Subject:Message-Id:Date:MIME-Version:Content-Type; b=FJ0U2cV3271QLKTh67gtUudbOeRPkPzReO/h7MnNEyo6EDoHiFcK5GxzQu5zBA6ZR vB4v0HRXGLI3nDdTRtm8ktCnSPss6Wn6rKJTmdiubbE40vhgzbYkBnH2hxzRsZCV4H MzLnJZDQDe5Nd87Gy0KtyZRJXthsr83yRHzD2J7c=
X-AOL-SCOLL-SCORE: 0:2:475858752:93952408  
X-AOL-SCOLL-URL_COUNT: 0  
x-aol-sid: 3039ac1d294c50a89edf1a42
X-Mailman-Approved-At: Sun, 18 Nov 2012 08:01:42 -0800
Cc: ietf@ietf.org, lisp@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 18 Nov 2012 08:40:19 -0000

This is a multi-part message in MIME format.
----------MB_8CF937F6DE25FD2_D74_822A9_webmail-d037.sysops.aol.com
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"

And:
LISP does neither describe how to cope with the address depletion issue nor=
 prove that it is able to.


Imho, there is not even the slightest chance not to fail.


Heiner



-----Urspr=C3=BCngliche Mitteilung-----=20
Von: Geoff Huston <gih@apnic.net>
An: Joel Halpern Direct <jmh.direct@joelhalpern.com>
Cc: ietf <ietf@ietf.org>; lisp <lisp@ietf.org>; Brian E Carpenter <brian.e.=
carpenter@gmail.com>
Verschickt: So, 18 Nov 2012 7:22 am
Betreff: Re: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID=
 Block) to Informational RFC


But why request the reservation of a /12? Or even a /16 for that matter?

If the LISP experimental deployers have filled a /32 with /48 prefixes then=
=20
should this imply that the experiment is all over over and its time to reca=
st =20
this not as an experiment but as an application which requires global unica=
st=20
address allocations, and proceed along those grounds?

Indeed if the entire point of this experimental use allocation request is o=
n the=20
basis that at the time when deployment numbers are sufficiently large (orde=
rs of=20
millions of end sites presumably) then this block allocation will have some=
=20
beneficial effects. But thats NOT an experimental justification.

So what is this request? Experimental? Planning for large scale deployment?

If its the latter than I do not understand how this draft, calling for a=20
allocation from the IANA special purpose address registry on the grounds of=
=20
supporting an IETF experimental activity, can be supported by the existing=
=20
processes. The IANA Special purpose address registry and RFC 4773 do not=20
encompass the allocation of address blocks for use in a global unicast addr=
ess=20
context in the context of large scale deployment activities.

If its the former then the scale of the allocation is unwarranted. The broa=
d=20
characterisation of the experiment allocation is to test concepts, and if t=
hat's=20
the case then once the "test" is over what are the plans to migrate OUT of =
the=20
"test" allocation and support unicast global address allocations in the con=
text=20
of LISP under the general framework of RFC2860 and RFC 2050? What is the sc=
ale=20
of this "test"? When would the "test" be completed?

I think this draft is not well thought through and the draft's proposals fo=
r=20
address allocation from the IANA Special Purpose Address Registry  is=20
inconsistent with the processes we use for management of addresses in the I=
ETF.=20
I do not support the publication of this draft.

regards,

   Geoff




On 17/11/2012, at 8:19 AM, Joel Halpern Direct <jmh.direct@joelhalpern.com>=
=20
wrote:

> Most of what you describe Sander sounds reasonable, and sounds aligned wi=
th=20
what is i the deployment documents.
>=20
> The WG debated the EID allocation extensively.  One could argue that ther=
e is=20
no need for it, that we could merely request that PI allocations be granted=
 for=20
LISP EID usage individually.  The WG felt that if we could get all IPv6 LIS=
P EID=20
allocations from a single block that was not used for anything else, that w=
ould=20
simplify avoiding lookups in the mapping system that were inevitably going =
to=20
fail.  Thus the allocations request.
>=20
> Yours,
> Joel
>=20
> On 11/16/2012 4:12 PM, Sander Steffann wrote:
>> Hi Joel,
>>=20
>>> Why does any operator have a reason to carr any routes other than their=
=20
paying customers?  Because it provides connectivity for their customers.
>>> If we get this block allocaed, then it results in 1 extra routing entry=
 in=20
the global routing table to support LISP inter-working.
>>> An entry that some of their customers may use, whether the operator car=
rying=20
it knows that or not.
>>>=20
>>> In fact, it would take significant extra work for the operator to someh=
ow=20
block this aggregate.
>>>=20
>>> If LISP fails, this is a small cost to find out.
>>> If LISP succeeds, this results in significant reduction in core tabl si=
zes=20
for everyone.
>>=20
>> That still assumes the altruistic routing of the prefix. And I am afraid=
 that=20
if the usage of this block gets a bad reputation that all LISP usage will s=
hare=20
that reputation. I really like LISP but I am still not convinced that it's =
a=20
good idea. If we can find a way to get the EID prefix routed in a reliable =
way=20
then I would love it!
>>=20
>> I really care about LISP and I am afraid that: people see unreliable rou=
ting=20
for EID /16 =3D> assume LISP is unreliable. That is why I am pushing so har=
d to=20
get this sorted out.
>>=20
>> Hmmm. What about the following strategy:
>> - Start with the EID prefix being handed out like PI
>>   - Either through the RIRs if they are willing to take the responsibili=
ty
>>   - Or from a separate registry
>> - Some altruistic /16 PITRs might show up in the global BGP table
>> - A holders of a (assume) /48 from the EID prefix can arrange PITRs for =
their=20
own space
>>   - And announce it as a separate route in the global BGP table (for now=
)
>>   - Keep the routing and reliability under their own control
>> - If the experiment is a success we advise ISPs to:
>>   - Install their own PITRs for the /16
>>   - Filter out the /48s at their border
>>=20
>> The filtering of the more-specifics once they have their own PITRs will =
make=20
sure that they use those PITRs and that they will use the most optimal path=
 to=20
the locators as soon as possible. It will also keep their routing table sma=
ller.=20
If enough big transit providers offer /16 PITRs to their customers then the=
=20
more-specifics might be filtered on a larger scale.
>>=20
>> So, summary:
>>=20
>> The ways to reach a PITR would be
>> a) Run your own PITR (big networks, LISP users)
>> b) Use one from your transit(s) (smaller networks that don't have their =
own)
>> c) Use an altruistic one as last resort
>>=20
>> As long as (a) and (b) aren't a reality the LISP users who don't want to=
 rely=20
on (c) can run/rent/etc a PITR for their own space. I think the routing=20
community would really appreciate it if all those more-specific routes woul=
d be=20
temporary until wide deployment of (a) and (b) make them unnecessary.
>>=20
>> And if this doesn't become a success we have a bunch of /48 prefixes to =
the=20
separate PITRs in the BGP table. It won't be much, otherwise we would have=
=20
declared success. So the risk of messing the BGP table up is very limited. =
And=20
when can tell people: if you are bothered by those more-specifics in your=
=20
routing table you can always deploy your own PITRs and filter the more-spec=
ifics=20
at your border. That might keep everyone happy.
>>=20
>> What do you think?
>>=20
>> Thanks,
>> Sander
>>=20
> _______________________________________________
> lisp mailing list
> lisp@ietf.org
> https://www.ietf.org/mailman/listinfo/lisp

--

Geoff Huston
Chief Scientist, APNIC

+61 7 3858 3100
gih@apnic.net




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

=20

----------MB_8CF937F6DE25FD2_D74_822A9_webmail-d037.sysops.aol.com
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset="utf-8"

<font color=3D'black' size=3D'2' face=3D'arial'>And:
<div>LISP does neither describe how to cope with the address depletion issu=
e nor prove that it is able to.</div>

<div><br>
</div>

<div>Imho, there is not even the slightest chance not to fail.</div>

<div><br>
</div>

<div>Heiner<br>
<br>
<br>

<div style=3D"font-family:arial,helvetica;font-size:10pt;color:black">-----=
Urspr=C3=BCngliche Mitteilung----- <br>
Von: Geoff Huston &lt;gih@apnic.net&gt;<br>
An: Joel Halpern Direct &lt;jmh.direct@joelhalpern.com&gt;<br>
Cc: ietf &lt;ietf@ietf.org&gt;; lisp &lt;lisp@ietf.org&gt;; Brian E Carpent=
er &lt;brian.e.carpenter@gmail.com&gt;<br>
Verschickt: So, 18 Nov 2012 7:22 am<br>
Betreff: Re: [lisp] Last Call: &lt;draft-ietf-lisp-eid-block-03.txt&gt; (LI=
SP EID Block) to Informational RFC<br>
<br>







<div id=3D"AOLMsgPart_0_58bc4189-7065-4ba9-9ab4-1c7af3aa62cc" style=3D"marg=
in: 0px;font-family: Tahoma, Verdana, Arial, Sans-Serif;font-size: 12px;col=
or: #000;background-color: #fff;">

<pre style=3D"font-size: 9pt;"><tt>But why request the reservation of a /12=
? Or even a /16 for that matter?

If the LISP experimental deployers have filled a /32 with /48 prefixes then=
=20
should this imply that the experiment is all over over and its time to reca=
st =20
this not as an experiment but as an application which requires global unica=
st=20
address allocations, and proceed along those grounds?

Indeed if the entire point of this experimental use allocation request is o=
n the=20
basis that at the time when deployment numbers are sufficiently large (orde=
rs of=20
millions of end sites presumably) then this block allocation will have some=
=20
beneficial effects. But thats NOT an experimental justification.

So what is this request? Experimental? Planning for large scale deployment?

If its the latter than I do not understand how this draft, calling for a=20
allocation from the IANA special purpose address registry on the grounds of=
=20
supporting an IETF experimental activity, can be supported by the existing=
=20
processes. The IANA Special purpose address registry and RFC 4773 do not=20
encompass the allocation of address blocks for use in a global unicast addr=
ess=20
context in the context of large scale deployment activities.

If its the former then the scale of the allocation is unwarranted. The broa=
d=20
characterisation of the experiment allocation is to test concepts, and if t=
hat's=20
the case then once the "test" is over what are the plans to migrate OUT of =
the=20
"test" allocation and support unicast global address allocations in the con=
text=20
of LISP under the general framework of RFC2860 and RFC 2050? What is the sc=
ale=20
of this "test"? When would the "test" be completed?

I think this draft is not well thought through and the draft's proposals fo=
r=20
address allocation from the IANA Special Purpose Address Registry  is=20
inconsistent with the processes we use for management of addresses in the I=
ETF.=20
I do not support the publication of this draft.

regards,

   Geoff




On 17/11/2012, at 8:19 AM, Joel Halpern Direct &lt;<a href=3D"mailto:jmh.di=
rect@joelhalpern.com">jmh.direct@joelhalpern.com</a>&gt;=20
wrote:

&gt; Most of what you describe Sander sounds reasonable, and sounds aligned=
 with=20
what is i the deployment documents.
&gt;=20
&gt; The WG debated the EID allocation extensively.  One could argue that t=
here is=20
no need for it, that we could merely request that PI allocations be granted=
 for=20
LISP EID usage individually.  The WG felt that if we could get all IPv6 LIS=
P EID=20
allocations from a single block that was not used for anything else, that w=
ould=20
simplify avoiding lookups in the mapping system that were inevitably going =
to=20
fail.  Thus the allocations request.
&gt;=20
&gt; Yours,
&gt; Joel
&gt;=20
&gt; On 11/16/2012 4:12 PM, Sander Steffann wrote:
&gt;&gt; Hi Joel,
&gt;&gt;=20
&gt;&gt;&gt; Why does any operator have a reason to carr any routes other t=
han their=20
paying customers?  Because it provides connectivity for their customers.
&gt;&gt;&gt; If we get this block allocaed, then it results in 1 extra rout=
ing entry in=20
the global routing table to support LISP inter-working.
&gt;&gt;&gt; An entry that some of their customers may use, whether the ope=
rator carrying=20
it knows that or not.
&gt;&gt;&gt;=20
&gt;&gt;&gt; In fact, it would take significant extra work for the operator=
 to somehow=20
block this aggregate.
&gt;&gt;&gt;=20
&gt;&gt;&gt; If LISP fails, this is a small cost to find out.
&gt;&gt;&gt; If LISP succeeds, this results in significant reduction in cor=
e tabl sizes=20
for everyone.
&gt;&gt;=20
&gt;&gt; That still assumes the altruistic routing of the prefix. And I am =
afraid that=20
if the usage of this block gets a bad reputation that all LISP usage will s=
hare=20
that reputation. I really like LISP but I am still not convinced that it's =
a=20
good idea. If we can find a way to get the EID prefix routed in a reliable =
way=20
then I would love it!
&gt;&gt;=20
&gt;&gt; I really care about LISP and I am afraid that: people see unreliab=
le routing=20
for EID /16 =3D&gt; assume LISP is unreliable. That is why I am pushing so =
hard to=20
get this sorted out.
&gt;&gt;=20
&gt;&gt; Hmmm. What about the following strategy:
&gt;&gt; - Start with the EID prefix being handed out like PI
&gt;&gt;   - Either through the RIRs if they are willing to take the respon=
sibility
&gt;&gt;   - Or from a separate registry
&gt;&gt; - Some altruistic /16 PITRs might show up in the global BGP table
&gt;&gt; - A holders of a (assume) /48 from the EID prefix can arrange PITR=
s for their=20
own space
&gt;&gt;   - And announce it as a separate route in the global BGP table (f=
or now)
&gt;&gt;   - Keep the routing and reliability under their own control
&gt;&gt; - If the experiment is a success we advise ISPs to:
&gt;&gt;   - Install their own PITRs for the /16
&gt;&gt;   - Filter out the /48s at their border
&gt;&gt;=20
&gt;&gt; The filtering of the more-specifics once they have their own PITRs=
 will make=20
sure that they use those PITRs and that they will use the most optimal path=
 to=20
the locators as soon as possible. It will also keep their routing table sma=
ller.=20
If enough big transit providers offer /16 PITRs to their customers then the=
=20
more-specifics might be filtered on a larger scale.
&gt;&gt;=20
&gt;&gt; So, summary:
&gt;&gt;=20
&gt;&gt; The ways to reach a PITR would be
&gt;&gt; a) Run your own PITR (big networks, LISP users)
&gt;&gt; b) Use one from your transit(s) (smaller networks that don't have =
their own)
&gt;&gt; c) Use an altruistic one as last resort
&gt;&gt;=20
&gt;&gt; As long as (a) and (b) aren't a reality the LISP users who don't w=
ant to rely=20
on (c) can run/rent/etc a PITR for their own space. I think the routing=20
community would really appreciate it if all those more-specific routes woul=
d be=20
temporary until wide deployment of (a) and (b) make them unnecessary.
&gt;&gt;=20
&gt;&gt; And if this doesn't become a success we have a bunch of /48 prefix=
es to the=20
separate PITRs in the BGP table. It won't be much, otherwise we would have=
=20
declared success. So the risk of messing the BGP table up is very limited. =
And=20
when can tell people: if you are bothered by those more-specifics in your=
=20
routing table you can always deploy your own PITRs and filter the more-spec=
ifics=20
at your border. That might keep everyone happy.
&gt;&gt;=20
&gt;&gt; What do you think?
&gt;&gt;=20
&gt;&gt; Thanks,
&gt;&gt; Sander
&gt;&gt;=20
&gt; _______________________________________________
&gt; lisp mailing list
&gt; <a href=3D"mailto:lisp@ietf.org">lisp@ietf.org</a>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/lisp" target=3D"_blan=
k">https://www.ietf.org/mailman/listinfo/lisp</a>

--

Geoff Huston
Chief Scientist, APNIC

+61 7 3858 3100
<a href=3D"mailto:gih@apnic.net">gih@apnic.net</a>




_______________________________________________
lisp mailing list
<a href=3D"mailto:lisp@ietf.org">lisp@ietf.org</a>
<a href=3D"https://www.ietf.org/mailman/listinfo/lisp" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/lisp</a>
</tt></pre>
</div>
 <!-- end of AOLMsgPart_0_58bc4189-7065-4ba9-9ab4-1c7af3aa62cc -->



</div>
</div>
</font>
----------MB_8CF937F6DE25FD2_D74_822A9_webmail-d037.sysops.aol.com--

From jiangsheng@huawei.com  Sun Nov 18 18:10:37 2012
Return-Path: <jiangsheng@huawei.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 251BE21F84CF; Sun, 18 Nov 2012 18:10:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.449
X-Spam-Level: 
X-Spam-Status: No, score=-6.449 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 ZiCYjp0KHRRq; Sun, 18 Nov 2012 18:10:33 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 4317F21F84CC; Sun, 18 Nov 2012 18:10:31 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AMX51124; Mon, 19 Nov 2012 02:10:29 +0000 (GMT)
Received: from LHREML403-HUB.china.huawei.com (10.201.5.217) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.3; Mon, 19 Nov 2012 02:10:05 +0000
Received: from SZXEML460-HUB.china.huawei.com (10.82.67.203) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.1.323.3; Mon, 19 Nov 2012 02:10:27 +0000
Received: from szxeml545-mbx.china.huawei.com ([169.254.1.6]) by szxeml460-hub.china.huawei.com ([10.82.67.203]) with mapi id 14.01.0323.003; Mon, 19 Nov 2012 10:10:24 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: Maglione Roberta <roberta.maglione@telecomitalia.it>, "'Leaf Yeh'" <leaf.yeh.sdo@gmail.com>
Subject: RE: [Softwires] Last	Call: <draft-ietf-softwire-6rd-radius-attrib-07.txt>	(RADIUS	Attribute	for 6rd) to Proposed Standard
Thread-Topic: [Softwires] Last	Call: <draft-ietf-softwire-6rd-radius-attrib-07.txt>	(RADIUS	Attribute	for 6rd) to Proposed Standard
Thread-Index: AQHNxAP5LyU1QcTX80yMPtxTT00nhZfwafBg
Date: Mon, 19 Nov 2012 02:10:23 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B9239F8ECAC@szxeml545-mbx.china.huawei.com>
References: <20121115213918.3949.85119.idtracker@ietfa.amsl.com> <50a63503.848f440a.6460.6ac1@mx.google.com> <282BBE8A501E1F4DA9C775F964BB21FE519AC44BEA@GRFMBX704BA020.griffon.local> <50a6465d.4b53440a.7e28.73cc@mx.google.com> <282BBE8A501E1F4DA9C775F964BB21FE519AC44BEB@GRFMBX704BA020.griffon.local>
In-Reply-To: <282BBE8A501E1F4DA9C775F964BB21FE519AC44BEB@GRFMBX704BA020.griffon.local>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.140]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mailman-Approved-At: Mon, 19 Nov 2012 08:06:58 -0800
Cc: "softwires@ietf.org" <softwires@ietf.org>, "dhcwg@ietf.org" <dhcwg@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Nov 2012 02:10:37 -0000

SGksIFJvYmVydGEgYW5kIExlYWYsDQoNCkNhcmVmdWxseSBjaGVja2VkIFJGQzIxMzEsIHRoZSBv
cmlnaW5hbCB0ZXh0IHdhcyByaWdodCwgYnV0IG5vdCBjbGVhcmx5IGRlZmluZSB0aGUgdGltZSB0
aGF0IGNsaWVudCBlbnRlcnMgUkVCSU5ESU5HIHN0YXRlLiBTbyBMZWFmJ3MgY29tbWVudHMgYWxz
byByaWdodC4gTmV3IHRleHQgd2lsbCBiZSB0aGUgYmVsb3cuIEl0IHdvdWxkIGJlIGFkZGVkIGFm
dGVyIEFEJ3MgaW5zdHJ1Y3Rpb24gZm9yIG5leHQgdXBkYXRlLCBtYXliZSB3aXRoIG90aGVyIGNv
bW1lbnRzIGZyb20gSUVTRy4gDQoNCklmIHRoZSBESENQIHNlcnZlciB0byB3aGljaCB0aGUgREhD
UCBSZXF1ZXN0IG1lc3NhZ2Ugd2FzIHNlbnQgYXQgdGltZSANCiAgIFQxIGhhcyBub3QgcmVzcG9u
ZGVkICJ0aWxsIFQyIiwgdGhlIERIQ1AgY2xpZW50IGVudGVycyB0aGUgUkVCSU5ESU5HIHN0YXRl
IGFuZCANCiAgIGF0dGVtcHRzIHRvIGNvbnRhY3QgYW55IHNlcnZlci4NCg0KTWFueSB0aGFua3Mg
YW5kIGJlc3QgcmVnYXJkcywNCg0KU2hlbmcNCg0KPi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0t
DQo+RnJvbTogTWFnbGlvbmUgUm9iZXJ0YSBbbWFpbHRvOnJvYmVydGEubWFnbGlvbmVAdGVsZWNv
bWl0YWxpYS5pdF0NCj5TZW50OiBGcmlkYXksIE5vdmVtYmVyIDE2LCAyMDEyIDEwOjA5IFBNDQo+
VG86ICdMZWFmIFllaCc7IFNoZW5nIEppYW5nDQo+Q2M6IHNvZnR3aXJlc0BpZXRmLm9yZzsgZGhj
d2dAaWV0Zi5vcmc7IGlldGZAaWV0Zi5vcmcNCj5TdWJqZWN0OiBSRTogW1NvZnR3aXJlc10gTGFz
dCBDYWxsOiA8ZHJhZnQtaWV0Zi1zb2Z0d2lyZS02cmQtcmFkaXVzLWF0dHJpYi0wNy50eHQ+DQo+
KFJBRElVUyBBdHRyaWJ1dGUgZm9yIDZyZCkgdG8gUHJvcG9zZWQgU3RhbmRhcmQNCj4NCj5MZWFm
LA0KPkluIG15IG9waW5pb24gY3VycmVudCB0ZXh0IGlzIGZpbmUgYW5kIGlubGluZSB3aXRoIFJG
QzIxMzEsIHdoaWxlIHRoZSB0ZXh0IHlvdQ0KPmFyZSBwcm9wb3NpbmcgaXMgbm90IGNvbXBsZXRl
bHkgYWNjdXJhdGUgYmVjYXVzZSBpdCBkb2VzIG5vdCBjbGFyaWZ5ICJ3aGljaA0KPkRIQ1AgU2Vy
dmVyIiBoYXMgbm90IHJlcGxpZWQuDQo+DQo+J0lmIHRoZSBESENQIHNlcnZlciBoYXMgbm90IHJl
cGxpZWQgdGhlDQo+REhDUFJFUVVFU1QgbWVzc2FnZSB0aWxsIFQyLCB0aGUgREhDUCBjbGllbnQg
ZW50ZXJzIGludG8gdGhlIFJFQklORElORw0KPnN0YXRlDQo+YW5kIGF0dGVtcHRzIHRvIGNvbnRh
Y3QgYW55IHBvc3NpYmxlIHNlcnZlci4gJw0KPg0KPlNoZW5nLA0KPiBBcyBvcmlnaW5hbCBhdXRo
b3Igb2YgdGhpcyB0ZXh0LCB3aGF0IGRvIHlvdSB0aGluaz8NCj4NCj5UaGFua3MsDQo+Um9iZXJ0
YQ0KPg0KPi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+RnJvbTogTGVhZiBZZWggW21haWx0
bzpsZWFmLnllaC5zZG9AZ21haWwuY29tXQ0KPlNlbnQ6IEZyaWRheSwgTm92ZW1iZXIgMTYsIDIw
MTIgMjo1OCBQTQ0KPlRvOiBNYWdsaW9uZSBSb2JlcnRhOyBpZXRmQGlldGYub3JnDQo+Q2M6IHNv
ZnR3aXJlc0BpZXRmLm9yZzsgZGhjd2dAaWV0Zi5vcmcNCj5TdWJqZWN0OiBSRTogW1NvZnR3aXJl
c10gTGFzdCBDYWxsOiA8ZHJhZnQtaWV0Zi1zb2Z0d2lyZS02cmQtcmFkaXVzLWF0dHJpYi0wNy50
eHQ+DQo+KFJBRElVUyBBdHRyaWJ1dGUgZm9yIDZyZCkgdG8gUHJvcG9zZWQgU3RhbmRhcmQNCj4N
Cj48Um9iZXJ0YT4gQWNjb3JkaW5nIHRvIHNlY3Rpb24gNC40LjUgb2YgUkZDIDIxMzE6DQo+IiBB
dCB0aW1lIFQxIHRoZSBjbGllbnQgbW92ZXMgdG8gUkVORVdJTkcgc3RhdGUgYW5kIHNlbmRzICh2
aWEgdW5pY2FzdCkNCj4gICBhIERIQ1BSRVFVRVNUIG1lc3NhZ2UgdG8gdGhlIHNlcnZlciB0byBl
eHRlbmQgaXRzIGxlYXNlLiINCj5bLi5dDQo+IiBJZiBubyBESENQQUNLIGFycml2ZXMgYmVmb3Jl
IHRpbWUgVDIsIHRoZSBjbGllbnQgbW92ZXMgdG8gUkVCSU5ESU5HDQo+ICAgc3RhdGUgYW5kIHNl
bmRzICh2aWEgYnJvYWRjYXN0KSBhIERIQ1BSRVFVRVNUIG1lc3NhZ2UgdG8gZXh0ZW5kIGl0cw0K
PiAgIGxlYXNlLiINCj5UaGUgREhDUFJFUVVFU1QgaXMgc2VudCBhdCBUMSwgaW4gbXkgb3Bpbmlv
biB0aGUgY3VycmVudCB0ZXh0IGlzIGNvcnJlY3QuDQo+PC9Sb2JlcnRhPg0KPg0KPg0KPkNvcnJl
Y3QgYnV0IG5vdCBhY2N1cmF0ZS4gVGhlIGNsaWVudCBlbnRlcnMgdGhlIHJlYmluZGluZyBzdGF0
ZSBhZnRlciBUMg0KPmV4cGlyZWQuDQo+DQo+SG93IGFib3V0IHRvIHVwZGF0ZSB0aGUgdGV4dCB0
byBiZSAnSWYgdGhlIERIQ1Agc2VydmVyIGhhcyBub3QgcmVwbGllZCB0aGUNCj5ESENQUkVRVUVT
VCBtZXNzYWdlIHRpbGwgVDIsIHRoZSBESENQIGNsaWVudCBlbnRlcnMgaW50byB0aGUgUkVCSU5E
SU5HDQo+c3RhdGUNCj5hbmQgYXR0ZW1wdHMgdG8gY29udGFjdCBhbnkgcG9zc2libGUgc2VydmVy
LiAnPw0KPg0KPg0KPkJlc3QgUmVnYXJkcywNCj5MZWFmDQo+DQo+DQo+DQo+LS0tLS1PcmlnaW5h
bCBNZXNzYWdlLS0tLS0NCj5Gcm9tOiBNYWdsaW9uZSBSb2JlcnRhIFttYWlsdG86cm9iZXJ0YS5t
YWdsaW9uZUB0ZWxlY29taXRhbGlhLml0XQ0KPlNlbnQ6IEZyaWRheSwgTm92ZW1iZXIgMTYsIDIw
MTIgOToxMyBQTQ0KPlRvOiAnTGVhZiBZZWgnOyBpZXRmQGlldGYub3JnDQo+Q2M6IHNvZnR3aXJl
c0BpZXRmLm9yZzsgPGRoY3dnQGlldGYub3JnPiBXRw0KPlN1YmplY3Q6IFJFOiBbU29mdHdpcmVz
XSBMYXN0IENhbGw6DQo+PGRyYWZ0LWlldGYtc29mdHdpcmUtNnJkLXJhZGl1cy1hdHRyaWItMDcu
dHh0PiAoUkFESVVTIEF0dHJpYnV0ZSBmb3IgNnJkKSB0bw0KPlByb3Bvc2VkIFN0YW5kYXJkDQo+
DQo+SGkgTGVhZiwNCj4+IFNlY3Rpb24gMyAtIElmIHRoZSBESENQIHNlcnZlciB0byB3aGljaCB0
aGUgREhDUCBSZXF1ZXN0IG1lc3NhZ2Ugd2FzIHNlbnQNCj4+IGF0IHRpbWUgIFQxIGhhcyBub3Qg
cmVzcG9uZGVkLCB0aGUgREhDUCBjbGllbnQgZW50ZXJzIHRoZSBSRUJJTkRJTkcNCj5zdGF0ZQ0K
Pj4gYW5kICBhdHRlbXB0cyB0byBjb250YWN0IGFueSBzZXJ2ZXIuDQo+DQo+PiBQZXIgdGhlIEZp
Z3VyZSA1IGluIFJGQzIxMzEsIHRoZSBhYm92ZSAnVDEnIHNvdW5kcyAnVDInLg0KPihodHRwOi8v
d3d3LnJmYy1lZGl0b3Iub3JnL3JmYy9yZmMyMTMxLnR4dCkNCj4NCj5XaHkgVDI/DQo+QWNjb3Jk
aW5nIHRvIHNlY3Rpb24gNC40LjUgb2YgUkZDIDIxMzE6DQo+IiBBdCB0aW1lIFQxIHRoZSBjbGll
bnQgbW92ZXMgdG8gUkVORVdJTkcgc3RhdGUgYW5kIHNlbmRzICh2aWEgdW5pY2FzdCkNCj4gICBh
IERIQ1BSRVFVRVNUIG1lc3NhZ2UgdG8gdGhlIHNlcnZlciB0byBleHRlbmQgaXRzIGxlYXNlLiIN
Cj5bLi5dDQo+DQo+IiBJZiBubyBESENQQUNLIGFycml2ZXMgYmVmb3JlIHRpbWUgVDIsIHRoZSBj
bGllbnQgbW92ZXMgdG8gUkVCSU5ESU5HDQo+ICAgc3RhdGUgYW5kIHNlbmRzICh2aWEgYnJvYWRj
YXN0KSBhIERIQ1BSRVFVRVNUIG1lc3NhZ2UgdG8gZXh0ZW5kIGl0cw0KPiAgIGxlYXNlLiINCj4N
Cj5UaGUgREhDUFJFUVVFU1QgaXMgc2VudCBhdCBUMSwgaW4gbXkgb3BpbmlvbiB0aGUgY3VycmVu
dCB0ZXh0IGlzIGNvcnJlY3QuDQo+VGhhbmtzDQo+UmVnYXJkcywNCj5Sb2JlcnRhDQo+DQo+LS0t
LS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj5Gcm9tOiBzb2Z0d2lyZXMtYm91bmNlc0BpZXRmLm9y
ZyBbbWFpbHRvOnNvZnR3aXJlcy1ib3VuY2VzQGlldGYub3JnXSBPbg0KPkJlaGFsZiBPZiBMZWFm
IFllaA0KPlNlbnQ6IEZyaWRheSwgTm92ZW1iZXIgMTYsIDIwMTIgMTo0NCBQTQ0KPlRvOiBpZXRm
QGlldGYub3JnDQo+Q2M6IHNvZnR3aXJlc0BpZXRmLm9yZw0KPlN1YmplY3Q6IFJlOiBbU29mdHdp
cmVzXSBMYXN0IENhbGw6DQo+PGRyYWZ0LWlldGYtc29mdHdpcmUtNnJkLXJhZGl1cy1hdHRyaWIt
MDcudHh0PiAoUkFESVVTIEF0dHJpYnV0ZSBmb3IgNnJkKSB0bw0KPlByb3Bvc2VkIFN0YW5kYXJk
DQo+DQo+U2VjdGlvbiAzIC0gQWZ0ZXIgdGhlIEJORyByZXNwb25kcyB0byB0aGUgdXNlciB3aXRo
DQo+ICAgYW4gQWR2ZXJ0aXNlIG1lc3NhZ2UsIHRoZSB1c2VyIHJlcXVlc3RzIGZvciBhIERIQ1Ag
NnJkIE9wdGlvbiBieQ0KPiAgIGNhcnJ5aW5nIGEgUGFyYW1ldGVyIFJlcXVlc3Qgb3B0aW9uICg1
NSkgW1JGQzIxMzJdLg0KPg0KPlBlciB0aGUgRmlndXJlIDEgaW4gU2VjdGlvbiAzLCB0aGUgYWJv
dmUgJ0FkdmVydGlzZSBtZXNzYWdlJyBzb3VuZHMgdGhlDQo+REhDUHY0IG1lc3NhZ2Ugb2YgJ0RI
Q1BPRkZFUiAoMiknLg0KPihodHRwOi8vd3d3LmlhbmEub3JnL2Fzc2lnbm1lbnRzL2Jvb3RwLWRo
Y3AtcGFyYW1ldGVycy9ib290cC1kaGNwLXBhcmENCj5tZXRlcnMNCj4ueG1sKQ0KPg0KPg0KPlNl
Y3Rpb24gMyAtIElmIHRoZSBESENQIHNlcnZlciB0byB3aGljaCB0aGUgREhDUCBSZXF1ZXN0IG1l
c3NhZ2Ugd2FzIHNlbnQNCj5hdA0KPnRpbWUNCj4gICBUMSBoYXMgbm90IHJlc3BvbmRlZCwgdGhl
IERIQ1AgY2xpZW50IGVudGVycyB0aGUgUkVCSU5ESU5HIHN0YXRlIGFuZA0KPiAgIGF0dGVtcHRz
IHRvIGNvbnRhY3QgYW55IHNlcnZlci4NCj4NCj5QZXIgdGhlIEZpZ3VyZSA1IGluIFJGQzIxMzEs
IHRoZSBhYm92ZSAnVDEnIHNvdW5kcyAnVDInLg0KPihodHRwOi8vd3d3LnJmYy1lZGl0b3Iub3Jn
L3JmYy9yZmMyMTMxLnR4dCkNCj4NCj4NCj5CZXN0IFJlZ2FyZHMsDQo+TGVhZg0KPg0KPg0KPg0K
Pg0KPg0KPi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+RnJvbTogc29mdHdpcmVzLWJvdW5j
ZXNAaWV0Zi5vcmcgW21haWx0bzpzb2Z0d2lyZXMtYm91bmNlc0BpZXRmLm9yZ10gT24NCj5CZWhh
bGYgT2YgVGhlIElFU0cNCj5TZW50OiBGcmlkYXksIE5vdmVtYmVyIDE2LCAyMDEyIDU6MzkgQU0N
Cj5UbzogSUVURi1Bbm5vdW5jZQ0KPkNjOiBzb2Z0d2lyZXNAaWV0Zi5vcmcNCj5TdWJqZWN0OiBb
U29mdHdpcmVzXSBMYXN0IENhbGw6DQo+PGRyYWZ0LWlldGYtc29mdHdpcmUtNnJkLXJhZGl1cy1h
dHRyaWItMDcudHh0PiAoUkFESVVTIEF0dHJpYnV0ZSBmb3IgNnJkKSB0bw0KPlByb3Bvc2VkIFN0
YW5kYXJkDQo+DQo+DQo+VGhlIElFU0cgaGFzIHJlY2VpdmVkIGEgcmVxdWVzdCBmcm9tIHRoZSBT
b2Z0d2lyZXMgV0cgKHNvZnR3aXJlKSB0byBjb25zaWRlcg0KPnRoZSBmb2xsb3dpbmcgZG9jdW1l
bnQ6DQo+LSAnUkFESVVTIEF0dHJpYnV0ZSBmb3IgNnJkJw0KPiAgPGRyYWZ0LWlldGYtc29mdHdp
cmUtNnJkLXJhZGl1cy1hdHRyaWItMDcudHh0PiBhcyBQcm9wb3NlZCBTdGFuZGFyZA0KPg0KPlRo
ZSBJRVNHIHBsYW5zIHRvIG1ha2UgYSBkZWNpc2lvbiBpbiB0aGUgbmV4dCBmZXcgd2Vla3MsIGFu
ZCBzb2xpY2l0cyBmaW5hbA0KPmNvbW1lbnRzIG9uIHRoaXMgYWN0aW9uLiBQbGVhc2Ugc2VuZCBz
dWJzdGFudGl2ZSBjb21tZW50cyB0byB0aGUNCj5pZXRmQGlldGYub3JnIG1haWxpbmcgbGlzdHMg
YnkgMjAxMi0xMS0yOS4gRXhjZXB0aW9uYWxseSwgY29tbWVudHMgbWF5IGJlDQo+c2VudCB0byBp
ZXNnQGlldGYub3JnIGluc3RlYWQuIEluIGVpdGhlciBjYXNlLCBwbGVhc2UgcmV0YWluIHRoZSBi
ZWdpbm5pbmcNCj5vZiB0aGUgU3ViamVjdCBsaW5lIHRvIGFsbG93IGF1dG9tYXRlZCBzb3J0aW5n
Lg0KPg0KPkFic3RyYWN0DQo+DQo+DQo+ICAgSVB2NiBSYXBpZCBEZXBsb3ltZW50ICg2cmQpIGlz
IG9uZSBvZiB0aGUgbW9zdCBwb3B1bGFyIG1ldGhvZHMgdG8NCj4gICBwcm92aWRlIGJvdGggSVB2
NCBhbmQgSVB2NiBjb25uZWN0aXZpdHkgc2VydmljZXMgc2ltdWx0YW5lb3VzbHkNCj4gICBkdXJp
bmcgdGhlIElQdjQvSVB2NiBjby1leGlzdGluZyBwZXJpb2QuIFRoZSBEeW5hbWljIEhvc3QNCj4g
ICBDb25maWd1cmF0aW9uIFByb3RvY29sIChESENQKSA2cmQgb3B0aW9uIGhhcyBiZWVuIGRlZmlu
ZWQgdG8NCj4gICBjb25maWd1cmUgNnJkIEN1c3RvbWVyIEVkZ2UgKENFKS4gSG93ZXZlciwgaW4g
bWFueSBuZXR3b3JrcywgdGhlDQo+ICAgY29uZmlndXJhdGlvbiBpbmZvcm1hdGlvbiBtYXkgYmUg
c3RvcmVkIGluIEF1dGhlbnRpY2F0aW9uDQo+ICAgQXV0aG9yaXphdGlvbiBhbmQgQWNjb3VudGlu
ZyAoQUFBKSBzZXJ2ZXJzIHdoaWxlIHVzZXIgY29uZmlndXJhdGlvbg0KPiAgIGlzIG1haW5seSBm
cm9tIEJyb2FkYmFuZCBOZXR3b3JrIEdhdGV3YXkgKEJORykgdGhyb3VnaCBESENQDQo+cHJvdG9j
b2wuDQo+ICAgVGhpcyBkb2N1bWVudCBkZWZpbmVzIGEgUmVtb3RlIEF1dGhlbnRpY2F0aW9uIERp
YWwgSW4gVXNlciBTZXJ2aWNlDQo+ICAgKFJBRElVUykgYXR0cmlidXRlIHRoYXQgY2FycmllcyA2
cmQgY29uZmlndXJhdGlvbiBpbmZvcm1hdGlvbiBmcm9tDQo+ICAgQUFBIHNlcnZlciB0byBCTkcu
DQo+DQo+DQo+DQo+DQo+DQo+DQo+VGhlIGZpbGUgY2FuIGJlIG9idGFpbmVkIHZpYQ0KPmh0dHA6
Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQtaWV0Zi1zb2Z0d2lyZS02cmQtcmFkaXVz
LWF0dHJpYi8NCj4NCj5JRVNHIGRpc2N1c3Npb24gY2FuIGJlIHRyYWNrZWQgdmlhDQo+aHR0cDov
L2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC1pZXRmLXNvZnR3aXJlLTZyZC1yYWRpdXMt
YXR0cmliL2JhbGxvdA0KPi8NCj4NCj4NCj5ObyBJUFIgZGVjbGFyYXRpb25zIGhhdmUgYmVlbiBz
dWJtaXR0ZWQgZGlyZWN0bHkgb24gdGhpcyBJLUQuDQo+DQo+DQo+X19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj5Tb2Z0d2lyZXMgbWFpbGluZyBsaXN0DQo+
U29mdHdpcmVzQGlldGYub3JnDQo+aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5m
by9zb2Z0d2lyZXMNCj4NCj5fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fXw0KPlNvZnR3aXJlcyBtYWlsaW5nIGxpc3QNCj5Tb2Z0d2lyZXNAaWV0Zi5vcmcNCj5o
dHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3NvZnR3aXJlcw0KPg0KPlF1ZXN0
byBtZXNzYWdnaW8gZSBpIHN1b2kgYWxsZWdhdGkgc29ubyBpbmRpcml6emF0aSBlc2NsdXNpdmFt
ZW50ZSBhbGxlDQo+cGVyc29uZSBpbmRpY2F0ZS4gTGEgZGlmZnVzaW9uZSwgY29waWEgbyBxdWFs
c2lhc2kgYWx0cmEgYXppb25lIGRlcml2YW50ZQ0KPmRhbGxhIGNvbm9zY2VuemEgZGkgcXVlc3Rl
IGluZm9ybWF6aW9uaSBzb25vIHJpZ29yb3NhbWVudGUgdmlldGF0ZS4gUXVhbG9yYQ0KPmFiYmlh
dGUgcmljZXZ1dG8gcXVlc3RvIGRvY3VtZW50byBwZXIgZXJyb3JlIHNpZXRlIGNvcnRlc2VtZW50
ZSBwcmVnYXRpIGRpDQo+ZGFybmUgaW1tZWRpYXRhIGNvbXVuaWNhemlvbmUgYWwgbWl0dGVudGUg
ZSBkaSBwcm92dmVkZXJlIGFsbGEgc3VhDQo+ZGlzdHJ1emlvbmUsIEdyYXppZS4NCj4NCj5UaGlz
IGUtbWFpbCBhbmQgYW55IGF0dGFjaG1lbnRzIGlzIGNvbmZpZGVudGlhbCBhbmQgbWF5IGNvbnRh
aW4gcHJpdmlsZWdlZA0KPmluZm9ybWF0aW9uIGludGVuZGVkIGZvciB0aGUgYWRkcmVzc2VlKHMp
IG9ubHkuIERpc3NlbWluYXRpb24sIGNvcHlpbmcsDQo+cHJpbnRpbmcgb3IgdXNlIGJ5IGFueWJv
ZHkgZWxzZSBpcyB1bmF1dGhvcmlzZWQuIElmIHlvdSBhcmUgbm90IHRoZSBpbnRlbmRlZA0KPnJl
Y2lwaWVudCwgcGxlYXNlIGRlbGV0ZSB0aGlzIG1lc3NhZ2UgYW5kIGFueSBhdHRhY2htZW50cyBh
bmQgYWR2aXNlIHRoZQ0KPnNlbmRlciBieSByZXR1cm4gZS1tYWlsLCBUaGFua3MuDQo+DQo+DQo+
UXVlc3RvIG1lc3NhZ2dpbyBlIGkgc3VvaSBhbGxlZ2F0aSBzb25vIGluZGlyaXp6YXRpIGVzY2x1
c2l2YW1lbnRlIGFsbGUNCj5wZXJzb25lIGluZGljYXRlLiBMYSBkaWZmdXNpb25lLCBjb3BpYSBv
IHF1YWxzaWFzaSBhbHRyYSBhemlvbmUgZGVyaXZhbnRlIGRhbGxhDQo+Y29ub3NjZW56YSBkaSBx
dWVzdGUgaW5mb3JtYXppb25pIHNvbm8gcmlnb3Jvc2FtZW50ZSB2aWV0YXRlLiBRdWFsb3JhDQo+
YWJiaWF0ZSByaWNldnV0byBxdWVzdG8gZG9jdW1lbnRvIHBlciBlcnJvcmUgc2lldGUgY29ydGVz
ZW1lbnRlIHByZWdhdGkgZGkNCj5kYXJuZSBpbW1lZGlhdGEgY29tdW5pY2F6aW9uZSBhbCBtaXR0
ZW50ZSBlIGRpIHByb3Z2ZWRlcmUgYWxsYSBzdWENCj5kaXN0cnV6aW9uZSwgR3JhemllLg0KPg0K
PlRoaXMgZS1tYWlsIGFuZCBhbnkgYXR0YWNobWVudHMgaXMgY29uZmlkZW50aWFsIGFuZCBtYXkg
Y29udGFpbiBwcml2aWxlZ2VkDQo+aW5mb3JtYXRpb24gaW50ZW5kZWQgZm9yIHRoZSBhZGRyZXNz
ZWUocykgb25seS4gRGlzc2VtaW5hdGlvbiwgY29weWluZywNCj5wcmludGluZyBvciB1c2UgYnkg
YW55Ym9keSBlbHNlIGlzIHVuYXV0aG9yaXNlZC4gSWYgeW91IGFyZSBub3QgdGhlIGludGVuZGVk
DQo+cmVjaXBpZW50LCBwbGVhc2UgZGVsZXRlIHRoaXMgbWVzc2FnZSBhbmQgYW55IGF0dGFjaG1l
bnRzIGFuZCBhZHZpc2UgdGhlDQo+c2VuZGVyIGJ5IHJldHVybiBlLW1haWwsIFRoYW5rcy4NCg0K

From mjethanandani@gmail.com  Sun Nov 18 23:58:40 2012
Return-Path: <mjethanandani@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6375821F84E8; Sun, 18 Nov 2012 23:58:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[AWL=-1.150, BAYES_00=-2.599, HTML_MESSAGE=0.001, MANGLED_LIST=2.3, 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 6eBfwlC3bOiz; Sun, 18 Nov 2012 23:58:39 -0800 (PST)
Received: from mail-da0-f44.google.com (mail-da0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id 56CA521F8616; Sun, 18 Nov 2012 23:58:39 -0800 (PST)
Received: by mail-da0-f44.google.com with SMTP id h15so2074484dan.31 for <multiple recipients>; Sun, 18 Nov 2012 23:58:39 -0800 (PST)
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=M4giSIc/BkvbUrg2BNJmFdxGpyBW2dBCS65v2obv+Jw=; b=P404mYWgADoqfYQubjn9dqwTL6a6xZ24bpniGZB+kLpsZGToB245vkfg0gwI62NjI/ 2f2MkgIHjmYFqGQjW+aVuJ2abYipY2O7+bwYijWnfNNDJxtfP6jY0s/OXrMA3tAmaFj/ Fp0hKQLFpIf8qby0K7Qymjqlk2yHZSoh3ilBbndxAaUlOUecpB5hBMEEJTjY5+LnRGGm JMRjyACpfz/ZBoW2FyJ7MEj+egNs5zsDx2on7dRffYLub56gaLx+o3vMUSYCNEusrszo NTBD+LVqT/f8dDeOX3qx0ZRnHCSyIhCj4ZMLMidGxSw3zeDd4kZ8uFcqr7Z0Vs/EURlk Yfrg==
Received: by 10.66.90.65 with SMTP id bu1mr33679867pab.31.1353311919024; Sun, 18 Nov 2012 23:58:39 -0800 (PST)
Received: from [192.168.1.123] (c-24-6-180-144.hsd1.ca.comcast.net. [24.6.180.144]) by mx.google.com with ESMTPS id l5sm5773034paz.14.2012.11.18.23.58.37 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 18 Nov 2012 23:58:38 -0800 (PST)
Subject: Re: Gen-ART LC Review of draft-ietf-karp-routing-tcp-analysis-05.txt
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: multipart/alternative; boundary=Apple-Mail-36--804921993
From: Mahesh Jethanandani <mjethanandani@gmail.com>
In-Reply-To: <18E6B18A-D465-47C6-9E06-886DFBFA1F67@nostrum.com>
Date: Sun, 18 Nov 2012 23:58:36 -0800
Message-Id: <F53DCC9A-8AA1-42D4-BF19-88ABCCCA68A7@gmail.com>
References: <18E6B18A-D465-47C6-9E06-886DFBFA1F67@nostrum.com>
To: Ben Campbell <ben@nostrum.com>
X-Mailer: Apple Mail (2.1085)
X-Mailman-Approved-At: Mon, 19 Nov 2012 08:06:57 -0800
Cc: draft-ietf-karp-routing-tcp-analysis.all@tools.ietf.org, "gen-art@ietf.org Review Team" <gen-art@ietf.org>, "ietf@ietf.org List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Nov 2012 07:58:40 -0000

--Apple-Mail-36--804921993
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252


On Nov 14, 2012, at 3:39 PM, Ben Campbell wrote:

> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
>=20
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please resolve these comments along with any other Last Call comments
> you may receive.
>=20
> Document: draft-ietf-karp-routing-tcp-analysis-05.txt
> Reviewer: Ben Campbell
> Review Date: 2012-11-14
> IETF LC End Date: 2012-11-19
>=20
> Summary: This draft is almost ready for publication as an =
informational RFC. There are a few minor issues and a number of =
editorial issues that should be considered prior to publication.
>=20
> *** Major issues ***:
>=20
> None
>=20
> *** Minor issues *** :
>=20
> -- section 2.2, last paragraph:
>=20
> The IKE mention lacks context. Do you mean to suggest IKE with IPSec? =
I assume so, but there's been no mention of IPSec so far.

No. It implies the use of IKEv2 protocol for performing mutual =
authentication and establishing SA. There is no suggestion of using IKE =
with IPSec.

How about this?

For point-to-point key management IKEv2[RFC5996] protocol provides ...


>=20
> -- section 2.3.2:
>=20
> It would be helpful for this section to describe whether privacy =
issues actually matter or not, rather than just stating the issues to be =
similar to those for other routing protocols.

Changed it to:

Labels, like routing information are distributed in the clear. There is =
currently no requirement for labels to be encrypted and that work is =
outside the scope of the KARP working group.

>=20
> -- section 3.1, 2nd paragraph:
>=20
> Does this mean that privacy is really not needed, or just that LDP =
does not state a requirement for privacy?

Further clarified it in this section.

Labels are similar to routing information which is distributed in the =
clear. It is important to ensure that routers exchaning labels are =
mutually authenticated and that there are no rogue peers or =
unauthenticated peers that can compromise the stability of the network. =
However, there is currently no requirement that the labels be encrypted.

>=20
> -- Section 6 (Security Considerations), 4th paragraph:
>=20
> If replay protection is required, shouldn't the draft discuss the =
details somewhere? I see only one mention in passing outside of this =
section.

I have moved the replay protection requirement to the gap analysis =
section.=20

However, this document is a analysis draft, and it is my understanding =
that details on what replay protection methods should be adopted, is =
best left to the routing protocols in question.=20

>=20
> *** Nits/editorial comments ***:
>=20
> -- IDNits indicates some unused and obsoleted references. Please =
check.

Found one unused reference and have removed it.

>=20
> -- The IANA considerations section is missing. If the draft makes =
requests of IANA, it should include the section and state that.

There are no IANA requests. I have gone ahead and added a section on =
IANA considerations and stated none are requested.

>=20
> -- the short title is "The IANA considerations section is missing. If =
the draft makes requests of IANA, it should include the section and say =
that

>=20
> -- The short title is "draft-ietf-karp-routing-tcp-analysis-05.txt". =
Is this draft in any way specific to TCP? If so, it would be helpful to =
mention that in the abstract and introduction.

Done.

>=20
> -- Punctuation errors are pervasive, particularly in the early and =
late sections. These make it harder to read than it needs to be. In =
particular, I suggest the draft be proofread for missing commas and =
missing quotes (or other marks) around document titles.
>=20
> -- Section 1, paragraph 1:
>=20
> The cited doc name should be quoted, or otherwise marked. Also, it's =
not necessary to put the full reference here, since you are citing the =
references section.
>=20
> -- Section 1, paragraph 1: "Four main steps were identified for that =
tightening:"
>=20
> For what tightening? This is the first mention. Perhaps the previous =
sentence should have gone on to say "... and suggests steps to tighten =
the infrastructure against the attack"?

Done.

>=20
> -- section 1, 1st paragraph after numbered list:
>=20
> The end of the paragraph does not seem related to the beginning. I =
suggest a paragraph split before the sentence starting with "The OPSEC =
working group..."=20

Done.

>=20
> -- section 1, 2nd to last paragraph: "current state of security =
method"
>=20
> Missing article before "security method".

Done.

>=20
> -- section 1.1:
>=20
> Why is 2119 language needed? I see two potentially normative =
statements--but both of those merely describe the existing MAC =
requirements in TCP-AO. It would be better to state those in descriptive =
language (e.g. TCP-AO requires=85) and to drop the 2119 section =
entirely.=20

Done.

>=20
> -- section 2.1,  5th paragraph:
>=20
> A mention of SHA1 seems needed here. Section 2.3.1.2 states the =
concerns about TCP-md5 more clearly.

The 6th paragraph states the concern and mentions SHA-1. Did you want =
something more to be included?

>=20
> -- section 2.3.1.2, 1st paragraph: "As stated above..."
>=20
> A section reference would be helpful.

Done.

>=20
> -- section 4, 2nd paragraph: "In addition Improving TCP=92s Robustness =
to Blind In-Window Attacks."
>=20
> sentence fragment.

Changed it to say:

In addition, the recommendations in Improving TCP's Robustness to Blind =
In-Window Attacks

>=20
> -- section 4, 3rd paragraph:
>=20
> It would have been helpful to mention the MKT manual config issue back =
in the "state of the security method" sections.
>=20

Good point. Moved the mention to section 2.2 - Keying issue.

>=20

Mahesh Jethanandani
mjethanandani@gmail.com




--Apple-Mail-36--804921993
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=windows-1252

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><div><div>On Nov 14, 2012, at 3:39 PM, Ben Campbell =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div>I am the assigned Gen-ART reviewer for this draft. =
For background on<br>Gen-ART, please see the FAQ at<br><br>&lt;<a =
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq">http://wi=
ki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a>&gt;.<br><br>Please =
resolve these comments along with any other Last Call comments<br>you =
may receive.<br><br>Document: =
draft-ietf-karp-routing-tcp-analysis-05.txt<br>Reviewer: Ben =
Campbell<br>Review Date: 2012-11-14<br>IETF LC End Date: =
2012-11-19<br><br>Summary: This draft is almost ready for publication as =
an informational RFC. There are a few minor issues and a number of =
editorial issues that should be considered prior to =
publication.<br><br>*** Major issues ***:<br><br>None<br><br>*** Minor =
issues *** :<br><br>-- section 2.2, last paragraph:<br><br>The IKE =
mention lacks context. Do you mean to suggest IKE with IPSec? I assume =
so, but there's been no mention of IPSec so =
far.<br></div></blockquote><div><br></div>No. It implies the use of =
IKEv2 protocol for performing mutual authentication and establishing SA. =
There is no suggestion of using IKE with =
IPSec.</div><div><br></div><div>How about =
this?</div><div><br></div><div><i>For point-to-point key management =
IKEv2[RFC5996] protocol provides =
...</i></div><div><br></div><div><br><blockquote type=3D"cite"><div><br>--=
 section 2.3.2:<br><br>It would be helpful for this section to describe =
whether privacy issues actually matter or not, rather than just stating =
the issues to be similar to those for other routing =
protocols.<br></div></blockquote><div><br></div>Changed it =
to:</div><div><br></div><div><i>Labels, like routing information are =
distributed in the clear. There is currently no requirement for labels =
to be encrypted and that work is outside the scope of the KARP working =
group.</i></div><div><br><blockquote type=3D"cite"><div><br>-- section =
3.1, 2nd paragraph:<br><br>Does this mean that privacy is really not =
needed, or just that LDP does not state a requirement for =
privacy?<br></div></blockquote><div><br></div>Further clarified it in =
this section.</div><div><br></div><div><i>Labels are similar to routing =
information which is distributed in the clear. It is important to ensure =
that routers exchaning labels are mutually authenticated and that there =
are no rogue peers or unauthenticated peers that can compromise the =
stability of the network. However, there is currently no requirement =
that the labels be encrypted.</i></div><div><br><blockquote =
type=3D"cite"><div><br>-- Section 6 (Security Considerations), 4th =
paragraph:<br><br>If replay protection is required, shouldn't the draft =
discuss the details somewhere? I see only one mention in passing outside =
of this section.<br></div></blockquote><div><br></div><div>I have moved =
the replay protection requirement to the gap analysis =
section.&nbsp;</div><div><br></div><div>However, this document is a =
analysis draft, and it is my understanding that details on what replay =
protection methods should be adopted, is best left to the routing =
protocols in question.&nbsp;</div></div><div><br><blockquote =
type=3D"cite"><div><br>*** Nits/editorial comments ***:<br><br>-- IDNits =
indicates some unused and obsoleted references. Please =
check.<br></div></blockquote><div><br></div>Found one unused reference =
and have removed it.</div><div><br><blockquote type=3D"cite"><div><br>-- =
The IANA considerations section is missing. If the draft makes requests =
of IANA, it should include the section and state =
that.<br></div></blockquote><div><br></div>There are no IANA requests. I =
have gone ahead and added a section on IANA considerations and stated =
none are requested.</div><div><br><blockquote type=3D"cite"><div><br>-- =
the short title is "The IANA considerations section is missing. If the =
draft makes requests of IANA, it should include the section and say =
that</div></blockquote></div><div><blockquote type=3D"cite"><div><br>-- =
The short title is "draft-ietf-karp-routing-tcp-analysis-05.txt". Is =
this draft in any way specific to TCP? If so, it would be helpful to =
mention that in the abstract and =
introduction.<br></div></blockquote><br>Done.</div><div><br><blockquote =
type=3D"cite"><div><br>-- Punctuation errors are pervasive, particularly =
in the early and late sections. These make it harder to read than it =
needs to be. In particular, I suggest the draft be proofread for missing =
commas and missing quotes (or other marks) around document =
titles.<br><br>-- Section 1, paragraph 1:<br><br>The cited doc name =
should be quoted, or otherwise marked. Also, it's not necessary to put =
the full reference here, since you are citing the references =
section.<br><br>-- Section 1, paragraph 1: "Four main steps were =
identified for that tightening:"<br><br>For what tightening? This is the =
first mention. Perhaps the previous sentence should have gone on to say =
"... and suggests steps to tighten the infrastructure against the =
attack"?<br></div></blockquote><div><br></div>Done.</div><div><br><blockqu=
ote type=3D"cite"><div><br>-- section 1, 1st paragraph after numbered =
list:<br><br>The end of the paragraph does not seem related to the =
beginning. I suggest a paragraph split before the sentence starting with =
"The OPSEC working group..." =
<br></div></blockquote><div><br></div>Done.</div><div><br><blockquote =
type=3D"cite"><div><br>-- section 1, 2nd to last paragraph: "current =
state of security method"<br><br>Missing article before "security =
method".<br></div></blockquote><div><br></div>Done.</div><div><br><blockqu=
ote type=3D"cite"><div><br>-- section 1.1:<br><br>Why is 2119 language =
needed? I see two potentially normative statements--but both of those =
merely describe the existing MAC requirements in TCP-AO. It would be =
better to state those in descriptive language (e.g. TCP-AO requires=85) =
and to drop the 2119 section entirely. =
<br></div></blockquote><div><br></div>Done.</div><div><br><blockquote =
type=3D"cite"><div><br>-- section 2.1, &nbsp;5th paragraph:<br><br>A =
mention of SHA1 seems needed here. Section 2.3.1.2 states the concerns =
about TCP-md5 more clearly.<br></div></blockquote><div><br></div>The 6th =
paragraph states the concern and mentions SHA-1. Did you want something =
more to be included?</div><div><br><blockquote type=3D"cite"><div><br>-- =
section 2.3.1.2, 1st paragraph: "As stated above..."<br><br>A section =
reference would be =
helpful.<br></div></blockquote><div><br></div>Done.</div><div><br><blockqu=
ote type=3D"cite"><div><br>-- section 4, 2nd paragraph: "In addition =
Improving TCP=92s Robustness to Blind In-Window =
Attacks."<br><br>sentence =
fragment.<br></div></blockquote><div><br></div>Changed it to =
say:</div><div><br></div><div><i>In addition, the recommendations in =
Improving TCP's Robustness to Blind In-Window =
Attacks</i></div><div><br><blockquote type=3D"cite"><div><br>-- section =
4, 3rd paragraph:<br><br>It would have been helpful to mention the MKT =
manual config issue back in the "state of the security method" =
sections.<br><br></div></blockquote><br>Good point. Moved the mention to =
section 2.2 - Keying issue.</div><div><br><blockquote =
type=3D"cite"><div><br></div></blockquote></div><br><div>
<div>Mahesh Jethanandani</div><div><a =
href=3D"mailto:mjethanandani@gmail.com">mjethanandani@gmail.com</a></div><=
div><br></div><br class=3D"Apple-interchange-newline">
</div>
<br></body></html>=

--Apple-Mail-36--804921993--

From nomcom-chair@ietf.org  Mon Nov 19 18:54:18 2012
Return-Path: <nomcom-chair@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 27EFA21F87FA; Mon, 19 Nov 2012 18:54:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.727
X-Spam-Level: 
X-Spam-Status: No, score=-101.727 tagged_above=-999 required=5 tests=[AWL=-0.523, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, 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 nG2-y57CWQR2; Mon, 19 Nov 2012 18:54:17 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD98321F87F6; Mon, 19 Nov 2012 18:54:17 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: NomCom Chair <nomcom-chair@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
Subject: NomCom: Call for Nominations - IAOC Mid-Term Vacancy 
X-Test-IDTracker: no
X-IETF-IDTracker: 4.36
Message-ID: <20121120025417.29733.20380.idtracker@ietfa.amsl.com>
Date: Mon, 19 Nov 2012 18:54:17 -0800
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Nov 2012 02:54:18 -0000

The IETF Nominating Committee (NomCom) has been asked to fill the =

IAOC position previously held by Marshall Eubanks. Therefore, the =

NomCom is soliciting nominations for individuals who would be a good =

choice to fill this position.

The desired qualifications for IAOC members can be found at: =

https://www.ietf.org/group/nomcom/2012/iaoc-requirements

The NomCom is currently considering the following three individuals for =

the IAOC position previously held by Dave Crocker. The NomCom will =

additionally consider these individuals to fill the mid-term vacancy on the =

IAOC:
-- Randy Bush
-- Tobias Gondrom
-- Chris Griffiths


If you know of another individual that the NomCom should consider in =

filling the mid-term vacancy on the IAOC, please send email to =

nomcom12@ietf.org. As always, the NomCom is happy to accept self-
nominations.

The NomCom wishes to move as quickly as possible in filling this mid-term =

vacancy. Therefore, if you have a Nomination to make, please do so by =

Monday, December 3.

Thank you for your help,
- Matt Lepinski
  nomcom-chair@ietf.org

From hallam@gmail.com  Tue Nov 20 06:46:56 2012
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 98C0321F8722; Tue, 20 Nov 2012 06:46:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.127
X-Spam-Level: 
X-Spam-Status: No, score=-4.127 tagged_above=-999 required=5 tests=[AWL=-0.529, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 9pkdGsG5kMqS; Tue, 20 Nov 2012 06:46:55 -0800 (PST)
Received: from mail-ob0-f172.google.com (mail-ob0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id 6D7B121F870A; Tue, 20 Nov 2012 06:46:55 -0800 (PST)
Received: by mail-ob0-f172.google.com with SMTP id ef5so6519089obb.31 for <multiple recipients>; Tue, 20 Nov 2012 06:46:55 -0800 (PST)
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 :cc:content-type; bh=mCI5/dAiWm9wqgZqNbNp9u4vZ6SNz49jZjoUW1wAxR4=; b=FSK74Iu1S/Cj+DRCc8NcW8szxp3innsJTSEZfSbQGaX07jWjcYtdcNV+e1seo36xdX HAY2XkeWAhipa1ybyLQ9pp+XPBLb6zWxIUvkwAEcinEEgsPt+f4BCMqLEvmw9EnCNupG q1gIkvBrwkkyjUwGLiunTjM8F3C1kHrLY6Tqdnir7hdIwIqgneHlJmJEu3Ml54eR/WkM ABuJpRA1iewID1/NwjZK5E3OKT92zrIIc4K2SvYpXKMOXthnjW5AuaTK/GyjE0L/Ob8y nhdhVtKskj0jBU23K3jP/zS7QWM2sNY8MhfP8WsHWPwkUoX/A4vFP8rCNiLQpRnSX6hZ GDng==
MIME-Version: 1.0
Received: by 10.182.113.5 with SMTP id iu5mr13549740obb.36.1353422814973; Tue, 20 Nov 2012 06:46:54 -0800 (PST)
Received: by 10.76.27.103 with HTTP; Tue, 20 Nov 2012 06:46:54 -0800 (PST)
In-Reply-To: <20121120025417.29733.20380.idtracker@ietfa.amsl.com>
References: <20121120025417.29733.20380.idtracker@ietfa.amsl.com>
Date: Tue, 20 Nov 2012 09:46:54 -0500
Message-ID: <CAMm+Lwj6bxV=M5pPrS0tL7PzG-3SFpsq2GGnKiQz9eho-YepTA@mail.gmail.com>
Subject: Re: NomCom: Call for Nominations - IAOC Mid-Term Vacancy
From: Phillip Hallam-Baker <hallam@gmail.com>
To: NomCom Chair <nomcom-chair@ietf.org>
Content-Type: multipart/alternative; boundary=f46d0447f1881e109304ceee4e37
Cc: ietf@ietf.org, IETF Announcement List <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Nov 2012 14:46:56 -0000

--f46d0447f1881e109304ceee4e37
Content-Type: text/plain; charset=ISO-8859-1

I am confused, is the NomCon filling one position here or two?

On Mon, Nov 19, 2012 at 9:54 PM, NomCom Chair <nomcom-chair@ietf.org> wrote:

> The IETF Nominating Committee (NomCom) has been asked to fill the
> IAOC position previously held by Marshall Eubanks. Therefore, the
> NomCom is soliciting nominations for individuals who would be a good
> choice to fill this position.
>
> The desired qualifications for IAOC members can be found at:
> https://www.ietf.org/group/nomcom/2012/iaoc-requirements
>
> The NomCom is currently considering the following three individuals for
> the IAOC position previously held by Dave Crocker. The NomCom will
> additionally consider these individuals to fill the mid-term vacancy on the
> IAOC:
> -- Randy Bush
> -- Tobias Gondrom
> -- Chris Griffiths
>
>
> If you know of another individual that the NomCom should consider in
> filling the mid-term vacancy on the IAOC, please send email to
> nomcom12@ietf.org. As always, the NomCom is happy to accept self-
> nominations.
>
> The NomCom wishes to move as quickly as possible in filling this mid-term
> vacancy. Therefore, if you have a Nomination to make, please do so by
> Monday, December 3.
>
> Thank you for your help,
> - Matt Lepinski
>   nomcom-chair@ietf.org
>



-- 
Website: http://hallambaker.com/

--f46d0447f1881e109304ceee4e37
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

I am confused, is the NomCon filling one position here or two?=A0<br><br><d=
iv class=3D"gmail_quote">On Mon, Nov 19, 2012 at 9:54 PM, NomCom Chair <spa=
n dir=3D"ltr">&lt;<a href=3D"mailto:nomcom-chair@ietf.org" target=3D"_blank=
">nomcom-chair@ietf.org</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">The IETF Nominating Committee (NomCom) has b=
een asked to fill the<br>
IAOC position previously held by Marshall Eubanks. Therefore, the<br>
NomCom is soliciting nominations for individuals who would be a good<br>
choice to fill this position.<br>
<br>
The desired qualifications for IAOC members can be found at:<br>
<a href=3D"https://www.ietf.org/group/nomcom/2012/iaoc-requirements" target=
=3D"_blank">https://www.ietf.org/group/nomcom/2012/iaoc-requirements</a><br=
>
<br>
The NomCom is currently considering the following three individuals for<br>
the IAOC position previously held by Dave Crocker. The NomCom will<br>
additionally consider these individuals to fill the mid-term vacancy on the=
<br>
IAOC:<br>
-- Randy Bush<br>
-- Tobias Gondrom<br>
-- Chris Griffiths<br>
<br>
<br>
If you know of another individual that the NomCom should consider in<br>
filling the mid-term vacancy on the IAOC, please send email to<br>
<a href=3D"mailto:nomcom12@ietf.org">nomcom12@ietf.org</a>. As always, the =
NomCom is happy to accept self-<br>
nominations.<br>
<br>
The NomCom wishes to move as quickly as possible in filling this mid-term<b=
r>
vacancy. Therefore, if you have a Nomination to make, please do so by<br>
Monday, December 3.<br>
<br>
Thank you for your help,<br>
- Matt Lepinski<br>
=A0 <a href=3D"mailto:nomcom-chair@ietf.org">nomcom-chair@ietf.org</a><br>
</blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>Website: <a =
href=3D"http://hallambaker.com/">http://hallambaker.com/</a><br><br>

--f46d0447f1881e109304ceee4e37--

From mlepinski.ietf@gmail.com  Tue Nov 20 07:01:24 2012
Return-Path: <mlepinski.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 02F2C21F870C for <ietf@ietfa.amsl.com>; Tue, 20 Nov 2012 07:01:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.515
X-Spam-Level: 
X-Spam-Status: No, score=-3.515 tagged_above=-999 required=5 tests=[AWL=0.084,  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 G06-QrHuDxkR for <ietf@ietfa.amsl.com>; Tue, 20 Nov 2012 07:01:23 -0800 (PST)
Received: from mail-ie0-f172.google.com (mail-ie0-f172.google.com [209.85.223.172]) by ietfa.amsl.com (Postfix) with ESMTP id 3EB7721F86C6 for <ietf@ietf.org>; Tue, 20 Nov 2012 07:01:23 -0800 (PST)
Received: by mail-ie0-f172.google.com with SMTP id c13so1333262ieb.31 for <ietf@ietf.org>; Tue, 20 Nov 2012 07:01:22 -0800 (PST)
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=i41i7wCq5Ae5Zi9M0Kj0Okn4kWSJ8yAgg6LUdoy/Fls=; b=EZsnPM2lQVYtNS2NLJ2jhqguF9XXsGsijqJwhwDI0HZpjDyfL8UJap8XoTLftti/eL nJvl5selYCeMCS8/yvUlZiBlkx96zpceaU5NAIJJO25RbC75CbcyDTTveKa3k9/e35oK HHXPr9LsCbQ6WaCNeHnmvuLJUw0g+JQlSAjTIqa5AQ4P/KGN8B2GIuyRtn9RIVSaG9iX sgCl/m3PMVW5hNvBqzUx7WFfwj9NbZuyL3VwMjN+rMlsAXtEYVevV2/vjD39/iLpVZrZ wHVyPPyDVw/K/gi4NII7DEYExZF/axLPblJcLLMJOz/RtdI/hAARXpjee3IpgBnvCJLr ez5Q==
MIME-Version: 1.0
Received: by 10.50.222.231 with SMTP id qp7mr9897847igc.74.1353423682789; Tue, 20 Nov 2012 07:01:22 -0800 (PST)
Received: by 10.231.76.82 with HTTP; Tue, 20 Nov 2012 07:01:22 -0800 (PST)
In-Reply-To: <CAMm+Lwj6bxV=M5pPrS0tL7PzG-3SFpsq2GGnKiQz9eho-YepTA@mail.gmail.com>
References: <20121120025417.29733.20380.idtracker@ietfa.amsl.com> <CAMm+Lwj6bxV=M5pPrS0tL7PzG-3SFpsq2GGnKiQz9eho-YepTA@mail.gmail.com>
Date: Tue, 20 Nov 2012 10:01:22 -0500
Message-ID: <CANTg3aDRta+s6ATgFvzaRS-J5ru6Shu65s_DXrnTc4AJThwLww@mail.gmail.com>
Subject: Re: NomCom: Call for Nominations - IAOC Mid-Term Vacancy
From: Matthew Lepinski <mlepinski.ietf@gmail.com>
To: ietf@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Nov 2012 15:01:24 -0000

I apologize for the confusion.

The NomCom, as part of its annual work, is required to fill the IAOC
position currently held by Dave Crocker. This position is a two-year
term starting in March 2013. The NomCom previously requested nominees
for this position and has received community feedback on these
nominees. The NomCom will make a public announcement about this
position once we have completed the confirmation process.

Additionally, the IAOC has a mid-term vacancy that was created by the
resignation of Marshall Eubanks. Marshall was serving a two year term
that began in March 2012. The NomCom has been asked to find an
individual to serve out the rest of Marshall's term. The first step in
filling this vacancy is to request nominations from the community of
individuals the NomCom should consider for this position.

I hope this provides some additional clarity.
- Matt Lepinski

On Tue, Nov 20, 2012 at 9:46 AM, Phillip Hallam-Baker <hallam@gmail.com> wrote:
> I am confused, is the NomCon filling one position here or two?
>
> On Mon, Nov 19, 2012 at 9:54 PM, NomCom Chair <nomcom-chair@ietf.org> wrote:
>>
>> The IETF Nominating Committee (NomCom) has been asked to fill the
>> IAOC position previously held by Marshall Eubanks. Therefore, the
>> NomCom is soliciting nominations for individuals who would be a good
>> choice to fill this position.
>>
>> The desired qualifications for IAOC members can be found at:
>> https://www.ietf.org/group/nomcom/2012/iaoc-requirements
>>
>> The NomCom is currently considering the following three individuals for
>> the IAOC position previously held by Dave Crocker. The NomCom will
>> additionally consider these individuals to fill the mid-term vacancy on
>> the
>> IAOC:
>> -- Randy Bush
>> -- Tobias Gondrom
>> -- Chris Griffiths
>>
>>
>> If you know of another individual that the NomCom should consider in
>> filling the mid-term vacancy on the IAOC, please send email to
>> nomcom12@ietf.org. As always, the NomCom is happy to accept self-
>> nominations.
>>
>> The NomCom wishes to move as quickly as possible in filling this mid-term
>> vacancy. Therefore, if you have a Nomination to make, please do so by
>> Monday, December 3.
>>
>> Thank you for your help,
>> - Matt Lepinski
>>   nomcom-chair@ietf.org
>
>
>
>
> --
> Website: http://hallambaker.com/
>

From ynir@checkpoint.com  Tue Nov 20 07:10:37 2012
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 673C721F85CB; Tue, 20 Nov 2012 07:10:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level: 
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
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 pc+uGQeqCEJy; Tue, 20 Nov 2012 07:10:36 -0800 (PST)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id DBC8121F85C3; Tue, 20 Nov 2012 07:10:35 -0800 (PST)
Received: from IL-EX10.ad.checkpoint.com ([194.29.34.147]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id qAKFAWDl016458; Tue, 20 Nov 2012 17:10:32 +0200
X-CheckPoint: {50AB9A1B-4-1B221DC2-1FFFF}
Received: from IL-EX10.ad.checkpoint.com ([169.254.2.194]) by IL-EX10.ad.checkpoint.com ([169.254.2.194]) with mapi id 14.02.0318.004; Tue, 20 Nov 2012 17:10:32 +0200
From: Yoav Nir <ynir@checkpoint.com>
To: Phillip Hallam-Baker <hallam@gmail.com>
Subject: Re: NomCom: Call for Nominations - IAOC Mid-Term Vacancy
Thread-Topic: NomCom: Call for Nominations - IAOC Mid-Term Vacancy
Thread-Index: AQHNxy64Y9n2CBXLhkCS/ciVivE0L5fysniA
Date: Tue, 20 Nov 2012 15:10:31 +0000
Message-ID: <4613980CFC78314ABFD7F85CC302772101C613@IL-EX10.ad.checkpoint.com>
References: <20121120025417.29733.20380.idtracker@ietfa.amsl.com> <CAMm+Lwj6bxV=M5pPrS0tL7PzG-3SFpsq2GGnKiQz9eho-YepTA@mail.gmail.com>
In-Reply-To: <CAMm+Lwj6bxV=M5pPrS0tL7PzG-3SFpsq2GGnKiQz9eho-YepTA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [91.90.139.66]
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
x-cpdlp: 111c7b7501ac276e173e5b36161059930b43b33f9a
Content-Type: multipart/alternative; boundary="_000_4613980CFC78314ABFD7F85CC302772101C613ILEX10adcheckpoin_"
MIME-Version: 1.0
Cc: IETF Announcement List <ietf-announce@ietf.org>, "<ietf@ietf.org>" <ietf@ietf.org>, NomCom Chair <nomcom-chair@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Nov 2012 15:10:37 -0000

--_000_4613980CFC78314ABFD7F85CC302772101C613ILEX10adcheckpoin_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I think Dave is scheduled to be replaced anyway in March, and now they need=
 to fill two positions: one immediately (Marshal's) and one in March.

The question they're asking is whether they should be considering additiona=
l names now that (a) there's two positions to fill, and (b) one of them nee=
ds to be filled real soon.

On Nov 20, 2012, at 4:46 PM, Phillip Hallam-Baker wrote:

I am confused, is the NomCon filling one position here or two?

On Mon, Nov 19, 2012 at 9:54 PM, NomCom Chair <nomcom-chair@ietf.org<mailto=
:nomcom-chair@ietf.org>> wrote:
The IETF Nominating Committee (NomCom) has been asked to fill the
IAOC position previously held by Marshall Eubanks. Therefore, the
NomCom is soliciting nominations for individuals who would be a good
choice to fill this position.

The desired qualifications for IAOC members can be found at:
https://www.ietf.org/group/nomcom/2012/iaoc-requirements

The NomCom is currently considering the following three individuals for
the IAOC position previously held by Dave Crocker. The NomCom will
additionally consider these individuals to fill the mid-term vacancy on the
IAOC:
-- Randy Bush
-- Tobias Gondrom
-- Chris Griffiths


If you know of another individual that the NomCom should consider in
filling the mid-term vacancy on the IAOC, please send email to
nomcom12@ietf.org<mailto:nomcom12@ietf.org>. As always, the NomCom is happy=
 to accept self-
nominations.

The NomCom wishes to move as quickly as possible in filling this mid-term
vacancy. Therefore, if you have a Nomination to make, please do so by
Monday, December 3.

Thank you for your help,
- Matt Lepinski
  nomcom-chair@ietf.org<mailto:nomcom-chair@ietf.org>



--
Website: http://hallambaker.com/



Email secured by Check Point



--_000_4613980CFC78314ABFD7F85CC302772101C613ILEX10adcheckpoin_
Content-Type: text/html; charset="iso-8859-1"
Content-ID: <7454116FA0FB4A4088A4F4FBF81270D6@ad.checkpoint.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; ">
I think Dave is scheduled to be replaced anyway in March, and now they need=
 to fill two positions: one immediately (Marshal's) and one in March.&nbsp;
<div><br>
</div>
<div>The question they're asking is whether they should be considering addi=
tional names now that (a) there's two positions to fill, and (b) one of the=
m needs to be filled real soon.</div>
<div><br>
<div>
<div>On Nov 20, 2012, at 4:46 PM, Phillip Hallam-Baker wrote:</div>
<br class=3D"Apple-interchange-newline">
<blockquote type=3D"cite">I am confused, is the NomCon filling one position=
 here or two?&nbsp;<br>
<br>
<div class=3D"gmail_quote">On Mon, Nov 19, 2012 at 9:54 PM, NomCom Chair <s=
pan dir=3D"ltr">
&lt;<a href=3D"mailto:nomcom-chair@ietf.org" target=3D"_blank">nomcom-chair=
@ietf.org</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
The IETF Nominating Committee (NomCom) has been asked to fill the<br>
IAOC position previously held by Marshall Eubanks. Therefore, the<br>
NomCom is soliciting nominations for individuals who would be a good<br>
choice to fill this position.<br>
<br>
The desired qualifications for IAOC members can be found at:<br>
<a href=3D"https://www.ietf.org/group/nomcom/2012/iaoc-requirements" target=
=3D"_blank">https://www.ietf.org/group/nomcom/2012/iaoc-requirements</a><br=
>
<br>
The NomCom is currently considering the following three individuals for<br>
the IAOC position previously held by Dave Crocker. The NomCom will<br>
additionally consider these individuals to fill the mid-term vacancy on the=
<br>
IAOC:<br>
-- Randy Bush<br>
-- Tobias Gondrom<br>
-- Chris Griffiths<br>
<br>
<br>
If you know of another individual that the NomCom should consider in<br>
filling the mid-term vacancy on the IAOC, please send email to<br>
<a href=3D"mailto:nomcom12@ietf.org">nomcom12@ietf.org</a>. As always, the =
NomCom is happy to accept self-<br>
nominations.<br>
<br>
The NomCom wishes to move as quickly as possible in filling this mid-term<b=
r>
vacancy. Therefore, if you have a Nomination to make, please do so by<br>
Monday, December 3.<br>
<br>
Thank you for your help,<br>
- Matt Lepinski<br>
&nbsp; <a href=3D"mailto:nomcom-chair@ietf.org">nomcom-chair@ietf.org</a><b=
r>
</blockquote>
</div>
<br>
<br clear=3D"all">
<div><br>
</div>
-- <br>
Website: <a href=3D"http://hallambaker.com/">http://hallambaker.com/</a><br=
>
<br>
<br>
<br>
Email secured by Check Point <br>
<br>
</blockquote>
</div>
<br>
</div>
</body>
</html>

--_000_4613980CFC78314ABFD7F85CC302772101C613ILEX10adcheckpoin_--

From eric.gray@ericsson.com  Tue Nov 20 07:20:50 2012
Return-Path: <eric.gray@ericsson.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 922D721F8755; Tue, 20 Nov 2012 07:20:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 OoP7Cu81rb-0; Tue, 20 Nov 2012 07:20:49 -0800 (PST)
Received: from imr3.ericy.com (imr3.ericy.com [198.24.6.13]) by ietfa.amsl.com (Postfix) with ESMTP id 6F1CB21F85F4; Tue, 20 Nov 2012 07:20:49 -0800 (PST)
Received: from eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) by imr3.ericy.com (8.13.8/8.13.8) with ESMTP id qAKFKeuI012323 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 20 Nov 2012 09:20:40 -0600
Received: from EUSAAHC007.ericsson.se (147.117.188.93) by eusaamw0707.eamcs.ericsson.se (147.117.20.32) with Microsoft SMTP Server (TLS) id 8.3.279.1; Tue, 20 Nov 2012 10:20:40 -0500
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC007.ericsson.se ([147.117.188.93]) with mapi id 14.02.0318.001; Tue, 20 Nov 2012 10:20:39 -0500
From: Eric Gray <eric.gray@ericsson.com>
To: Yoav Nir <ynir@checkpoint.com>, Phillip Hallam-Baker <hallam@gmail.com>
Subject: RE: NomCom: Call for Nominations - IAOC Mid-Term Vacancy
Thread-Topic: NomCom: Call for Nominations - IAOC Mid-Term Vacancy
Thread-Index: AQHNxy3/toJUjOcZm0m0Kt/FOBweVpfzJ9KA//+uXXA=
Date: Tue, 20 Nov 2012 15:20:38 +0000
Message-ID: <48E1A67CB9CA044EADFEAB87D814BFF6027509@eusaamb107.ericsson.se>
References: <20121120025417.29733.20380.idtracker@ietfa.amsl.com> <CAMm+Lwj6bxV=M5pPrS0tL7PzG-3SFpsq2GGnKiQz9eho-YepTA@mail.gmail.com> <4613980CFC78314ABFD7F85CC302772101C613@IL-EX10.ad.checkpoint.com>
In-Reply-To: <4613980CFC78314ABFD7F85CC302772101C613@IL-EX10.ad.checkpoint.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.134]
Content-Type: multipart/alternative; boundary="_000_48E1A67CB9CA044EADFEAB87D814BFF6027509eusaamb107ericsso_"
MIME-Version: 1.0
Cc: NomCom Chair <nomcom-chair@ietf.org>, "<ietf@ietf.org>" <ietf@ietf.org>, IETF Announcement List <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Nov 2012 15:20:50 -0000

--_000_48E1A67CB9CA044EADFEAB87D814BFF6027509eusaamb107ericsso_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I think this is a point of confusion, anyway.

I thought the process was for the previous NomCom to be coopted to address =
any
unexpected mid-term vacancies, rather than to add the burden to the current
NomCom.

Has this changed?

From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Yoa=
v Nir
Sent: Tuesday, November 20, 2012 10:11 AM
To: Phillip Hallam-Baker
Cc: IETF Announcement List; <ietf@ietf.org>; NomCom Chair
Subject: Re: NomCom: Call for Nominations - IAOC Mid-Term Vacancy

I think Dave is scheduled to be replaced anyway in March, and now they need=
 to fill two positions: one immediately (Marshal's) and one in March.

The question they're asking is whether they should be considering additiona=
l names now that (a) there's two positions to fill, and (b) one of them nee=
ds to be filled real soon.

On Nov 20, 2012, at 4:46 PM, Phillip Hallam-Baker wrote:


I am confused, is the NomCon filling one position here or two?
On Mon, Nov 19, 2012 at 9:54 PM, NomCom Chair <nomcom-chair@ietf.org<mailto=
:nomcom-chair@ietf.org>> wrote:
The IETF Nominating Committee (NomCom) has been asked to fill the
IAOC position previously held by Marshall Eubanks. Therefore, the
NomCom is soliciting nominations for individuals who would be a good
choice to fill this position.

The desired qualifications for IAOC members can be found at:
https://www.ietf.org/group/nomcom/2012/iaoc-requirements

The NomCom is currently considering the following three individuals for
the IAOC position previously held by Dave Crocker. The NomCom will
additionally consider these individuals to fill the mid-term vacancy on the
IAOC:
-- Randy Bush
-- Tobias Gondrom
-- Chris Griffiths


If you know of another individual that the NomCom should consider in
filling the mid-term vacancy on the IAOC, please send email to
nomcom12@ietf.org<mailto:nomcom12@ietf.org>. As always, the NomCom is happy=
 to accept self-
nominations.

The NomCom wishes to move as quickly as possible in filling this mid-term
vacancy. Therefore, if you have a Nomination to make, please do so by
Monday, December 3.

Thank you for your help,
- Matt Lepinski
  nomcom-chair@ietf.org<mailto:nomcom-chair@ietf.org>



--
Website: http://hallambaker.com/



Email secured by Check Point


--_000_48E1A67CB9CA044EADFEAB87D814BFF6027509eusaamb107ericsso_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">I think this is a point o=
f confusion, anyway.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">I thought the process was=
 for the previous NomCom to be coopted to address any<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">unexpected mid-term vacan=
cies, rather than to add the burden to the current
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">NomCom.<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Has this changed?<o:p></o=
:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> ietf-bou=
nces@ietf.org [mailto:ietf-bounces@ietf.org]
<b>On Behalf Of </b>Yoav Nir<br>
<b>Sent:</b> Tuesday, November 20, 2012 10:11 AM<br>
<b>To:</b> Phillip Hallam-Baker<br>
<b>Cc:</b> IETF Announcement List; &lt;ietf@ietf.org&gt;; NomCom Chair<br>
<b>Subject:</b> Re: NomCom: Call for Nominations - IAOC Mid-Term Vacancy<o:=
p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">I think Dave is scheduled to be replaced anyway in M=
arch, and now they need to fill two positions: one immediately (Marshal's) =
and one in March.&nbsp;
<o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">The question they're asking is whether they should b=
e considering additional names now that (a) there's two positions to fill, =
and (b) one of them needs to be filled real soon.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<div>
<p class=3D"MsoNormal">On Nov 20, 2012, at 4:46 PM, Phillip Hallam-Baker wr=
ote:<o:p></o:p></p>
</div>
<p class=3D"MsoNormal"><br>
<br>
<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">I am confused, is the=
 NomCon filling one position here or two?&nbsp;<o:p></o:p></p>
<div>
<p class=3D"MsoNormal">On Mon, Nov 19, 2012 at 9:54 PM, NomCom Chair &lt;<a=
 href=3D"mailto:nomcom-chair@ietf.org" target=3D"_blank">nomcom-chair@ietf.=
org</a>&gt; wrote:<o:p></o:p></p>
<p class=3D"MsoNormal">The IETF Nominating Committee (NomCom) has been aske=
d to fill the<br>
IAOC position previously held by Marshall Eubanks. Therefore, the<br>
NomCom is soliciting nominations for individuals who would be a good<br>
choice to fill this position.<br>
<br>
The desired qualifications for IAOC members can be found at:<br>
<a href=3D"https://www.ietf.org/group/nomcom/2012/iaoc-requirements" target=
=3D"_blank">https://www.ietf.org/group/nomcom/2012/iaoc-requirements</a><br=
>
<br>
The NomCom is currently considering the following three individuals for<br>
the IAOC position previously held by Dave Crocker. The NomCom will<br>
additionally consider these individuals to fill the mid-term vacancy on the=
<br>
IAOC:<br>
-- Randy Bush<br>
-- Tobias Gondrom<br>
-- Chris Griffiths<br>
<br>
<br>
If you know of another individual that the NomCom should consider in<br>
filling the mid-term vacancy on the IAOC, please send email to<br>
<a href=3D"mailto:nomcom12@ietf.org">nomcom12@ietf.org</a>. As always, the =
NomCom is happy to accept self-<br>
nominations.<br>
<br>
The NomCom wishes to move as quickly as possible in filling this mid-term<b=
r>
vacancy. Therefore, if you have a Nomination to make, please do so by<br>
Monday, December 3.<br>
<br>
Thank you for your help,<br>
- Matt Lepinski<br>
&nbsp; <a href=3D"mailto:nomcom-chair@ietf.org">nomcom-chair@ietf.org</a><o=
:p></o:p></p>
</div>
<p class=3D"MsoNormal"><br>
<br clear=3D"all">
<o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">-- <br>
Website: <a href=3D"http://hallambaker.com/">http://hallambaker.com/</a><br=
>
<br>
<br>
<br>
Email secured by Check Point <o:p></o:p></p>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</body>
</html>

--_000_48E1A67CB9CA044EADFEAB87D814BFF6027509eusaamb107ericsso_--

From sm@resistor.net  Tue Nov 20 07:38:09 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 678F721F8692 for <ietf@ietfa.amsl.com>; Tue, 20 Nov 2012 07:38:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.507
X-Spam-Level: 
X-Spam-Status: No, score=-102.507 tagged_above=-999 required=5 tests=[AWL=0.092, 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 HEZkGEBPcGtq for <ietf@ietfa.amsl.com>; Tue, 20 Nov 2012 07:38:09 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0CD5B21F8691 for <ietf@ietf.org>; Tue, 20 Nov 2012 07:38:08 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id qAKFc0cI010685; Tue, 20 Nov 2012 07:38:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1353425885; bh=V+WDgE4LvOJuxMJvA2dhd53fQNKJy5RkXU+OJrUVqIM=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=kbU4cm7k5pn4YFvgZjFybPChqla1CzMBef+3DpxsTLJb6+mo3XnDFJwcojXSdL+gd ia9HAflJq2ne30Yx10jsdFATwqShrd5m/61sZTCpAPep2NVupIYNy5aoDqMpoUORBf 73RgqOlEVrOCOxPrXubuIj93RGCzQ/rCnE7RdPqg=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1353425885; i=@resistor.net; bh=V+WDgE4LvOJuxMJvA2dhd53fQNKJy5RkXU+OJrUVqIM=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=waQod4o6wDwVrGPVt5pxx1xpx6kTn4vIef5J8DWCF2EnyOPuhMn1rDCU4/A7zyWsw Tiyc1YqQ/ckKQ8C4CsEudJmRHyLQmw+QCLDMFYMm1yjNaqVxeIEYajg4yvwEyRn/3v UZvGOMtF77LR8gO+pcBqErak1wmQL0d+cJUNMTlI=
Message-Id: <6.2.5.6.2.20121120073357.09739990@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 20 Nov 2012 07:37:57 -0800
To: Eric Gray <eric.gray@ericsson.com>
From: SM <sm@resistor.net>
Subject: RE: NomCom: Call for Nominations - IAOC Mid-Term Vacancy
In-Reply-To: <48E1A67CB9CA044EADFEAB87D814BFF6027509@eusaamb107.ericsson .se>
References: <20121120025417.29733.20380.idtracker@ietfa.amsl.com> <CAMm+Lwj6bxV=M5pPrS0tL7PzG-3SFpsq2GGnKiQz9eho-YepTA@mail.gmail.com> <4613980CFC78314ABFD7F85CC302772101C613@IL-EX10.ad.checkpoint.com> <48E1A67CB9CA044EADFEAB87D814BFF6027509@eusaamb107.ericsson.se>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Nov 2012 15:38:09 -0000

Hi Eric,
At 07:20 20-11-2012, Eric Gray wrote:
>I thought the process was for the previous NomCom to be coopted to address any
>unexpected mid-term vacancies, rather than to add the burden to the current
>NomCom.

   "First, when there is only one official nominating committee, the
    body with the mid-term vacancy relegates the responsibility to
    fill the vacancy to it.  If the mid-term vacancy occurs during the
    period of time that the term of the prior year's nominating
    committee overlaps with the term of the current year's nominating
    committee, the body with the mid-term vacancy must relegate the
    responsibility to fill the vacancy to the prior year's nominating
    committee."

Regards,
-sm  


From suresh.krishnan@ericsson.com  Tue Nov 20 07:45:51 2012
Return-Path: <suresh.krishnan@ericsson.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D71F621F873A; Tue, 20 Nov 2012 07:45:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 FFuYFZRCUxgX; Tue, 20 Nov 2012 07:45:51 -0800 (PST)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id 5206D21F8733; Tue, 20 Nov 2012 07:45:51 -0800 (PST)
Received: from eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id qAKFqnci023781; Tue, 20 Nov 2012 09:52:51 -0600
Received: from [142.133.112.133] (147.117.20.214) by smtps-am.internal.ericsson.com (147.117.20.31) with Microsoft SMTP Server (TLS) id 8.3.279.1; Tue, 20 Nov 2012 10:45:37 -0500
Message-ID: <50ABA509.5070505@ericsson.com>
Date: Tue, 20 Nov 2012 10:43:05 -0500
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121028 Thunderbird/16.0.2
MIME-Version: 1.0
To: Eric Gray <eric.gray@ericsson.com>
Subject: Re: NomCom: Call for Nominations - IAOC Mid-Term Vacancy
References: <20121120025417.29733.20380.idtracker@ietfa.amsl.com> <CAMm+Lwj6bxV=M5pPrS0tL7PzG-3SFpsq2GGnKiQz9eho-YepTA@mail.gmail.com> <4613980CFC78314ABFD7F85CC302772101C613@IL-EX10.ad.checkpoint.com> <48E1A67CB9CA044EADFEAB87D814BFF6027509@eusaamb107.ericsson.se>
In-Reply-To: <48E1A67CB9CA044EADFEAB87D814BFF6027509@eusaamb107.ericsson.se>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: Phillip Hallam-Baker <hallam@gmail.com>, IETF Announcement List <ietf-announce@ietf.org>, "<ietf@ietf.org>" <ietf@ietf.org>, NomCom Chair <nomcom-chair@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Nov 2012 15:45:52 -0000

Hi Eric,

On 11/20/2012 10:20 AM, Eric Gray wrote:
> I think this is a point of confusion, anyway.
> 
>  
> 
> I thought the process was for the previous NomCom to be coopted to
> address any
> 
> unexpected mid-term vacancies, rather than to add the burden to the current
> 
> NomCom.

The previous Nomcom stayed constituted until the Atlanta meeting. If the
vacancy was announced before Atlanta, the previous Nomcom would have
filled the position. Right now, there is only one constituted Nomcom and
it has to fill the position.

Thanks
Suresh


From rdroms.ietf@gmail.com  Tue Nov 20 07:50:30 2012
Return-Path: <rdroms.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5460521F847C; Tue, 20 Nov 2012 07:50:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.432
X-Spam-Level: 
X-Spam-Status: No, score=-103.432 tagged_above=-999 required=5 tests=[AWL=0.167, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, 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 SwxZXwXoWFvi; Tue, 20 Nov 2012 07:50:25 -0800 (PST)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 70F9421F8470; Tue, 20 Nov 2012 07:50:25 -0800 (PST)
Received: by mail-vc0-f172.google.com with SMTP id fw7so4359520vcb.31 for <multiple recipients>; Tue, 20 Nov 2012 07:50:24 -0800 (PST)
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 :content-transfer-encoding:message-id:references:to:x-mailer; bh=Q8RObQzqv0JhHLCAKl12mH1ILf0IL+B93QxuKsEuchE=; b=wIL9VEv65LR5zg36kGvj5s0yxk+89+11jqS5qZzHVRLuoQI9MCWH1zKhPkz1OhdP8n wLku7Ho+EQ9tLJJBXdiqn4shFHq5ZTpsKcrzewsITI14EZqkKzYI0I6Mb47plnUBvelN u99YlrT4JFUNnDRXoS/o1RlEqaZ3OitdHXmKSMypSgb+Whzr9Oz1rGwpl/xVr+2HtZ59 etwZerrY5Cx3u7hRen2atLekMQDLOpQmL0WZIIKDriqbaI1lL4EXuBdSGJhz5DSmuGpM SPYkQ0qozFm/axizbaZNBfXfgFQ3s2WfP7xAYJfFBVVAzwDSHUqF2/hA5fHi8kQ9Yje4 tc9A==
Received: by 10.52.34.42 with SMTP id w10mr21672519vdi.10.1353426624894; Tue, 20 Nov 2012 07:50:24 -0800 (PST)
Received: from rtp-rdroms-8916.cisco.com (rtp-isp-nat1.cisco.com. [64.102.254.33]) by mx.google.com with ESMTPS id dl18sm4099640vdb.2.2012.11.20.07.50.22 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 20 Nov 2012 07:50:23 -0800 (PST)
Subject: Re: NomCom: Call for Nominations - IAOC Mid-Term Vacancy
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=iso-8859-1
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <50ABA509.5070505@ericsson.com>
Date: Tue, 20 Nov 2012 10:50:22 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <650CFFAF-45BF-47E7-851C-63367709CE8B@gmail.com>
References: <20121120025417.29733.20380.idtracker@ietfa.amsl.com> <CAMm+Lwj6bxV=M5pPrS0tL7PzG-3SFpsq2GGnKiQz9eho-YepTA@mail.gmail.com> <4613980CFC78314ABFD7F85CC302772101C613@IL-EX10.ad.checkpoint.com> <48E1A67CB9CA044EADFEAB87D814BFF6027509@eusaamb107.ericsson.se> <50ABA509.5070505@ericsson.com>
To: Eric Gray <eric.gray@ericsson.com>
X-Mailer: Apple Mail (2.1283)
Cc: NomCom Chair <nomcom-chair@ietf.org>, Phillip Hallam-Baker <hallam@gmail.com>, IETF list discussion <ietf@ietf.org>, IETF Announcement List <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Nov 2012 15:50:30 -0000

On Nov 20, 2012, at 10:43 AM 11/20/12, Suresh Krishnan wrote:

> Hi Eric,
>=20
> On 11/20/2012 10:20 AM, Eric Gray wrote:
>> I think this is a point of confusion, anyway.
>>=20
>>=20
>>=20
>> I thought the process was for the previous NomCom to be coopted to
>> address any
>>=20
>> unexpected mid-term vacancies, rather than to add the burden to the =
current
>>=20
>> NomCom.
>=20
> The previous Nomcom stayed constituted until the Atlanta meeting. If =
the
> vacancy was announced before Atlanta, the previous Nomcom would have
> filled the position. Right now, there is only one constituted Nomcom =
and
> it has to fill the position.

Suresh has it right; from RFC 3777:

       The term of a nominating committee begins when its members are
       officially announced.  The term ends at the Third IETF (not three
       meetings), i.e., the IETF meeting after the next nominating
       committee's term begins.

- Ralph

>=20
> Thanks
> Suresh
>=20


From eric.gray@ericsson.com  Tue Nov 20 07:51:40 2012
Return-Path: <eric.gray@ericsson.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D890321F870A; Tue, 20 Nov 2012 07:51:40 -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=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 MoS5h5UZICC4; Tue, 20 Nov 2012 07:51:40 -0800 (PST)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id 2E2BA21F8472; Tue, 20 Nov 2012 07:51:37 -0800 (PST)
Received: from eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id qAKFwZdm025349; Tue, 20 Nov 2012 09:58:37 -0600
Received: from EUSAAHC002.ericsson.se (147.117.188.78) by eusaamw0711.eamcs.ericsson.se (147.117.20.178) with Microsoft SMTP Server (TLS) id 8.3.279.1; Tue, 20 Nov 2012 10:51:24 -0500
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC002.ericsson.se ([147.117.188.78]) with mapi id 14.02.0318.001; Tue, 20 Nov 2012 10:51:24 -0500
From: Eric Gray <eric.gray@ericsson.com>
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
Subject: RE: NomCom: Call for Nominations - IAOC Mid-Term Vacancy
Thread-Topic: NomCom: Call for Nominations - IAOC Mid-Term Vacancy
Thread-Index: AQHNxy3/toJUjOcZm0m0Kt/FOBweVpfzJ9KA//+uXXCAAFq8gP//rndA
Date: Tue, 20 Nov 2012 15:51:23 +0000
Message-ID: <48E1A67CB9CA044EADFEAB87D814BFF60275CE@eusaamb107.ericsson.se>
References: <20121120025417.29733.20380.idtracker@ietfa.amsl.com> <CAMm+Lwj6bxV=M5pPrS0tL7PzG-3SFpsq2GGnKiQz9eho-YepTA@mail.gmail.com> <4613980CFC78314ABFD7F85CC302772101C613@IL-EX10.ad.checkpoint.com> <48E1A67CB9CA044EADFEAB87D814BFF6027509@eusaamb107.ericsson.se> <50ABA509.5070505@ericsson.com>
In-Reply-To: <50ABA509.5070505@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.134]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Phillip Hallam-Baker <hallam@gmail.com>, IETF Announcement List <ietf-announce@ietf.org>, "<ietf@ietf.org>" <ietf@ietf.org>, NomCom Chair <nomcom-chair@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Nov 2012 15:51:41 -0000

Okay, thanks!

-----Original Message-----
From: Suresh Krishnan=20
Sent: Tuesday, November 20, 2012 10:43 AM
To: Eric Gray
Cc: Yoav Nir; Phillip Hallam-Baker; NomCom Chair; <ietf@ietf.org>; IETF Ann=
ouncement List
Subject: Re: NomCom: Call for Nominations - IAOC Mid-Term Vacancy
Importance: High

Hi Eric,

On 11/20/2012 10:20 AM, Eric Gray wrote:
> I think this is a point of confusion, anyway.
>=20
> =20
>=20
> I thought the process was for the previous NomCom to be coopted to=20
> address any
>=20
> unexpected mid-term vacancies, rather than to add the burden to the=20
> current
>=20
> NomCom.

The previous Nomcom stayed constituted until the Atlanta meeting. If the va=
cancy was announced before Atlanta, the previous Nomcom would have filled t=
he position. Right now, there is only one constituted Nomcom and it has to =
fill the position.

Thanks
Suresh


From eric.gray@ericsson.com  Tue Nov 20 07:52:58 2012
Return-Path: <eric.gray@ericsson.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B8E821F874B; Tue, 20 Nov 2012 07:52:58 -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=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 5gXc+qHEJx5P; Tue, 20 Nov 2012 07:52:57 -0800 (PST)
Received: from imr3.ericy.com (imr3.ericy.com [198.24.6.13]) by ietfa.amsl.com (Postfix) with ESMTP id 1A35A21F8472; Tue, 20 Nov 2012 07:52:57 -0800 (PST)
Received: from eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) by imr3.ericy.com (8.13.8/8.13.8) with ESMTP id qAKFqfij016638 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 20 Nov 2012 09:52:55 -0600
Received: from EUSAAHC006.ericsson.se (147.117.188.90) by eusaamw0707.eamcs.ericsson.se (147.117.20.32) with Microsoft SMTP Server (TLS) id 8.3.279.1; Tue, 20 Nov 2012 10:52:45 -0500
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC006.ericsson.se ([147.117.188.90]) with mapi id 14.02.0318.001; Tue, 20 Nov 2012 10:52:45 -0500
From: Eric Gray <eric.gray@ericsson.com>
To: Ralph Droms <rdroms.ietf@gmail.com>
Subject: RE: NomCom: Call for Nominations - IAOC Mid-Term Vacancy
Thread-Topic: NomCom: Call for Nominations - IAOC Mid-Term Vacancy
Thread-Index: AQHNxy3/toJUjOcZm0m0Kt/FOBweVpfzJ9KA//+uXXCAAFq8gIAAAgkA//+sv1A=
Date: Tue, 20 Nov 2012 15:52:44 +0000
Message-ID: <48E1A67CB9CA044EADFEAB87D814BFF60275F5@eusaamb107.ericsson.se>
References: <20121120025417.29733.20380.idtracker@ietfa.amsl.com> <CAMm+Lwj6bxV=M5pPrS0tL7PzG-3SFpsq2GGnKiQz9eho-YepTA@mail.gmail.com> <4613980CFC78314ABFD7F85CC302772101C613@IL-EX10.ad.checkpoint.com> <48E1A67CB9CA044EADFEAB87D814BFF6027509@eusaamb107.ericsson.se> <50ABA509.5070505@ericsson.com> <650CFFAF-45BF-47E7-851C-63367709CE8B@gmail.com>
In-Reply-To: <650CFFAF-45BF-47E7-851C-63367709CE8B@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.134]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: NomCom Chair <nomcom-chair@ietf.org>, Phillip Hallam-Baker <hallam@gmail.com>, IETF list discussion <ietf@ietf.org>, IETF Announcement List <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Nov 2012 15:52:58 -0000

Ralph,

	Thanks for the confirmation.

--
Eric

-----Original Message-----
From: Ralph Droms [mailto:rdroms.ietf@gmail.com]=20
Sent: Tuesday, November 20, 2012 10:50 AM
To: Eric Gray
Cc: Phillip Hallam-Baker; IETF Announcement List; IETF list discussion; Nom=
Com Chair; Suresh Krishnan
Subject: Re: NomCom: Call for Nominations - IAOC Mid-Term Vacancy
Importance: High


On Nov 20, 2012, at 10:43 AM 11/20/12, Suresh Krishnan wrote:

> Hi Eric,
>=20
> On 11/20/2012 10:20 AM, Eric Gray wrote:
>> I think this is a point of confusion, anyway.
>>=20
>>=20
>>=20
>> I thought the process was for the previous NomCom to be coopted to=20
>> address any
>>=20
>> unexpected mid-term vacancies, rather than to add the burden to the=20
>> current
>>=20
>> NomCom.
>=20
> The previous Nomcom stayed constituted until the Atlanta meeting. If=20
> the vacancy was announced before Atlanta, the previous Nomcom would=20
> have filled the position. Right now, there is only one constituted=20
> Nomcom and it has to fill the position.

Suresh has it right; from RFC 3777:

       The term of a nominating committee begins when its members are
       officially announced.  The term ends at the Third IETF (not three
       meetings), i.e., the IETF meeting after the next nominating
       committee's term begins.

- Ralph

>=20
> Thanks
> Suresh
>=20


From mlepinski.ietf@gmail.com  Tue Nov 20 06:54:06 2012
Return-Path: <mlepinski.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B02D21F8695 for <ietf@ietfa.amsl.com>; Tue, 20 Nov 2012 06:54:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.513
X-Spam-Level: 
X-Spam-Status: No, score=-3.513 tagged_above=-999 required=5 tests=[AWL=0.086,  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 rvtW6J41q6u8 for <ietf@ietfa.amsl.com>; Tue, 20 Nov 2012 06:54:05 -0800 (PST)
Received: from mail-ia0-f172.google.com (mail-ia0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 3549121F86C4 for <ietf@ietf.org>; Tue, 20 Nov 2012 06:54:05 -0800 (PST)
Received: by mail-ia0-f172.google.com with SMTP id j26so4683082iaf.31 for <ietf@ietf.org>; Tue, 20 Nov 2012 06:54:03 -0800 (PST)
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 :cc:content-type; bh=E5lv6E4XVoLG/CEc7k1brvn2nsIfZqPlXOcVTlgZ0os=; b=aQWRv7/yOXA+zfAewkaSPuFSlxua9+UkkIMnEKwLQexpKpgIO0wsD13Visuh8zQ95v 2Ht3omXHcvVKqrLmIyLku2ou/KX0STxIIVprNSx5wcSj5pQSkoXzO665vR0a1yuHa5G7 tP9t4ptBhmWCLnRu/tutft8E8YNMi0H+KNHo2t662xkTu2euu9ktFOqg4oFeyKJtC9rP LdlMax1uVrTlDFM6rkJ15d50UmNW2aDqTifg0F5XoSrZElg7h2iL0yRpvFFhN5LFyUzP ZCoODQUOkbNd/7XXE7ClFHM9wZCT9abMZJZOS+Bx1a0zrD3834F0Pq64w6vYW5mMzrWs NXYA==
MIME-Version: 1.0
Received: by 10.42.68.68 with SMTP id w4mr14156234ici.30.1353423243166; Tue, 20 Nov 2012 06:54:03 -0800 (PST)
Received: by 10.231.76.82 with HTTP; Tue, 20 Nov 2012 06:54:03 -0800 (PST)
In-Reply-To: <CAMm+Lwj6bxV=M5pPrS0tL7PzG-3SFpsq2GGnKiQz9eho-YepTA@mail.gmail.com>
References: <20121120025417.29733.20380.idtracker@ietfa.amsl.com> <CAMm+Lwj6bxV=M5pPrS0tL7PzG-3SFpsq2GGnKiQz9eho-YepTA@mail.gmail.com>
Date: Tue, 20 Nov 2012 09:54:03 -0500
Message-ID: <CANTg3aCD0v28Ck3hVNXog2=X2zs3fBTS7ryPs6_QJEdoi8HkmA@mail.gmail.com>
Subject: Re: NomCom: Call for Nominations - IAOC Mid-Term Vacancy
From: Matthew Lepinski <mlepinski.ietf@gmail.com>
To: Phillip Hallam-Baker <hallam@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
X-Mailman-Approved-At: Tue, 20 Nov 2012 08:13:45 -0800
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Nov 2012 14:54:06 -0000

Phil,

I apologize for the confusion.

The NomCom, as part of its annual work, is required to fill the IAOC
position currently held by Dave Crocker. This position is a two-year
term starting in March 2013. The NomCom previously requested nominees
for this position and has received community feedback on these
nominees. The NomCom will make a public announcement about this
position once we have completed the confirmation process.

Additionally, the IAOC has a mid-term vacancy that was created by the
resignation of Marshall Eubanks. Marshall was serving a two year term
that began in March 2012. The NomCom has been asked to find an
individual to serve out the rest of Marshall's term. The first step in
filling this vacancy is to request nominations from the community of
individuals the NomCom should consider for this position.

I hope this provides some additional clarity.
- Matt Lepinski

On Tue, Nov 20, 2012 at 9:46 AM, Phillip Hallam-Baker <hallam@gmail.com> wrote:
> I am confused, is the NomCon filling one position here or two?
>
> On Mon, Nov 19, 2012 at 9:54 PM, NomCom Chair <nomcom-chair@ietf.org> wrote:
>>
>> The IETF Nominating Committee (NomCom) has been asked to fill the
>> IAOC position previously held by Marshall Eubanks. Therefore, the
>> NomCom is soliciting nominations for individuals who would be a good
>> choice to fill this position.
>>
>> The desired qualifications for IAOC members can be found at:
>> https://www.ietf.org/group/nomcom/2012/iaoc-requirements
>>
>> The NomCom is currently considering the following three individuals for
>> the IAOC position previously held by Dave Crocker. The NomCom will
>> additionally consider these individuals to fill the mid-term vacancy on
>> the
>> IAOC:
>> -- Randy Bush
>> -- Tobias Gondrom
>> -- Chris Griffiths
>>
>>
>> If you know of another individual that the NomCom should consider in
>> filling the mid-term vacancy on the IAOC, please send email to
>> nomcom12@ietf.org. As always, the NomCom is happy to accept self-
>> nominations.
>>
>> The NomCom wishes to move as quickly as possible in filling this mid-term
>> vacancy. Therefore, if you have a Nomination to make, please do so by
>> Monday, December 3.
>>
>> Thank you for your help,
>> - Matt Lepinski
>>   nomcom-chair@ietf.org
>
>
>
>
> --
> Website: http://hallambaker.com/
>

From iad@ietf.org  Tue Nov 20 09:05:58 2012
Return-Path: <iad@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D92B21F8735; Tue, 20 Nov 2012 09:05:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.299
X-Spam-Level: 
X-Spam-Status: No, score=-101.299 tagged_above=-999 required=5 tests=[AWL=-1.300, BAYES_50=0.001, 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 StSJSJRuV6DF; Tue, 20 Nov 2012 09:05:58 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F3B8021F8566; Tue, 20 Nov 2012 09:05:57 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: IETF Administrative Director <iad@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
Subject: Round 2:  Proposed IETF Meeting Dates 2018 - 2022
X-Test-IDTracker: no
X-IETF-IDTracker: 4.36
Message-ID: <20121120170557.4615.48062.idtracker@ietfa.amsl.com>
Date: Tue, 20 Nov 2012 09:05:57 -0800
Cc: iaoc@ietf.org, iab@iab.org, ietf@ietf.org, wgchairs@ietf.org, iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Nov 2012 17:05:58 -0000

All


On 6 September the IAOC announced proposed meeting =

dates for 2018 - 2022 and requested community feedback =

before adopting.

Several points were raised.  =


1.  IETF 110 21 - 26 March 2021

	It was noted that those dates conflicted with a major =

religious holiday.  As this will impact travel the IAOC is recommending a
change to 7 - 12 March 2021.

2.  IETF 106		17 - 22 November 2019

  It was commented that IETF 106 seemed a bit late in =

November and asked whether we are boxed in by other SDO
meetings, or was this by our own choice?

  Well, kind of boxed in, the week before is IEEE 802, and =

the week after is Thanksgiving in the US and a major travel =

holiday.

  The IAOC is recommending no change to these dates.

3.  2018, 2021, 2022 likely conflicts with ANSI T-10 with
November IETF meetings.

  The ANSI T-10 calendar has not been set.  November is a
short month with the Thanksgiving holiday and the IEEE =

802 meeting to avoid as well.  So, there is very limited =

flexibility to move the meeting.  The IAOC is recommending
no change for these meetings.

4.  Summer time meetings and school holidays. =


  We received comments about the overlap of meetings with
school holidays.  We schedule meetings March, July and
November, roughly 16 - 17 weeks apart.  The meetings can =

occur in July and occasionally include part of August.  It's
inevitable that a July meeting will overlap with someone's =

school holidays, whichever way the meeting is shifted during
this window.  Maintaining meetings three times a year =

doesn't seem to lend itself to a solution satisfactory to all.
 The IAOC is recommending no change to the summer =

schedules as proposed, unless there is another reason to do =

so.

All of the proposed dates for 2018 - 2022 are below.  =


Comments appreciated to ietf@ietf.org by 4 December 2012.

Ray

2018
  IETF 101		18-23 March 2018
  IETF 102		22-27 July 2018
  IETF 103		4 - 9 November 2018

2019
  IETF 104		24 - 29 March 2019
  IETF 105		21 - 26 July 2019
  IETF 106		17 - 22 November 2019

2020
  IETF 107		22 - 27 March 2020
  IETF 108		26 - 31 July 2020
  IETF 109		15 - 20 November 2020

2021
  IETF 110		7 - 12 March 2021
  IETF 111		25 - 30 July 2021
  IETF 112		7 - 12 November 2021

2022
  IETF 113		20 - 25 March 2022
  IETF 114		24 - 29 July 2022
  IETF 115		6 - 11 November 2022

From gih@apnic.net  Tue Nov 20 22:17:10 2012
Return-Path: <gih@apnic.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 53A6F21F880A; Tue, 20 Nov 2012 22:17:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.695
X-Spam-Level: 
X-Spam-Status: No, score=-98.695 tagged_above=-999 required=5 tests=[AWL=-0.679, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, RCVD_IN_XBL=3.033, RDNS_NONE=0.1, 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 Bb8gMmqeqZKU; Tue, 20 Nov 2012 22:17:09 -0800 (PST)
Received: from asmtp.apnic.net (asmtp.apnic.net [IPv6:2001:dc0:2001:11::199]) by ietfa.amsl.com (Postfix) with ESMTP id 2504D21F8808; Tue, 20 Nov 2012 22:17:08 -0800 (PST)
Received: from [192.168.51.200] (unknown [87.213.29.58]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by asmtp.apnic.net (Postfix) with ESMTP id 5418CB6840; Wed, 21 Nov 2012 16:17:03 +1000 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
From: Geoff Huston <gih@apnic.net>
In-Reply-To: <45813A84-7BE9-4D21-AE3E-F3401D6E1B50@apnic.net>
Date: Wed, 21 Nov 2012 17:16:58 +1100
Content-Transfer-Encoding: 7bit
Message-Id: <99B9866C-41D6-4784-AA69-CD25E5910F4B@apnic.net>
References: <20121113144545.12836.71935.idtracker@ietfa.amsl.com>	<CAKFn1SF4+k5gWip-WBNfbjt-qAafPbTSY8L_EBLA9Pqvbw4=kQ@mail.gmail.com> <50A66313.9090002@joelhalpern.com> <50A66B67.5000609@gmail.com> <50A67758.8000001@joelhalpern.com> <33C6C196-B881-4BAA-8E57-082B266C831A@steffann.nl> <50A6ADD0.3040000@joelhalpern.com> <45813A84-7BE9-4D21-AE3E-F3401D6E1B50@apnic.net>
To: "ietf@ietf.org List" <ietf@ietf.org>
X-Mailer: Apple Mail (2.1499)
Cc: Paul Wilson <pwilson@apnic.net>, John Curran <jcurran@arin.net>, lisp@ietf.org, "iesg@ietf.org IESG" <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Nov 2012 06:17:10 -0000

Hi,

We would like to make the following comments in response to the IETF
Last Call on the proposal to publish this draft as an Informational 
RFC.

The guidelines for IP address allocations were documented in RFC2050,
adopted in November 1996 as a Best Current Practice. This document
described the framework of the Internet Registry system, and the roles
and responsibilities of various parties involved in the distribution of
addresses in the Internet. The document was not intentionally related to
any particular routing technology, and addressed guidelines that would
maximise the effective use of address space.

The Memorandum of Understanding between the IETF and ICANN over the IANA
activity, RFC2860, published in June 2000, provides further details of
the address management function. In particular, the document notes that
"assignments of specialised address blocks (such as multicast or anycast
blocks), and experimental assignments are not considered to be policy
issues, and shall remain subject to the provisions of this [document]."

RFC 4773, published in December 2006, provides some guidelines to the
IANA concerning the management of these specialised address assignments
in IPv6: "IANA may undertake IPv6 address designations in support of
special purposes as requested in "IANA Considerations" sections in IESG-
reviewed RFCs, where an address is requested with an intended use of the
designated address block for the purpose of testing or experimental
usage activities initiated by IETF, or for specialised use of the
address block in a context (e.g., anycast) associated with an Internet
Standards track protocol."

In this context the request to IANA to reserve an IPv6 /12 address and
allocate out of it a /16 block for use as an EID space for the
experimental LISP protocol presents some questions.

It is noted that the LISP experiment already makes use of a /32 prefix,
"with more than 250 sites using a /48 sub prefix", as noted in
draft-ietf-lisp-eid-block-03.txt. Even with an overall 50% utilisation
rate of this prefix there is scope in the current /32 address block to
address some 32,000 further sites using a /48 sub prefix.

If the LISP experiment fills this /32 prefix to such a level of
utilisation then there would be reasonable grounds to make the case that
at such a time the LISP activity would no longer be an experimental
effort, as it would be an instance of an application that makes use of
the global unicast address pool. In this case the provisions of RFC
4773, and the applicability of a special purpose address allocation
would not be expected to apply, as this would fall under the terms of
RFC2050 and the address allocation function would be administered by the
Regional internet Registries, according to RFC2860.

If we were to consider this request for the reservation of a /12 and the
allocation of a /16 in the context of support for an experiment, then
the nature of the experiment is unclear. At the scale of a /16 being
capable of supporting a theoretical maximum of some 4.3 billion /48 end
sites, and a /12 supporting a theoretical maximum of 68.7 billion /48
end sites, then the boundary conditions of such an experiment become
challenging to define. How can one define the experiment to have
finished? What are the plans to migrate out of the experimental address
allocation? Would this renumbering out of an experimental address
allocation even be feasible to contemplate if the experiment achieves a
level of deployment that is commensurate with the allocation of /16?

Such large scale deployment activities being undertaken under the
provisions of an experimental activity also raises a number of questions
about the registry services to be provided in support of such a
reservation. Given that this particular experiment is intended to
operate on the global IPv6 Internet it is apparent that some form of
directory (e.g. Whois) and reverse DNS services will be necessary; is
the provision of such services on a large scale (i.e. for potentially
tens of thousands of individual entities) to be performed by the IANA? 
If so then this appears contrary to RFC 4773's statement that the "IANA
will not maintain further sub-registries for any special purpose address
block designated according to this direction."  Further, the
implementation of any large scale directory such as resulting from this
type of experimental reservation would definitely pose serious policy
issues, e.g. trading off operational visibility, privacy, and law
enforcement needs, and by the spirit of the IETF/ICANN MOU on IANA
activities (RFC 2860). It would appear from this perspective that such
an assignment of address resources is not suitable to be made as an
experimental assignment.

The question this draft raises is to identify the basis of the request.
An experimental allocation of this size does not appear to be consistent
with a conventional view of an experiment. The draft's proposals appear
more aligned to the activity of planning for large scale public
deployment of a global routing infrastructure for global unicast
addresses. But if that is indeed the case then the provisions of RFC4773
do not apply, as the special Purpose Address Allocation Registry does
not encompass the allocation of address blocks for use in a global
unicast address context in the context of large scale deployment
activities.

A possible course of action for the LISP Working Group and the IESG to
consider would be for the existing /32 address be documented as an IANA
Special Purpose Address allocation for use in supporting the current
LISP experiment, and for the LISP advocates to make their case for
particular requirements in the handling of global unicast address
allocations in IPv6 to the regional addressing communities. This would
allow the existing address policy development process to generate
outcomes that appropriately address the desires and concerns of the
broader community of stakeholders in supporting the potential
requirements of a broad base of deployment of LISP in the Internet's
routing environment.

We do not support the publication of this draft as an Informational RFC.

regards,

  John Curran,
  Paul Wilson, and
  Geoff Huston

From sm@resistor.net  Wed Nov 21 02:40:29 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E336921F8624; Wed, 21 Nov 2012 02:40:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.51
X-Spam-Level: 
X-Spam-Status: No, score=-102.51 tagged_above=-999 required=5 tests=[AWL=0.089, 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 5faPZZWASsps; Wed, 21 Nov 2012 02:40:27 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0655021F8440; Wed, 21 Nov 2012 02:40:17 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id qALAeA3B015359; Wed, 21 Nov 2012 02:40:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1353494416; bh=XRdU9Pqp3mKfHt3EmHsvTw+10GvMaizVw5iPeiRMw2I=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=E3gW6oCvksJww+o2DfAuXOpj9jxUxnb1hSpzivt2adHU53XDfrexqzfKeHeh/RLIU kwwUa5xrScHlDxG2qYRy/cKstzBlOKhDPowWfY7pmbqq6vBA5+mszy+ap6A72Olb/v +kKBtBc/zuM10NVNlZM0SpMCuuU2MmW2H3moh0BI=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1353494416; i=@resistor.net; bh=XRdU9Pqp3mKfHt3EmHsvTw+10GvMaizVw5iPeiRMw2I=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=UekhTUtD8yphtTBIX3tKiy1LZEE/8iCa592YgGTqOKgQ80XdJ+QF/rXU2/7AHS9BG mKB4z4vldHKkwGca/lRRQP4ltMYu/hagT+X89Z6flKwWlgDqWsWh7uejJ3yeQL6JBu O0GCVzbxD2OmIKZDT/dueZwI3+IRmKa1wOnBDTBc=
Message-Id: <6.2.5.6.2.20121121005659.0a1349a8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 21 Nov 2012 02:29:24 -0800
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
In-Reply-To: <99B9866C-41D6-4784-AA69-CD25E5910F4B@apnic.net>
References: <20121113144545.12836.71935.idtracker@ietfa.amsl.com> <CAKFn1SF4+k5gWip-WBNfbjt-qAafPbTSY8L_EBLA9Pqvbw4=kQ@mail.gmail.com> <50A66313.9090002@joelhalpern.com> <50A66B67.5000609@gmail.com> <50A67758.8000001@joelhalpern.com> <33C6C196-B881-4BAA-8E57-082B266C831A@steffann.nl> <50A6ADD0.3040000@joelhalpern.com> <45813A84-7BE9-4D21-AE3E-F3401D6E1B50@apnic.net> <99B9866C-41D6-4784-AA69-CD25E5910F4B@apnic.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: lisp@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Nov 2012 10:40:29 -0000

At 22:16 20-11-2012, Geoff Huston wrote:
>The guidelines for IP address allocations were documented in RFC2050,
>adopted in November 1996 as a Best Current Practice. This document

Some parts of RFC 2050 could be considered as Historic.   As a FYI 
there is only one IANA policy about IPv6 [1].

>It is noted that the LISP experiment already makes use of a /32 prefix,
>"with more than 250 sites using a /48 sub prefix", as noted in
>draft-ietf-lisp-eid-block-03.txt. Even with an overall 50% utilisation
>rate of this prefix there is scope in the current /32 address block to
>address some 32,000 further sites using a /48 sub prefix.

Yes.

>If the LISP experiment fills this /32 prefix to such a level of
>utilisation then there would be reasonable grounds to make the case that
>at such a time the LISP activity would no longer be an experimental
>effort, as it would be an instance of an application that makes use of
>the global unicast address pool. In this case the provisions of RFC
>4773, and the applicability of a special purpose address allocation
>would not be expected to apply, as this would fall under the terms of
>RFC2050 and the address allocation function would be administered by the
>Regional internet Registries, according to RFC2860.

There is ample material in the Last Call comments to generate 
DISCUSSes.  The question is how many DISCUSSes will be filed.  It's 
easier to leave the progress of the draft to a matter of IETF 
consensus than to invoke the RFC 4773 or RFC 2860.  IANA is bound to 
follow technical guidance exclusively from the IESG.  It is 
improbable that IANA would invoke the dispute clause.

>A possible course of action for the LISP Working Group and the IESG to
>consider would be for the existing /32 address be documented as an IANA
>Special Purpose Address allocation for use in supporting the current
>LISP experiment, and for the LISP advocates to make their case for
>particular requirements in the handling of global unicast address
>allocations in IPv6 to the regional addressing communities. This would

Anything more than a /32 might have to be a global policy 
proposal.  It would likely take over a year to get such a proposal 
through all the RIRs.

Regards,
-sm

P.S. Don't boil the ocean to kill a single fish (credits - Noel Chiappa)

1. 
https://www.icann.org/en/news/in-focus/global-addressing/allocation-ipv6-rirs 


From sander@steffann.nl  Wed Nov 21 03:21:52 2012
Return-Path: <sander@steffann.nl>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B7E6E21F85C1; Wed, 21 Nov 2012 03:21:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_53=0.6]
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 g0v8btdhvYNq; Wed, 21 Nov 2012 03:21:52 -0800 (PST)
Received: from mail.sintact.nl (mail.sintact.nl [IPv6:2001:4038:0:16::7]) by ietfa.amsl.com (Postfix) with ESMTP id EE87D21F85B0; Wed, 21 Nov 2012 03:21:51 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.sintact.nl (Postfix) with ESMTP id DF86F2063; Wed, 21 Nov 2012 12:21:49 +0100 (CET)
X-Virus-Scanned: amavisd-new at mail.sintact.nl
Received: from mail.sintact.nl ([127.0.0.1]) by localhost (mail.sintact.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vrLF4SzieQ6T; Wed, 21 Nov 2012 12:21:46 +0100 (CET)
Received: from [IPv6:2a00:8640:1::bc78:afc:293b:85a0] (unknown [IPv6:2a00:8640:1:0:bc78:afc:293b:85a0]) by mail.sintact.nl (Postfix) with ESMTP id 76C882009; Wed, 21 Nov 2012 12:21:41 +0100 (CET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
From: Sander Steffann <sander@steffann.nl>
In-Reply-To: <99B9866C-41D6-4784-AA69-CD25E5910F4B@apnic.net>
Date: Wed, 21 Nov 2012 12:16:40 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <F05F08E4-18DA-4F45-AC0F-0930FD978E64@steffann.nl>
References: <20121113144545.12836.71935.idtracker@ietfa.amsl.com>	<CAKFn1SF4+k5gWip-WBNfbjt-qAafPbTSY8L_EBLA9Pqvbw4=kQ@mail.gmail.com> <50A66313.9090002@joelhalpern.com> <50A66B67.5000609@gmail.com> <50A67758.8000001@joelhalpern.com> <33C6C196-B881-4BAA-8E57-082B266C831A@steffann.nl> <50A6ADD0.3040000@joelhalpern.com> <45813A84-7BE9-4D21-AE3E-F3401D6E1B50@apnic.net> <99B9866C-41D6-4784-AA69-CD25E5910F4B@apnic.net>
To: "lisp@ietf.org list" <lisp@ietf.org>
X-Mailer: Apple Mail (2.1499)
Cc: "iesg@ietf.org IESG" <iesg@ietf.org>, Paul Wilson <pwilson@apnic.net>, John Curran <jcurran@arin.net>, "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Nov 2012 11:21:52 -0000

Hi,

> A possible course of action for the LISP Working Group and the IESG to
> consider would be for the existing /32 address be documented as an =
IANA
> Special Purpose Address allocation for use in supporting the current
> LISP experiment, and for the LISP advocates to make their case for
> particular requirements in the handling of global unicast address
> allocations in IPv6 to the regional addressing communities. This would
> allow the existing address policy development process to generate
> outcomes that appropriately address the desires and concerns of the
> broader community of stakeholders in supporting the potential
> requirements of a broad base of deployment of LISP in the Internet's
> routing environment.

So, if I understand you correctly you say that this should be a =
(global?) policy proposal in the different RIR regions. Is that correct?

If yes, then that could mean that every region allocates/assigns LISP =
prefixes from a separate block. Together with the current experimental =
/32 that would mean 6 prefixes for LISP in total. That's not as ideal as =
a single prefix, but still very acceptable for the BGP table.

If this wg agrees that this is the way forward then there are a few =
things that should be done as far as I can see:
- Define when the current experiment with the /32 is successful
- Document a vision of how LISP should be deployed using a few prefixes =
that cover all the LISP space
  - Advise on how LISP prefixes could/should be assigned
  - Probably also looking at different phases, for example:
    - Early adopters: separate PITRs+BGP routes for each /48?
    - Middle: central PITRs covering the whole LISP space (public? in =
tier-1 nets?)
    - Long term: LISP PITRs in all major networks
  - Describe a strategy to go from each phase to the next
  - How to deal with the prefixes if LISP isn't as widely accepted as we =
hope
- Writing a (global?) policy proposal for assignment of LISP prefixes
- Submitting that proposal to all RIR regions and try to get consensus =
there

I think that if we do the above we can show the operators a possible =
future where the BGP table isn't cluttered with PI prefixes. Worst case =
we end up with a prefix in BGP for every LISP end-site, but that's no =
worst than with current PI assignments. Best case we end up with a much =
smaller routing table (compared to normal PI) where all those end-sites =
are covered by a few prefixes. IMHO the most important thing is to plan =
on how to get there :-)

And yes: of course I volunteer to help writing this stuff :-)
Sander


From jnc@mercury.lcs.mit.edu  Wed Nov 21 05:48:53 2012
Return-Path: <jnc@mercury.lcs.mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F7CD21F85C8; Wed, 21 Nov 2012 05:48:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.603
X-Spam-Level: 
X-Spam-Status: No, score=-6.603 tagged_above=-999 required=5 tests=[AWL=-0.004, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 suBmShR9ewl4; Wed, 21 Nov 2012 05:48:52 -0800 (PST)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 8288521F85C7; Wed, 21 Nov 2012 05:48:52 -0800 (PST)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 6FFEF18C0CF; Wed, 21 Nov 2012 08:48:51 -0500 (EST)
To: ietf@ietf.org, lisp@ietf.org
Subject: Re: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
Message-Id: <20121121134851.6FFEF18C0CF@mercury.lcs.mit.edu>
Date: Wed, 21 Nov 2012 08:48:51 -0500 (EST)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu, jcurran@arin.net, pwilson@apnic.net, iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Nov 2012 13:48:53 -0000

    > From: Geoff Huston <gih@apnic.net>

I don't have any comment, one way or another, on what seems to be the basic
point of your note (about what role, if any, the IETF should play in
allocation).

However, there was one aspect I wanted to comment on (it's not clear, reading
your note, if this was clear in your minds):

    > It is noted that the LISP experiment already makes use of a /32 prefix
    > ...
    > If the LISP experiment fills this /32 prefix to such a level of
    > utilisation
    > ...
    > What are the plans to migrate out of the experimental address
    > allocation? Would this renumbering out of an experimental address
    > allocation even be feasible to contemplate if the experiment achieves a
    > level of deployment that is commensurate with the allocation of /16?

The concept, as I understand it, is that there will be no migration "out of
[that] allocation", for the simple reason that the entire rationale of this
range of namespace is that it will be processed differently, i.e. require
special casing in the code in various places; something like:

	if ((dest & EIDSPACEMASK) == EIDSPACEALLOCATION)
		process_one_way();
	  else
		process_another_way();

That being the case, the last thing one would want is either i) changing the
block that is handled specially, or ii) having a number of smaller blocks,
allocated over time, as either one would require much more complex code to
handle: you'd have to have some sort of config file, which could hold
multiple blocks, code to read it, the code to process packets (above) would
have to be able to handle multiple blocks, yadda-yadda.

(Changing the block is the same as having multiple blocks, because past a
certain point you're too big for a flag day, which would be the only way to
avoid having multiple blocks in use at the same time.)

It's that that's driving the suggested reservation, and the smaller actual
allocation: the code would handle any address inside the _reservation_ with
the special processing, but the bulk of the space would be left
_unallocated_, for future allocation in some yet-to-be-determined process
(one which would presumably be set up by the existing namespace allocation
entities), while a small chunk would be allocated to the experiment, for now.


I suspect (I haven't communicated with them directly) that the people who are
involved with this scheme don't really care _who_ allocates the space, and how
- all they care about is that it's all in one chunk - for the reason laid out
above.

	Noel

From wesley.george@twcable.com  Wed Nov 21 06:58:03 2012
Return-Path: <wesley.george@twcable.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3AC3721F8477; Wed, 21 Nov 2012 06:58:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.872
X-Spam-Level: 
X-Spam-Status: No, score=-0.872 tagged_above=-999 required=5 tests=[AWL=0.591,  BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, 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 4aL528nybOl6; Wed, 21 Nov 2012 06:58:02 -0800 (PST)
Received: from cdpipgw01.twcable.com (cdpipgw01.twcable.com [165.237.59.22]) by ietfa.amsl.com (Postfix) with ESMTP id 31E5021F8458; Wed, 21 Nov 2012 06:58:02 -0800 (PST)
X-SENDER-IP: 10.136.163.14
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.83,293,1352091600"; d="scan'208";a="474942891"
Received: from unknown (HELO PRVPEXHUB05.corp.twcable.com) ([10.136.163.14]) by cdpipgw01.twcable.com with ESMTP/TLS/RC4-MD5; 21 Nov 2012 09:57:47 -0500
Received: from PRVPEXVS15.corp.twcable.com ([10.136.163.79]) by PRVPEXHUB05.corp.twcable.com ([10.136.163.14]) with mapi; Wed, 21 Nov 2012 09:57:56 -0500
From: "George, Wes" <wesley.george@twcable.com>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>, "ietf@ietf.org" <ietf@ietf.org>, "lisp@ietf.org" <lisp@ietf.org>
Date: Wed, 21 Nov 2012 09:58:01 -0500
Subject: RE: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
Thread-Topic: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
Thread-Index: Ac3H7wPoZ/jx8irBTXOMm522xE1I8wAAU15g
Message-ID: <2671C6CDFBB59E47B64C10B3E0BD592303385FBC23@PRVPEXVS15.corp.twcable.com>
References: <20121121134851.6FFEF18C0CF@mercury.lcs.mit.edu>
In-Reply-To: <20121121134851.6FFEF18C0CF@mercury.lcs.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "pwilson@apnic.net" <pwilson@apnic.net>, "jcurran@arin.net" <jcurran@arin.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Nov 2012 14:58:03 -0000

> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> Noel Chiappa
> Sent: Wednesday, November 21, 2012 8:49 AM
> To: ietf@ietf.org; lisp@ietf.org
> Cc: jnc@mercury.lcs.mit.edu; jcurran@arin.net; pwilson@apnic.net;
> iesg@ietf.org
> Subject: Re: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP
> EID Block) to Informational RFC
>
> The concept, as I understand it, is that there will be no migration "out
> of [that] allocation", for the simple reason that the entire rationale
> of this range of namespace is that it will be processed differently,
> i.e. require special casing in the code in various places; something
> like:
>
>       if ((dest & EIDSPACEMASK) =3D=3D EIDSPACEALLOCATION)
>               process_one_way();
>         else
>               process_another_way();
>
> That being the case, the last thing one would want is either i) changing
> the block that is handled specially, or ii) having a number of smaller
> blocks, allocated over time, as either one would require much more
> complex code to
> handle: you'd have to have some sort of config file, which could hold
> multiple blocks, code to read it, the code to process packets (above)
> would have to be able to handle multiple blocks, yadda-yadda.
>
> (Changing the block is the same as having multiple blocks, because past
> a certain point you're too big for a flag day, which would be the only
> way to avoid having multiple blocks in use at the same time.)
>
[WEG] Then the draft needs to say some variant of the above - why it can't =
migrate, why a flag day won't work, and why it needs that size block right =
now for an experimental technology, including some justification about the =
size of the block. If the allocation justification is not going to be done =
within the RIR community, then it needs to be done here. Noel, you specific=
ally complained about IETF not allowing experiments to proceed while some d=
etails are still a little hand-wavey [1], but you seem to want it both ways=
. If this is to be permanent space, then permanent justification and level =
of detail is required. If it's to be an experiment, then it should expect t=
hat there will be at least one renumber as it transitions from experiment t=
o production. I don't think that expecting code to handle two blocks (the e=
xperimental one and the permanent one) is asking too much, nor is it expect=
ing too much to require a line in the sand to ensure that the transition be=
tween experiment and production happens before "you're too big for a flag d=
ay".
If a single permanent allocation that never changes is truly necessary, put=
ting a sunset date on the allocation from IANA seems a reasonable solution =
to me, but no one really responded to that in my last mail [2]. If the expe=
riment is wildly successful and leads to a permanent deployment, then the c=
urrently experimental RFCs get updates written to elevate them to proposed =
standard, and while we're at it, we remove the sunset date from the IANA al=
location. If the experiment ends up being a science project and doesn't gai=
n wide deployment, this reclaims the space to prevent it from being another=
 "Class E" space that is essentially stranded by an allocation that is no l=
onger used.
>
> I suspect (I haven't communicated with them directly) that the people
> who are involved with this scheme don't really care _who_ allocates the
> space, and how
> - all they care about is that it's all in one chunk - for the reason
> laid out above.
>
[WEG] and the people who are involved in number allocation have clearly tol=
d "the people involved in this scheme" that they do care who allocates the =
space and how, especially if the experiment has no bounded end. I think a c=
ompromise is doable, but saying "it's not important right now" probably isn=
't going to make the problem go away.


Thanks,
Wes George

[1] http://www.ietf.org/mail-archive/web/ietf/current/msg75920.html
[2] http://www.ietf.org/mail-archive/web/ietf/current/msg75919.html


This E-mail and any of its attachments may contain Time Warner Cable propri=
etary information, which is privileged, confidential, or subject to copyrig=
ht belonging to Time Warner Cable. This E-mail is intended solely for the u=
se of the individual or entity to which it is addressed. If you are not the=
 intended recipient of this E-mail, you are hereby notified that any dissem=
ination, distribution, copying, or action taken in relation to the contents=
 of and attachments to this E-mail is strictly prohibited and may be unlawf=
ul. If you have received this E-mail in error, please notify the sender imm=
ediately and permanently delete the original and any copy of this E-mail an=
d any printout.

From jnc@mercury.lcs.mit.edu  Wed Nov 21 09:58:38 2012
Return-Path: <jnc@mercury.lcs.mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D6AC21F85B8; Wed, 21 Nov 2012 09:58:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.603
X-Spam-Level: 
X-Spam-Status: No, score=-6.603 tagged_above=-999 required=5 tests=[AWL=-0.004, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 dsWXT7ct74XF; Wed, 21 Nov 2012 09:58:37 -0800 (PST)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 7BEC321F8532; Wed, 21 Nov 2012 09:58:37 -0800 (PST)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id EE11B18C0D3; Wed, 21 Nov 2012 12:58:36 -0500 (EST)
To: ietf@ietf.org, lisp@ietf.org
Subject: RE: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
Message-Id: <20121121175836.EE11B18C0D3@mercury.lcs.mit.edu>
Date: Wed, 21 Nov 2012 12:58:36 -0500 (EST)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Nov 2012 17:58:38 -0000

    > From: "George, Wes" <wesley.george@twcable.com>

    > I don't think that expecting code to handle two blocks (the
    > experimental one and the permanent one) is asking too much

We disagree. For me, it's extra code/complexity, and it buys you absolutely
nothing at all.

    > If a single permanent allocation that never changes is truly necessary

Allocation != reservation. Nobody is asking for the entire chunk to be
_allocated_ (i.e. given out), just that it be _reserved_ for this use.

	Noel

From chair@ietf.org  Wed Nov 21 11:03:51 2012
Return-Path: <chair@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 554E821F8458; Wed, 21 Nov 2012 11:03:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.573
X-Spam-Level: 
X-Spam-Status: No, score=-102.573 tagged_above=-999 required=5 tests=[AWL=0.026, 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 nJgrjEUMsVo5; Wed, 21 Nov 2012 11:03:48 -0800 (PST)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:123a::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id 2270F21F8448; Wed, 21 Nov 2012 11:03:48 -0800 (PST)
Received: from localhost (c8a.amsl.com [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id D45401242AF; Wed, 21 Nov 2012 11:03:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NWpqrxksspst; Wed, 21 Nov 2012 11:03:46 -0800 (PST)
Received: from [192.168.2.105] (pool-96-255-37-162.washdc.fios.verizon.net [96.255.37.162]) by c8a.amsl.com (Postfix) with ESMTPSA id 789D21242A6; Wed, 21 Nov 2012 11:03:46 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Subject: IETF Chair's Presentation at the Global Standards Symposium in Dubai
Mime-Version: 1.0 (Apple Message framework v1085)
From: IETF Chair <chair@ietf.org>
Date: Wed, 21 Nov 2012 14:03:45 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <68DCA9DE-6FC1-4462-826D-E7D313279A0A@ietf.org>
To: IETF Announce <ietf-announce@ietf.org>
X-Mailer: Apple Mail (2.1085)
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: IETF <ietf@ietf.org>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Nov 2012 19:03:51 -0000

Last Monday, I gave a short presentation on collaboration among =
standards development organizations at the Global Standards Symposium in =
Dubai, UAE.

The Internest Society has posted my slides and a transcript of my words. =
 These are available here: =
http://www.internetsociety.org/doc/remarks-global-standards-symposium-2012=


I referenced the OpenStand principles in my comments.  These can be =
found at http:www.open-stand.org.

Leslie Daigle, the Chief Internet Technology Officer at the Internet =
Society, took this opportunity to write a brief post about OpenStand; it =
is available here: =
http://www.internetsociety.org/blog/2012/11/open-internet-standards-collab=
oration

Thanks,
  Russ=

From kre@munnari.OZ.AU  Wed Nov 21 11:12:30 2012
Return-Path: <kre@munnari.OZ.AU>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C6CD21F87E7; Wed, 21 Nov 2012 11:12:30 -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 AZo-WlUu-YFF; Wed, 21 Nov 2012 11:12:24 -0800 (PST)
Received: from jade.coe.psu.ac.th (unknown [IPv6:2001:3c8:9009:181::2]) by ietfa.amsl.com (Postfix) with ESMTP id 4839321F87DA; Wed, 21 Nov 2012 11:12:23 -0800 (PST)
Received: from epsilon.noi.kre.to (jade.coe.psu.AC.TH [IPv6:2001:3c8:9007:1::21]) by jade.coe.psu.ac.th with ESMTP id qALJC7rA007625; Thu, 22 Nov 2012 02:12:08 +0700 (ICT)
Received: from epsilon.noi.kre.to (localhost [127.0.0.1]) by epsilon.noi.kre.to (8.14.4/8.14.2) with ESMTP id qALJ9lBF025273; Thu, 22 Nov 2012 02:09:47 +0700 (ICT)
From: Robert Elz <kre@munnari.OZ.AU>
To: Geoff Huston <gih@apnic.net>
Subject: Re: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
In-Reply-To: <99B9866C-41D6-4784-AA69-CD25E5910F4B@apnic.net>
References: <99B9866C-41D6-4784-AA69-CD25E5910F4B@apnic.net> <20121113144545.12836.71935.idtracker@ietfa.amsl.com> <CAKFn1SF4+k5gWip-WBNfbjt-qAafPbTSY8L_EBLA9Pqvbw4=kQ@mail.gmail.com> <50A66313.9090002@joelhalpern.com> <50A66B67.5000609@gmail.com> <50A67758.8000001@joelhalpern.com> <33C6C196-B881-4BAA-8E57-082B266C831A@steffann.nl> <50A6ADD0.3040000@joelhalpern.com> <45813A84-7BE9-4D21-AE3E-F3401D6E1B50@apnic.net> 
Date: Thu, 22 Nov 2012 02:09:47 +0700
Message-ID: <19339.1353524987@epsilon.noi.kre.to>
Sender: kre@munnari.OZ.AU
Cc: "iesg@ietf.org IESG" <iesg@ietf.org>, Paul Wilson <pwilson@apnic.net>, John Curran <jcurran@arin.net>, "ietf@ietf.org List" <ietf@ietf.org>, lisp@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Nov 2012 19:12:31 -0000

    Date:        Wed, 21 Nov 2012 17:16:58 +1100
    From:        Geoff Huston <gih@apnic.net>
    Message-ID:  <99B9866C-41D6-4784-AA69-CD25E5910F4B@apnic.net>

I have no idea whether the allocation requested is reasonable or not,
I haven't read the draft (and unless it becomes more widely used than
currently, might never do so), but I do know that this argument ...

  | The guidelines for IP address allocations were documented in RFC2050,
  | adopted in November 1996 as a Best Current Practice. ...

is totally bogus in these circumstances.

The rules in RFCs and BCPs bind ordinary users making ordinary requests
for address space - were I to approach IANA with a request for address
space to be allocated, a quick denial quoting the relevant RFC would indeed
be the correct response.

But when the IETF publishes an updated RFC, that always overrides any
earlier RFC, and establishes new policy - either for the general case, or
perhaps (as seems to be happening here) just a one off override of the
normal rules.

Doing that is always acceptable, whatever the issue - it is never adequate
to simply refuse to consider such requests upon the basis that they don't
follow the rules and should be done some other way.

Now, when the IETF (via the last call consensus mechanism) consider whether
the proposed RFC should be published, it is perfectly reasonable to point
out the existing policy, and ask for reasons why use of that mechanism would
not be adequate - if the proponents cannnot explain why doing it the way
they are suggesting is required, or at least is better than the normal way,
then the request (to publish the RFC, not just to perform whatever allocation
it requested - that just falls out of the failure to publish the RFC) should
be refused.

On the other hand, if the proponents can convince the IETF that the
procedure they're suggesting is the best way to proceed, then that's
what should happen - and that it isn't being done the way that the
normal allocation rules would suggest it should be done is 100% irrelevant.

If you have an argument against the proposal, please make it upon the
merits of the request, and not based upon some supposed viloation of
address allocation quidelines.

What the result will be I have no idea - I don't know if this allocation
should happen or not.   I might suggest however, that if Noel is correct
about the way this allocation would be used (and Noel usually is correct)
then it may be that an assignment out of the 0::/3 address space (which is
out of the ordinary allocation space for which the guidelines apply)
sounds like it might be the right thing to do - perhaps something like
10f0::/12 (or something near there not currently allocated).

kre

From sander@steffann.nl  Wed Nov 21 12:03:21 2012
Return-Path: <sander@steffann.nl>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0A8421F83EF; Wed, 21 Nov 2012 12:03:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.504
X-Spam-Level: 
X-Spam-Status: No, score=-0.504 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545]
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 ryv4Ej6jpveY; Wed, 21 Nov 2012 12:03:20 -0800 (PST)
Received: from mail.sintact.nl (mail.sintact.nl [IPv6:2001:4038:0:16::7]) by ietfa.amsl.com (Postfix) with ESMTP id 618AE21F842B; Wed, 21 Nov 2012 12:03:20 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.sintact.nl (Postfix) with ESMTP id 2C1F42009; Wed, 21 Nov 2012 21:03:10 +0100 (CET)
X-Virus-Scanned: amavisd-new at mail.sintact.nl
Received: from mail.sintact.nl ([127.0.0.1]) by localhost (mail.sintact.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QEpz6dW213Gd; Wed, 21 Nov 2012 21:03:05 +0100 (CET)
Received: from macpro.10ww.steffann.nl (macpro.10ww.steffann.nl [37.77.56.75]) by mail.sintact.nl (Postfix) with ESMTP id 5C94B206A; Wed, 21 Nov 2012 21:03:04 +0100 (CET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
From: Sander Steffann <sander@steffann.nl>
In-Reply-To: <20121121175836.EE11B18C0D3@mercury.lcs.mit.edu>
Date: Wed, 21 Nov 2012 21:03:04 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <ED60EE46-DFC3-47B0-8D96-BDE5465EF81C@steffann.nl>
References: <20121121175836.EE11B18C0D3@mercury.lcs.mit.edu>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
X-Mailer: Apple Mail (2.1499)
Cc: ietf@ietf.org, lisp@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Nov 2012 20:03:22 -0000

Hi Noel,

>> I don't think that expecting code to handle two blocks (the
>> experimental one and the permanent one) is asking too much
>=20
> We disagree. For me, it's extra code/complexity, and it buys you =
absolutely
> nothing at all.

I don't agree. See below.

>> If a single permanent allocation that never changes is truly =
necessary
>=20
> Allocation !=3D reservation. Nobody is asking for the entire chunk to =
be
> _allocated_ (i.e. given out), just that it be _reserved_ for this use.

But if I understand correctly it's going to be hard-coded somewhere. =
That will mean that everything that is reserved now will be unusable for =
anything else ever. I'm not *that* worried about wasting IPv6 addresses, =
but I do worry about any hard-coding of prefixes. What for example if =
LISP is such a success that the block is too small?

Wouldn't it be better to have a bootstrap method that is more flexible? =
The DDT root servers know which prefixes are delegated, so we might =
extend the DDT protocol to return that list of prefixes. I write code =
myself, so I know it's a lot more work to implement something like that =
properly. I'm worried about the consequences of making this hard-coded =
though. We can't foresee all the possibilities at this point in time (if =
ever).

Another benefit of making this flexible is that multiple models of LISP =
deployment can be used. It doesn't matter anymore if IANA reserves a =
special block, RIRs assign from separate blocks, or even if ISPs offer =
LISP based solutions to their customers (which happens to be what I am =
doing).

You get all that, but yes: it does make the code more complex. On the =
other hand: LISP implementations know how to talk to DDT servers and =
probably also have prefix-list-matching code already, so it shouldn't be =
too difficult to get a list of prefixes and match against it.

- Sander


From wesley.george@twcable.com  Wed Nov 21 12:25:10 2012
Return-Path: <wesley.george@twcable.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 798EB21F85FC; Wed, 21 Nov 2012 12:25:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.409
X-Spam-Level: 
X-Spam-Status: No, score=-0.409 tagged_above=-999 required=5 tests=[AWL=0.054,  BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368]
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 P39HwDp9I7ew; Wed, 21 Nov 2012 12:25:10 -0800 (PST)
Received: from cdpipgw02.twcable.com (cdpipgw02.twcable.com [165.237.59.23]) by ietfa.amsl.com (Postfix) with ESMTP id B08F321F85DF; Wed, 21 Nov 2012 12:25:09 -0800 (PST)
X-SENDER-IP: 10.136.163.12
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.83,294,1352091600"; d="scan'208";a="456095235"
Received: from unknown (HELO PRVPEXHUB03.corp.twcable.com) ([10.136.163.12]) by cdpipgw02.twcable.com with ESMTP/TLS/RC4-MD5; 21 Nov 2012 15:24:51 -0500
Received: from PRVPEXVS15.corp.twcable.com ([10.136.163.79]) by PRVPEXHUB03.corp.twcable.com ([10.136.163.12]) with mapi; Wed, 21 Nov 2012 15:25:08 -0500
From: "George, Wes" <wesley.george@twcable.com>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>, "ietf@ietf.org" <ietf@ietf.org>, "lisp@ietf.org" <lisp@ietf.org>
Date: Wed, 21 Nov 2012 15:25:12 -0500
Subject: RE: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
Thread-Topic: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
Thread-Index: Ac3IEeLx7gw52o/PQTOjMBiBnBLqwwAE4fQg
Message-ID: <2671C6CDFBB59E47B64C10B3E0BD592303385FBF7A@PRVPEXVS15.corp.twcable.com>
References: <20121121175836.EE11B18C0D3@mercury.lcs.mit.edu>
In-Reply-To: <20121121175836.EE11B18C0D3@mercury.lcs.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Nov 2012 20:25:10 -0000

> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> Noel Chiappa
>
>     > If a single permanent allocation that never changes is truly
> necessary
>
> Allocation !=3D reservation. Nobody is asking for the entire chunk to be
> _allocated_ (i.e. given out), just that it be _reserved_ for this use.
>

[WEG] You're hairsplitting on semantics in a way that is mostly unhelpful t=
o the discussion at hand. Reserving the block for LISP means that it cannot=
 be used for anything else. Whether that's an IANA reservation or an RIR al=
location is really immaterial to the point I was making, which is that if y=
ou truly believe we have to identify a block once and for all for LISP that=
 is the correct size to be used permanently and indefinitely, you need a be=
tter justification than you've given, and using "experimental" as a justifi=
cation for not having the details worked out isn't going to be acceptable.

Regards,

Wes George

This E-mail and any of its attachments may contain Time Warner Cable propri=
etary information, which is privileged, confidential, or subject to copyrig=
ht belonging to Time Warner Cable. This E-mail is intended solely for the u=
se of the individual or entity to which it is addressed. If you are not the=
 intended recipient of this E-mail, you are hereby notified that any dissem=
ination, distribution, copying, or action taken in relation to the contents=
 of and attachments to this E-mail is strictly prohibited and may be unlawf=
ul. If you have received this E-mail in error, please notify the sender imm=
ediately and permanently delete the original and any copy of this E-mail an=
d any printout.

From jnc@mercury.lcs.mit.edu  Wed Nov 21 12:42:57 2012
Return-Path: <jnc@mercury.lcs.mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EEC6E21F887E; Wed, 21 Nov 2012 12:42:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.602
X-Spam-Level: 
X-Spam-Status: No, score=-6.602 tagged_above=-999 required=5 tests=[AWL=-0.003, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 VHhYQcSQIsXq; Wed, 21 Nov 2012 12:42:56 -0800 (PST)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 58A7221F8A21; Wed, 21 Nov 2012 12:42:56 -0800 (PST)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 3742818C0C9; Wed, 21 Nov 2012 15:42:55 -0500 (EST)
To: ietf@ietf.org, lisp@ietf.org
Subject: RE: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
Message-Id: <20121121204255.3742818C0C9@mercury.lcs.mit.edu>
Date: Wed, 21 Nov 2012 15:42:55 -0500 (EST)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Nov 2012 20:42:57 -0000

    > From: "George, Wes" <wesley.george@twcable.com>

    >> Allocation != reservation.

    > You're hairsplitting on semantics in a way that is mostly unhelpful to
    > the discussion at hand.

I _thought_ that the point of the messages from Geoff and others (who were
questioning about how there were no details in the document of how the
allocation would work) was about _how_ the space was to be handed out - to
which the allocation/reservation distinction _is_ important.

	Noel

From farinacci@gmail.com  Wed Nov 21 14:01:18 2012
Return-Path: <farinacci@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 76B9821F8528; Wed, 21 Nov 2012 14:01:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.535
X-Spam-Level: 
X-Spam-Status: No, score=-3.535 tagged_above=-999 required=5 tests=[AWL=0.064,  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 wY4+CFdZCvqL; Wed, 21 Nov 2012 14:01:18 -0800 (PST)
Received: from mail-pa0-f44.google.com (mail-pa0-f44.google.com [209.85.220.44]) by ietfa.amsl.com (Postfix) with ESMTP id E2D1621F84DF; Wed, 21 Nov 2012 14:01:17 -0800 (PST)
Received: by mail-pa0-f44.google.com with SMTP id hz11so3381321pad.31 for <multiple recipients>; Wed, 21 Nov 2012 14:01:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=8XtVZ4N29/ajQjbRF6boaEj6+v/EqX8IbB+wwMAgjWw=; b=WPjcm9eFmqImKzJ1QhL9G8CsG2iGn0XRy0xXiP71bgdCWbUu0uAjQk2ZMhtCFyW7pu OsjxEVEJ/LzWD6YyUv7/KjAX5PLd8Ep2yFwpdYGQt/KdhOM8TJGzrCtaWpySuRVTo4qy Gz7glm+jBqTz6YwCJ25o0WnPxuCMiL18iO6v4qG2qKt2i1/v0XpqVvpdpAeWjby032rD FVFIjIy5KvL0onGgL0E9bOIHWwwhPFf+8hUpmvIyT2y8FMCHuXLrJGAMT3sqcekKSBmW G59e4UkSB/qYfoteA1TdtujmuQBIDnhJh6JtNg+T5FrbuV7qzof9tMCcikVf7Ktd8QZD 5dmA==
Received: by 10.66.72.136 with SMTP id d8mr21110216pav.4.1353535277735; Wed, 21 Nov 2012 14:01:17 -0800 (PST)
Received: from sjc-vpn5-1696.cisco.com (128-107-239-233.cisco.com. [128.107.239.233]) by mx.google.com with ESMTPS id v9sm661678paz.6.2012.11.21.14.01.14 (version=SSLv3 cipher=OTHER); Wed, 21 Nov 2012 14:01:15 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
From: Dino Farinacci <farinacci@gmail.com>
In-Reply-To: <2671C6CDFBB59E47B64C10B3E0BD592303385FBF7A@PRVPEXVS15.corp.twcable.com>
Date: Wed, 21 Nov 2012 14:01:14 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <A19BAA78-C359-4AB5-8C22-046938B64ACB@gmail.com>
References: <20121121175836.EE11B18C0D3@mercury.lcs.mit.edu> <2671C6CDFBB59E47B64C10B3E0BD592303385FBF7A@PRVPEXVS15.corp.twcable.com>
To: "George, Wes" <wesley.george@twcable.com>
X-Mailer: Apple Mail (2.1499)
Cc: "lisp@ietf.org" <lisp@ietf.org>, Noel Chiappa <jnc@mercury.lcs.mit.edu>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Nov 2012 22:01:18 -0000

Make it an allocation for EIDs and ILNP can use it too.

Dino

On Nov 21, 2012, at 12:25 PM, "George, Wes" <wesley.george@twcable.com> =
wrote:

>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf =
Of
>> Noel Chiappa
>>=20
>>> If a single permanent allocation that never changes is truly
>> necessary
>>=20
>> Allocation !=3D reservation. Nobody is asking for the entire chunk to =
be
>> _allocated_ (i.e. given out), just that it be _reserved_ for this =
use.
>>=20
>=20
> [WEG] You're hairsplitting on semantics in a way that is mostly =
unhelpful to the discussion at hand. Reserving the block for LISP means =
that it cannot be used for anything else. Whether that's an IANA =
reservation or an RIR allocation is really immaterial to the point I was =
making, which is that if you truly believe we have to identify a block =
once and for all for LISP that is the correct size to be used =
permanently and indefinitely, you need a better justification than =
you've given, and using "experimental" as a justification for not having =
the details worked out isn't going to be acceptable.
>=20
> Regards,
>=20
> Wes George
>=20
> This E-mail and any of its attachments may contain Time Warner Cable =
proprietary information, which is privileged, confidential, or subject =
to copyright belonging to Time Warner Cable. This E-mail is intended =
solely for the use of the individual or entity to which it is addressed. =
If you are not the intended recipient of this E-mail, you are hereby =
notified that any dissemination, distribution, copying, or action taken =
in relation to the contents of and attachments to this E-mail is =
strictly prohibited and may be unlawful. If you have received this =
E-mail in error, please notify the sender immediately and permanently =
delete the original and any copy of this E-mail and any printout.
> _______________________________________________
> lisp mailing list
> lisp@ietf.org
> https://www.ietf.org/mailman/listinfo/lisp


From farinacci@gmail.com  Wed Nov 21 14:11:39 2012
Return-Path: <farinacci@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C2F4721F8903; Wed, 21 Nov 2012 14:11:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.539
X-Spam-Level: 
X-Spam-Status: No, score=-3.539 tagged_above=-999 required=5 tests=[AWL=0.060,  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 IFb0AeD2h6ib; Wed, 21 Nov 2012 14:11:39 -0800 (PST)
Received: from mail-pa0-f44.google.com (mail-pa0-f44.google.com [209.85.220.44]) by ietfa.amsl.com (Postfix) with ESMTP id 2AD5821F88A7; Wed, 21 Nov 2012 14:11:39 -0800 (PST)
Received: by mail-pa0-f44.google.com with SMTP id hz11so3386559pad.31 for <multiple recipients>; Wed, 21 Nov 2012 14:11:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=9Lxys3f1ZhkTCa1s6RvD2j0zLKO8P2YiFWcCtNu/R/g=; b=pq9bCorpC+COfzVDvlvQfd2qeNpJ94MiyqMkdffeP2Sklf4hwuMr8x8B1Y6Qhw1/YP 9HbHbyVOe8013WDx7WbPHBvbJ/gqUY/l0L7bAfVCJ9WxBxpKmtsjgGjgpH5QXY2yNOxV 6+p2CY46fXaZY9/Uqky6cdJu+2ozZIdkApwWR9zHyAKm3sIWz1z3Nnu6xfLZbFgTEexp 6fucCeK1C55JIR4yPzUw7/x4qOpaGeyzh4qFTyYUpFQMK966jwTp/J2cqFhfvjga2mrQ suZEytau+TJcEu02ZaFXGAB7G3VlBZ7YQi7MFOqAQF4M9Ln0zmmO3Vw9ekDJGD6p7UtX FBsg==
Received: by 10.68.134.233 with SMTP id pn9mr3260133pbb.125.1353535899014; Wed, 21 Nov 2012 14:11:39 -0800 (PST)
Received: from sjc-vpn5-1696.cisco.com (128-107-239-233.cisco.com. [128.107.239.233]) by mx.google.com with ESMTPS id c1sm668511pav.23.2012.11.21.14.11.36 (version=SSLv3 cipher=OTHER); Wed, 21 Nov 2012 14:11:38 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
From: Dino Farinacci <farinacci@gmail.com>
In-Reply-To: <99B9866C-41D6-4784-AA69-CD25E5910F4B@apnic.net>
Date: Wed, 21 Nov 2012 14:11:35 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <2227244C-BE63-4CED-A4EE-5DBE2881247A@gmail.com>
References: <20121113144545.12836.71935.idtracker@ietfa.amsl.com>	<CAKFn1SF4+k5gWip-WBNfbjt-qAafPbTSY8L_EBLA9Pqvbw4=kQ@mail.gmail.com> <50A66313.9090002@joelhalpern.com> <50A66B67.5000609@gmail.com> <50A67758.8000001@joelhalpern.com> <33C6C196-B881-4BAA-8E57-082B266C831A@steffann.nl> <50A6ADD0.3040000@joelhalpern.com> <45813A84-7BE9-4D21-AE3E-F3401D6E1B50@apnic.net> <99B9866C-41D6-4784-AA69-CD25E5910F4B@apnic.net>
To: Geoff Huston <gih@apnic.net>
X-Mailer: Apple Mail (2.1499)
Cc: "iesg@ietf.org IESG" <iesg@ietf.org>, Paul Wilson <pwilson@apnic.net>, John Curran <jcurran@arin.net>, "ietf@ietf.org List" <ietf@ietf.org>, lisp@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Nov 2012 22:11:40 -0000

> A possible course of action for the LISP Working Group and the IESG to
> consider would be for the existing /32 address be documented as an =
IANA
> Special Purpose Address allocation for use in supporting the current
> LISP experiment, and for the LISP advocates to make their case for
> particular requirements in the handling of global unicast address
> allocations in IPv6 to the regional addressing communities. This would
> allow the existing address policy development process to generate
> outcomes that appropriately address the desires and concerns of the
> broader community of stakeholders in supporting the potential
> requirements of a broad base of deployment of LISP in the Internet's
> routing environment.

I think this is a reasonable suggestion. I do believe the size of the =
prefix is less important than having a semantic associated with the =
prefix.

> We do not support the publication of this draft as an Informational =
RFC.
>=20
> regards,
>=20
>  John Curran,
>  Paul Wilson, and
>  Geoff Huston

Thanks guys.

Dino


From ben@nostrum.com  Wed Nov 21 15:13:05 2012
Return-Path: <ben@nostrum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 54FA821F84C4; Wed, 21 Nov 2012 15:13:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.479
X-Spam-Level: 
X-Spam-Status: No, score=-102.479 tagged_above=-999 required=5 tests=[AWL=0.121, BAYES_00=-2.599, SPF_PASS=-0.001, 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 TNe4AXAf5M6S; Wed, 21 Nov 2012 15:13:04 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 4EDB021F84C2; Wed, 21 Nov 2012 15:13:04 -0800 (PST)
Received: from [10.0.1.9] (cpe-76-187-92-156.tx.res.rr.com [76.187.92.156]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id qALNCx3D077248 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 21 Nov 2012 17:12:59 -0600 (CST) (envelope-from ben@nostrum.com)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: Gen-ART LC Review of draft-ietf-karp-routing-tcp-analysis-05.txt
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <F53DCC9A-8AA1-42D4-BF19-88ABCCCA68A7@gmail.com>
Date: Wed, 21 Nov 2012 17:12:57 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <3B3FEC40-3D96-4F77-A628-E80DFAEB2278@nostrum.com>
References: <18E6B18A-D465-47C6-9E06-886DFBFA1F67@nostrum.com> <F53DCC9A-8AA1-42D4-BF19-88ABCCCA68A7@gmail.com>
To: Mahesh Jethanandani <mjethanandani@gmail.com>
X-Mailer: Apple Mail (2.1499)
Received-SPF: pass (nostrum.com: 76.187.92.156 is authenticated by a trusted mechanism)
Cc: draft-ietf-karp-routing-tcp-analysis.all@tools.ietf.org, "gen-art@ietf.org Review Team" <gen-art@ietf.org>, "ietf@ietf.org List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Nov 2012 23:13:05 -0000

Hi, thanks for the response. I removed sections that didn't seem to need =
further comment:

On Nov 19, 2012, at 1:58 AM, Mahesh Jethanandani =
<mjethanandani@gmail.com> wrote:

[...]

>>=20
>> *** Minor issues *** :
>>=20
>> -- section 2.2, last paragraph:
>>=20
>> The IKE mention lacks context. Do you mean to suggest IKE with IPSec? =
I assume so, but there's been no mention of IPSec so far.
>=20
> No. It implies the use of IKEv2 protocol for performing mutual =
authentication and establishing SA. There is no suggestion of using IKE =
with IPSec.
>=20
> How about this?
>=20
> For point-to-point key management IKEv2[RFC5996] protocol provides ...

5996 describes IKEv2 as a component of IPSec, and a key-management =
mechanism for ESP and AH SAs. Now, I won't claim to be an IKE expert by =
any extent, but I think that if you mean to use IKE _without_ IPSec it =
would be good to add a sentence or two pointing that out. Or is there =
some other reference that could be used that describes using IKEv2 for =
non-IPSec SAs?

>=20
>=20
>>=20
>> -- section 2.3.2:
>>=20
>> It would be helpful for this section to describe whether privacy =
issues actually matter or not, rather than just stating the issues to be =
similar to those for other routing protocols.
>=20
> Changed it to:
>=20
> Labels, like routing information are distributed in the clear. There =
is currently no requirement for labels to be encrypted and that work is =
outside the scope of the KARP working group.

WFM

>=20
>>=20
>> -- section 3.1, 2nd paragraph:
>>=20
>> Does this mean that privacy is really not needed, or just that LDP =
does not state a requirement for privacy?
>=20
> Further clarified it in this section.
>=20
> Labels are similar to routing information which is distributed in the =
clear. It is important to ensure that routers exchaning labels are =
mutually authenticated and that there are no rogue peers or =
unauthenticated peers that can compromise the stability of the network. =
However, there is currently no requirement that the labels be encrypted.

Okay

>=20
>>=20
>> -- Section 6 (Security Considerations), 4th paragraph:
>>=20
>> If replay protection is required, shouldn't the draft discuss the =
details somewhere? I see only one mention in passing outside of this =
section.
>=20
> I have moved the replay protection requirement to the gap analysis =
section.=20
>=20
> However, this document is a analysis draft, and it is my understanding =
that details on what replay protection methods should be adopted, is =
best left to the routing protocols in question.=20

That's fine, pointing out the gap is sufficient.

>=20
>>=20
>> *** Nits/editorial comments ***:
>>=20
>> -- IDNits indicates some unused and obsoleted references. Please =
check.
>=20
> Found one unused reference and have removed it.

Seems like there were more than one. =46rom IDNits:

  =3D=3D Missing Reference: 'IRR' is mentioned on line 92, but not =
defined

  =3D=3D Unused Reference: 'RFC2409' is defined on line 585, but no =
explicit
     reference was found in the text

  =3D=3D Unused Reference: 'RFC3547' is defined on line 588, but no =
explicit
     reference was found in the text

  ** Obsolete normative reference: RFC 2385 (Obsoleted by RFC 5925)

  -- Obsolete informational reference (is this intentional?): RFC 2409
     (Obsoleted by RFC 4306)

  -- Obsolete informational reference (is this intentional?): RFC 3547
     (Obsoleted by RFC 6407)

[...]
>=20
>>=20
>> -- section 2.1,  5th paragraph:
>>=20
>> A mention of SHA1 seems needed here. Section 2.3.1.2 states the =
concerns about TCP-md5 more clearly.
>=20
> The 6th paragraph states the concern and mentions SHA-1. Did you want =
something more to be included?

No, sorry, on a re-read I think it's okay.

[...]

>>=20
>> -- section 4, 2nd paragraph: "In addition Improving TCP=92s =
Robustness to Blind In-Window Attacks."
>>=20
>> sentence fragment.
>=20
> Changed it to say:
>=20
> In addition, the recommendations in Improving TCP's Robustness to =
Blind In-Window Attacks
>=20

Am I correct in assuming this merges with the following sentence? =
Otherwise, it's still a fragment.

[...]

Thanks!

Ben.=

From gih@apnic.net  Wed Nov 21 21:51:04 2012
Return-Path: <gih@apnic.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2343821F850E; Wed, 21 Nov 2012 21:51:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.559
X-Spam-Level: 
X-Spam-Status: No, score=-98.559 tagged_above=-999 required=5 tests=[AWL=-0.544, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, RCVD_IN_XBL=3.033, RDNS_NONE=0.1, 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 tX53a6AgDUfK; Wed, 21 Nov 2012 21:51:03 -0800 (PST)
Received: from asmtp.apnic.net (asmtp.apnic.net [IPv6:2001:dc0:2001:11::199]) by ietfa.amsl.com (Postfix) with ESMTP id 12B7D21F850D; Wed, 21 Nov 2012 21:51:01 -0800 (PST)
Received: from [192.168.51.200] (unknown [87.213.29.58]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by asmtp.apnic.net (Postfix) with ESMTP id 441B9B68B7; Thu, 22 Nov 2012 15:50:56 +1000 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
From: Geoff Huston <gih@apnic.net>
In-Reply-To: <19339.1353524987@epsilon.noi.kre.to>
Date: Thu, 22 Nov 2012 16:50:40 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <08FCD406-F556-4F7E-BA98-9591D161A3A6@apnic.net>
References: <99B9866C-41D6-4784-AA69-CD25E5910F4B@apnic.net> <20121113144545.12836.71935.idtracker@ietfa.amsl.com> <CAKFn1SF4+k5gWip-WBNfbjt-qAafPbTSY8L_EBLA9Pqvbw4=kQ@mail.gmail.com> <50A66313.9090002@joelhalpern.com> <50A66B67.5000609@gmail.com> <50A67758.8000001@joelhalpern.com> <33C6C196-B881-4BAA-8E57-082B266C831A@steffann.nl> <50A6ADD0.3040000@joelhalpern.com> <45813A84-7BE9-4D21-AE3E-F3401D6E1B50@apnic.net> <19339.1353524987@epsilon.noi.kre.to>
To: Robert Elz <kre@munnari.OZ.AU>
X-Mailer: Apple Mail (2.1499)
Cc: "iesg@ietf.org IESG" <iesg@ietf.org>, "ietf@ietf.org List" <ietf@ietf.org>, lisp@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Nov 2012 05:51:04 -0000

With respect Robert, I disagree with your line of argument and I =
disagree
with your assertion that a reference to an existing RFC is "bogus under=20=

these circumstances"

This eid draft does not claim to obsolete or update either the =
description
of roles and responsibilities in RFC2860 or the directions to the IANA =
in=20
RFC4773, yet the document's directions to the IANA appear to me to be =
inconsistent
with those existing procedures and policies.

To claim, if I understand your line of argument correctly, that every=20
RFC essentially is an implicit update of all existing RFCs, and every=20
RFC does not need to explicitly obsolete or update any other RFC, as=20
it does does so by default upon publication of the RFC is not a line
of argument that I find that I could agree with.

For me, it's like proclaiming that: "everything I do is right, and if=20
whatever I do contravenes existing processes and procedures then my
actions implicitly update those processes and procedures such that
everything I do is right" I find that I cannot agree with such a=20
circular self-referential line of reasoning.

Instead, I believe that the processes and processes that the IETF follow =
are
deliberative decisions, and that we update and amend those processes and
procedures explicitly, and documents that perform such updates say so
explicitly, and are accepted and published on the basis of explicit
consideration of the processes and procedures and acceptance of the
amendment.

But I appreciate that I am by training a mathematician and not a lawyer,
and you may indeed be making some critical observations about the nature
of the IETF's processes and procedures whose finer points may well have
escaped me. However, it seems to me that it would be more productive
for the IETF to consider that this issue is a distinct issue, and not
confound the consideration of the IETF Last Call of this particular
eid draft with the broader issue of the manner  by which the IETF crafts=20=

and maintains its own procedures, processes and policies.

regards,

  Geoff

  speaking for myself and noone else








On 22/11/2012, at 6:09 AM, Robert Elz <kre@munnari.OZ.AU> wrote:

>    Date:        Wed, 21 Nov 2012 17:16:58 +1100
>    From:        Geoff Huston <gih@apnic.net>
>    Message-ID:  <99B9866C-41D6-4784-AA69-CD25E5910F4B@apnic.net>
>=20
> I have no idea whether the allocation requested is reasonable or not,
> I haven't read the draft (and unless it becomes more widely used than
> currently, might never do so), but I do know that this argument ...
>=20
>  | The guidelines for IP address allocations were documented in =
RFC2050,
>  | adopted in November 1996 as a Best Current Practice. ...
>=20
> is totally bogus in these circumstances.
>=20
> The rules in RFCs and BCPs bind ordinary users making ordinary =
requests
> for address space - were I to approach IANA with a request for address
> space to be allocated, a quick denial quoting the relevant RFC would =
indeed
> be the correct response.
>=20
> But when the IETF publishes an updated RFC, that always overrides any
> earlier RFC, and establishes new policy - either for the general case, =
or
> perhaps (as seems to be happening here) just a one off override of the
> normal rules.
>=20
> Doing that is always acceptable, whatever the issue - it is never =
adequate
> to simply refuse to consider such requests upon the basis that they =
don't
> follow the rules and should be done some other way.
>=20
> Now, when the IETF (via the last call consensus mechanism) consider =
whether
> the proposed RFC should be published, it is perfectly reasonable to =
point
> out the existing policy, and ask for reasons why use of that mechanism =
would
> not be adequate - if the proponents cannnot explain why doing it the =
way
> they are suggesting is required, or at least is better than the normal =
way,
> then the request (to publish the RFC, not just to perform whatever =
allocation
> it requested - that just falls out of the failure to publish the RFC) =
should
> be refused.
>=20
> On the other hand, if the proponents can convince the IETF that the
> procedure they're suggesting is the best way to proceed, then that's
> what should happen - and that it isn't being done the way that the
> normal allocation rules would suggest it should be done is 100% =
irrelevant.
>=20
> If you have an argument against the proposal, please make it upon the
> merits of the request, and not based upon some supposed viloation of
> address allocation quidelines.
>=20
> What the result will be I have no idea - I don't know if this =
allocation
> should happen or not.   I might suggest however, that if Noel is =
correct
> about the way this allocation would be used (and Noel usually is =
correct)
> then it may be that an assignment out of the 0::/3 address space =
(which is
> out of the ordinary allocation space for which the guidelines apply)
> sounds like it might be the right thing to do - perhaps something like
> 10f0::/12 (or something near there not currently allocated).
>=20
> kre




From rogerj@gmail.com  Thu Nov 22 01:04:46 2012
Return-Path: <rogerj@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 070B121F868A; Thu, 22 Nov 2012 01:04:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.299
X-Spam-Level: 
X-Spam-Status: No, score=-3.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, 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 CNMFghDC76cv; Thu, 22 Nov 2012 01:04:44 -0800 (PST)
Received: from mail-ie0-f172.google.com (mail-ie0-f172.google.com [209.85.223.172]) by ietfa.amsl.com (Postfix) with ESMTP id C196321F867D; Thu, 22 Nov 2012 01:04:44 -0800 (PST)
Received: by mail-ie0-f172.google.com with SMTP id c13so4559187ieb.31 for <multiple recipients>; Thu, 22 Nov 2012 01:04:44 -0800 (PST)
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 :cc:content-type; bh=7YIuR98Vw24VjMvYpVNv0wnVeVcv+4nPqD/f4LHOemM=; b=xuEaV+pAobBCYGj5FbgGqszRj+b6qZYJWqU95Eom2O9PAgsSc0SAtwKOpSLRruqwvZ 6CoBhZFSlaB7VNiC40OcO4mL23aUnm7AbsPsD+gIHDEwJ7SCSs8XCqICn898GbZnpPZj UwsvXHFxrS5sZRqV5MRXwJqQNqVh4ExMSLFBzYCKApO76myCvEdqKdMDZ6yeblbTjktv Z3IbKGKjOglPsYZjQFV/pCHO5e463KeNnxHgabB5CICgO9wB1mSZPxQQWuHogw9sVGah pB5edLMA8DRfhUIg/9992+HmfuRtoSn89esmKyS5tMPlD4dCsKl5EvWYAyhAn8LM44a3 55jQ==
MIME-Version: 1.0
Received: by 10.50.209.65 with SMTP id mk1mr2558029igc.8.1353575083226; Thu, 22 Nov 2012 01:04:43 -0800 (PST)
Received: by 10.64.138.169 with HTTP; Thu, 22 Nov 2012 01:04:43 -0800 (PST)
In-Reply-To: <A19BAA78-C359-4AB5-8C22-046938B64ACB@gmail.com>
References: <20121121175836.EE11B18C0D3@mercury.lcs.mit.edu> <2671C6CDFBB59E47B64C10B3E0BD592303385FBF7A@PRVPEXVS15.corp.twcable.com> <A19BAA78-C359-4AB5-8C22-046938B64ACB@gmail.com>
Date: Thu, 22 Nov 2012 10:04:43 +0100
Message-ID: <CAKFn1SFz0g2ZmTudPOu4y1hY+u=BXG8awQUbWrwvbRzRxBsZtw@mail.gmail.com>
Subject: Re: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
From: =?ISO-8859-1?Q?Roger_J=F8rgensen?= <rogerj@gmail.com>
To: Dino Farinacci <farinacci@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "lisp@ietf.org" <lisp@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Nov 2012 09:04:46 -0000

On Wed, Nov 21, 2012 at 11:01 PM, Dino Farinacci <farinacci@gmail.com> wrote:
> Make it an allocation for EIDs and ILNP can use it too.

Somehow I hear a voice in the back of my head asking if we're talking
about starting to use another big IPv6 block than 2000::/3 for the two
above mention usage?

2000::/3 for our current model of Internet with our current style of
allocation/assignment of address space to ISP/end users
xxxx::/3 for future modells, LISP/EID, ILNP and others?



-- 

Roger Jorgensen           | ROJO9-RIPE
rogerj@gmail.com          | - IPv6 is The Key!
http://www.jorgensen.no   | roger@jorgensen.no

From brian.e.carpenter@gmail.com  Thu Nov 22 01:44:33 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6023221F88A9; Thu, 22 Nov 2012 01:44:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.429
X-Spam-Level: 
X-Spam-Status: No, score=-101.429 tagged_above=-999 required=5 tests=[AWL=-0.038, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, 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 nJB3NYbQ8xbb; Thu, 22 Nov 2012 01:44:33 -0800 (PST)
Received: from mail-wg0-f44.google.com (mail-wg0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id 7A10621F8735; Thu, 22 Nov 2012 01:44:32 -0800 (PST)
Received: by mail-wg0-f44.google.com with SMTP id dr13so3476306wgb.13 for <multiple recipients>; Thu, 22 Nov 2012 01:44:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=BvsTk82ZB+qKD/OQdl2Llfha8JttLNjNSjxIejs34CM=; b=StG+MrOx4cTDlkAQdnzLXWhW0DWrOS929dnmd/oIGKHXz6xoNzx2wdT5vc2axA+CQp 0Zt5Clv+dJcvS3NoxZ1ghTQowqEyzd74+lLxd8xzZ5VvbxfYkxIsSI8qfd4AwzaNf5pz 7LVcryWTH3fxx2FOD8IXeq9zZBL41fXPy2eG786h9+MGVSJsV721csQxEnl1o+vZ+9bm 89oYuY01ISaCyaDNa+H8MXBojNqiiHPgUWMEdLqK0Sqrievw2UNZYtQxv4ykTnQJxGnO UOfKFep+JsBYIXjb3h2Yzt8X5Ix0c9pDTTeju5g++jsp8++uIuF/XSi29AKhei8/pLkX aJtw==
Received: by 10.216.211.84 with SMTP id v62mr68144weo.158.1353577471087; Thu, 22 Nov 2012 01:44:31 -0800 (PST)
Received: from [192.168.1.65] (host-2-102-218-157.as13285.net. [2.102.218.157]) by mx.google.com with ESMTPS id w5sm3579846wiz.10.2012.11.22.01.44.28 (version=SSLv3 cipher=OTHER); Thu, 22 Nov 2012 01:44:29 -0800 (PST)
Message-ID: <50ADF407.1090300@gmail.com>
Date: Thu, 22 Nov 2012 09:44:39 +0000
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: =?UTF-8?B?Um9nZXIgSsO4cmdlbnNlbg==?= <rogerj@gmail.com>
Subject: Re: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
References: <20121121175836.EE11B18C0D3@mercury.lcs.mit.edu>	<2671C6CDFBB59E47B64C10B3E0BD592303385FBF7A@PRVPEXVS15.corp.twcable.com>	<A19BAA78-C359-4AB5-8C22-046938B64ACB@gmail.com> <CAKFn1SFz0g2ZmTudPOu4y1hY+u=BXG8awQUbWrwvbRzRxBsZtw@mail.gmail.com>
In-Reply-To: <CAKFn1SFz0g2ZmTudPOu4y1hY+u=BXG8awQUbWrwvbRzRxBsZtw@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: "lisp@ietf.org" <lisp@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Nov 2012 09:44:33 -0000

Hi Roger,

On 22/11/2012 09:04, Roger J=C3=B8rgensen wrote:
> On Wed, Nov 21, 2012 at 11:01 PM, Dino Farinacci <farinacci@gmail.com> =
wrote:
>> Make it an allocation for EIDs and ILNP can use it too.
>=20
> Somehow I hear a voice in the back of my head asking if we're talking
> about starting to use another big IPv6 block than 2000::/3 for the two
> above mention usage?
>=20
> 2000::/3 for our current model of Internet with our current style of
> allocation/assignment of address space to ISP/end users
> xxxx::/3 for future modells, LISP/EID, ILNP and others?

I've been relatively relaxed for many years about allocation policy
in 2000::/3, precisely because that leaves most of the total address
space free in case we turn 2000::/3 into a swamp.

I would be a bit nervous about dedicating another /3 for unproven
use. There's a risk of it ending up unusable like Class E. So
if we are going to do this, doing it inside 2000::/3 seems a
bit safer to me.

    Brian


From kre@munnari.OZ.AU  Thu Nov 22 07:28:08 2012
Return-Path: <kre@munnari.OZ.AU>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 68D6321F8973; Thu, 22 Nov 2012 07:28:08 -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 UVD4yslEdKMo; Thu, 22 Nov 2012 07:28:07 -0800 (PST)
Received: from jade.coe.psu.ac.th (unknown [IPv6:2001:3c8:9009:181::2]) by ietfa.amsl.com (Postfix) with ESMTP id E15F921F8972; Thu, 22 Nov 2012 07:28:06 -0800 (PST)
Received: from epsilon.noi.kre.to (jade.coe.psu.AC.TH [IPv6:2001:3c8:9007:1::21]) by jade.coe.psu.ac.th with ESMTP id qAMFRvE9019088; Thu, 22 Nov 2012 22:27:58 +0700 (ICT)
Received: from epsilon.noi.kre.to (localhost [127.0.0.1]) by epsilon.noi.kre.to (8.14.4/8.14.2) with ESMTP id qAMFPWmx017251; Thu, 22 Nov 2012 22:25:32 +0700 (ICT)
From: Robert Elz <kre@munnari.OZ.AU>
To: Geoff Huston <gih@apnic.net>
Subject: Re: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
In-Reply-To: <08FCD406-F556-4F7E-BA98-9591D161A3A6@apnic.net>
References: <08FCD406-F556-4F7E-BA98-9591D161A3A6@apnic.net> <99B9866C-41D6-4784-AA69-CD25E5910F4B@apnic.net> <20121113144545.12836.71935.idtracker@ietfa.amsl.com> <CAKFn1SF4+k5gWip-WBNfbjt-qAafPbTSY8L_EBLA9Pqvbw4=kQ@mail.gmail.com> <50A66313.9090002@joelhalpern.com> <50A66B67.5000609@gmail.com> <50A67758.8000001@joelhalpern.com> <33C6C196-B881-4BAA-8E57-082B266C831A@steffann.nl> <50A6ADD0.3040000@joelhalpern.com> <45813A84-7BE9-4D21-AE3E-F3401D6E1B50@apnic.net> <19339.1353524987@epsilon.noi.kre.to> 
Date: Thu, 22 Nov 2012 22:25:32 +0700
Message-ID: <16573.1353597932@epsilon.noi.kre.to>
Sender: kre@munnari.OZ.AU
Cc: "iesg@ietf.org IESG" <iesg@ietf.org>, "ietf@ietf.org List" <ietf@ietf.org>, lisp@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Nov 2012 15:28:08 -0000

    Date:        Thu, 22 Nov 2012 16:50:40 +1100
    From:        Geoff Huston <gih@apnic.net>
    Message-ID:  <08FCD406-F556-4F7E-BA98-9591D161A3A6@apnic.net>

  | With respect Robert, I disagree with your line of argument and I disagree
  | with your assertion that a reference to an existing RFC is "bogus under 
  | these circumstances"

That's not what I said - what I said was that relying upon an RFC as
disqualifying a new one was bogus - that's never going to be possible,
nor should it be.   Referencing existing RFCs is of course just fine.

  | This eid draft does not claim to obsolete or update either the description
  | of roles and responsibilities in RFC2860 or the directions to the IANA in 
  | RFC4773,

My guess would be that is because it doesn't intend to do either of
those things (still just a guess, I am not arguing the merits or
correctness of that particular draft).   It is entirely reasonable
to leave existing procedures in place, but override them for a specific
case.   If RFC's had an "Ignores" header, then perhaps this one should
say "Ignores: RFC2860 RFC773" (or perhaps Overrides), but there are
no such headers.

  | yet the document's directions to the IANA appear to me to be inconsistent
  | with those existing procedures and policies.

Yes, that is why it is an RFC, and why it should need IETF consensus to
proceed.   If they were just to follow the existing guidelines, they'd
just get address space the normal way.  Clearly the proponents of this
draft don't believe that is adequate, or they wouldn't have gone to all
the trouble of writing a draft and attempting to publish it as an RFC.

Before someone else raises it, one issue might be that this is apparently
just intended as an Informational RFC, yet the others are BCP or PS or
something.  That's kind of unfortunate, but indicates something of a lack
of categories for RFCs - this is clearly not a BCP (its purpose isn't to
sent any policy, or describe how things should be done, aside from for
this one specific case), nor can it be on standards track (it isn't capable
of multiple independent implementations), Informational is all that is
plausible.  Ideally we'd have a separate cagegory so we can divide the
Info docs that are "This is FYI" (that is agreed useful enough to pubish),
from "this is the IETF's consensus about ..."

That is, for this, Info is correct (as things stand) and that doesn't
have any effect upon my opinions.

  | To claim, if I understand your line of argument correctly, that every 
  | RFC essentially is an implicit update of all existing RFCs,

Of course they are, or at least the ones published as the result of
IETF consensus are.  Each of them adjusts the overall view of the
state of the world, and how things are, or should be done, in some
particular area, and necessarily have some impact on all kinds of
previous specifications.   Where there's a major change, we note that
in order to make it easier to keep track of what's happening, but
whether that happens or not, clearly anything we agree is the right
thing to do is an update.

  | For me, it's like proclaiming that: "everything I do is right, and if 
  | whatever I do contravenes existing processes and procedures then my
  | actions implicitly update those processes and procedures such that
  | everything I do is right" I find that I cannot agree with such a 
  | circular self-referential line of reasoning.

There's nothing circular about it.  We could adopt all kinds of bureaucratic
rules, requiring us to explicitly agree to vary the rules of procedure,
before doing anything that is different than has been done before - but
there's really no point.  If we (the community as a whole) have agreed
that X is the right thing to do, then we will do whatever is necessary to be
done to make X happen (since that is what we want the result to be).
Insisting on lots of meaningless make-work just to get to the result that
will happen anyway is pointless, we all have better things to do.

  | But I appreciate that I am by training a mathematician and not a lawyer,

If you attempt to apply rules of mathematics to this kind of process you
are certainly doomed - the two are nothing at all alike.

Just consider if we did have some rule where earlier RFCs (BCPs or
whatever) must always be followed - and then imagine that at some
point we decided that we're happy with the rules as we have them, and
include in a BCP a rule that says that none of this particular set
of RFCs (including itself) may ever be updated or obsoleted.

How would progress ever be made in the future given that combination
of events?   In mathematics it doesn't matter, what is true is true, and
undisputable once proved.  In other fields, circumstances change, and
what was correct yesterday is incorrect today.

There's a simple way out, which is one of the basic tenets of any
organisation like this - and that is that we cannot bind future
instances of ourselves.   Anything we agree to do, following the
correct procedure to get that agreement (which itself can be altered
if that is so agreed), is always correct, and overrides anything
inconistent that existed earlier (to the extent necessary to give
effect to the new agreement).

  | However, it seems to me that it would be more productive
  | for the IETF to consider that this issue is a distinct issue,

I doubt it needs consideration at all, I doubt it is even really the
kind of thing that can be considered - even if we were to explicitly
say that existing rules apply and can't be overridden, that would be
meaningless.   Attempting to believe that we know better than future
generations is one of the best ways to make a mess - they will just
ignore us anyway.

  | and not confound the consideration of the IETF Last Call of this particular
  | eid draft with the broader issue of the manner  by which the IETF crafts 
  | and maintains its own procedures, processes and policies.

That's fine, and in that case, the IESG should ignore your earlier message
as having almost no relevant content.   And of course, my messages have
(beyond this point) no relevance to the consideration of the draft at all.

If you wanted (and if it is appropriate) you could reasonably request that
the authors of the draft explain why the existing procedures are inadequate,
and that the draft should be updated to include that explanation, and
(or course provided that the pposition is correct, and generally accepted)
that would be a push back on publishing this (and assigning the addr block).

Or (or perhaps later) you could argue that the authors reasons aren't
good ones, and that the existing procedures are adequate.

Or you could explain why the whole experiment is useless and a waste
of time, and that allocating address space to it would be senseless.

Or ...

Just not that "we have rules, this ignores them, so dump it" - that
line of argument is bogus.

kre

From farinacci@gmail.com  Thu Nov 22 12:56:20 2012
Return-Path: <farinacci@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 791C121F867A; Thu, 22 Nov 2012 12:56:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.203
X-Spam-Level: 
X-Spam-Status: No, score=-2.203 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, 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 IalP1l0FdW3a; Thu, 22 Nov 2012 12:56:20 -0800 (PST)
Received: from mail-pa0-f44.google.com (mail-pa0-f44.google.com [209.85.220.44]) by ietfa.amsl.com (Postfix) with ESMTP id 0A45521F8675; Thu, 22 Nov 2012 12:56:19 -0800 (PST)
Received: by mail-pa0-f44.google.com with SMTP id hz11so4073648pad.31 for <multiple recipients>; Thu, 22 Nov 2012 12:56:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:x-mailer:from:subject:date :to; bh=UMy02y22gBXU+oJo3bCrgsflQzMQhLikDfm9GPmh1lI=; b=cv64l7druRyo3oraWP0ca3he5nOGvfx6UPktSh96IMc7RVFn/mfGNhwb6diKO5kaYJ fQOEmYC9qmdmtpajVZzaBrxengOetepMMZJxeIoLaIoYShMcS2qt3j98u8e8I3sD9pSi wwat8buGAVWxL4f4kDnfUXT/c53Ls3D8pqpfR/ROUqhF9IeA6C1YoB7DfuN2G07CNZyq ctr9+vSvWVU/d1yvOQlAfybK9+131U0Wq/qZxDjPc9cmG1Ik+evkRc07b3/x3Yw0cb8k AEHNIN5VX7LrhpMroZpLXnyfOAOGQk7MFWdQjJOKPLUWWQgfnKfN9XaS+r2P0+f4LTbf hOjA==
Received: by 10.66.80.194 with SMTP id t2mr4385589pax.43.1353617779760; Thu, 22 Nov 2012 12:56:19 -0800 (PST)
Received: from [192.168.1.214] (adsl-107-198-84-82.dsl.pltn13.sbcglobal.net. [107.198.84.82]) by mx.google.com with ESMTPS id mt15sm2570601pbc.49.2012.11.22.12.56.17 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 22 Nov 2012 12:56:18 -0800 (PST)
References: <20121121175836.EE11B18C0D3@mercury.lcs.mit.edu> <2671C6CDFBB59E47B64C10B3E0BD592303385FBF7A@PRVPEXVS15.corp.twcable.com> <A19BAA78-C359-4AB5-8C22-046938B64ACB@gmail.com> <CAKFn1SFz0g2ZmTudPOu4y1hY+u=BXG8awQUbWrwvbRzRxBsZtw@mail.gmail.com> <50ADF407.1090300@gmail.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <50ADF407.1090300@gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <E7EC87FF-E913-4CC9-9ACC-7A1CB372B830@gmail.com>
X-Mailer: iPhone Mail (10A525)
From: Dino Farinacci <farinacci@gmail.com>
Subject: Re: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
Date: Thu, 22 Nov 2012 12:56:17 -0800
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: "lisp@ietf.org" <lisp@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Nov 2012 20:56:20 -0000

> I would be a bit nervous about dedicating another /3 for unproven
> use. There's a risk of it ending up unusable like Class E. So
> if we are going to do this, doing it inside 2000::/3 seems a
> bit safer to me.

So what if we could say the use is simply to assign addresses out of this bl=
ock that stay relatively permanent to a device that sources packets from thi=
s address.=20

The address has no dependency on the topology the device connects to, the nu=
mber of interfaces the device has  connected to the network, or even if the d=
evice is connected at all to the network.=20

So this proposal doesn't have to be associated with LISP or any other mechan=
ism being used. This block could be used today as simply a PI block if no ne=
w mechanism is deployed.  And if a sub-block of this prefix is used for LISP=
 purposes, then so be it.=20

And I don't think we have to jump in with 2 feet and allocate a very coarse p=
refix for this.=20

Dino=

From narten@us.ibm.com  Thu Nov 22 21:53:16 2012
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE19A21F8CDA for <ietf@ietfa.amsl.com>; Thu, 22 Nov 2012 21:53:16 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SOBXbvPk7zhP for <ietf@ietfa.amsl.com>; Thu, 22 Nov 2012 21:53:15 -0800 (PST)
Received: from e8.ny.us.ibm.com (e8.ny.us.ibm.com [32.97.182.138]) by ietfa.amsl.com (Postfix) with ESMTP id B308521F8C4B for <ietf@ietf.org>; Thu, 22 Nov 2012 21:53:13 -0800 (PST)
Received: from /spool/local by e8.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Fri, 23 Nov 2012 00:53:12 -0500
Received: from d01dlp02.pok.ibm.com (9.56.250.167) by e8.ny.us.ibm.com (192.168.1.108) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Fri, 23 Nov 2012 00:53:09 -0500
Received: from d01relay04.pok.ibm.com (d01relay04.pok.ibm.com [9.56.227.236]) by d01dlp02.pok.ibm.com (Postfix) with ESMTP id EFE1C6E803A for <ietf@ietf.org>; Fri, 23 Nov 2012 00:53:08 -0500 (EST)
Received: from d01av01.pok.ibm.com (d01av01.pok.ibm.com [9.56.224.215]) by d01relay04.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id qAN5r9tn349974 for <ietf@ietf.org>; Fri, 23 Nov 2012 00:53:09 -0500
Received: from d01av01.pok.ibm.com (loopback [127.0.0.1]) by d01av01.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id qAN5r8C7003508 for <ietf@ietf.org>; Fri, 23 Nov 2012 00:53:08 -0500
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.44.115.148]) by d01av01.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id qAN5r80v003503 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Fri, 23 Nov 2012 00:53:08 -0500
Received: from rotala.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.5/8.12.5) with ESMTP id qAN5r7na003199 for <ietf@ietf.org>; Fri, 23 Nov 2012 00:53:07 -0500
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.5/8.14.5/Submit) id qAN5r7e4003175 for ietf@ietf.org; Fri, 23 Nov 2012 00:53:07 -0500
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201211230553.qAN5r7e4003175@rotala.raleigh.ibm.com>
Date: Fri, 23 Nov 2012 00:53:07 -0500
To: ietf@ietf.org
Subject: Weekly posting summary for ietf@ietf.org
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 12112305-9360-0000-0000-00000D168E84
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Nov 2012 05:53:16 -0000

Total of 74 messages in the last 7 days.
 
script run at: Fri Nov 23 00:53:07 EST 2012
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
 16.22% |   12 | 15.79% |    97125 | farinacci@gmail.com
  8.11% |    6 |  5.06% |    31138 | jnc@mercury.lcs.mit.edu
  5.41% |    4 |  4.73% |    29113 | sander@steffann.nl
  4.05% |    3 |  5.26% |    32339 | gih@apnic.net
  4.05% |    3 |  4.52% |    27785 | eric.gray@ericsson.com
  4.05% |    3 |  4.26% |    26220 | wesley.george@twcable.com
  4.05% |    3 |  3.28% |    20191 | brian.e.carpenter@gmail.com
  4.05% |    3 |  3.21% |    19744 | sm@resistor.net
  2.70% |    2 |  3.65% |    22475 | roberta.maglione@telecomitalia.it
  2.70% |    2 |  3.54% |    21765 | ggm+ietf@apnic.net
  2.70% |    2 |  3.25% |    20015 | cb.list6@gmail.com
  2.70% |    2 |  3.19% |    19599 | leaf.yeh.sdo@gmail.com
  2.70% |    2 |  3.14% |    19322 | kre@munnari.oz.au
  2.70% |    2 |  2.98% |    18321 | ynir@checkpoint.com
  2.70% |    2 |  2.55% |    15671 | jmh@joelhalpern.com
  2.70% |    2 |  2.45% |    15068 | mlepinski.ietf@gmail.com
  2.70% |    2 |  2.23% |    13732 | rogerj@gmail.com
  1.35% |    1 |  3.52% |    21664 | heinerhummel@aol.com
  2.70% |    2 |  1.97% |    12129 | pvinci@vinciconsulting.com
  2.70% |    2 |  1.97% |    12103 | aservin@lacnic.net
  1.35% |    1 |  3.14% |    19348 | mjethanandani@gmail.com
  1.35% |    1 |  2.31% |    14186 | jiangsheng@huawei.com
  1.35% |    1 |  1.51% |     9282 | narten@us.ibm.com
  1.35% |    1 |  1.48% |     9075 | jmh.direct@joelhalpern.com
  1.35% |    1 |  1.46% |     8971 | ben@nostrum.com
  1.35% |    1 |  1.40% |     8596 | hallam@gmail.com
  1.35% |    1 |  1.30% |     8005 | carlosm3011@gmail.com
  1.35% |    1 |  1.17% |     7169 | tjc@ecs.soton.ac.uk
  1.35% |    1 |  1.11% |     6813 | rdroms.ietf@gmail.com
  1.35% |    1 |  1.06% |     6519 | iad@ietf.org
  1.35% |    1 |  0.91% |     5590 | suresh.krishnan@ericsson.com
  1.35% |    1 |  0.89% |     5482 | chair@ietf.org
  1.35% |    1 |  0.88% |     5407 | johnl@iecc.com
  1.35% |    1 |  0.85% |     5240 | nomcom-chair@ietf.org
--------+------+--------+----------+------------------------
100.00% |   74 |100.00% |   615202 | Total


From listsebby@me.com  Fri Nov 23 17:46:35 2012
Return-Path: <listsebby@me.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9EA5521F862D for <ietf@ietfa.amsl.com>; Fri, 23 Nov 2012 17:46:35 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Tf9PGsLPNtJ2 for <ietf@ietfa.amsl.com>; Fri, 23 Nov 2012 17:46:35 -0800 (PST)
Received: from nk11p04mm-asmtp008.mac.com (nk11p04mm-asmtp008.mac.com [17.158.236.243]) by ietfa.amsl.com (Postfix) with ESMTP id 806CE21F8613 for <ietf@ietf.org>; Fri, 23 Nov 2012 17:46:35 -0800 (PST)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII
Received: from [192.168.1.5] (natbox.sabahattin-gucukoglu.com [213.123.192.30]) by nk11p04mm-asmtp008.mac.com (Oracle Communications Messaging Server 7u4-24.01(7.0.4.24.0) 64bit (built Jan 3 2012)) with ESMTPSA id <0MDY00LU3Y9LGM20@nk11p04mm-asmtp008.mac.com> for ietf@ietf.org; Sat, 24 Nov 2012 01:46:35 +0000 (GMT)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.9.8185,1.0.431,0.0.0000 definitions=2012-11-23_16:2012-11-23, 2012-11-23, 1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 suspectscore=15 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=6.0.2-1203120001 definitions=main-1211230340
From: Sabahattin Gucukoglu <listsebby@me.com>
Subject: A Splendid Example Of A Renumbering Disaster
Message-id: <54E43A43-A9F3-4803-BAB9-B06F4EB0CB19@me.com>
Date: Sat, 24 Nov 2012 01:46:32 +0000
To: ietf@ietf.org
X-Mailer: Apple Mail (2.1499)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 24 Nov 2012 01:46:35 -0000

It's Friday.  Time to plug IPv6 some more. :-)

http://b.logme.in/2012/11/07/changes-to-hamachi-on-november-19th/

LogMeIn Hamachi is basically a NAT-traversing layer 2 VPN solution.  They avoided conflicts with RFC 1918 space by hijacking IPv4 space in 5/8, now actively being allocated by LIRs in Europe.  When that didn't work (see link above), they moved to 25/8, allocated to the UK MoD.  While I'm almost sure that they haven't got it quite so wrong this time, following the comments says that the idea was not only a very bad one to start with, it's cost a lot of people a lot of grief that IPv6 was clearly going to mitigate in renumbering.  Perhaps it is why they recommend it per default, if not for the number of applications that would be broken by it.

By the way, is this an application that the new shared transition space might benefit?

Cheers,
Sabahattin


From drc@virtualized.org  Fri Nov 23 18:54:37 2012
Return-Path: <drc@virtualized.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 98C3421F8605 for <ietf@ietfa.amsl.com>; Fri, 23 Nov 2012 18:54:37 -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 XgPHm6UIP5P9 for <ietf@ietfa.amsl.com>; Fri, 23 Nov 2012 18:54:37 -0800 (PST)
Received: from trantor.virtualized.org (trantor.virtualized.org [199.48.134.42]) by ietfa.amsl.com (Postfix) with ESMTP id F07FD21F8604 for <ietf@ietf.org>; Fri, 23 Nov 2012 18:54:36 -0800 (PST)
Received: from [10.0.1.2] (c-24-4-109-25.hsd1.ca.comcast.net [24.4.109.25]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: drc) by trantor.virtualized.org (Postfix) with ESMTPSA id 3B64417066; Sat, 24 Nov 2012 02:54:35 +0000 (UTC)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: A Splendid Example Of A Renumbering Disaster
From: David Conrad <drc@virtualized.org>
In-Reply-To: <54E43A43-A9F3-4803-BAB9-B06F4EB0CB19@me.com>
Date: Fri, 23 Nov 2012 18:54:34 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <2ABE8946-A59E-4E15-987C-EC0A45949934@virtualized.org>
References: <54E43A43-A9F3-4803-BAB9-B06F4EB0CB19@me.com>
To: Sabahattin Gucukoglu <listsebby@me.com>
X-Mailer: Apple Mail (2.1499)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 24 Nov 2012 02:54:37 -0000

On Nov 23, 2012, at 5:46 PM, Sabahattin Gucukoglu <listsebby@me.com> =
wrote:
> It's Friday.  Time to plug IPv6 some more. :-)
>=20
> http://b.logme.in/2012/11/07/changes-to-hamachi-on-november-19th/
>=20
> LogMeIn Hamachi is basically a NAT-traversing layer 2 VPN solution.  =
They avoided conflicts with RFC 1918 space by hijacking IPv4 space in =
5/8,

Back when I was running IANA and we noticed this (back in 2006 or so -- =
don't remember the exact dates), we suggested to the folks at Hamachi =
that using squat space was perhaps not the best idea.  They floated the =
idea of a /8 dedicated to VPNs, but it didn't go anywhere (we at IANA =
told them to bring it up with the IETF -- not sure if they ever did). =20=


> now actively being allocated by LIRs in Europe.  When that didn't work =
(see link above), they moved to 25/8, allocated to the UK MoD. =20

Sigh.  You would think that after a number of years they could've come =
up with a better solution than to use different squat space. Given 25/8 =
is 'legacy' space, unencumbered by registration service agreements, I =
suspect folks using Hamachi for v4 VPNs will get another unpleasant =
surprise in the future.

Regards,
-drc


From christopher.morrow@gmail.com  Fri Nov 23 20:24:49 2012
Return-Path: <christopher.morrow@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 50EF221F85C3 for <ietf@ietfa.amsl.com>; Fri, 23 Nov 2012 20:24:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, 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 D4VTfsRJqhwi for <ietf@ietfa.amsl.com>; Fri, 23 Nov 2012 20:24:48 -0800 (PST)
Received: from mail-ea0-f172.google.com (mail-ea0-f172.google.com [209.85.215.172]) by ietfa.amsl.com (Postfix) with ESMTP id 3AE7421F85B3 for <ietf@ietf.org>; Fri, 23 Nov 2012 20:24:48 -0800 (PST)
Received: by mail-ea0-f172.google.com with SMTP id a1so3348105eaa.31 for <ietf@ietf.org>; Fri, 23 Nov 2012 20:24:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=rIeo5ReyoevDVEiHOEJF7WYIB1uk/wkrwGLmzyxEvHw=; b=bNmRDnaiHIc5K/hCrs9cEAfzHJim10nKoN0ADL/109n6+wGCjE0ljzAasiepqa/RcN Hc56ng2/t90UzXownrdk7mpv4AsNbq5O8Lm+WhwGIlv9k8cEMsNjPVtyVo7Ij9FfOlRc P7EdhhiD+ozRLfDYVKu7k5P5ywUKpjRSprasXDI20yBmSvg0FnS3rpr2jI3ksmF72/lx dFIsaQxkwSyAcGmjctCvJZVD57duv3KuErVawYZHqL+0dqAwaIBXqCdY97El36b12WDo f4lDdimqtnAtP2TZKSB8mV10LRAYazrSevTXtZ8+/8d69kdB3Tx5kxAr8+tJNrqfJL4I QGjA==
MIME-Version: 1.0
Received: by 10.14.211.135 with SMTP id w7mr20983789eeo.4.1353731086807; Fri, 23 Nov 2012 20:24:46 -0800 (PST)
Sender: christopher.morrow@gmail.com
Received: by 10.223.96.5 with HTTP; Fri, 23 Nov 2012 20:24:46 -0800 (PST)
In-Reply-To: <2ABE8946-A59E-4E15-987C-EC0A45949934@virtualized.org>
References: <54E43A43-A9F3-4803-BAB9-B06F4EB0CB19@me.com> <2ABE8946-A59E-4E15-987C-EC0A45949934@virtualized.org>
Date: Fri, 23 Nov 2012 23:24:46 -0500
X-Google-Sender-Auth: O94ucYz-GxBNpm-IxLPjCdpzNWY
Message-ID: <CAL9jLaaMAB=AiwPOiskLW7ixFrQBriyPq3NuqKTrapkmfapXVw@mail.gmail.com>
Subject: Re: A Splendid Example Of A Renumbering Disaster
From: Christopher Morrow <morrowc.lists@gmail.com>
To: David Conrad <drc@virtualized.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 24 Nov 2012 04:24:49 -0000

On Fri, Nov 23, 2012 at 9:54 PM, David Conrad <drc@virtualized.org> wrote:

> Sigh.  You would think that after a number of years they could've come up=
 with a better solution than to use different squat space. Given 25/8 is 'l=
egacy' space, unencumbered by registration service agreements, I suspect fo=
lks using Hamachi for v4 VPNs will get another unpleasant surprise in the f=
uture.
>

'doctor! doctor! it hurts when I do this!' - 'Then STOP DOING IT YOU
IDIOT!!' - 'No, it's fun to  hurt!'

you can't help people who don't want help... :(

From brian.e.carpenter@gmail.com  Sat Nov 24 00:08:47 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9DFC221F87FD for <ietf@ietfa.amsl.com>; Sat, 24 Nov 2012 00:08:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.587
X-Spam-Level: 
X-Spam-Status: No, score=-101.587 tagged_above=-999 required=5 tests=[AWL=0.104, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, 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 LGa3N+D34GDP for <ietf@ietfa.amsl.com>; Sat, 24 Nov 2012 00:08:46 -0800 (PST)
Received: from mail-wg0-f44.google.com (mail-wg0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id 71F6021F86D3 for <ietf@ietf.org>; Sat, 24 Nov 2012 00:08:46 -0800 (PST)
Received: by mail-wg0-f44.google.com with SMTP id dr13so723940wgb.13 for <ietf@ietf.org>; Sat, 24 Nov 2012 00:08:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=elWYVJtHo7No/EpLwYa+bo5MdeasXMShyCNnxWrh8pU=; b=TaGbyU08RxZ0e+RD55y0w7OrK1t8HywEDaahnOrGVsgb7/92D/18MYH3OM5h7qdKge SLgUMntcq9e1EFA2iKdp8FV+mJMTorei3nXY8dKjhSmazwiDj6u104How6uV/znaWK01 Z06ltZeepExWR24gCS6PGsdyCegscVvhgQO4S1uXfQmF8UR5J+0gv7vPL4O3ukwA6f/m 6wq7aEM1w3E3Y+Jsfbmhtm3lwPxGcsSKfeTkJRiQIqs0M6/o2NlczJz+hVxkxhqEGzdU rwumT41pken4FajqQxqcrmMuXkcIGUUi6es4Zv5AbzGwE7sDtHH1BRZpeUmBX4xhUuiE xUcQ==
Received: by 10.180.93.3 with SMTP id cq3mr13411955wib.1.1353744525444; Sat, 24 Nov 2012 00:08:45 -0800 (PST)
Received: from [192.168.1.65] (host-2-102-216-61.as13285.net. [2.102.216.61]) by mx.google.com with ESMTPS id az2sm11624377wib.7.2012.11.24.00.08.43 (version=SSLv3 cipher=OTHER); Sat, 24 Nov 2012 00:08:44 -0800 (PST)
Message-ID: <50B08097.1080407@gmail.com>
Date: Sat, 24 Nov 2012 08:08:55 +0000
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: David Conrad <drc@virtualized.org>
Subject: Re: A Splendid Example Of A Renumbering Disaster
References: <54E43A43-A9F3-4803-BAB9-B06F4EB0CB19@me.com> <2ABE8946-A59E-4E15-987C-EC0A45949934@virtualized.org>
In-Reply-To: <2ABE8946-A59E-4E15-987C-EC0A45949934@virtualized.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 24 Nov 2012 08:08:47 -0000

On 24/11/2012 02:54, David Conrad wrote:
> On Nov 23, 2012, at 5:46 PM, Sabahattin Gucukoglu <listsebby@me.com> wr=
ote:
>> It's Friday.  Time to plug IPv6 some more. :-)
>>
>> http://b.logme.in/2012/11/07/changes-to-hamachi-on-november-19th/
>>
>> LogMeIn Hamachi is basically a NAT-traversing layer 2 VPN solution.  T=
hey avoided conflicts with RFC 1918 space by hijacking IPv4 space in 5/8,=

>=20
> Back when I was running IANA and we noticed this (back in 2006 or so --=
 don't remember the exact dates), we suggested to the folks at Hamachi th=
at using squat space was perhaps not the best idea.  They floated the ide=
a of a /8 dedicated to VPNs, but it didn't go anywhere (we at IANA told t=
hem to bring it up with the IETF -- not sure if they ever did). =20
>=20
>> now actively being allocated by LIRs in Europe.  When that didn't work=
 (see link above), they moved to 25/8, allocated to the UK MoD. =20
>=20
> Sigh.  You would think that after a number of years they could've come =
up with a better solution than to use different squat space. Given 25/8 i=
s 'legacy' space, unencumbered by registration service agreements, I susp=
ect folks using Hamachi for v4 VPNs will get another unpleasant surprise =
in the future.

In all fairness, they do say (at the above URL):

"However, our general recommendation is that if you can, please turn off
IPv4 support in your Hamachi clients. The IPv6 space we=E2=80=99re using =
has been
registered to LogMeIn, and most modern software should function perfectly=

without needing an IPv4 address."

so let's give them some credit. (For extra credit, they could make
IPv6 the default in their client software.)

   Brian


From mjethanandani@gmail.com  Sun Nov 25 17:56:46 2012
Return-Path: <mjethanandani@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CEC6D21F869B; Sun, 25 Nov 2012 17:56:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.999
X-Spam-Level: 
X-Spam-Status: No, score=-0.999 tagged_above=-999 required=5 tests=[HTML_MESSAGE=0.001, 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 NyswiWmSVs4S; Sun, 25 Nov 2012 17:56:46 -0800 (PST)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id E043E21F8661; Sun, 25 Nov 2012 17:56:42 -0800 (PST)
Received: by mail-vb0-f44.google.com with SMTP id fc26so3108193vbb.31 for <multiple recipients>; Sun, 25 Nov 2012 17:56:42 -0800 (PST)
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=uawVPv3zf6hdvvSh8dyA8OCbxFSvGJx61e6TmJZ3CLs=; b=D9mcBIKitEFHZVQNhgf38xWQ5vEI1eH40268Jcnq0FUQtZYfTW3JR7uDAFtoFId3ns 6F8clc/psVXjNgmC5/yoBhbFLoEr/Y3AkT10pSZj+N7lKsVWDUsgrGBzM+2rZlTPNUta p1jtOxRRJb8+JPX5AHjScYX9w63KWcmEqEsS0fhO8rE8vTsM7EAG61WRI5cwsunomq5B gOnitbMCLfZOLpBCHjQ8/xLb+GaEJW+F63Vjz4xLx/6m4RY/H/R0I50A06rUhmTqBPwq LgFu204M6OnQs7Lbq6SGWDXPCSPE+T3eVryS6W4G2y0LdvRpPOfTS2MMF+Cq7kNlfX4z Pj3A==
Received: by 10.220.220.7 with SMTP id hw7mr16705849vcb.17.1353895002265; Sun, 25 Nov 2012 17:56:42 -0800 (PST)
Received: from txw-scook-01.ciena.com (c-24-6-180-144.hsd1.ca.comcast.net. [24.6.180.144]) by mx.google.com with ESMTPS id y15sm7549351vdt.9.2012.11.25.17.56.40 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 25 Nov 2012 17:56:41 -0800 (PST)
Subject: Re: Gen-ART LC Review of draft-ietf-karp-routing-tcp-analysis-05.txt
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: multipart/alternative; boundary=Apple-Mail-8--221838846
From: Mahesh Jethanandani <mjethanandani@gmail.com>
In-Reply-To: <3B3FEC40-3D96-4F77-A628-E80DFAEB2278@nostrum.com>
Date: Sun, 25 Nov 2012 17:56:39 -0800
Message-Id: <F60EDDFC-0612-4636-AFC7-3D7FD9052D74@gmail.com>
References: <18E6B18A-D465-47C6-9E06-886DFBFA1F67@nostrum.com> <F53DCC9A-8AA1-42D4-BF19-88ABCCCA68A7@gmail.com> <3B3FEC40-3D96-4F77-A628-E80DFAEB2278@nostrum.com>
To: Ben Campbell <ben@nostrum.com>
X-Mailer: Apple Mail (2.1085)
X-Mailman-Approved-At: Mon, 26 Nov 2012 08:23:30 -0800
Cc: draft-ietf-karp-routing-tcp-analysis.all@tools.ietf.org, "gen-art@ietf.org Review Team" <gen-art@ietf.org>, "ietf@ietf.org List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Nov 2012 01:56:47 -0000

--Apple-Mail-8--221838846
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

Further trimming it to sections that require a response.

On Nov 21, 2012, at 3:12 PM, Ben Campbell wrote:

>=20
>>>=20
>>> *** Minor issues *** :
>>>=20
>>> -- section 2.2, last paragraph:
>>>=20
>>> The IKE mention lacks context. Do you mean to suggest IKE with =
IPSec? I assume so, but there's been no mention of IPSec so far.
>>=20
>> No. It implies the use of IKEv2 protocol for performing mutual =
authentication and establishing SA. There is no suggestion of using IKE =
with IPSec.
>>=20
>> How about this?
>>=20
>> For point-to-point key management IKEv2[RFC5996] protocol provides =
...
>=20
> 5996 describes IKEv2 as a component of IPSec, and a key-management =
mechanism for ESP and AH SAs. Now, I won't claim to be an IKE expert by =
any extent, but I think that if you mean to use IKE _without_ IPSec it =
would be good to add a sentence or two pointing that out. Or is there =
some other reference that could be used that describes using IKEv2 for =
non-IPSec SAs?

Added this sentence.

Although IKEv2 is discussed as a component of IPsec, KMP can use just =
the mutual authentication and SA establishment portion of IKEv2.

>=20
>>=20
>>>=20
>>> *** Nits/editorial comments ***:
>>>=20
>>> -- IDNits indicates some unused and obsoleted references. Please =
check.
>>=20
>> Found one unused reference and have removed it.
>=20
> Seems like there were more than one. =46rom IDNits:
>=20
>  =3D=3D Missing Reference: 'IRR' is mentioned on line 92, but not =
defined
>=20
>  =3D=3D Unused Reference: 'RFC2409' is defined on line 585, but no =
explicit
>     reference was found in the text
>=20
>  =3D=3D Unused Reference: 'RFC3547' is defined on line 588, but no =
explicit
>     reference was found in the text
>=20
>  ** Obsolete normative reference: RFC 2385 (Obsoleted by RFC 5925)
>=20
>  -- Obsolete informational reference (is this intentional?): RFC 2409
>     (Obsoleted by RFC 4306)
>=20
>  -- Obsolete informational reference (is this intentional?): RFC 3547
>     (Obsoleted by RFC 6407)

I have removed these unused references.

>=20
>>>=20
>>> -- section 4, 2nd paragraph: "In addition Improving TCP=92s =
Robustness to Blind In-Window Attacks."
>>>=20
>>> sentence fragment.
>>=20
>> Changed it to say:
>>=20
>> In addition, the recommendations in Improving TCP's Robustness to =
Blind In-Window Attacks
>>=20
>=20
> Am I correct in assuming this merges with the following sentence? =
Otherwise, it's still a fragment.
>=20

Changed it to:

In addition, the recommendations in RFC 5961 should also be followed ...

Mahesh Jethanandani
mjethanandani@gmail.com




--Apple-Mail-8--221838846
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=windows-1252

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
">Further trimming it to sections that require a =
response.<div><br><div><div>On Nov 21, 2012, at 3:12 PM, Ben Campbell =
wrote:</div><br><blockquote type=3D"cite"><div><br><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">*** Minor issues *** =
:<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">-- section 2.2, last =
paragraph:<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">The IKE mention lacks context. =
Do you mean to suggest IKE with IPSec? I assume so, but there's been no =
mention of IPSec so far.<br></blockquote></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">No. It implies =
the use of IKEv2 protocol for performing mutual authentication and =
establishing SA. There is no suggestion of using IKE with =
IPSec.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">How about =
this?<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">For =
point-to-point key management IKEv2[RFC5996] protocol provides =
...<br></blockquote><br>5996 describes IKEv2 as a component of IPSec, =
and a key-management mechanism for ESP and AH SAs. Now, I won't claim to =
be an IKE expert by any extent, but I think that if you mean to use IKE =
_without_ IPSec it would be good to add a sentence or two pointing that =
out. Or is there some other reference that could be used that describes =
using IKEv2 for non-IPSec =
SAs?<br></div></blockquote><div><br></div>Added this =
sentence.</div><div><br></div><div><i>Although IKEv2 is discussed as a =
component of IPsec, KMP can use just the mutual authentication and SA =
establishment portion of IKEv2.</i></div><div><br><blockquote =
type=3D"cite"><div><br><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">*** Nits/editorial comments =
***:<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">-- IDNits indicates some unused =
and obsoleted references. Please =
check.<br></blockquote></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Found one =
unused reference and have removed it.<br></blockquote><br>Seems like =
there were more than one. =46rom IDNits:<br><br> &nbsp;=3D=3D Missing =
Reference: 'IRR' is mentioned on line 92, but not defined<br><br> =
&nbsp;=3D=3D Unused Reference: 'RFC2409' is defined on line 585, but no =
explicit<br> &nbsp;&nbsp;&nbsp;&nbsp;reference was found in the =
text<br><br> &nbsp;=3D=3D Unused Reference: 'RFC3547' is defined on line =
588, but no explicit<br> &nbsp;&nbsp;&nbsp;&nbsp;reference was found in =
the text<br><br> &nbsp;** Obsolete normative reference: RFC 2385 =
(Obsoleted by RFC 5925)<br><br> &nbsp;-- Obsolete informational =
reference (is this intentional?): RFC 2409<br> =
&nbsp;&nbsp;&nbsp;&nbsp;(Obsoleted by RFC 4306)<br><br> &nbsp;-- =
Obsolete informational reference (is this intentional?): RFC 3547<br> =
&nbsp;&nbsp;&nbsp;&nbsp;(Obsoleted by RFC =
6407)<br></div></blockquote><div><br></div>I have removed these unused =
references.</div><div><br><blockquote type=3D"cite"><div><br><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">-- section 4, 2nd paragraph: "In =
addition Improving TCP=92s Robustness to Blind In-Window =
Attacks."<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">sentence =
fragment.<br></blockquote></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Changed it to =
say:<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">In addition, =
the recommendations in Improving TCP's Robustness to Blind In-Window =
Attacks<br></blockquote><blockquote type=3D"cite"><br></blockquote><br>Am =
I correct in assuming this merges with the following sentence? =
Otherwise, it's still a =
fragment.<br><br></div></blockquote><br></div><div>Changed it =
to:</div><div><br></div><div><i>In addition, the recommendations in RFC =
5961 should also be followed ...</i></div><br><div>
<div>Mahesh Jethanandani</div><div><a =
href=3D"mailto:mjethanandani@gmail.com">mjethanandani@gmail.com</a></div><=
div><br></div><br class=3D"Apple-interchange-newline">
</div>
<br></div></body></html>=

--Apple-Mail-8--221838846--

From paul@nohats.ca  Sat Nov 24 08:36:55 2012
Return-Path: <paul@nohats.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8CA0B21F8508 for <ietf@ietfa.amsl.com>; Sat, 24 Nov 2012 08:36:55 -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 H4rCtENjTvzP for <ietf@ietfa.amsl.com>; Sat, 24 Nov 2012 08:36:54 -0800 (PST)
Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) by ietfa.amsl.com (Postfix) with ESMTP id D2A1C21F84CE for <ietf@ietf.org>; Sat, 24 Nov 2012 08:36:54 -0800 (PST)
Received: by bofh.nohats.ca (Postfix, from userid 500) id 8C930804F3; Sat, 24 Nov 2012 11:36:07 -0500 (EST)
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id 813A1804EE; Sat, 24 Nov 2012 11:36:07 -0500 (EST)
Date: Sat, 24 Nov 2012 11:36:07 -0500 (EST)
From: Paul Wouters <paul@nohats.ca>
To: Sabahattin Gucukoglu <listsebby@me.com>
Subject: Re: A Splendid Example Of A Renumbering Disaster
In-Reply-To: <54E43A43-A9F3-4803-BAB9-B06F4EB0CB19@me.com>
Message-ID: <alpine.LFD.2.02.1211241129320.2810@bofh.nohats.ca>
References: <54E43A43-A9F3-4803-BAB9-B06F4EB0CB19@me.com>
User-Agent: Alpine 2.02 (LFD 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Mailman-Approved-At: Mon, 26 Nov 2012 08:23:54 -0800
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 24 Nov 2012 16:36:55 -0000

On Sat, 24 Nov 2012, Sabahattin Gucukoglu wrote:

> http://b.logme.in/2012/11/07/changes-to-hamachi-on-november-19th/
>
> LogMeIn Hamachi is basically a NAT-traversing layer 2 VPN solution.  They avoided conflicts with RFC 1918 space by hijacking IPv4 space in 5/8, now actively being allocated by LIRs in Europe.  When that didn't work (see link above), they moved to 25/8, allocated to the UK MoD.  While I'm almost sure that they haven't got it quite so wrong this time, following the comments says that the idea was not only a very bad one to start with, it's cost a lot of people a lot of grief that IPv6 was clearly going to mitigate in renumbering.  Perhaps it is why they recommend it per default, if not for the number of applications that would be broken by it.

Both TMobile in the US, and Rogers/Fido in Canada use 25/8. Our IPsec
client per default only allows incoming NAT-T for ranges in RFC1918, due
to security reasons (you don't want them hijacking google's ip range). So
we actually had to add 25/8 to the white list a few years ago.

But, it would be nice to have an IPv4 range dedicated to VPN ranges, so
you can setup things like L2TP tunnels without fear of collision in the
RFC1918 space, although I guess technology has advanced enough to
implement proper segmentation and workarounds for this these days.

Paul

From agmalis@gmail.com  Mon Nov 26 08:52:28 2012
Return-Path: <agmalis@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 59FDF21F86C2 for <ietf@ietfa.amsl.com>; Mon, 26 Nov 2012 08:52:28 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4MKonaFjnRBA for <ietf@ietfa.amsl.com>; Mon, 26 Nov 2012 08:52:27 -0800 (PST)
Received: from mail-ia0-f172.google.com (mail-ia0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 5372921F843E for <ietf@ietf.org>; Mon, 26 Nov 2012 08:52:27 -0800 (PST)
Received: by mail-ia0-f172.google.com with SMTP id j26so8906613iaf.31 for <ietf@ietf.org>; Mon, 26 Nov 2012 08:52:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=AmYqtT0ct0FNZfXBJAohIJGY3q/a9I4k9YkAU35aFLU=; b=IJ4MqE1M7aAIIue5rq4OeejlCBvgzl65MEr7KBFros4vkkV1Dm1hy+QKdBIqBE5/kb kK6NVYF3ykziUgk7zFgVjjNGz7U9SGZFMIH7nLTjtXPp1n56t/EQ8ZX0PeTywHfscrqT Pif15vz5Bldka09EtPn7F6N+Y2U5P+P3DGdAgPCA7JKSmb7ZKfiXxLJNyOQm4Guxx7eM mqGCZUJOKolNASaina1AkaQEO5gPYeg9kE5Z/aM+j4hcMzUzn9m+K38d8d0lndtz+H8H DPWMmdekWOWimpNfoQ2cg1jve6EpEXDgIM4YqcYqnJHjHhkGr4S3Y0FBE34UIt1v7MeF NUow==
Received: by 10.50.151.238 with SMTP id ut14mr11993384igb.58.1353948746861; Mon, 26 Nov 2012 08:52:26 -0800 (PST)
MIME-Version: 1.0
Received: by 10.64.35.195 with HTTP; Mon, 26 Nov 2012 08:52:06 -0800 (PST)
In-Reply-To: <alpine.LFD.2.02.1211241129320.2810@bofh.nohats.ca>
References: <54E43A43-A9F3-4803-BAB9-B06F4EB0CB19@me.com> <alpine.LFD.2.02.1211241129320.2810@bofh.nohats.ca>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Mon, 26 Nov 2012 11:52:06 -0500
Message-ID: <CAA=duU3cuFPhii9d4Gab74N_cxzPALZP0K1ENVsyfrj7P+2AdA@mail.gmail.com>
Subject: Re: A Splendid Example Of A Renumbering Disaster
To: Paul Wouters <paul@nohats.ca>
Content-Type: multipart/alternative; boundary=e89a8f3b9f7d19cd2104cf68c21f
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Nov 2012 16:52:28 -0000

--e89a8f3b9f7d19cd2104cf68c21f
Content-Type: text/plain; charset=ISO-8859-1

As LogMein says, even with the TMobile and Rogers use, it's extremely
unlikely that their customers will need to communicate with any hosts in
25/8. That said, I absolutely agree that an IPv4 range devoted to VPNs
would be great. I run a personal VPN to my home LAN, and I specifically use
different ranges of RFC 1918 space for the addresses in my home and my VPN.

Cheers,
Andy



On Sat, Nov 24, 2012 at 11:36 AM, Paul Wouters <paul@nohats.ca> wrote:

> On Sat, 24 Nov 2012, Sabahattin Gucukoglu wrote:
>
>  http://b.logme.in/2012/11/07/**changes-to-hamachi-on-**november-19th/<http://b.logme.in/2012/11/07/changes-to-hamachi-on-november-19th/>
>>
>> LogMeIn Hamachi is basically a NAT-traversing layer 2 VPN solution.  They
>> avoided conflicts with RFC 1918 space by hijacking IPv4 space in 5/8, now
>> actively being allocated by LIRs in Europe.  When that didn't work (see
>> link above), they moved to 25/8, allocated to the UK MoD.  While I'm almost
>> sure that they haven't got it quite so wrong this time, following the
>> comments says that the idea was not only a very bad one to start with, it's
>> cost a lot of people a lot of grief that IPv6 was clearly going to mitigate
>> in renumbering.  Perhaps it is why they recommend it per default, if not
>> for the number of applications that would be broken by it.
>>
>
> Both TMobile in the US, and Rogers/Fido in Canada use 25/8. Our IPsec
> client per default only allows incoming NAT-T for ranges in RFC1918, due
> to security reasons (you don't want them hijacking google's ip range). So
> we actually had to add 25/8 to the white list a few years ago.
>
> But, it would be nice to have an IPv4 range dedicated to VPN ranges, so
> you can setup things like L2TP tunnels without fear of collision in the
> RFC1918 space, although I guess technology has advanced enough to
> implement proper segmentation and workarounds for this these days.
>
> Paul
>

--e89a8f3b9f7d19cd2104cf68c21f
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

As LogMein says, even with the TMobile and Rogers use, it&#39;s extremely u=
nlikely that their customers will need to communicate with any hosts in 25/=
8. That said, I absolutely agree that an IPv4 range devoted to VPNs would b=
e great. I run a personal VPN to my home LAN, and I specifically use differ=
ent ranges of RFC 1918 space for the addresses in my home and my VPN.<br>

<br>Cheers,<br>Andy<br><br><div class=3D"gmail_extra"><br><br><div class=3D=
"gmail_quote">On Sat, Nov 24, 2012 at 11:36 AM, Paul Wouters <span dir=3D"l=
tr">&lt;<a href=3D"mailto:paul@nohats.ca" target=3D"_blank">paul@nohats.ca<=
/a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im">On Sat, 24 Nov 2012, Sabah=
attin Gucukoglu wrote:<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<a href=3D"http://b.logme.in/2012/11/07/changes-to-hamachi-on-november-19th=
/" target=3D"_blank">http://b.logme.in/2012/11/07/<u></u>changes-to-hamachi=
-on-<u></u>november-19th/</a><br>
<br>
LogMeIn Hamachi is basically a NAT-traversing layer 2 VPN solution. =A0They=
 avoided conflicts with RFC 1918 space by hijacking IPv4 space in 5/8, now =
actively being allocated by LIRs in Europe. =A0When that didn&#39;t work (s=
ee link above), they moved to 25/8, allocated to the UK MoD. =A0While I&#39=
;m almost sure that they haven&#39;t got it quite so wrong this time, follo=
wing the comments says that the idea was not only a very bad one to start w=
ith, it&#39;s cost a lot of people a lot of grief that IPv6 was clearly goi=
ng to mitigate in renumbering. =A0Perhaps it is why they recommend it per d=
efault, if not for the number of applications that would be broken by it.<b=
r>


</blockquote>
<br></div>
Both TMobile in the US, and Rogers/Fido in Canada use 25/8. Our IPsec<br>
client per default only allows incoming NAT-T for ranges in RFC1918, due<br=
>
to security reasons (you don&#39;t want them hijacking google&#39;s ip rang=
e). So<br>
we actually had to add 25/8 to the white list a few years ago.<br>
<br>
But, it would be nice to have an IPv4 range dedicated to VPN ranges, so<br>
you can setup things like L2TP tunnels without fear of collision in the<br>
RFC1918 space, although I guess technology has advanced enough to<br>
implement proper segmentation and workarounds for this these days.<span cla=
ss=3D"HOEnZb"><font color=3D"#888888"><br>
<br>
Paul<br>
</font></span></blockquote></div><br></div>

--e89a8f3b9f7d19cd2104cf68c21f--

From bensons@queuefull.net  Mon Nov 26 09:12:46 2012
Return-Path: <bensons@queuefull.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B4E9821F84E1 for <ietf@ietfa.amsl.com>; Mon, 26 Nov 2012 09:12:46 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rUmPLcZFXdqt for <ietf@ietfa.amsl.com>; Mon, 26 Nov 2012 09:12:45 -0800 (PST)
Received: from mail-qa0-f44.google.com (mail-qa0-f44.google.com [209.85.216.44]) by ietfa.amsl.com (Postfix) with ESMTP id 7AAFC21F870B for <ietf@ietf.org>; Mon, 26 Nov 2012 09:12:45 -0800 (PST)
Received: by mail-qa0-f44.google.com with SMTP id c4so3033062qae.10 for <ietf@ietf.org>; Mon, 26 Nov 2012 09:12:44 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:x-gm-message-state; bh=/TqGzWbnNm0TzrM7OZ7HOtArcODgYXIP65eqDG5cVIQ=; b=pWrtOk2KXVCtCdvZyzKUTfSLQyE+VMjG877w12Cp/X0C7FRkVO+tfO8iCqFG7RPtNj 1Gk/xB7U0F8GqltVwCWeI+F5w3FQ0aMxzaV77GYsNn+26BWxCQmma8c1h+ukuBlENMpJ +UkPD5DzJW8Mq6V9jR3X34BhCxKGHmNX86/zuYbnRadSYNjggsS7gt1ChRxTa/E7qXnj B00kZhLZYQzIVmxNrjXMYrcvVqpQEsTKgZnl3KEAhnRT1vzk/EUP1gNSN4k713h0Ifop 06v4XSMrDnh8X3tDYoN24saBp3z6HpsgOjQHv4UjmSa591BLpAMbJScaag8zUhu/ymFX 5GCA==
Received: by 10.49.13.202 with SMTP id j10mr14380360qec.27.1353949964511; Mon, 26 Nov 2012 09:12:44 -0800 (PST)
Received: from wasteland.local (westford-nat.juniper.net. [66.129.232.2]) by mx.google.com with ESMTPS id gg3sm7856105qeb.5.2012.11.26.09.12.43 (version=SSLv3 cipher=OTHER); Mon, 26 Nov 2012 09:12:44 -0800 (PST)
Message-ID: <50B3A30A.3000201@queuefull.net>
Date: Mon, 26 Nov 2012 12:12:42 -0500
From: Benson Schliesser <bensons@queuefull.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: "Andrew G. Malis" <agmalis@gmail.com>
Subject: Re: A Splendid Example Of A Renumbering Disaster
References: <54E43A43-A9F3-4803-BAB9-B06F4EB0CB19@me.com> <alpine.LFD.2.02.1211241129320.2810@bofh.nohats.ca> <CAA=duU3cuFPhii9d4Gab74N_cxzPALZP0K1ENVsyfrj7P+2AdA@mail.gmail.com>
In-Reply-To: <CAA=duU3cuFPhii9d4Gab74N_cxzPALZP0K1ENVsyfrj7P+2AdA@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------060708000009070509060200"
X-Gm-Message-State: ALoCoQmRKiDvkYuquF6PCIwv6wM2V+R/1gowYNBwPthFmC+XTjkY32aLfyxoG1dBKzQfqIAXluPF
Cc: Paul Wouters <paul@nohats.ca>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Nov 2012 17:12:46 -0000

This is a multi-part message in MIME format.
--------------060708000009070509060200
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

I expect to be flamed for suggesting it, but why not use the Shared 
Address Space for this purpose? (http://tools.ietf.org/html/rfc6598)

Cheers,
-Benson


On 11/26/12 11:52 AM, Andrew G. Malis wrote:
> As LogMein says, even with the TMobile and Rogers use, it's extremely 
> unlikely that their customers will need to communicate with any hosts 
> in 25/8. That said, I absolutely agree that an IPv4 range devoted to 
> VPNs would be great. I run a personal VPN to my home LAN, and I 
> specifically use different ranges of RFC 1918 space for the addresses 
> in my home and my VPN.
>
> Cheers,
> Andy
>
>
>
> On Sat, Nov 24, 2012 at 11:36 AM, Paul Wouters <paul@nohats.ca 
> <mailto:paul@nohats.ca>> wrote:
>
>     On Sat, 24 Nov 2012, Sabahattin Gucukoglu wrote:
>
>         http://b.logme.in/2012/11/07/changes-to-hamachi-on-november-19th/
>
>         LogMeIn Hamachi is basically a NAT-traversing layer 2 VPN
>         solution.  They avoided conflicts with RFC 1918 space by
>         hijacking IPv4 space in 5/8, now actively being allocated by
>         LIRs in Europe.  When that didn't work (see link above), they
>         moved to 25/8, allocated to the UK MoD.  While I'm almost sure
>         that they haven't got it quite so wrong this time, following
>         the comments says that the idea was not only a very bad one to
>         start with, it's cost a lot of people a lot of grief that IPv6
>         was clearly going to mitigate in renumbering.  Perhaps it is
>         why they recommend it per default, if not for the number of
>         applications that would be broken by it.
>
>
>     Both TMobile in the US, and Rogers/Fido in Canada use 25/8. Our IPsec
>     client per default only allows incoming NAT-T for ranges in
>     RFC1918, due
>     to security reasons (you don't want them hijacking google's ip
>     range). So
>     we actually had to add 25/8 to the white list a few years ago.
>
>     But, it would be nice to have an IPv4 range dedicated to VPN
>     ranges, so
>     you can setup things like L2TP tunnels without fear of collision
>     in the
>     RFC1918 space, although I guess technology has advanced enough to
>     implement proper segmentation and workarounds for this these days.
>
>     Paul
>
>


--------------060708000009070509060200
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">I expect to be flamed for suggesting
      it, but why not use the Shared Address Space for this purpose?
      (<a class="moz-txt-link-freetext" href="http://tools.ietf.org/html/rfc6598">http://tools.ietf.org/html/rfc6598</a>)<br>
      <br>
      Cheers,<br>
      -Benson<br>
      <br>
      <br>
      On 11/26/12 11:52 AM, Andrew G. Malis wrote:<br>
    </div>
    <blockquote
cite="mid:CAA=duU3cuFPhii9d4Gab74N_cxzPALZP0K1ENVsyfrj7P+2AdA@mail.gmail.com"
      type="cite">As LogMein says, even with the TMobile and Rogers use,
      it's extremely unlikely that their customers will need to
      communicate with any hosts in 25/8. That said, I absolutely agree
      that an IPv4 range devoted to VPNs would be great. I run a
      personal VPN to my home LAN, and I specifically use different
      ranges of RFC 1918 space for the addresses in my home and my VPN.<br>
      <br>
      Cheers,<br>
      Andy<br>
      <br>
      <div class="gmail_extra"><br>
        <br>
        <div class="gmail_quote">On Sat, Nov 24, 2012 at 11:36 AM, Paul
          Wouters <span dir="ltr">&lt;<a moz-do-not-send="true"
              href="mailto:paul@nohats.ca" target="_blank">paul@nohats.ca</a>&gt;</span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <div class="im">On Sat, 24 Nov 2012, Sabahattin Gucukoglu
              wrote:<br>
              <br>
              <blockquote class="gmail_quote" style="margin:0 0 0
                .8ex;border-left:1px #ccc solid;padding-left:1ex">
                <a moz-do-not-send="true"
                  href="http://b.logme.in/2012/11/07/changes-to-hamachi-on-november-19th/"
                  target="_blank">http://b.logme.in/2012/11/07/changes-to-hamachi-on-november-19th/</a><br>
                <br>
                LogMeIn Hamachi is basically a NAT-traversing layer 2
                VPN solution. &nbsp;They avoided conflicts with RFC 1918
                space by hijacking IPv4 space in 5/8, now actively being
                allocated by LIRs in Europe. &nbsp;When that didn't work (see
                link above), they moved to 25/8, allocated to the UK
                MoD. &nbsp;While I'm almost sure that they haven't got it
                quite so wrong this time, following the comments says
                that the idea was not only a very bad one to start with,
                it's cost a lot of people a lot of grief that IPv6 was
                clearly going to mitigate in renumbering. &nbsp;Perhaps it is
                why they recommend it per default, if not for the number
                of applications that would be broken by it.<br>
              </blockquote>
              <br>
            </div>
            Both TMobile in the US, and Rogers/Fido in Canada use 25/8.
            Our IPsec<br>
            client per default only allows incoming NAT-T for ranges in
            RFC1918, due<br>
            to security reasons (you don't want them hijacking google's
            ip range). So<br>
            we actually had to add 25/8 to the white list a few years
            ago.<br>
            <br>
            But, it would be nice to have an IPv4 range dedicated to VPN
            ranges, so<br>
            you can setup things like L2TP tunnels without fear of
            collision in the<br>
            RFC1918 space, although I guess technology has advanced
            enough to<br>
            implement proper segmentation and workarounds for this these
            days.<span class="HOEnZb"><font color="#888888"><br>
                <br>
                Paul<br>
              </font></span></blockquote>
        </div>
        <br>
      </div>
    </blockquote>
    <br>
  </body>
</html>

--------------060708000009070509060200--

From presnick@qti.qualcomm.com  Mon Nov 26 12:41:50 2012
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C501121F8527 for <ietf@ietfa.amsl.com>; Mon, 26 Nov 2012 12:41:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.449
X-Spam-Level: 
X-Spam-Status: No, score=-102.449 tagged_above=-999 required=5 tests=[AWL=0.150, 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 9yPYyq2+WBCc for <ietf@ietfa.amsl.com>; Mon, 26 Nov 2012 12:41:48 -0800 (PST)
Received: from sabertooth01.qualcomm.com (sabertooth01.qualcomm.com [65.197.215.72]) by ietfa.amsl.com (Postfix) with ESMTP id 634B321F851C for <ietf@ietf.org>; Mon, 26 Nov 2012 12:41:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1353961557; x=1385497557; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=q5hRA2QlKLYstwmBOvxhXiJqQYdlnmC3Mqk57sXsEio=; b=gtdkoTrYjX2kGbsxDc1pPGa91sJvbVadjRAR03fDRqVlVdQyryT7NQSb AGAZVxtk18yag/ZqTbJtPWkViLaaCjY1y8FOnbPPK1xnPiv5wX9K0Ji/X 7+Cc5t+W1O5saqdiEPewvq9REpfDmBeGNk0TuNOozXAa5zNmED+jbMWWp E=;
X-IronPort-AV: E=McAfee;i="5400,1158,6908"; a="9101172"
Received: from ironmsg02-lv.qualcomm.com ([10.47.202.183]) by sabertooth01.qualcomm.com with ESMTP; 26 Nov 2012 12:25:57 -0800
X-IronPort-AV: E=McAfee;i="5400,1158,6908"; a="2472926"
Received: from nasanexhc04.na.qualcomm.com ([172.30.48.17]) by ironmsg02-lv.qualcomm.com with ESMTP/TLS/RC4-SHA; 26 Nov 2012 12:41:39 -0800
Received: from presnick-mac.local (172.30.48.1) by qcmail1.qualcomm.com (172.30.48.17) with Microsoft SMTP Server (TLS) id 14.2.318.4; Mon, 26 Nov 2012 12:41:40 -0800
Message-ID: <50B3D402.7070502@qti.qualcomm.com>
Date: Mon, 26 Nov 2012 14:41:38 -0600
From: Pete Resnick <presnick@qti.qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: Sabahattin Gucukoglu <listsebby@me.com>
Subject: Re: A Splendid Example Of A Renumbering Disaster
References: <54E43A43-A9F3-4803-BAB9-B06F4EB0CB19@me.com>
In-Reply-To: <54E43A43-A9F3-4803-BAB9-B06F4EB0CB19@me.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.48.1]
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Nov 2012 20:41:50 -0000

On 11/23/12 7:46 PM, Sabahattin Gucukoglu wrote:
> It's Friday.  Time to plug IPv6 some more. :-)
>
> http://b.logme.in/2012/11/07/changes-to-hamachi-on-november-19th/
>
> LogMeIn Hamachi is basically a NAT-traversing layer 2 VPN solution.  They avoided conflicts with RFC 1918 space by hijacking IPv4 space in 5/8, now actively being allocated by LIRs in Europe.  When that didn't work (see link above), they moved to 25/8, allocated to the UK MoD.  While I'm almost sure that they haven't got it quite so wrong this time, following the comments says that the idea was not only a very bad one to start with, it's cost a lot of people a lot of grief that IPv6 was clearly going to mitigate in renumbering.  Perhaps it is why they recommend it per default, if not for the number of applications that would be broken by it.
>
> By the way, is this an application that the new shared transition space might benefit?
>    

Yes, like Benson, I am at a loss for why they do not use RFC 6598 
addresses. That's what someone should tell these goofballs to do.

pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478


From cb.list6@gmail.com  Mon Nov 26 12:56:46 2012
Return-Path: <cb.list6@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8FEE221F86F9 for <ietf@ietfa.amsl.com>; Mon, 26 Nov 2012 12:56:46 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Pmkjo+ANFUEr for <ietf@ietfa.amsl.com>; Mon, 26 Nov 2012 12:56:46 -0800 (PST)
Received: from mail-we0-f172.google.com (mail-we0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id B0D6321F86F8 for <ietf@ietf.org>; Mon, 26 Nov 2012 12:56:45 -0800 (PST)
Received: by mail-we0-f172.google.com with SMTP id r3so3354939wey.31 for <ietf@ietf.org>; Mon, 26 Nov 2012 12:56:44 -0800 (PST)
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 :cc:content-type; bh=F+VIpv1ewiumlttnmcjSVYCSZVNzXhVH8wOggVeIOr8=; b=bR2ard+N9bmyurHsvFrBDCGSSihjM+szcYe2F6I2ei0ch7wbu4rR1QYaua5SSpaWjf jxaUK4ea+mQoaZAW0+/MJFub5/OELrHjO6LIE5umy7rkJ0r4yw7ZvMorh1jHSMOT9rQI QCKCJVXP5QBw/Wq4ZUTn2VSN9I6q4DEo6wgMEpCDofXeTlDhap30RUZSFfQs435m0kwC ZeTGJWcFHBGXn323q35ILzx4NvX3YtjcHzBjlWdYtFsTrbgK2mjE1eq4W3bJtmb5zqv1 0SZHcPF83WrWEfxkrVizAld/nEEf2sE4P5kuBgJjYcF1oGBa8B/OszMZ/BoPPSikJ8Mj YpWQ==
MIME-Version: 1.0
Received: by 10.216.140.73 with SMTP id d51mr5194882wej.222.1353963404718; Mon, 26 Nov 2012 12:56:44 -0800 (PST)
Received: by 10.194.41.100 with HTTP; Mon, 26 Nov 2012 12:56:44 -0800 (PST)
In-Reply-To: <50B3D402.7070502@qti.qualcomm.com>
References: <54E43A43-A9F3-4803-BAB9-B06F4EB0CB19@me.com> <50B3D402.7070502@qti.qualcomm.com>
Date: Mon, 26 Nov 2012 12:56:44 -0800
Message-ID: <CAD6AjGS9VSkffmLU1yD65VpaM_OZi8me6cPWwJtjJnLYQbF4CA@mail.gmail.com>
Subject: Re: A Splendid Example Of A Renumbering Disaster
From: Cameron Byrne <cb.list6@gmail.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Nov 2012 20:56:46 -0000

On Mon, Nov 26, 2012 at 12:41 PM, Pete Resnick
<presnick@qti.qualcomm.com> wrote:
> On 11/23/12 7:46 PM, Sabahattin Gucukoglu wrote:
>>
>> It's Friday.  Time to plug IPv6 some more. :-)
>>
>> http://b.logme.in/2012/11/07/changes-to-hamachi-on-november-19th/
>>
>> LogMeIn Hamachi is basically a NAT-traversing layer 2 VPN solution.  They
>> avoided conflicts with RFC 1918 space by hijacking IPv4 space in 5/8, now
>> actively being allocated by LIRs in Europe.  When that didn't work (see link
>> above), they moved to 25/8, allocated to the UK MoD.  While I'm almost sure
>> that they haven't got it quite so wrong this time, following the comments
>> says that the idea was not only a very bad one to start with, it's cost a
>> lot of people a lot of grief that IPv6 was clearly going to mitigate in
>> renumbering.  Perhaps it is why they recommend it per default, if not for
>> the number of applications that would be broken by it.
>>
>> By the way, is this an application that the new shared transition space
>> might benefit?
>>
>
>
> Yes, like Benson, I am at a loss for why they do not use RFC 6598 addresses.
> That's what someone should tell these goofballs to do.
>

Unfortunately, RFC1918 and RFC 6598 are not enough to number all that
needs numbers.

Lots of love,

Goofball

> pr
>
> --
> Pete Resnick<http://www.qualcomm.com/~presnick/>
> Qualcomm Technologies, Inc. - +1 (858)651-4478
>

From presnick@qti.qualcomm.com  Mon Nov 26 13:27:05 2012
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 78D9C21F84FE for <ietf@ietfa.amsl.com>; Mon, 26 Nov 2012 13:27:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.499
X-Spam-Level: 
X-Spam-Status: No, score=-102.499 tagged_above=-999 required=5 tests=[AWL=0.100, 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 KQ+favnUavww for <ietf@ietfa.amsl.com>; Mon, 26 Nov 2012 13:27:04 -0800 (PST)
Received: from sabertooth02.qualcomm.com (sabertooth02.qualcomm.com [65.197.215.38]) by ietfa.amsl.com (Postfix) with ESMTP id CF72E21F84EB for <ietf@ietf.org>; Mon, 26 Nov 2012 13:27:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1353963701; x=1385499701; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=Lp+OxWi3kFTglOEVR3eLSL8XHZTk1xEv1vJB1AU5a5o=; b=S6x0m1RvA75AgTumoChG2CEQ1B+iof57Qg6QBwoyv+5qC5ruxn30K93m uHWsMpYalQEM8cdFMenOSc1Y8BZqamEy4eKGs/7QbmIMQv0ZmFmLOYmbz RuzyTEWpAoTrJyAuy6BxCVFdS6k6eszE9uMopQJ0sbUgQii1Zbo+3lwcd w=;
X-IronPort-AV: E=McAfee;i="5400,1158,6908"; a="9103914"
Received: from ironmsg04-l.qualcomm.com ([172.30.48.19]) by sabertooth02.qualcomm.com with ESMTP; 26 Nov 2012 13:01:40 -0800
X-IronPort-AV: E=McAfee;i="5400,1158,6908"; a="347068837"
Received: from nasanexhc04.na.qualcomm.com ([172.30.48.17]) by Ironmsg04-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 26 Nov 2012 13:27:03 -0800
Received: from presnick-mac.local (172.30.48.1) by qcmail1.qualcomm.com (172.30.48.17) with Microsoft SMTP Server (TLS) id 14.2.318.4; Mon, 26 Nov 2012 13:27:03 -0800
Message-ID: <50B3DEA6.2070502@qti.qualcomm.com>
Date: Mon, 26 Nov 2012 15:27:02 -0600
From: Pete Resnick <presnick@qti.qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: Cameron Byrne <cb.list6@gmail.com>
Subject: Re: A Splendid Example Of A Renumbering Disaster
References: <54E43A43-A9F3-4803-BAB9-B06F4EB0CB19@me.com>	<50B3D402.7070502@qti.qualcomm.com> <CAD6AjGS9VSkffmLU1yD65VpaM_OZi8me6cPWwJtjJnLYQbF4CA@mail.gmail.com>
In-Reply-To: <CAD6AjGS9VSkffmLU1yD65VpaM_OZi8me6cPWwJtjJnLYQbF4CA@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.48.1]
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Nov 2012 21:27:05 -0000

On 11/26/12 2:56 PM, Cameron Byrne wrote:
> On Mon, Nov 26, 2012 at 12:41 PM, Pete Resnick
> <presnick@qti.qualcomm.com>  wrote:
>    
>> On 11/23/12 7:46 PM, Sabahattin Gucukoglu wrote:
>>      
>>> http://b.logme.in/2012/11/07/changes-to-hamachi-on-november-19th/
>>>
>>> LogMeIn Hamachi is basically a NAT-traversing layer 2 VPN solution.  They
>>> avoided conflicts with RFC 1918 space by hijacking IPv4 space in 5/8, now
>>> actively being allocated by LIRs in Europe.  When that didn't work (see link
>>> above), they moved to 25/8, allocated to the UK MoD. [...]
>>>
>>> By the way, is this an application that the new shared transition space
>>> might benefit?
>>>        
>>
>> Yes, like Benson, I am at a loss for why they do not use RFC 6598 addresses.
>> That's what someone should tell these goofballs to do.
>>      
> Unfortunately, RFC1918 and RFC 6598 are not enough to number all that
> needs numbers.
>    

I'm sorry, I don't understand. Are you saying that Hamachi needs more 
than a /10? Or are you saying that other people need more than a /10 and 
the 1918 /8, /12, and /16? If so, please explain.

pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478


From listsebby@me.com  Mon Nov 26 15:02:26 2012
Return-Path: <listsebby@me.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F11521F8711 for <ietf@ietfa.amsl.com>; Mon, 26 Nov 2012 15:02:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.999
X-Spam-Level: 
X-Spam-Status: No, score=-0.999 tagged_above=-999 required=5 tests=[BAYES_50=0.001, 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 C+9URcxmzAdV for <ietf@ietfa.amsl.com>; Mon, 26 Nov 2012 15:02:25 -0800 (PST)
Received: from nk11p04mm-asmtp004.mac.com (nk11p04mm-asmtpout004.mac.com [17.158.236.239]) by ietfa.amsl.com (Postfix) with ESMTP id E2A6921F8594 for <ietf@ietf.org>; Mon, 26 Nov 2012 15:02:25 -0800 (PST)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII
Received: from [192.168.1.5] (natbox.sabahattin-gucukoglu.com [213.123.192.30]) by nk11p04mm-asmtp004.mac.com (Oracle Communications Messaging Server 7u4-24.01(7.0.4.24.0) 64bit (built Jan 3 2012)) with ESMTPSA id <0ME4004L7ANX8330@nk11p04mm-asmtp004.mac.com> for ietf@ietf.org; Mon, 26 Nov 2012 23:02:25 +0000 (GMT)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.9.8185,1.0.431,0.0.0000 definitions=2012-11-26_03:2012-11-26, 2012-11-25, 1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 suspectscore=9 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=6.0.2-1203120001 definitions=main-1211260253
Subject: Re: A Splendid Example Of A Renumbering Disaster
From: Sabahattin Gucukoglu <listsebby@me.com>
In-reply-to: <50B3D402.7070502@qti.qualcomm.com>
Date: Mon, 26 Nov 2012 23:02:20 +0000
Message-id: <DE8FD3FC-4C3B-41B7-ADDB-4605D7D87E6F@me.com>
References: <54E43A43-A9F3-4803-BAB9-B06F4EB0CB19@me.com> <50B3D402.7070502@qti.qualcomm.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
X-Mailer: Apple Mail (2.1499)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Nov 2012 23:02:26 -0000

On 26 Nov 2012, at 20:41, Pete Resnick <presnick@qti.qualcomm.com> wrote:
> On 11/23/12 7:46 PM, Sabahattin Gucukoglu wrote:
>> http://b.logme.in/2012/11/07/changes-to-hamachi-on-november-19th/

> Yes, like Benson, I am at a loss for why they do not use RFC 6598 addresses. That's what someone should tell these goofballs to do.

OK, I'm getting the idea.  I've left a comment there.  Hopefully somebody will find it.

Cheers,
Sabahattin


From fernando@gont.com.ar  Tue Nov 27 04:57:38 2012
Return-Path: <fernando@gont.com.ar>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A60621F84C8 for <ietf@ietfa.amsl.com>; Tue, 27 Nov 2012 04:57:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.11
X-Spam-Level: 
X-Spam-Status: No, score=-1.11 tagged_above=-999 required=5 tests=[BAYES_05=-1.11]
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 4vA1hdruigWQ for <ietf@ietfa.amsl.com>; Tue, 27 Nov 2012 04:57:38 -0800 (PST)
Received: from web01.jbserver.net (web01.jbserver.net [93.186.182.34]) by ietfa.amsl.com (Postfix) with ESMTP id BDADE21F84C7 for <ietf@ietf.org>; Tue, 27 Nov 2012 04:57:37 -0800 (PST)
Received: from 187-135-17-190.fibertel.com.ar ([190.17.135.187] helo=[192.168.1.113]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fernando@gont.com.ar>) id 1TdKi1-00010C-TG; Tue, 27 Nov 2012 13:57:05 +0100
Message-ID: <50B49F5D.9020609@gont.com.ar>
Date: Tue, 27 Nov 2012 08:09:17 -0300
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: John Levine <johnl@taugh.com>
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
References: <20121116032738.11495.qmail@joyce.lan>
In-Reply-To: <20121116032738.11495.qmail@joyce.lan>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Nov 2012 12:57:38 -0000

On 11/16/2012 12:27 AM, John Levine wrote:
>> 	Shall we move on?
> 
> Sure.  Since we agree that there is no way to pay for the extra costs
> involved in meeting in places where there are insignificant numbers of
> IETF participants, it won't happen, and we're done.

I wonder how you measure/count "IETF participants"...

Do you measure participants based on subscriptions to IETF
mailing-lists? -- If so, how do you assign a location to the plenty of
gTLD addresses? (including those at gmail.com)

Do you measure participants based on subscriptions to mailing-lists
*and* whether they actually get to post to the mailing-lists?

Or do you count as "participants" those that write documents and/or send
feedback about documents?

etc..

Thanks,
-- 
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@si6networks.com
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1




From brian@innovationslab.net  Tue Nov 27 05:30:39 2012
Return-Path: <brian@innovationslab.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 71F5321F8449; Tue, 27 Nov 2012 05:30:39 -0800 (PST)
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=-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 v8K75zqf1Hhx; Tue, 27 Nov 2012 05:30:38 -0800 (PST)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by ietfa.amsl.com (Postfix) with ESMTP id DB73621F8444; Tue, 27 Nov 2012 05:30:38 -0800 (PST)
Received: from clairseach.fuaim.com (clairseach-high.fuaim.com [206.197.161.158]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id 5FEBE8809A; Tue, 27 Nov 2012 05:30:38 -0800 (PST)
Received: from clemson.local (nat-gwifi.jhuapl.edu [128.244.87.132]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id 0BB5B130019; Tue, 27 Nov 2012 05:30:37 -0800 (PST)
Message-ID: <50B4C07C.4010807@innovationslab.net>
Date: Tue, 27 Nov 2012 08:30:36 -0500
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to	Informational RFC
References: <20121113144545.12836.71935.idtracker@ietfa.amsl.com>
In-Reply-To: <20121113144545.12836.71935.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: lisp@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Nov 2012 13:30:39 -0000

I want to thank everyone who has provided feedback on this draft.  Given 
the issues raised, I am sending the draft back to the LISP WG for 
additional work.  I encourage folks interested in this draft to 
participate on the LISP mailing list.

Regards,
Brian

On 11/13/12 9:45 AM, The IESG wrote:
>
> The IESG has received a request from the Locator/ID Separation Protocol
> WG (lisp) to consider the following document:
> - 'LISP EID Block'
>    <draft-ietf-lisp-eid-block-03.txt> as Informational RFC
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2012-11-27. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>
> Abstract
>
>
>     This is a direction to IANA to allocate a /16 IPv6 prefix for use
>     with the Locator/ID Separation Protocol (LISP).  The prefix will be
>     used for local intra-domain routing and global endpoint
>     identification, by sites deploying LISP as EID (Endpoint IDentifier)
>     addressing space.
>
>
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-lisp-eid-block/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-lisp-eid-block/ballot/
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>
> _______________________________________________
> lisp mailing list
> lisp@ietf.org
> https://www.ietf.org/mailman/listinfo/lisp
>


From paul@nohats.ca  Mon Nov 26 09:34:39 2012
Return-Path: <paul@nohats.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 970D621F85EE for <ietf@ietfa.amsl.com>; Mon, 26 Nov 2012 09:34:39 -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 KiCQ1f0UuPhc for <ietf@ietfa.amsl.com>; Mon, 26 Nov 2012 09:34:39 -0800 (PST)
Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) by ietfa.amsl.com (Postfix) with ESMTP id 3818421F86C6 for <ietf@ietf.org>; Mon, 26 Nov 2012 09:34:38 -0800 (PST)
Received: by bofh.nohats.ca (Postfix, from userid 500) id 7EDA682B73; Mon, 26 Nov 2012 12:33:51 -0500 (EST)
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id 733F1803FD; Mon, 26 Nov 2012 12:33:51 -0500 (EST)
Date: Mon, 26 Nov 2012 12:33:51 -0500 (EST)
From: Paul Wouters <paul@nohats.ca>
To: Benson Schliesser <bensons@queuefull.net>
Subject: Re: A Splendid Example Of A Renumbering Disaster
In-Reply-To: <50B3A30A.3000201@queuefull.net>
Message-ID: <alpine.LFD.2.02.1211261231160.7313@bofh.nohats.ca>
References: <54E43A43-A9F3-4803-BAB9-B06F4EB0CB19@me.com> <alpine.LFD.2.02.1211241129320.2810@bofh.nohats.ca> <CAA=duU3cuFPhii9d4Gab74N_cxzPALZP0K1ENVsyfrj7P+2AdA@mail.gmail.com> <50B3A30A.3000201@queuefull.net>
User-Agent: Alpine 2.02 (LFD 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
X-Mailman-Approved-At: Tue, 27 Nov 2012 08:48:05 -0800
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Nov 2012 17:34:39 -0000

On Mon, 26 Nov 2012, Benson Schliesser wrote:

> I expect to be flamed for suggesting it, but why not use the Shared Address Space for this purpose?
> (http://tools.ietf.org/html/rfc6598)

You can't, if carriers are assigning you that IP range. You'd still get
a conflict if you use it for your own VPN range, as the inner address
cannot be in the same subnet as the outer address (whether in tunnel
mode, or when using transport mode with L2TP)

Paul

From johnl@taugh.com  Tue Nov 27 09:21:59 2012
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E4FD421F84DF for <ietf@ietfa.amsl.com>; Tue, 27 Nov 2012 09:21:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.259
X-Spam-Level: 
X-Spam-Status: No, score=0.259 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, GB_AFFORDABLE=1, NO_RELAYS=-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 QtmQYULDGeQ1 for <ietf@ietfa.amsl.com>; Tue, 27 Nov 2012 09:21:59 -0800 (PST)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id CA8CD21F869A for <ietf@ietf.org>; Tue, 27 Nov 2012 09:21:58 -0800 (PST)
Received: (qmail 7320 invoked from network); 27 Nov 2012 17:21:52 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:vbr-info:user-agent:cleverness; s=1c97.50b4f6b0.k1211; bh=B0Ifn0TcC8n4/O36ZuXOrkvvkK6xyIOzNhWYDw9EXWU=; b=SlisHeJEIQLqSLM617z9bz/Brjnh3cFihF0foqqGcTR4OVbj7WTzg+LlIjuIfj5IIxrkZrkDfwqGiYQDdzETqYvRjX3AMjynHsajtfZHJ/rDy1dA5Y0/YaYq/1snh8hrILQocYlRSLc8aJ6pCYx0vkRpbiN2NbfyNQTDUpd6LKo=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:vbr-info:user-agent:cleverness; s=1c97.50b4f6b0.k1211; bh=B0Ifn0TcC8n4/O36ZuXOrkvvkK6xyIOzNhWYDw9EXWU=; b=r235mRijo8VRsOyispN7Ta1R1gRcBfrfFaLn6Qva/Iu/BgTKONJbRLr/327U9nXgEw2n4PUo1EDcYA7SAVlhHdBfASXxrNRG84kMGRpTJbHlAaDVLQv7OKoxTIRlV3Tu2Fj1ihhPqT3cJeaoYCWkiMPzzyhjWYIOrSZ6jkvXuTE=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Received: (ofmipd 127.0.0.1); 27 Nov 2012 17:21:30 -0000
Date: 27 Nov 2012 12:21:52 -0500
Message-ID: <alpine.BSF.2.00.1211271218050.6166@joyce.lan>
From: "John R Levine" <johnl@taugh.com>
To: "Fernando Gont" <fernando@gont.com.ar>
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
In-Reply-To: <50B49F5D.9020609@gont.com.ar>
References: <20121116032738.11495.qmail@joyce.lan> <50B49F5D.9020609@gont.com.ar>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Nov 2012 17:22:00 -0000

> I wonder how you measure/count "IETF participants"...
>
> Do you measure participants based on subscriptions to IETF
> mailing-lists? -- If so, how do you assign a location to the plenty of
> gTLD addresses? (including those at gmail.com)

I'm guessing based on the mail I see on the lists I'm on and the drafts I 
look at.  I really don't think there's a vast group of Latin Americans or 
south Asians or Africans lurking behind gmail addresses.

As I think I've said many times, I think it would be great if we got more 
activity from underrepresented parts of the world, but the way to do that 
is to get people active on mailing lists and writing drafts, not to have 
unaffordable ICANN-style road shows.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
"I dropped the toothpaste", said Tom, crestfallenly.

From worley@shell01.TheWorld.com  Tue Nov 27 09:26:11 2012
Return-Path: <worley@shell01.TheWorld.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A0EDA21F8562 for <ietf@ietfa.amsl.com>; Tue, 27 Nov 2012 09:26:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.68
X-Spam-Level: 
X-Spam-Status: No, score=-1.68 tagged_above=-999 required=5 tests=[AWL=-1.300,  BAYES_50=0.001, RCVD_IN_DNSWL_LOW=-1, RCVD_IN_SORBS_WEB=0.619]
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 ih9WmYxA3LQU for <ietf@ietfa.amsl.com>; Tue, 27 Nov 2012 09:26:11 -0800 (PST)
Received: from TheWorld.com (pcls6.std.com [192.74.137.146]) by ietfa.amsl.com (Postfix) with ESMTP id 64BBA21F84FD for <ietf@ietf.org>; Tue, 27 Nov 2012 09:26:02 -0800 (PST)
Received: from shell.TheWorld.com (svani@shell01.theworld.com [192.74.137.71]) by TheWorld.com (8.14.5/8.14.5) with ESMTP id qARHPf5C027629 for <ietf@ietf.org>; Tue, 27 Nov 2012 12:25:43 -0500
Received: from shell01.TheWorld.com (localhost [127.0.0.1]) by shell.TheWorld.com (8.13.6/8.12.8) with ESMTP id qARHPeea1884099 for <ietf@ietf.org>; Tue, 27 Nov 2012 12:25:41 -0500 (EST)
Received: (from worley@localhost) by shell01.TheWorld.com (8.13.6/8.13.6/Submit) id qARHPekn1882648; Tue, 27 Nov 2012 12:25:40 -0500 (EST)
Date: Tue, 27 Nov 2012 12:25:40 -0500 (EST)
Message-Id: <201211271725.qARHPekn1882648@shell01.TheWorld.com>
From: worley@ariadne.com (Dale R. Worley)
Sender: worley@ariadne.com (Dale R. Worley)
To: ietf@ietf.org
In-reply-to: <003901cdc316$0d19bda0$4001a8c0@gateway.2wire.net> (daedulus@btconnect.com)
Subject: Re: Newcomers [Was: Evolutionizing the IETF]
References: <201211121745.qACHjiXS919660@shell01.TheWorld.com>	<50A13B43.7000309@dcrocker.net>	<72F0897C-D473-4F34-8D21-B9A60DDBBB09@tzi.org>	<50A3F814.1030509@dcrocker.net><50A44418.2010707@gmail.com>	<50A44B7C.10103@gmail.com><50A4599A.8080507@lacnic.net>	<50A45A6F.70900@gmail.com><50A4640D.1060800@lacnic.net> <50A464E5.5050104@gmail.com> <50A4A3AF.1060704@gmail.com> <003901cdc316$0d19bda0$4001a8c0@gateway.2wire.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Nov 2012 17:26:11 -0000

Responses to a couple of points that people have made:

> From: "t.p." <daedulus@btconnect.com>
> 
> I started, some years ago, with a meeting, because the culture that I
> was used to was that conferences, be they annual or triannual, were
> where things really happened and that e-mail filled in the gaps in
> between (and I think that this remains the case in other, related,
> fora).  That attendance showed me that most of the IETF meeting was a
> waste of time, that it was e-mail that was the main vehicle for work,
> and I think that the IETF web site has it about right when it says

This is all true.  Any decision come to during a meeting session must
be reviewed and approved on the WG mailing list.  The reason for this
is to ensure that one can participate completely *without* attending
the meetings and paying the associated expenses.

> From: "Carlos M. Martinez" <carlosm3011@gmail.com>
> 
> The feeling I kept receiving here is that there is a kernel of IETFers
> who still believe that IETF is some kind of ivory tower that exists by
> itself, for itself and is self-sufficient.

First, I think you are not using the correct term.  "Ivory tower" is
used specifically to mean an excessively academic or theoretical
approach.  In the IETF's case, it is considerably more practical and
"hands-on" than other organizations.  In particular, contrast can be
drawn with the ITU's OSI networking protocols.  I think a better term
for the concept is "insular", meaning "isolated" or "island-like".

> The IETF is one more component of the complex ecosystem of Internet
> governance.

However, I think you are correct in that the IETF is insular, that it
does not concern itself much with other parts of the "ecosystem of
Internet governance".  Partly this is historical, in that there wasn't
much "Internet governance" when the IETF was founded.  And for a long,
formative period (15 years or so), the only other global element of
the networking world was the ITU's OSI effort, which was directly
competitive.

But to a considerable degree, the IETF confines itself to aspects of
networking which do not greatly intersect with "Internet governance".
We design and implement protocols.

The connection with the larger ecosystem is more done by the Internet
Society.

> - What is a reasonable goal in terms of participation, so that having a
> meeting in Latin America is actually meaningful?: "X attendees from the
> region and Y people actively participating in mailing lists and
> contributing text"

Success can probably be judged simply by attendance numbers -- does
the meeting have an attendance at least as large as meetings in more
traditional places (within statistical error)?

> - After that, set the goal: "The IETF will hold a meeting in Latin
> America in the next four to five years"
> 
> - What does the IETF to do that?: "The IETF needs partners to pledge X $
> in sponsorship funds", or whatever else.

As far as I can tell from others' postings:

A venue needs to be found that has adequate space and tolerance of our
networking needs.

Sponsors need to be found to cover the costs that the standard meeting
fee will not cover.

The typical attendee budget (air fare, hotel, meeting) needs to be no
higher than in traditional locations.  (This can probably be ensured
with sufficient sponsor support.)

Air travel to the location should not be substantially longer or
inconvenient than to traditional locations (because employers consider
employee's time to be more expensive than direct expenses).

Dale

From barryleiba.mailing.lists@gmail.com  Tue Nov 27 10:00:03 2012
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CA4AC21F867E for <ietf@ietfa.amsl.com>; Tue, 27 Nov 2012 10:00:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.977
X-Spam-Level: 
X-Spam-Status: No, score=-102.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, 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 rI63iprB5Xkk for <ietf@ietfa.amsl.com>; Tue, 27 Nov 2012 10:00:03 -0800 (PST)
Received: from mail-la0-f44.google.com (mail-la0-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id 05AE721F8563 for <ietf@ietf.org>; Tue, 27 Nov 2012 10:00:02 -0800 (PST)
Received: by mail-la0-f44.google.com with SMTP id d3so10455654lah.31 for <ietf@ietf.org>; Tue, 27 Nov 2012 10:00:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; bh=fn+UEEU+eXhj2DyIU1jm0XB+A9QL/LYQWQ/QZGcBjXI=; b=hkyds/t/rxfDCpjhOjVrs7KI36Xo7gPJNomEDjbdl0J3KJsxXjR5bN12+deRFFA2IH hViCmMXgvUMNGQ8RHHxn9zeQVMb6wcSP5u3kAR0G0+0MhBpT46IBXtOfAq/RrJDiaVwJ PyreJVW8Tg3Pb+goQVh6X6osfew8WcT+F6Xj7ZrKXimUgjSygGwN5rKUcE11caj/ffaL vn2vxssUeJ6oEWX1nGrCR0iqccGtGwYG27h18UDF7sritWxsgZpOtanAQx4eETCMHTCH wMN1u4QItCAs/EpqJac70eM9F8RJ3RwL5HXwZseCt9nZjJSGPey4gVer+09NCDsrPzWV oIWw==
MIME-Version: 1.0
Received: by 10.112.10.34 with SMTP id f2mr7190907lbb.47.1354039201982; Tue, 27 Nov 2012 10:00:01 -0800 (PST)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.112.12.166 with HTTP; Tue, 27 Nov 2012 10:00:01 -0800 (PST)
Date: Tue, 27 Nov 2012 13:00:01 -0500
X-Google-Sender-Auth: MVAASKwZFRyYWtTPp3Ea6e5bQ_A
Message-ID: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com>
Subject: "IETF work is done on the mailing lists"
From: Barry Leiba <barryleiba@computer.org>
To: IETF discussion list <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Nov 2012 18:00:03 -0000

On Tue, Nov 27, 2012 at 12:25 PM, Dale R. Worley <worley@ariadne.com> wrote:
>
>> That attendance showed me that most of the IETF meeting was a
>> waste of time, that it was e-mail that was the main vehicle for work,
>> and I think that the IETF web site has it about right when it says
>
> This is all true.  Any decision come to during a meeting session must
> be reviewed and approved on the WG mailing list.  The reason for this
> is to ensure that one can participate completely *without* attending
> the meetings and paying the associated expenses.

This brings up a question that I have as an AD:

A number of times since I started in this position in March, documents
have come to the IESG that prompted me (or another AD) to look into
the document history for... to find that there's basically no history.
 We see a string of versions posted, some with significant updates to
the text, but *no* corresponding mailing list discussion.  Nothing at
all.  The first we see of the document on the mailing list is a
working group last call message, which gets somewhere between zero and
two responses (which say "It's ready."), and then it's sent to the
responsible AD requesting publication.

When I ask the responsible AD or the document shepherd about that, the
response is that, well, no one commented on the list, but it was
discussed in the face-to-face meetings.  A look in the minutes of a
few meetings shows that it was discussed, but, of course, the minutes
show little or none of the discussion.

We accept that, and we review the document as usual, accepting the
document shepherd's writeup that says that the document has "broad
consensus of the working group."

So here's my question:
Does the community want us to push back on those situations?  Does the
community believe that the real IETF work is done on the mailing
lists, and not in the face-to-face meetings, to the extent that the
community would want the IESG to refuse to publish documents whose
process went as I've described above, on the basis that IETF process
was not properly followed?

I realize that this question is going to elicit some vehemence.
Please be brief and polite, as you respond.  :-)

Barry, Applications AD

From marc.blanchet@viagenie.ca  Tue Nov 27 10:07:41 2012
Return-Path: <marc.blanchet@viagenie.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA8A121F867B for <ietf@ietfa.amsl.com>; Tue, 27 Nov 2012 10:07:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.598
X-Spam-Level: 
X-Spam-Status: No, score=-102.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 FPZBqCSRABWJ for <ietf@ietfa.amsl.com>; Tue, 27 Nov 2012 10:07:41 -0800 (PST)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id ED29921F85E6 for <ietf@ietf.org>; Tue, 27 Nov 2012 10:07:40 -0800 (PST)
Received: from [172.23.0.52] (c207.134.45-187.clta.globetrotter.net [207.134.45.187]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 64A3841592; Tue, 27 Nov 2012 13:07:40 -0500 (EST)
Subject: Re: "IETF work is done on the mailing lists"
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: multipart/alternative; boundary="Apple-Mail=_9A630887-09D7-487D-89DB-CDF0A0E9B326"
From: Marc Blanchet <marc.blanchet@viagenie.ca>
In-Reply-To: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com>
Date: Tue, 27 Nov 2012 13:07:38 -0500
Message-Id: <4833FEEC-138C-4B70-91DA-722C256B10F5@viagenie.ca>
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
X-Mailer: Apple Mail (2.1283)
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Nov 2012 18:07:41 -0000

--Apple-Mail=_9A630887-09D7-487D-89DB-CDF0A0E9B326
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1


Le 2012-11-27 =E0 13:00, Barry Leiba a =E9crit :
>=20
> So here's my question:
> Does the community want us to push back on those situations?  Does the
> community believe that the real IETF work is done on the mailing
> lists, and not in the face-to-face meetings, to the extent that the
> community would want the IESG to refuse to publish documents whose
> process went as I've described above, on the basis that IETF process
> was not properly followed?

no. Our work is done both on mailing lists and f2f meetings. As co-chair =
of a few wg, we have been doing great progress during f2f meeting with =
high-bandwidth interactions.=20

so document shepherd and AD should exercise judgement on how to see the =
community consensus/participation.

Marc.

>=20
> I realize that this question is going to elicit some vehemence.
> Please be brief and polite, as you respond.  :-)
>=20
> Barry, Applications AD


--Apple-Mail=_9A630887-09D7-487D-89DB-CDF0A0E9B326
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=iso-8859-1

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><div><div>Le 2012-11-27 =E0 13:00, Barry Leiba a =E9crit =
:</div><blockquote type=3D"cite"><div><font class=3D"Apple-style-span" =
color=3D"#000000"><br></font>So here's my question:<br>Does the =
community want us to push back on those situations? &nbsp;Does =
the<br>community believe that the real IETF work is done on the =
mailing<br>lists, and not in the face-to-face meetings, to the extent =
that the<br>community would want the IESG to refuse to publish documents =
whose<br>process went as I've described above, on the basis that IETF =
process<br>was not properly =
followed?<br></div></blockquote><div><br></div><div>no. Our work is done =
both on mailing lists and f2f meetings. As co-chair of a few wg, we have =
been doing great progress during f2f meeting with high-bandwidth =
interactions.&nbsp;</div><div><br></div><div>so document shepherd and AD =
should exercise judgement on how to see the community =
consensus/participation.</div><div><br></div><div>Marc.</div><br><blockquo=
te type=3D"cite"><div><br>I realize that this question is going to =
elicit some vehemence.<br>Please be brief and polite, as you respond. =
&nbsp;:-)<br><br>Barry, Applications =
AD<br></div></blockquote></div><br></body></html>=

--Apple-Mail=_9A630887-09D7-487D-89DB-CDF0A0E9B326--

From joelja@bogus.com  Tue Nov 27 10:14:49 2012
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3075921F85FF for <ietf@ietfa.amsl.com>; Tue, 27 Nov 2012 10:14:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.999
X-Spam-Level: 
X-Spam-Status: No, score=-101.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_13=0.6, 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 eLlpoDoB-l2B for <ietf@ietfa.amsl.com>; Tue, 27 Nov 2012 10:14:48 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id A562E21F85E6 for <ietf@ietf.org>; Tue, 27 Nov 2012 10:14:48 -0800 (PST)
Received: from joels-MacBook-Air.local (host-64-47-153-50.masergy.com [64.47.153.50]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id qARIEb5v035588 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Tue, 27 Nov 2012 18:14:37 GMT (envelope-from joelja@bogus.com)
Message-ID: <50B50307.2070408@bogus.com>
Date: Tue, 27 Nov 2012 10:14:31 -0800
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Barry Leiba <barryleiba@computer.org>
Subject: Re: "IETF work is done on the mailing lists"
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com>
In-Reply-To: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Tue, 27 Nov 2012 18:14:37 +0000 (UTC)
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Nov 2012 18:14:49 -0000

On 11/27/12 10:00 AM, Barry Leiba wrote:
> On Tue, Nov 27, 2012 at 12:25 PM, Dale R. Worley <worley@ariadne.com> wrote:
>>> That attendance showed me that most of the IETF meeting was a
>>> waste of time, that it was e-mail that was the main vehicle for work,
>>> and I think that the IETF web site has it about right when it says
>> This is all true.  Any decision come to during a meeting session must
>> be reviewed and approved on the WG mailing list.  The reason for this
>> is to ensure that one can participate completely *without* attending
>> the meetings and paying the associated expenses.
> This brings up a question that I have as an AD:
>
> A number of times since I started in this position in March, documents
> have come to the IESG that prompted me (or another AD) to look into
> the document history for... to find that there's basically no history.
>   We see a string of versions posted, some with significant updates to
> the text, but *no* corresponding mailing list discussion.  Nothing at
> all.
There are v6ops wg documents that have arrived in the IESG  queue with 
more than 1000 messages associated with them... I'm not sure that is 
indicative of any entirely healthy wg mailing list process but it does 
leave behind a lot of evidence.

even if all these things were healthy it seems like the actual outcomes 
would be wildly divergent given varying levels of interest.

>   The first we see of the document on the mailing list is a
> working group last call message, which gets somewhere between zero and
> two responses (which say "It's ready."), and then it's sent to the
> responsible AD requesting publication.
>
> When I ask the responsible AD or the document shepherd about that, the
> response is that, well, no one commented on the list, but it was
> discussed in the face-to-face meetings.  A look in the minutes of a
> few meetings shows that it was discussed, but, of course, the minutes
> show little or none of the discussion.
>
> We accept that, and we review the document as usual, accepting the
> document shepherd's writeup that says that the document has "broad
> consensus of the working group."
>
> So here's my question:
> Does the community want us to push back on those situations?  Does the
> community believe that the real IETF work is done on the mailing
> lists, and not in the face-to-face meetings, to the extent that the
> community would want the IESG to refuse to publish documents whose
> process went as I've described above, on the basis that IETF process
> was not properly followed?
>
> I realize that this question is going to elicit some vehemence.
> Please be brief and polite, as you respond.  :-)
>
> Barry, Applications AD
>


From ned+ietf@mauve.mrochek.com  Tue Nov 27 10:59:36 2012
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F03EA21F85C0 for <ietf@ietfa.amsl.com>; Tue, 27 Nov 2012 10:59:36 -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 HWAd2B-9S3gW for <ietf@ietfa.amsl.com>; Tue, 27 Nov 2012 10:59:36 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 8993821F8570 for <ietf@ietf.org>; Tue, 27 Nov 2012 10:59:36 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01ON45HQ17UO002FTS@mauve.mrochek.com> for ietf@ietf.org; Tue, 27 Nov 2012 10:54:35 -0800 (PST)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OMGB2WUMLC00008S@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Tue, 27 Nov 2012 10:54:33 -0800 (PST)
From: ned+ietf@mauve.mrochek.com
Message-id: <01ON45HP32QY00008S@mauve.mrochek.com>
Date: Tue, 27 Nov 2012 10:50:35 -0800 (PST)
Subject: Re: "IETF work is done on the mailing lists"
In-reply-to: "Your message dated Tue, 27 Nov 2012 13:00:01 -0500" <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Nov 2012 18:59:37 -0000

> So here's my question:
> Does the community want us to push back on those situations?  Does the
> community believe that the real IETF work is done on the mailing
> lists, and not in the face-to-face meetings, to the extent that the
> community would want the IESG to refuse to publish documents whose
> process went as I've described above, on the basis that IETF process
> was not properly followed?

The issue isn't the lack of comments but any potential lack of opportunity to
comment. If the document was announced on the list, prefably including
ancillary about changes that have been made, and people chose not to comment
there, then that's fine. But if information about the document wasn't made
available - as is sometimes the case if the document isn't named under the WG - 
then that's a problem.

				Ned

From daedulus@btconnect.com  Tue Nov 27 11:35:09 2012
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B94C021F8788 for <ietf@ietfa.amsl.com>; Tue, 27 Nov 2012 11:35:09 -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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y2MzJ0OBSizr for <ietf@ietfa.amsl.com>; Tue, 27 Nov 2012 11:35:08 -0800 (PST)
Received: from tx2outboundpool.messaging.microsoft.com (tx2ehsobe004.messaging.microsoft.com [65.55.88.14]) by ietfa.amsl.com (Postfix) with ESMTP id 8705521F86DD for <ietf@ietf.org>; Tue, 27 Nov 2012 11:35:08 -0800 (PST)
Received: from mail22-tx2-R.bigfish.com (10.9.14.254) by TX2EHSOBE009.bigfish.com (10.9.40.29) with Microsoft SMTP Server id 14.1.225.23; Tue, 27 Nov 2012 19:35:00 +0000
Received: from mail22-tx2 (localhost [127.0.0.1])	by mail22-tx2-R.bigfish.com (Postfix) with ESMTP id 58274A0254; Tue, 27 Nov 2012 19:35:00 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.253.197; KIP:(null); UIP:(null); IPV:NLI; H:DBXPRD0710HT003.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -25
X-BigFish: PS-25(zz98dI9371I542M1432I1418Izz1de0h1202h1d1ah1d2ahzz1033IL8275bh8275dhz2dh2a8h5a9h668h839hd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h304l1155h)
Received: from mail22-tx2 (localhost.localdomain [127.0.0.1]) by mail22-tx2 (MessageSwitch) id 1354044899133372_16005; Tue, 27 Nov 2012 19:34:59 +0000 (UTC)
Received: from TX2EHSMHS024.bigfish.com (unknown [10.9.14.245])	by mail22-tx2.bigfish.com (Postfix) with ESMTP id 117F3C02D4; Tue, 27 Nov 2012 19:34:59 +0000 (UTC)
Received: from DBXPRD0710HT003.eurprd07.prod.outlook.com (157.56.253.197) by TX2EHSMHS024.bigfish.com (10.9.99.124) with Microsoft SMTP Server (TLS) id 14.1.225.23; Tue, 27 Nov 2012 19:34:58 +0000
Received: from CH1PRD0610HT002.namprd06.prod.outlook.com (157.56.244.229) by pod51017.outlook.com (10.255.79.166) with Microsoft SMTP Server (TLS) id 14.16.239.5; Tue, 27 Nov 2012 19:34:52 +0000
Message-ID: <076e01cdccd6$1956d0c0$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: Barry Leiba <barryleiba@computer.org>, IETF discussion list <ietf@ietf.org>
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com>
Subject: Re: "IETF work is done on the mailing lists"
Date: Tue, 27 Nov 2012 19:33:29 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [157.56.244.229]
X-OriginatorOrg: btconnect.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Nov 2012 19:35:09 -0000

----- Original Message -----
From: "Barry Leiba" <barryleiba@computer.org>
To: "IETF discussion list" <ietf@ietf.org>
Sent: Tuesday, November 27, 2012 6:00 PM

> On Tue, Nov 27, 2012 at 12:25 PM, Dale R. Worley <worley@ariadne.com>
wrote:
> >
> >> That attendance showed me that most of the IETF meeting was a
> >> waste of time, that it was e-mail that was the main vehicle for
work,
> >> and I think that the IETF web site has it about right when it says
> >
> > This is all true.  Any decision come to during a meeting session
must
> > be reviewed and approved on the WG mailing list.  The reason for
this
> > is to ensure that one can participate completely *without* attending
> > the meetings and paying the associated expenses.
>
> This brings up a question that I have as an AD:
>
> A number of times since I started in this position in March, documents
> have come to the IESG that prompted me (or another AD) to look into
> the document history for... to find that there's basically no history.
>  We see a string of versions posted, some with significant updates to
> the text, but *no* corresponding mailing list discussion.  Nothing at
> all.  The first we see of the document on the mailing list is a
> working group last call message, which gets somewhere between zero and
> two responses (which say "It's ready."), and then it's sent to the
> responsible AD requesting publication.
>
> When I ask the responsible AD or the document shepherd about that, the
> response is that, well, no one commented on the list, but it was
> discussed in the face-to-face meetings.  A look in the minutes of a
> few meetings shows that it was discussed, but, of course, the minutes
> show little or none of the discussion.
>
> We accept that, and we review the document as usual, accepting the
> document shepherd's writeup that says that the document has "broad
> consensus of the working group."
>
> So here's my question:
> Does the community want us to push back on those situations?  Does the
> community believe that the real IETF work is done on the mailing
> lists, and not in the face-to-face meetings, to the extent that the
> community would want the IESG to refuse to publish documents whose
> process went as I've described above, on the basis that IETF process
> was not properly followed?

Assuming that you are referring to I-Ds from a WG, then the WG chair is
saying that the document has been reviewed enough for it to progress.
The WG chair is appointed, in some sense of the word, by the ADs, past
or present, for the Area in question.  Thus what you seem to be asking
is should you trust the people appointed by the ADs.

Um, mostly yes, but then if you do push back, then that is an implicit
criticism of the WG chair and/or ADs.

In the WG in which I am active, I mostly do see push back from the WG
Chair, that unless and until people speak up on the list, eg during Last
Call, then the I-D in question is going nowhere - which I find healthy.
If people continue not to speak up, well then perhaps it is time to
close the WG, which is probably about right.

Tom Petch





>
> I realize that this question is going to elicit some vehemence.
> Please be brief and polite, as you respond.  :-)
>
> Barry, Applications AD
>



From melinda.shore@gmail.com  Tue Nov 27 11:41:42 2012
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6DEA321F86B5 for <ietf@ietfa.amsl.com>; Tue, 27 Nov 2012 11:41:42 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WFNAol9Giakt for <ietf@ietfa.amsl.com>; Tue, 27 Nov 2012 11:41:41 -0800 (PST)
Received: from mail-ie0-f172.google.com (mail-ie0-f172.google.com [209.85.223.172]) by ietfa.amsl.com (Postfix) with ESMTP id 7339221F867C for <ietf@ietf.org>; Tue, 27 Nov 2012 11:41:41 -0800 (PST)
Received: by mail-ie0-f172.google.com with SMTP id c13so12415690ieb.31 for <ietf@ietf.org>; Tue, 27 Nov 2012 11:41:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=/caRyRadmEIb63Z/ZG9K3ULhRar2S40LKBi0QOThbDg=; b=w0bbjw3NZ8kaow3Fgxv9DOCDGHDvjyTFvCZ/g4MtzHvtfYg5JBPOQXRzp2UUnU6/47 FqCK/0SZLdUvrc5M8SJtSa3pCaTje8pAAJ2yhgp1eAdKLzWhnmpU+yOlPzrcSIYYk3E5 TvmDaTFs9Tx9fUcurdfN2R+5+5k2GiC86/lG92RRVFf1+VaHAtNkGsCnCBigrv44iXGQ BiGpNbagz+rWuL41M6jSx2jPX4PGjIAr7axe24CLsZuc7o5CudK3fm9hFn/WPD95Mtvc 3TiV8Cbt9MvnF6SN7NFkv6A6UiTOSWXLEfExaBSykr+tt53QKWXoDMIegmjXZVJMT0mQ VSVg==
Received: by 10.50.171.101 with SMTP id at5mr16739967igc.60.1354045301021; Tue, 27 Nov 2012 11:41:41 -0800 (PST)
Received: from [172.19.241.232] ([205.234.44.18]) by mx.google.com with ESMTPS id hg2sm2293256igc.3.2012.11.27.11.41.39 (version=SSLv3 cipher=OTHER); Tue, 27 Nov 2012 11:41:40 -0800 (PST)
Message-ID: <50B51774.6070607@gmail.com>
Date: Tue, 27 Nov 2012 10:41:40 -0900
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: "IETF work is done on the mailing lists"
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com>
In-Reply-To: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Nov 2012 19:41:42 -0000

I think the core issue is whether or not there's been adequate
review, and it seems to me to be appropriate to request volunteers
from wg participants to review documents before moving them along.

Melinda

From ajs@anvilwalrusden.com  Tue Nov 27 11:50:00 2012
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B176921F8639 for <ietf@ietfa.amsl.com>; Tue, 27 Nov 2012 11:50:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.84
X-Spam-Level: 
X-Spam-Status: No, score=-0.84 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311]
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 zyL-nMrjbozg for <ietf@ietfa.amsl.com>; Tue, 27 Nov 2012 11:50:00 -0800 (PST)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id 4E70721F85FE for <ietf@ietf.org>; Tue, 27 Nov 2012 11:50:00 -0800 (PST)
Received: from mx1.yitter.info (69-196-144-227.dsl.teksavvy.com [69.196.144.227]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 8A65E8A031 for <ietf@ietf.org>; Tue, 27 Nov 2012 19:49:55 +0000 (UTC)
Date: Tue, 27 Nov 2012 14:49:53 -0500
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: "IETF work is done on the mailing lists"
Message-ID: <20121127194953.GC375@mx1.yitter.info>
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <076e01cdccd6$1956d0c0$4001a8c0@gateway.2wire.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <076e01cdccd6$1956d0c0$4001a8c0@gateway.2wire.net>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Nov 2012 19:50:00 -0000

On Tue, Nov 27, 2012 at 07:33:29PM +0000, t.p. wrote:
> Chair, that unless and until people speak up on the list, eg during Last
> Call, then the I-D in question is going nowhere - which I find healthy.

I strongly agree with this.

> If people continue not to speak up, well then perhaps it is time to
> close the WG, which is probably about right.

Even more with this.  It's a _working_ group, not a _meeting_ group.
If the work isn't getting done, shut it down.

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From gih@apnic.net  Tue Nov 27 12:02:59 2012
Return-Path: <gih@apnic.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B29221F8231 for <ietf@ietfa.amsl.com>; Tue, 27 Nov 2012 12:02:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, 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 5r3xkM1HGYYs for <ietf@ietfa.amsl.com>; Tue, 27 Nov 2012 12:02:58 -0800 (PST)
Received: from asmtp.apnic.net (asmtp.apnic.net [IPv6:2001:dc0:2001:11::199]) by ietfa.amsl.com (Postfix) with ESMTP id 590A121F81FF for <ietf@ietf.org>; Tue, 27 Nov 2012 12:02:58 -0800 (PST)
Received: from 2001-44b8-1121-1a00-3888-8c0d-b976-3501.static.ipv6.internode.on.net (2001-44b8-1121-1a00-3888-8c0d-b976-3501.static.ipv6.internode.on.net [IPv6:2001:44b8:1121:1a00:3888:8c0d:b976:3501]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by asmtp.apnic.net (Postfix) with ESMTP id 80952B68C8; Wed, 28 Nov 2012 06:02:56 +1000 (EST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: "IETF work is done on the mailing lists"
From: Geoff Huston <gih@apnic.net>
In-Reply-To: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com>
Date: Wed, 28 Nov 2012 07:02:55 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <92EE2BAA-B605-4F3A-BF55-2E05A165697B@apnic.net>
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
X-Mailer: Apple Mail (2.1499)
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Nov 2012 20:02:59 -0000

On 28/11/2012, at 5:00 AM, Barry Leiba <barryleiba@computer.org> wrote:

> On Tue, Nov 27, 2012 at 12:25 PM, Dale R. Worley <worley@ariadne.com> =
wrote:
>>=20
>>> That attendance showed me that most of the IETF meeting was a
>>> waste of time, that it was e-mail that was the main vehicle for =
work,
>>> and I think that the IETF web site has it about right when it says
>>=20
>> This is all true.  Any decision come to during a meeting session must
>> be reviewed and approved on the WG mailing list.  The reason for this
>> is to ensure that one can participate completely *without* attending
>> the meetings and paying the associated expenses.
>=20
> This brings up a question that I have as an AD:
>=20
> A number of times since I started in this position in March, documents
> have come to the IESG that prompted me (or another AD) to look into
> the document history for... to find that there's basically no history.
> We see a string of versions posted, some with significant updates to
> the text, but *no* corresponding mailing list discussion.  Nothing at
> all.  The first we see of the document on the mailing list is a
> working group last call message, which gets somewhere between zero and
> two responses (which say "It's ready."), and then it's sent to the
> responsible AD requesting publication.
>=20
> When I ask the responsible AD or the document shepherd about that, the
> response is that, well, no one commented on the list, but it was
> discussed in the face-to-face meetings.  A look in the minutes of a
> few meetings shows that it was discussed, but, of course, the minutes
> show little or none of the discussion.
>=20
> We accept that, and we review the document as usual, accepting the
> document shepherd's writeup that says that the document has "broad
> consensus of the working group."
>=20
> So here's my question:
> Does the community want us to push back on those situations?

I do not speak for the community, naturally, but this particular member =
of the community says: Very much so.

if neither the mailing list or the minutes of the meetings are showing =
no visible activity then its reasonable to conclude that the document is =
not the product of an open consensus based activity, and the proponents =
behind the document, who presumably used other fora (presumably closed) =
to get their document up the the IESG. If the IESG rubber stamps this =
because "its just an informational" or "well, the document shepherd =
claimed that it had been reviewed" then the IESG is as derelict in its =
duty.

If a document in WG last call gets no visible support on the WG mailing =
list then it should never head to the IESG, nor should the IESG publish =
to draft.


>  Does the
> community believe that the real IETF work is done on the mailing
> lists, and not in the face-to-face meetings, to the extent that the
> community would want the IESG to refuse to publish documents whose
> process went as I've described above, on the basis that IETF process
> was not properly followed?


I do not speak for the community, naturally, but this particular member =
of the community says: yes, of course.

regards,

 Geoff




From dmm@1-4-5.net  Tue Nov 27 12:15:44 2012
Return-Path: <dmm@1-4-5.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 520A121F8425 for <ietf@ietfa.amsl.com>; Tue, 27 Nov 2012 12:15:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.826
X-Spam-Level: 
X-Spam-Status: No, score=-2.826 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, 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 hI-iE0J2sVEm for <ietf@ietfa.amsl.com>; Tue, 27 Nov 2012 12:15:43 -0800 (PST)
Received: from mail-ob0-f172.google.com (mail-ob0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id 5FF1621F841C for <ietf@ietf.org>; Tue, 27 Nov 2012 12:15:43 -0800 (PST)
Received: by mail-ob0-f172.google.com with SMTP id v19so756273obq.31 for <ietf@ietf.org>; Tue, 27 Nov 2012 12:15:42 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=hO/d+u7zPVxoR7ZxMakW2lurlJx4duTREIanm7tvwqc=; b=f1aUOYCJ/3jIKf8pGZK/tcivSFCJlsrUNOnOTt+3hT0eAHpsCsJQTLzpzb7pzQ2Ek7 0FNA3hjPtqOHKXmERUnIae53wwiy135AlU4bbv1ycCmVJpnzeFNdBCWXpDkp3+ohuiy8 asTSEmQaWdy1sHf1+tMux/P1VjksHatWd6IrdREs6sKs465BJ7EcbNSq0M4dzmvPDudj bTSBOMnvGGW42laZyM1Y3I/gzIuNo1WRMEV2YHQZwbQhhIdTZU0bGDlQeXFNKFgn/8y7 /z9fq1MFm6GE87fUnuGdGRTUwr9qBcbWLw2o7o86jiJvYr+Ey6KrHuk8QZiDL4REyvRe K/3Q==
MIME-Version: 1.0
Received: by 10.60.32.37 with SMTP id f5mr9114534oei.19.1354047342596; Tue, 27 Nov 2012 12:15:42 -0800 (PST)
Received: by 10.76.84.103 with HTTP; Tue, 27 Nov 2012 12:15:42 -0800 (PST)
X-Originating-IP: [144.49.132.3]
In-Reply-To: <92EE2BAA-B605-4F3A-BF55-2E05A165697B@apnic.net>
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <92EE2BAA-B605-4F3A-BF55-2E05A165697B@apnic.net>
Date: Tue, 27 Nov 2012 12:15:42 -0800
Message-ID: <CAHiKxWiQKhrOCmMP=KTO4+T=i08BcM+EW_W6-ec11B_zuJroag@mail.gmail.com>
Subject: Re: "IETF work is done on the mailing lists"
From: David Meyer <dmm@1-4-5.net>
To: Geoff Huston <gih@apnic.net>
Content-Type: multipart/alternative; boundary=e89a8fb20020dd50f104cf7fb66e
X-Gm-Message-State: ALoCoQknamtkUIVhINABhhSVtbrxtZV+z+zrlQ7IcjCjpe/ol0DBJFu8OR3WQ3BnX50v3xEUmdRW
Cc: Barry Leiba <barryleiba@computer.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Nov 2012 20:15:44 -0000

--e89a8fb20020dd50f104cf7fb66e
Content-Type: text/plain; charset=ISO-8859-1

+1

--dmm


On Tue, Nov 27, 2012 at 12:02 PM, Geoff Huston <gih@apnic.net> wrote:

>
> On 28/11/2012, at 5:00 AM, Barry Leiba <barryleiba@computer.org> wrote:
>
> > On Tue, Nov 27, 2012 at 12:25 PM, Dale R. Worley <worley@ariadne.com>
> wrote:
> >>
> >>> That attendance showed me that most of the IETF meeting was a
> >>> waste of time, that it was e-mail that was the main vehicle for work,
> >>> and I think that the IETF web site has it about right when it says
> >>
> >> This is all true.  Any decision come to during a meeting session must
> >> be reviewed and approved on the WG mailing list.  The reason for this
> >> is to ensure that one can participate completely *without* attending
> >> the meetings and paying the associated expenses.
> >
> > This brings up a question that I have as an AD:
> >
> > A number of times since I started in this position in March, documents
> > have come to the IESG that prompted me (or another AD) to look into
> > the document history for... to find that there's basically no history.
> > We see a string of versions posted, some with significant updates to
> > the text, but *no* corresponding mailing list discussion.  Nothing at
> > all.  The first we see of the document on the mailing list is a
> > working group last call message, which gets somewhere between zero and
> > two responses (which say "It's ready."), and then it's sent to the
> > responsible AD requesting publication.
> >
> > When I ask the responsible AD or the document shepherd about that, the
> > response is that, well, no one commented on the list, but it was
> > discussed in the face-to-face meetings.  A look in the minutes of a
> > few meetings shows that it was discussed, but, of course, the minutes
> > show little or none of the discussion.
> >
> > We accept that, and we review the document as usual, accepting the
> > document shepherd's writeup that says that the document has "broad
> > consensus of the working group."
> >
> > So here's my question:
> > Does the community want us to push back on those situations?
>
> I do not speak for the community, naturally, but this particular member of
> the community says: Very much so.
>
> if neither the mailing list or the minutes of the meetings are showing no
> visible activity then its reasonable to conclude that the document is not
> the product of an open consensus based activity, and the proponents behind
> the document, who presumably used other fora (presumably closed) to get
> their document up the the IESG. If the IESG rubber stamps this because "its
> just an informational" or "well, the document shepherd claimed that it had
> been reviewed" then the IESG is as derelict in its duty.
>
> If a document in WG last call gets no visible support on the WG mailing
> list then it should never head to the IESG, nor should the IESG publish to
> draft.
>
>
> >  Does the
> > community believe that the real IETF work is done on the mailing
> > lists, and not in the face-to-face meetings, to the extent that the
> > community would want the IESG to refuse to publish documents whose
> > process went as I've described above, on the basis that IETF process
> > was not properly followed?
>
>
> I do not speak for the community, naturally, but this particular member of
> the community says: yes, of course.
>
> regards,
>
>  Geoff
>
>
>
>

--e89a8fb20020dd50f104cf7fb66e
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

+1<div><br></div><div>--dmm</div><div><br><br><div class=3D"gmail_quote">On=
 Tue, Nov 27, 2012 at 12:02 PM, Geoff Huston <span dir=3D"ltr">&lt;<a href=
=3D"mailto:gih@apnic.net" target=3D"_blank">gih@apnic.net</a>&gt;</span> wr=
ote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"HOEnZb"><div class=3D"h5"><br>
On 28/11/2012, at 5:00 AM, Barry Leiba &lt;<a href=3D"mailto:barryleiba@com=
puter.org">barryleiba@computer.org</a>&gt; wrote:<br>
<br>
&gt; On Tue, Nov 27, 2012 at 12:25 PM, Dale R. Worley &lt;<a href=3D"mailto=
:worley@ariadne.com">worley@ariadne.com</a>&gt; wrote:<br>
&gt;&gt;<br>
&gt;&gt;&gt; That attendance showed me that most of the IETF meeting was a<=
br>
&gt;&gt;&gt; waste of time, that it was e-mail that was the main vehicle fo=
r work,<br>
&gt;&gt;&gt; and I think that the IETF web site has it about right when it =
says<br>
&gt;&gt;<br>
&gt;&gt; This is all true. =A0Any decision come to during a meeting session=
 must<br>
&gt;&gt; be reviewed and approved on the WG mailing list. =A0The reason for=
 this<br>
&gt;&gt; is to ensure that one can participate completely *without* attendi=
ng<br>
&gt;&gt; the meetings and paying the associated expenses.<br>
&gt;<br>
&gt; This brings up a question that I have as an AD:<br>
&gt;<br>
&gt; A number of times since I started in this position in March, documents=
<br>
&gt; have come to the IESG that prompted me (or another AD) to look into<br=
>
&gt; the document history for... to find that there&#39;s basically no hist=
ory.<br>
&gt; We see a string of versions posted, some with significant updates to<b=
r>
&gt; the text, but *no* corresponding mailing list discussion. =A0Nothing a=
t<br>
&gt; all. =A0The first we see of the document on the mailing list is a<br>
&gt; working group last call message, which gets somewhere between zero and=
<br>
&gt; two responses (which say &quot;It&#39;s ready.&quot;), and then it&#39=
;s sent to the<br>
&gt; responsible AD requesting publication.<br>
&gt;<br>
&gt; When I ask the responsible AD or the document shepherd about that, the=
<br>
&gt; response is that, well, no one commented on the list, but it was<br>
&gt; discussed in the face-to-face meetings. =A0A look in the minutes of a<=
br>
&gt; few meetings shows that it was discussed, but, of course, the minutes<=
br>
&gt; show little or none of the discussion.<br>
&gt;<br>
&gt; We accept that, and we review the document as usual, accepting the<br>
&gt; document shepherd&#39;s writeup that says that the document has &quot;=
broad<br>
&gt; consensus of the working group.&quot;<br>
&gt;<br>
&gt; So here&#39;s my question:<br>
&gt; Does the community want us to push back on those situations?<br>
<br>
</div></div>I do not speak for the community, naturally, but this particula=
r member of the community says: Very much so.<br>
<br>
if neither the mailing list or the minutes of the meetings are showing no v=
isible activity then its reasonable to conclude that the document is not th=
e product of an open consensus based activity, and the proponents behind th=
e document, who presumably used other fora (presumably closed) to get their=
 document up the the IESG. If the IESG rubber stamps this because &quot;its=
 just an informational&quot; or &quot;well, the document shepherd claimed t=
hat it had been reviewed&quot; then the IESG is as derelict in its duty.<br=
>

<br>
If a document in WG last call gets no visible support on the WG mailing lis=
t then it should never head to the IESG, nor should the IESG publish to dra=
ft.<br>
<div class=3D"im"><br>
<br>
&gt; =A0Does the<br>
&gt; community believe that the real IETF work is done on the mailing<br>
&gt; lists, and not in the face-to-face meetings, to the extent that the<br=
>
&gt; community would want the IESG to refuse to publish documents whose<br>
&gt; process went as I&#39;ve described above, on the basis that IETF proce=
ss<br>
&gt; was not properly followed?<br>
<br>
<br>
</div>I do not speak for the community, naturally, but this particular memb=
er of the community says: yes, of course.<br>
<br>
regards,<br>
<br>
=A0Geoff<br>
<br>
<br>
<br>
</blockquote></div><br></div>

--e89a8fb20020dd50f104cf7fb66e--

From john-ietf@jck.com  Tue Nov 27 12:44:09 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A039221F8766 for <ietf@ietfa.amsl.com>; Tue, 27 Nov 2012 12:44:09 -0800 (PST)
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=-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 1a5oxOXKPC0J for <ietf@ietfa.amsl.com>; Tue, 27 Nov 2012 12:44:09 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 1DD5421F8765 for <ietf@ietf.org>; Tue, 27 Nov 2012 12:44:09 -0800 (PST)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1TdS0i-0007V8-F6; Tue, 27 Nov 2012 15:44:04 -0500
Date: Tue, 27 Nov 2012 15:43:56 -0500
From: John C Klensin <john-ietf@jck.com>
To: Barry Leiba <barryleiba@computer.org>, IETF discussion list <ietf@ietf.org>
Subject: Re: "IETF work is done on the mailing lists"
Message-ID: <3E37A498FAFCE1AC87DD66B6@JcK-HP8200.jck.com>
In-Reply-To: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com>
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Nov 2012 20:44:09 -0000

--On Tuesday, November 27, 2012 13:00 -0500 Barry Leiba
<barryleiba@computer.org> wrote:

>...
> So here's my question:
> Does the community want us to push back on those situations?
> Does the community believe that the real IETF work is done on
> the mailing lists, and not in the face-to-face meetings, to
> the extent that the community would want the IESG to refuse to
> publish documents whose process went as I've described above,
> on the basis that IETF process was not properly followed?
> 
> I realize that this question is going to elicit some vehemence.
> Please be brief and polite, as you respond.  :-)

Barry,

I find myself agreeing with Geoff and Andrew in thinking that
answer should usually be "yes, push back".  However, I think
that unusual situations do occur and that different WGs,
sometimes for good reason, have different styles.  As usual, I
favor good sense over the rigidity of process purity.  So a
suggestion: If a WG expects you the IESG to sign off on a
document based primarily on meeting list discussions, two
conditions should be met: (i) the minutes had better be
sufficiently detailed to be persuasive that there really was
review and that the document really is a WG product, not just
that of a few authors (or organizations) and (ii) there has to
be a clear opportunity, after the minutes appear (and Jabber
logs, etc., are available) for people on the mailing list to
comment on the presumed meeting decision.  I don't believe that
more specific guidelines for either of those conditions are
necessary or desirable other than to say that it is the
obligation of the WG and its chairs/shepherds to present
evidence that it persuasive to an IESG that out to be skeptical.

Speaking for myself only, of course.

    john




From sm@resistor.net  Tue Nov 27 12:48:15 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E9B321F8570 for <ietf@ietfa.amsl.com>; Tue, 27 Nov 2012 12:48:15 -0800 (PST)
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=-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 GQkr1nRuOgYU for <ietf@ietfa.amsl.com>; Tue, 27 Nov 2012 12:48:15 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id DF4DA21F84D7 for <ietf@ietf.org>; Tue, 27 Nov 2012 12:48:14 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id qARKm3Ta025284; Tue, 27 Nov 2012 12:48:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1354049287; bh=BaOI7qja82LrdtIGXGkzk7QDA+Wpla9is8ORrtQ4A7M=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=wVx9Vk32imdj2ybgo67qD3JM6Qmm0g712/M9WW4JLW+LsIlSxzOv5z+5MyvfcPgG/ Q67rw/lg66YOZUUki9DZZ9QcCR7U0epjDA/B5pDbb1wAtbLnQ9t2W14b1UoIf4gZZv isTR3/83+c/m5wlJKlhJfQrUeoQjahk/tR3+jCZ4=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1354049287; i=@resistor.net; bh=BaOI7qja82LrdtIGXGkzk7QDA+Wpla9is8ORrtQ4A7M=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=AxaLfmiVkDyk9OZ82i9zK9DCezm5fGMAStK4IFl4jZvVTb+S782Eg0MYgwb3eRbiI on7vZmo5iq4zmi66gOTzMiOen0322C2hSgvKBqX/gywBJI+jods9258LzOs4eEEf4O LhBJNSo47/hY4c1j0lUkw/oyN2TdA5VLumex4U1Q=
Message-Id: <6.2.5.6.2.20121127115614.0f0bae18@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 27 Nov 2012 12:37:29 -0800
To: Barry Leiba <barryleiba@computer.org>
From: SM <sm@resistor.net>
Subject: Re: "IETF work is done on the mailing lists"
In-Reply-To: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.g mail.com>
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Nov 2012 20:48:15 -0000

Hi Barry,
At 10:00 27-11-2012, Barry Leiba wrote:
>We accept that, and we review the document as usual, accepting the
>document shepherd's writeup that says that the document has "broad
>consensus of the working group."

:-)

>So here's my question:
>Does the community want us to push back on those situations?  Does the
>community believe that the real IETF work is done on the mailing
>lists, and not in the face-to-face meetings, to the extent that the
>community would want the IESG to refuse to publish documents whose
>process went as I've described above, on the basis that IETF process
>was not properly followed?

A working group would be using consensus by apathy if there isn't any 
mailing discussion or any trace of discussions in the minutes.  The 
alternatives are to push back or shut down the working group.

Regards,
-sm



From dwm@xpasc.com  Tue Nov 27 12:54:16 2012
Return-Path: <dwm@xpasc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D65A221F8769 for <ietf@ietfa.amsl.com>; Tue, 27 Nov 2012 12:54:16 -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=[AWL=-4.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 oxvNgbct2dqe for <ietf@ietfa.amsl.com>; Tue, 27 Nov 2012 12:54:16 -0800 (PST)
Received: from c2w3p-2.abacamail.com (c2w3p-2.abacamail.com [209.133.53.32]) by ietfa.amsl.com (Postfix) with ESMTP id 7046F21F8764 for <ietf@ietf.org>; Tue, 27 Nov 2012 12:54:16 -0800 (PST)
Received: from xpasc.com (unknown [68.164.244.188]) by c2w3p-2.abacamail.com (Postfix) with ESMTP id 088773FEEA for <ietf@ietf.org>; Tue, 27 Nov 2012 20:54:16 +0000 (UTC)
Received: from egate.xpasc.com (egate.xpasc.com [10.1.2.49]) by xpasc.com (8.13.8/8.13.8) with ESMTP id qARKsFm8001513 for <ietf@ietf.org>; Tue, 27 Nov 2012 12:54:15 -0800
Date: Tue, 27 Nov 2012 12:54:15 -0800 (PST)
From: David Morris <dwm@xpasc.com>
To: IETF discussion list <ietf@ietf.org>
Subject: Re: "IETF work is done on the mailing lists"
In-Reply-To: <3E37A498FAFCE1AC87DD66B6@JcK-HP8200.jck.com>
Message-ID: <alpine.LRH.2.01.1211271251470.1300@egate.xpasc.com>
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <3E37A498FAFCE1AC87DD66B6@JcK-HP8200.jck.com>
User-Agent: Alpine 2.01 (LRH 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Milter-Version: master.1+13-gbab1945
X-AV-Type: clean
X-AV-Accuracy: exact
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: IETF discussion list <ietf@ietf.org>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Nov 2012 20:54:16 -0000

On Tue, 27 Nov 2012, John C Klensin wrote:

> 
> 
> --On Tuesday, November 27, 2012 13:00 -0500 Barry Leiba
> <barryleiba@computer.org> wrote:
> 
> >...
> > So here's my question:
> > Does the community want us to push back on those situations?
> > Does the community believe that the real IETF work is done on
> > the mailing lists, and not in the face-to-face meetings, to
> > the extent that the community would want the IESG to refuse to
> > publish documents whose process went as I've described above,
> > on the basis that IETF process was not properly followed?
> > 
> > I realize that this question is going to elicit some vehemence.
> > Please be brief and polite, as you respond.  :-)
> 
> Barry,
> 
> I find myself agreeing with Geoff and Andrew in thinking that
> answer should usually be "yes, push back".  However, I think
> that unusual situations do occur and that different WGs,
> sometimes for good reason, have different styles.  As usual, I
> favor good sense over the rigidity of process purity.  So a
> suggestion: If a WG expects you the IESG to sign off on a
> document based primarily on meeting list discussions, two
> conditions should be met: (i) the minutes had better be
> sufficiently detailed to be persuasive that there really was
> review and that the document really is a WG product, not just
> that of a few authors (or organizations) and (ii) there has to
> be a clear opportunity, after the minutes appear (and Jabber
> logs, etc., are available) for people on the mailing list to
> comment on the presumed meeting decision.  I don't believe that
> more specific guidelines for either of those conditions are
> necessary or desirable other than to say that it is the
> obligation of the WG and its chairs/shepherds to present
> evidence that it persuasive to an IESG that out to be skeptical.

I agree, though I'd add the preference that the WGLC explicitly
acknowledge the meeting notes as the record of discussion.

Dave Morris

From touch@isi.edu  Tue Nov 27 13:21:07 2012
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F007421F8201 for <ietf@ietfa.amsl.com>; Tue, 27 Nov 2012 13:21:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.542
X-Spam-Level: 
X-Spam-Status: No, score=-102.542 tagged_above=-999 required=5 tests=[AWL=0.057, 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 Xtlqke91oIXI for <ietf@ietfa.amsl.com>; Tue, 27 Nov 2012 13:21:06 -0800 (PST)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by ietfa.amsl.com (Postfix) with ESMTP id 75A1E21F84B9 for <ietf@ietf.org>; Tue, 27 Nov 2012 13:21:06 -0800 (PST)
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 qARLKSeW015248 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 27 Nov 2012 13:20:28 -0800 (PST)
Message-ID: <50B52E9C.4090601@isi.edu>
Date: Tue, 27 Nov 2012 13:20:28 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: Marc Blanchet <marc.blanchet@viagenie.ca>
Subject: Re: "IETF work is done on the mailing lists"
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <4833FEEC-138C-4B70-91DA-722C256B10F5@viagenie.ca>
In-Reply-To: <4833FEEC-138C-4B70-91DA-722C256B10F5@viagenie.ca>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: Barry Leiba <barryleiba@computer.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Nov 2012 21:21:07 -0000

On 11/27/2012 10:07 AM, Marc Blanchet wrote:
>
> Le 2012-11-27 à 13:00, Barry Leiba a écrit :
>>
>> So here's my question:
>> Does the community want us to push back on those situations?  Does the
>> community believe that the real IETF work is done on the mailing
>> lists, and not in the face-to-face meetings, to the extent that the
>> community would want the IESG to refuse to publish documents whose
>> process went as I've described above, on the basis that IETF process
>> was not properly followed?
>
> no. Our work is done both on mailing lists and f2f meetings. As co-chair
> of a few wg, we have been doing great progress during f2f meeting with
> high-bandwidth interactions.

RFC2418 says that "business" happens in either place:

    ...
    All working group actions shall be taken in a public forum, and wide
    participation is encouraged. A working group will conduct much of its
    business via electronic mail distribution lists but may meet
    periodically to discuss and review task status and progress, to
    resolve specific issues and to direct future activities. ...

Overall, WG *decisions* are supposed to be "consensus of the WG", not 
just those who happen to be present at a given meeting, so I would 
expect that such decisions would be confirmed on the mailing list even 
if initiated at a meeting. At most meetings I've attended, this is how 
action items were confirmed.

So my conclusion is that:
	- activity/participation can happen in either place
	- consensus should include mailing list confirmation

YMMV.

Joe

> so document shepherd and AD should exercise judgement on how to see the
> community consensus/participation.
>
> Marc.
>
>>
>> I realize that this question is going to elicit some vehemence.
>> Please be brief and polite, as you respond.  :-)
>>
>> Barry, Applications AD
>

From hsantos@isdg.net  Tue Nov 27 14:24:16 2012
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E80A21F8754 for <ietf@ietfa.amsl.com>; Tue, 27 Nov 2012 14:24:16 -0800 (PST)
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=-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 i6wqmH1M1LSc for <ietf@ietfa.amsl.com>; Tue, 27 Nov 2012 14:24:15 -0800 (PST)
Received: from catinthebox.net (ftp.catinthebox.net [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 384E121F8665 for <ietf@ietf.org>; Tue, 27 Nov 2012 14:24:14 -0800 (PST)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=1898; t=1354055047; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=ziT0O2BKqJSFOAny2v4oojkI8go=; b=KJtbfMCZ5rtZKTunW4lm 9UsfBn75Cw3qZzYKrq4Fpw788Z4SmcCHJ+ZE9y9/mDNDu+HgsCs0LBrkOlOJqJPB o2tht29nWwhoYN2ToMJubOa/rb5KGtT17wesk2T5YRV9assu9oq/DNCH3nzzWYN8 YotMx41f56OH6XksdH6WdeE=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Tue, 27 Nov 2012 17:24:07 -0500
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from hector.wildcatblog.com ([208.247.131.23]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 1486815324.4245.4692; Tue, 27 Nov 2012 17:24:07 -0500
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=1898; t=1354054686; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=WirurU2 Sk8NDJYrKXeEw26j0R/mMleLTec565I+eUlc=; b=ffs/qpmoxNe/NHIGJytxVGH sLBxGUaSkA7MoTooczzNzXgp4Wo9oLM/N+3l/u4aVV06LAh/LskZAvxicyNCCqy2 wHP+oi5lzLFneYlrrhgInjgK+DEgFe72DqBO4CT/srOFLwLB0+yNy3AvoxoDcoEZ eXaSeyDhtudm+DFqZfX4=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Tue, 27 Nov 2012 17:18:06 -0500
Received: from [192.168.1.101] ([99.3.147.93]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 2085550147.9.7460; Tue, 27 Nov 2012 17:18:05 -0500
Message-ID: <50B53DAE.6050901@isdg.net>
Date: Tue, 27 Nov 2012 17:24:46 -0500
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: IETF discussion list <ietf@ietf.org>
Subject: Re: "IETF work is done on the mailing lists"
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <3E37A498FAFCE1AC87DD66B6@JcK-HP8200.jck.com>
In-Reply-To: <3E37A498FAFCE1AC87DD66B6@JcK-HP8200.jck.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Nov 2012 22:24:16 -0000

+1

John C Klensin wrote:
> 
> --On Tuesday, November 27, 2012 13:00 -0500 Barry Leiba
> <barryleiba@computer.org> wrote:
> 
>> ...
>> So here's my question:
>> Does the community want us to push back on those situations?
>> Does the community believe that the real IETF work is done on
>> the mailing lists, and not in the face-to-face meetings, to
>> the extent that the community would want the IESG to refuse to
>> publish documents whose process went as I've described above,
>> on the basis that IETF process was not properly followed?
>>
>> I realize that this question is going to elicit some vehemence.
>> Please be brief and polite, as you respond.  :-)
> 
> Barry,
> 
> I find myself agreeing with Geoff and Andrew in thinking that
> answer should usually be "yes, push back".  However, I think
> that unusual situations do occur and that different WGs,
> sometimes for good reason, have different styles.  As usual, I
> favor good sense over the rigidity of process purity.  So a
> suggestion: If a WG expects you the IESG to sign off on a
> document based primarily on meeting list discussions, two
> conditions should be met: (i) the minutes had better be
> sufficiently detailed to be persuasive that there really was
> review and that the document really is a WG product, not just
> that of a few authors (or organizations) and (ii) there has to
> be a clear opportunity, after the minutes appear (and Jabber
> logs, etc., are available) for people on the mailing list to
> comment on the presumed meeting decision.  I don't believe that
> more specific guidelines for either of those conditions are
> necessary or desirable other than to say that it is the
> obligation of the WG and its chairs/shepherds to present
> evidence that it persuasive to an IESG that out to be skeptical.
> 
> Speaking for myself only, of course.
> 
>     john
> 

-- 
HLS



From john@jlc.net  Tue Nov 27 15:14:16 2012
Return-Path: <john@jlc.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D0BA621F8897 for <ietf@ietfa.amsl.com>; Tue, 27 Nov 2012 15:14:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.486
X-Spam-Level: 
X-Spam-Status: No, score=-106.486 tagged_above=-999 required=5 tests=[AWL=0.114, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 jEIMucvGNv62 for <ietf@ietfa.amsl.com>; Tue, 27 Nov 2012 15:14:04 -0800 (PST)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by ietfa.amsl.com (Postfix) with ESMTP id F020421F880F for <ietf@ietf.org>; Tue, 27 Nov 2012 15:14:03 -0800 (PST)
Received: by mailhost.jlc.net (Postfix, from userid 104) id 169DB33CF0; Tue, 27 Nov 2012 18:14:04 -0500 (EST)
Date: Tue, 27 Nov 2012 18:14:04 -0500
From: John Leslie <john@jlc.net>
To: Barry Leiba <barryleiba@computer.org>
Subject: Re: "IETF work is done on the mailing lists"
Message-ID: <20121127231404.GC1941@verdi>
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com>
User-Agent: Mutt/1.4.1i
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Nov 2012 23:14:16 -0000

Barry Leiba <barryleiba@computer.org> wrote:
> 
> A number of times since I started in this position in March, documents
> have come to the IESG that prompted me (or another AD) to look into
> the document history for... to find that there's basically no history.
>  We see a string of versions posted, some with significant updates to
> the text, but *no* corresponding mailing list discussion.  Nothing at
> all.  The first we see of the document on the mailing list is a
> working group last call message, which gets somewhere between zero and
> two responses (which say "It's ready."), and then it's sent to the
> responsible AD requesting publication.

    I'm increasingly seeing a "paradigm" where the review happens _before_
adoption as a WG draft. After adoption, there's a great lull until the
deadline for the next IETF week. There tend to be a few, seemingly minor,
edits for a version to be discussed. The meeting time is taken up listing
changes, most of which get no discussion. Lather, rinse, repeat...

   After a few years, the WGCs tire of this, and issue a LastCall. Very
few WG participants reply, mostly being careful not to rock the boat.
The Document Editor, having other fish to fry by now, takes them under
consideration until the next IETF week. The document gets on the agenda,
but the story is pretty much indistinguishable from that of the previous
paragraph.

   Hearing no vocal objections, a WGC dutifully writes up a shepherding
report, saying "broad consensus". The document goes to IETF LastCall,
and gets some possibly less-gentle comments. Now it comes to the IESG
members.

> When I ask the responsible AD or the document shepherd about that, the
> response is that, well, no one commented on the list, but it was
> discussed in the face-to-face meetings.  A look in the minutes of a
> few meetings shows that it was discussed, but, of course, the minutes
> show little or none of the discussion.

   ... which is an honest reply by an overworked WGC. The very thought
of re-opening discussion in the WG sends shivers up his/her spine!

> We accept that, and we review the document as usual, accepting the
> document shepherd's writeup that says that the document has "broad
> consensus of the working group."

   (with several large grains of salt!)

> So here's my question:
> Does the community want us to push back on those situations?

   Speaking for myself, I very much want IESG members to push back on
calling no-visible-discussion "broad consensus".

   But understand, WGCs _don't_ want you to push back. And generally,
neither do the Document Editors. They have followed the rules as they
understood them. And they can point to a long list of RFCs that have
followed essentially the same paradigm.

> Does the community believe that the real IETF work is done on the
> mailing lists, and not in the face-to-face meetings, to the extent
> that the community would want the IESG to refuse to publish documents
> whose process went as I've described above, on the basis that IETF
> process was not properly followed?

   Understanding the dynamics of this paradigm, I wouldn't ask for that.
But I do believe this is a bad way to run a railroad.

   There are WGs where the WGCs prepare status-of-drafts reports. I
think such reports deserve to be formally presented to the Responsible
AD; and that two cycles of no-significant-discussion on-list is a
strong indicator that a new Document Editor is needed. Too often, the
Document Editor is the author of the pre-adoption draft, and lacks any
drive to make significant changes. (This is not an abuse if the WGC
never calls consensus to change anything; but the Document Editors I
consider good don't wait for a WGC declaration.)

   My point, essentially, is that some push-back is good, but it won't
solve the problem: even WG LastCall is often too late to fix this.

--
John Leslie <john@jlc.net>

From d3e3e3@gmail.com  Tue Nov 27 19:09:44 2012
Return-Path: <d3e3e3@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 914A221F8770 for <ietf@ietfa.amsl.com>; Tue, 27 Nov 2012 19:09:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.199
X-Spam-Level: 
X-Spam-Status: No, score=-103.199 tagged_above=-999 required=5 tests=[AWL=0.400, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, 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 V6IE5afYGgLC for <ietf@ietfa.amsl.com>; Tue, 27 Nov 2012 19:09:44 -0800 (PST)
Received: from mail-ia0-f172.google.com (mail-ia0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 054B221F876F for <ietf@ietf.org>; Tue, 27 Nov 2012 19:09:43 -0800 (PST)
Received: by mail-ia0-f172.google.com with SMTP id j26so10340418iaf.31 for <ietf@ietf.org>; Tue, 27 Nov 2012 19:09:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=i1+z25m9qh6gmoTgKa5q87IgT2oZzuJ+0hDlEj2L2Rc=; b=T5kvbXPsvXa7ZaQ3xOoUQ+okt0tOTR36DfsRp8IMeH96vwbMuVlPDcxlHeM8vg0D4j gGIByXrpLGVoqrWQ5pUDTQUln+rAbczbi19m06x4fINJQICfqdEkKm8LGZTbmMHrpDdl 0LWDdLAwmd5h1qQO84CqcFMDu/RUTCn4wCDNdT6H/RFL4oKygpgAB+KOQFZPDb5w4haF kofB7pEowL7zaf61aJiY45p6F9SRQh07H1IgFyvsZfdU+7GiTcB5SyNW3XdNvwLzU9qb l5yhF3cJxQmSaJxTKxirZDPNGyoeKj38LV5wmAlzecdC2e+/AlxPMIXzfn0u342iJGYl cqrw==
Received: by 10.42.180.10 with SMTP id bs10mr15331195icb.39.1354072183337; Tue, 27 Nov 2012 19:09:43 -0800 (PST)
MIME-Version: 1.0
Received: by 10.64.28.209 with HTTP; Tue, 27 Nov 2012 19:09:23 -0800 (PST)
In-Reply-To: <50B52E9C.4090601@isi.edu>
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <4833FEEC-138C-4B70-91DA-722C256B10F5@viagenie.ca> <50B52E9C.4090601@isi.edu>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Tue, 27 Nov 2012 22:09:23 -0500
Message-ID: <CAF4+nEGA1nSiUTgeLGUnoR_S4YNxPOiDkP8coWO38vENagYBZw@mail.gmail.com>
Subject: Re: "IETF work is done on the mailing lists"
To: Barry Leiba <barryleiba@computer.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Nov 2012 03:09:44 -0000

I generally agree with Joe. There should be discussion but the
distribution of that discussion between meeting and mailing list is
not significant; however, there must be sufficient opportunity for
objection or additional comments on the mailing list and, in the case
of discussion at a meeting, the meeting notes should be sufficiently
details to give you a feeling for what discussion occurred.

Thanks,
Donald
=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
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3@gmail.com


On Tue, Nov 27, 2012 at 4:20 PM, Joe Touch <touch@isi.edu> wrote:
>
>
> On 11/27/2012 10:07 AM, Marc Blanchet wrote:
>>
>>
>> Le 2012-11-27 =E0 13:00, Barry Leiba a =E9crit :
>>>
>>>
>>> So here's my question:
>>> Does the community want us to push back on those situations?  Does the
>>> community believe that the real IETF work is done on the mailing
>>> lists, and not in the face-to-face meetings, to the extent that the
>>> community would want the IESG to refuse to publish documents whose
>>> process went as I've described above, on the basis that IETF process
>>> was not properly followed?
>>
>>
>> no. Our work is done both on mailing lists and f2f meetings. As co-chair
>> of a few wg, we have been doing great progress during f2f meeting with
>> high-bandwidth interactions.
>
>
> RFC2418 says that "business" happens in either place:
>
>    ...
>    All working group actions shall be taken in a public forum, and wide
>    participation is encouraged. A working group will conduct much of its
>    business via electronic mail distribution lists but may meet
>    periodically to discuss and review task status and progress, to
>    resolve specific issues and to direct future activities. ...
>
> Overall, WG *decisions* are supposed to be "consensus of the WG", not jus=
t
> those who happen to be present at a given meeting, so I would expect that
> such decisions would be confirmed on the mailing list even if initiated a=
t a
> meeting. At most meetings I've attended, this is how action items were
> confirmed.
>
> So my conclusion is that:
>         - activity/participation can happen in either place
>         - consensus should include mailing list confirmation
>
> YMMV.
>
> Joe
>
>
>> so document shepherd and AD should exercise judgement on how to see the
>> community consensus/participation.
>>
>> Marc.
>>
>>>
>>> I realize that this question is going to elicit some vehemence.
>>> Please be brief and polite, as you respond.  :-)
>>>
>>> Barry, Applications AD
>>
>>
>

From brian.e.carpenter@gmail.com  Wed Nov 28 00:16:10 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8924721F8624 for <ietf@ietfa.amsl.com>; Wed, 28 Nov 2012 00:16:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.691
X-Spam-Level: 
X-Spam-Status: No, score=-101.691 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, 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 4cmDpWcOg73N for <ietf@ietfa.amsl.com>; Wed, 28 Nov 2012 00:16:10 -0800 (PST)
Received: from mail-we0-f172.google.com (mail-we0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id B07A021F843A for <ietf@ietf.org>; Wed, 28 Nov 2012 00:16:09 -0800 (PST)
Received: by mail-we0-f172.google.com with SMTP id r3so4121655wey.31 for <ietf@ietf.org>; Wed, 28 Nov 2012 00:16:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=iWTvDpQ5WDxuvrOZmX4ksqQeN9TzBg3vynP8/CmhbMI=; b=ZdeGmt1+RA/ZXRMR/LXp4dE/VWBcu2HlbyPbqMDJsRL3RvplC/e9OXqcmBFGS/tz9E VdTN2mNxDtig9bmxLMDkTYc0HTHl41eb3UPBv9NEbgaEdBfbMugdDgzU6YnTrwHIbMRe IflUBCBm86VHpIpqU9i1kTW8zsrxRx/fqvZJZgRYTCBamcYJf6vYgSOBYaRs3Y7HvVwX QIBzBro6GhnsPed89UbbC38XQUoBIe7eIyzzj/vNh8wtsS2F0haWMMgFow66yNtOaZHv kjB4xeeUOR4eAeVQMAKIDMQq6v+EjFtdl1qHvQ9cdd4VK4gvbpDYKgV0MtwPicJfgI/h ykYg==
Received: by 10.180.14.162 with SMTP id q2mr31124601wic.21.1354090568799; Wed, 28 Nov 2012 00:16:08 -0800 (PST)
Received: from [192.168.1.65] (host-2-102-217-221.as13285.net. [2.102.217.221]) by mx.google.com with ESMTPS id e6sm5926566wiy.4.2012.11.28.00.16.06 (version=SSLv3 cipher=OTHER); Wed, 28 Nov 2012 00:16:07 -0800 (PST)
Message-ID: <50B5C839.4060909@gmail.com>
Date: Wed, 28 Nov 2012 08:15:53 +0000
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Barry Leiba <barryleiba@computer.org>
Subject: Re: "IETF work is done on the mailing lists"
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com>
In-Reply-To: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Nov 2012 08:16:10 -0000

On 27/11/2012 18:00, Barry Leiba wrote:
...
> So here's my question:
> Does the community want us to push back on those situations?  Does the
> community believe that the real IETF work is done on the mailing
> lists, and not in the face-to-face meetings, to the extent that the
> community would want the IESG to refuse to publish documents whose
> process went as I've described above, on the basis that IETF process
> was not properly followed?

In general, yes please, with room for special cases as John suggested.

At the same time I would like this part of RFC 2418 to be applied:

"  All working group sessions (including those held outside of the IETF
   meetings) shall be reported by making minutes available.  These
   minutes should include the agenda for the session, an account of the
   discussion including any decisions made, and a list of attendees."

The list of attendees is now taken care of by the scanned blue sheets,
but the barely literate "he said, she said" minutes from most WGs
are pretty much useless. For people attempting to participate only
via the mailing list this is a problem.

Let's have more minutes like these:
http://www.ietf.org/proceedings/85/minutes/minutes-85-opsawg

   Brian

From ggx@gigix.net  Wed Nov 28 00:30:32 2012
Return-Path: <ggx@gigix.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 19F0C21F84D4 for <ietf@ietfa.amsl.com>; Wed, 28 Nov 2012 00:30:32 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qXv2LaZezw07 for <ietf@ietfa.amsl.com>; Wed, 28 Nov 2012 00:30:29 -0800 (PST)
Received: from mail-wg0-f44.google.com (mail-wg0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id 774C921F84E3 for <ietf@ietf.org>; Wed, 28 Nov 2012 00:30:26 -0800 (PST)
Received: by mail-wg0-f44.google.com with SMTP id dr13so2554282wgb.13 for <ietf@ietf.org>; Wed, 28 Nov 2012 00:30:25 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=a702pjWqx/qZG4nvUYPK9cTRJCXegks2fnV1HuvEr0w=; b=A+C4bobg1MUapVWAQumVewdGSV8PDH2yGCRho4Wa/9S8lm3Pn7BhPn3tSkTTBE+pXA LHjk6wWknBovhE1xXgKCwB4fmNzJvoZiquDam94aULsQKKJGwYNQi/dZ/9eW4h/ucfx9 WxcRa3EBVgEnyc1AftR8aPsk/fF+QtC4dsINFlGDWMQEuOeNVm7nrHQ/PLMvcL1UWgUD dBBQgXxmjF0yZlPFy1rpDOc20KL0ebSWaCurbnTf93Qea48lwrsU/20z4kfYek2/wZQV Y/VjP0NLhhYVjMy1IefboY67X1UIGmdDia1B0nvt5i5u0C2WgoXq0HdXw7nkyPHR6T1f BDKg==
Received: by 10.216.206.152 with SMTP id l24mr3505100weo.93.1354091425498; Wed, 28 Nov 2012 00:30:25 -0800 (PST)
Received: from ?IPv6:2001:660:330f:a4:3d92:de20:3a6b:8e49? ([2001:660:330f:a4:3d92:de20:3a6b:8e49]) by mx.google.com with ESMTPS id cf6sm5435743wib.3.2012.11.28.00.30.23 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 28 Nov 2012 00:30:24 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to	Informational RFC
From: Luigi Iannone <ggx@gigix.net>
In-Reply-To: <50B4C07C.4010807@innovationslab.net>
Date: Wed, 28 Nov 2012 09:30:23 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <471089C3-7E53-484A-AB2B-CE0E4B9E83A0@gigix.net>
References: <20121113144545.12836.71935.idtracker@ietfa.amsl.com> <50B4C07C.4010807@innovationslab.net>
To: Brian Haberman <brian@innovationslab.net>
X-Mailer: Apple Mail (2.1499)
X-Gm-Message-State: ALoCoQknaVqizR4qPa3O5eL+LGGGwETjLZP1TnsL6YfSZxwccJYgOT2Kydvm8m1WTIb7hXWvYxHC
Cc: ietf@ietf.org, lisp@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Nov 2012 08:30:32 -0000

+1

Thank all for the insightful discussion that took place around this =
draft.=20

Your feedback will be carefully considered to progress the work and we =
welcome any further comment/feedback/help. :-)

ciao

Luigi


On 27 Nov. 2012, at 14:30 , Brian Haberman <brian@innovationslab.net> =
wrote:

> I want to thank everyone who has provided feedback on this draft.  =
Given the issues raised, I am sending the draft back to the LISP WG for =
additional work.  I encourage folks interested in this draft to =
participate on the LISP mailing list.
>=20
> Regards,
> Brian
>=20
> On 11/13/12 9:45 AM, The IESG wrote:
>>=20
>> The IESG has received a request from the Locator/ID Separation =
Protocol
>> WG (lisp) to consider the following document:
>> - 'LISP EID Block'
>>   <draft-ietf-lisp-eid-block-03.txt> as Informational RFC
>>=20
>> The IESG plans to make a decision in the next few weeks, and solicits
>> final comments on this action. Please send substantive comments to =
the
>> ietf@ietf.org mailing lists by 2012-11-27. Exceptionally, comments =
may be
>> sent to iesg@ietf.org instead. In either case, please retain the
>> beginning of the Subject line to allow automated sorting.
>>=20
>> Abstract
>>=20
>>=20
>>    This is a direction to IANA to allocate a /16 IPv6 prefix for use
>>    with the Locator/ID Separation Protocol (LISP).  The prefix will =
be
>>    used for local intra-domain routing and global endpoint
>>    identification, by sites deploying LISP as EID (Endpoint =
IDentifier)
>>    addressing space.
>>=20
>>=20
>>=20
>>=20
>> The file can be obtained via
>> http://datatracker.ietf.org/doc/draft-ietf-lisp-eid-block/
>>=20
>> IESG discussion can be tracked via
>> http://datatracker.ietf.org/doc/draft-ietf-lisp-eid-block/ballot/
>>=20
>>=20
>> No IPR declarations have been submitted directly on this I-D.
>>=20
>>=20
>> _______________________________________________
>> lisp mailing list
>> lisp@ietf.org
>> https://www.ietf.org/mailman/listinfo/lisp
>>=20
>=20
> _______________________________________________
> lisp mailing list
> lisp@ietf.org
> https://www.ietf.org/mailman/listinfo/lisp


From dromasca@avaya.com  Wed Nov 28 01:24:07 2012
Return-Path: <dromasca@avaya.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B816F21F8745 for <ietf@ietfa.amsl.com>; Wed, 28 Nov 2012 01:24:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.266
X-Spam-Level: 
X-Spam-Status: No, score=-103.266 tagged_above=-999 required=5 tests=[AWL=0.333, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, 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 iYOzyFLpQI9F for <ietf@ietfa.amsl.com>; Wed, 28 Nov 2012 01:24:05 -0800 (PST)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by ietfa.amsl.com (Postfix) with ESMTP id B41A921F86AF for <ietf@ietf.org>; Wed, 28 Nov 2012 01:24:04 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAFAPsvoFCHCzI1/2dsb2JhbABEgmzAaYEIgh4BAQEBAxIoNBcEAgEIDQQEAQELFAkHMhQJCAIEARIIGodoAZ4xnACMFRqFT2EDnAmKNoJvgWQXHg
X-IronPort-AV: E=Sophos;i="4.80,759,1344225600"; d="scan'208";a="378042000"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by co300216-co-outbound.net.avaya.com with ESMTP; 28 Nov 2012 04:15:38 -0500
Received: from unknown (HELO DC-US1HCEX3.global.avaya.com) ([135.11.52.22]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 28 Nov 2012 04:00:13 -0500
Received: from AZ-FFEXHC03.global.avaya.com (135.64.58.13) by DC-US1HCEX3.global.avaya.com (135.11.52.22) with Microsoft SMTP Server (TLS) id 8.3.106.1; Wed, 28 Nov 2012 04:23:55 -0500
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC03.global.avaya.com ([135.64.58.13]) with mapi id 14.02.0318.004; Wed, 28 Nov 2012 04:23:53 -0500
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: Melinda Shore <melinda.shore@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: "IETF work is done on the mailing lists"
Thread-Topic: "IETF work is done on the mailing lists"
Thread-Index: AQHNzMkZpIsZvW2c9EmrcbE2PQN0W5f+aLAAgACQuWA=
Date: Wed, 28 Nov 2012 09:23:52 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA023279@AZ-FFEXMB04.global.avaya.com>
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <50B51774.6070607@gmail.com>
In-Reply-To: <50B51774.6070607@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.64.58.45]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Nov 2012 09:24:07 -0000

+1

The length of the written mail list track of a document is only one indicat=
or. It's an important one, but it should not be treated as absolute. Someti=
mes 2-3 people debated one obscure aspect of the document in tens of messag=
es.=20

In the case when a document generated zero or very little discussion on the=
 mail list, and yet the write-up mentions 'broad consensus' I would recomme=
nd to verify what is the 'broad consensus' assessment based upon.=20

Regards,

Dan



> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> Melinda Shore
> Sent: Tuesday, November 27, 2012 9:42 PM
> To: ietf@ietf.org
> Subject: Re: "IETF work is done on the mailing lists"
>=20
> I think the core issue is whether or not there's been adequate review,
> and it seems to me to be appropriate to request volunteers from wg
> participants to review documents before moving them along.
>=20
> Melinda

From john-ietf@jck.com  Wed Nov 28 01:25:19 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7524421F8870 for <ietf@ietfa.amsl.com>; Wed, 28 Nov 2012 01:25:18 -0800 (PST)
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=-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 b4yk+A7tmhv1 for <ietf@ietfa.amsl.com>; Wed, 28 Nov 2012 01:25:17 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 7349E21F87C5 for <ietf@ietf.org>; Wed, 28 Nov 2012 01:25:17 -0800 (PST)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1TddtK-0008lG-HS; Wed, 28 Nov 2012 04:25:14 -0500
Date: Wed, 28 Nov 2012 04:25:05 -0500
From: John C Klensin <john-ietf@jck.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Barry Leiba <barryleiba@computer.org>
Subject: Re: "IETF work is done on the mailing lists"
Message-ID: <59924CD37D50616BA8EB8EF7@JcK-HP8200.jck.com>
In-Reply-To: <50B5C839.4060909@gmail.com>
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <50B5C839.4060909@gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Nov 2012 09:25:19 -0000

--On Wednesday, November 28, 2012 08:15 +0000 Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:

>...
> The list of attendees is now taken care of by the scanned blue
> sheets, but the barely literate "he said, she said" minutes
> from most WGs are pretty much useless. For people attempting
> to participate only via the mailing list this is a problem.
> 
> Let's have more minutes like these:
> http://www.ietf.org/proceedings/85/minutes/minutes-85-opsawg

This is, IMO, a consequence of our developing fancy tools and
then uncritically relying on them.  A Jabber log or real-time
Etherpad may be, and probably is, a very helpful way to keep
real-time notes within a meeting but some WGs have substituted
nearly-unedited versions of them (especially the latter) for
minutes.  They are not minutes, certainly not minutes as
contemplated by RFC 2418, and I sincerely hope that the IESG and
the community push back on those "barely literate" notes before
there is an appeal against a WG decision or document approval
that is based, even in part, on failure of the WG to comply with
that 2418 requirement.

    john


From sm@resistor.net  Wed Nov 28 03:29:21 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 606A921F87CD for <ietf@ietfa.amsl.com>; Wed, 28 Nov 2012 03:29:21 -0800 (PST)
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=-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 UeQDEFR6h5re for <ietf@ietfa.amsl.com>; Wed, 28 Nov 2012 03:29:20 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id BD5F421F85A3 for <ietf@ietf.org>; Wed, 28 Nov 2012 03:29:20 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id qASBTFhq006380; Wed, 28 Nov 2012 03:29:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1354102159; bh=DXjB0fcQhCwnflF1z9aox/CRW7nRQrhPWEgk4q+E5lU=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=k7Oshfw8WU5UEQgRw2VOD3dBQhztCcPssD+SLD4pm7QSYyQvjM0IZ/Y9cFlv9FiTK kWynHJhJ3RK51B1jhqSMdzd6T6z7PpVn5whQ6wyBXcVAdnVauJ5Pes7lfTWbdzFHsV LeaSRXIVGr2CRZ7bI/w9xxgvzSHrRAQZzag2vZt8=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1354102159; i=@resistor.net; bh=DXjB0fcQhCwnflF1z9aox/CRW7nRQrhPWEgk4q+E5lU=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=c0AOYZidSrVMXvfkm/1DVKTUoruxs+OGgyczvbkTWlfl/VjwmykuOD/CzPfswbKkg uSLJPrFpYR532UWiyotn4C4sb27y95udZp5WD7WPbeL7vIYF5P9BFmHQBRYm7fLSw/ AanP7OtzGZluQawf1Xaa61gq2pfaJl9HTNRlR9iA=
Message-Id: <6.2.5.6.2.20121128023905.0afdcde0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 28 Nov 2012 03:28:37 -0800
To: John C Klensin <john-ietf@jck.com>
From: SM <sm@resistor.net>
Subject: Barely literate minutes (was: "IETF work is done on the mailing lists")
In-Reply-To: <59924CD37D50616BA8EB8EF7@JcK-HP8200.jck.com>
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <50B5C839.4060909@gmail.com> <59924CD37D50616BA8EB8EF7@JcK-HP8200.jck.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Nov 2012 11:29:21 -0000

Hi John,

[subject line mutated to reflect topic being discussed]

At 01:25 28-11-2012, John C Klensin wrote:
>This is, IMO, a consequence of our developing fancy tools and
>then uncritically relying on them.  A Jabber log or real-time
>Etherpad may be, and probably is, a very helpful way to keep
>real-time notes within a meeting but some WGs have substituted
>nearly-unedited versions of them (especially the latter) for
>minutes.  They are not minutes, certainly not minutes as

Yes.

Nobody likes to write minutes.  Very few people volunteer their free 
time to do them (thanks to John Leslie for scribing the IESG 
minutes).  When there is a discussion about producing minutes people 
come up with proposals for fancy tools.  This is where someone says: 
"Etherpad can do that".  There is a moment of silence when somebody 
finds out that there's nobody using Etherpad to take notes about 
what's going on.  Who would have thought that these fancy tools 
cannot work without people? :-)

>contemplated by RFC 2418, and I sincerely hope that the IESG and
>the community push back on those "barely literate" notes before
>there is an appeal against a WG decision or document approval
>that is based, even in part, on failure of the WG to comply with
>that 2418 requirement.

The community is too lethargic to push back on those "barely 
literate" notes.  One of these days there will be such an appeal.

Regards,
-sm 


From randy@psg.com  Wed Nov 28 03:57:22 2012
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A601321F8584 for <ietf@ietfa.amsl.com>; Wed, 28 Nov 2012 03:57:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.159
X-Spam-Level: 
X-Spam-Status: No, score=-2.159 tagged_above=-999 required=5 tests=[AWL=0.441,  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 d4qnqGsEPZ9W for <ietf@ietfa.amsl.com>; Wed, 28 Nov 2012 03:57:22 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 55FA621F8517 for <ietf@ietf.org>; Wed, 28 Nov 2012 03:57:22 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from <randy@psg.com>) id 1TdgGT-000591-6r; Wed, 28 Nov 2012 11:57:18 +0000
Date: Wed, 28 Nov 2012 20:57:14 +0900
Message-ID: <m2mwy26iud.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: John Leslie <john@jlc.net>
Subject: Re: "IETF work is done on the mailing lists"
In-Reply-To: <20121127231404.GC1941@verdi>
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <20121127231404.GC1941@verdi>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Cc: Barry Leiba <barryleiba@computer.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Nov 2012 11:57:22 -0000

> I'm increasingly seeing a "paradigm" where the review happens _before_
> adoption as a WG draft.

and one consequence is that the design gets done outside of the ietf
process.

randy

From ynir@checkpoint.com  Wed Nov 28 04:42:33 2012
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E4BDE21F8570 for <ietf@ietfa.amsl.com>; Wed, 28 Nov 2012 04:42:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.669
X-Spam-Level: 
X-Spam-Status: No, score=-9.669 tagged_above=-999 required=5 tests=[AWL=0.929,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 JGePjvq9m4nn for <ietf@ietfa.amsl.com>; Wed, 28 Nov 2012 04:42:33 -0800 (PST)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 06C6921F8565 for <ietf@ietf.org>; Wed, 28 Nov 2012 04:42:32 -0800 (PST)
Received: from IL-EX10.ad.checkpoint.com ([194.29.34.147]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id qASCgIPI024487; Wed, 28 Nov 2012 14:42:19 +0200
X-CheckPoint: {50B606BF-0-1B221DC2-2FFFF}
Received: from IL-EX10.ad.checkpoint.com ([169.254.2.194]) by IL-EX10.ad.checkpoint.com ([169.254.2.194]) with mapi id 14.02.0318.004; Wed, 28 Nov 2012 14:41:15 +0200
From: Yoav Nir <ynir@checkpoint.com>
To: Randy Bush <randy@psg.com>
Subject: Re: "IETF work is done on the mailing lists"
Thread-Topic: "IETF work is done on the mailing lists"
Thread-Index: AQHNzMkvuHQpFei0akq/z4gI6x0ECJf+Lq8AgADVOgCAAAw9AA==
Date: Wed, 28 Nov 2012 12:41:14 +0000
Message-ID: <4613980CFC78314ABFD7F85CC30277210245BE@IL-EX10.ad.checkpoint.com>
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <20121127231404.GC1941@verdi> <m2mwy26iud.wl%randy@psg.com>
In-Reply-To: <m2mwy26iud.wl%randy@psg.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.31.20.24]
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
Content-Type: text/plain; charset="us-ascii"
Content-ID: <048C92421B8F114E8091E79382AF92DD@ad.checkpoint.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Barry Leiba <barryleiba@computer.org>, John Leslie <john@jlc.net>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Nov 2012 12:42:34 -0000

On Nov 28, 2012, at 1:57 PM, Randy Bush <randy@psg.com> wrote:

>> I'm increasingly seeing a "paradigm" where the review happens _before_
>> adoption as a WG draft.
>=20
> and one consequence is that the design gets done outside of the ietf
> process.

+1



From Chris.Dearlove@baesystems.com  Wed Nov 28 05:31:41 2012
Return-Path: <Chris.Dearlove@baesystems.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6815B21F84B9 for <ietf@ietfa.amsl.com>; Wed, 28 Nov 2012 05:31:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 pij3EjsA1kFC for <ietf@ietfa.amsl.com>; Wed, 28 Nov 2012 05:31:40 -0800 (PST)
Received: from ukmta3.baesystems.com (ukmta3.baesystems.com [20.133.40.55]) by ietfa.amsl.com (Postfix) with ESMTP id 748FF21F8431 for <ietf@ietf.org>; Wed, 28 Nov 2012 05:31:40 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.84,177,1355097600"; d="scan'208";a="245954532"
Received: from unknown (HELO baemasodc004.greenlnk.net) ([10.108.36.11]) by Baemasodc001ir.sharelnk.net with ESMTP; 28 Nov 2012 13:31:39 +0000
Received: from GLKXH0004V.GREENLNK.net ([10.109.2.35]) by baemasodc004.greenlnk.net (Switch-3.4.4/Switch-3.4.4) with ESMTP id qASDVcmP011789 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 28 Nov 2012 13:31:39 GMT
Received: from GLKXM0002V.GREENLNK.net ([169.254.2.7]) by GLKXH0004V.GREENLNK.net ([10.109.2.35]) with mapi id 14.02.0309.002; Wed, 28 Nov 2012 13:31:39 +0000
From: "Dearlove, Christopher (UK)" <Chris.Dearlove@baesystems.com>
To: Randy Bush <randy@psg.com>, John Leslie <john@jlc.net>
Subject: RE: "IETF work is done on the mailing lists"
Thread-Topic: "IETF work is done on the mailing lists"
Thread-Index: AQHNzMkNhksJbZ+POUOdE+KWmMdmspf+UDYAgADVOgCAABnF4A==
Date: Wed, 28 Nov 2012 13:31:38 +0000
Message-ID: <B31EEDDDB8ED7E4A93FDF12A4EECD30D24FCD17F@GLKXM0002V.GREENLNK.net>
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <20121127231404.GC1941@verdi> <m2mwy26iud.wl%randy@psg.com>
In-Reply-To: <m2mwy26iud.wl%randy@psg.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.109.62.6]
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Barry Leiba <barryleiba@computer.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Nov 2012 13:31:41 -0000

I've certainly been to BOFs where I might think "this is a new topic" to di=
scover that it's actually indistinguishable from a WG I just hadn't attende=
d before - the documents already exist, and the inner circle of who knows w=
ho is already in place.

(The inner circle effect can be seen by examining minutes and seeing how of=
ten people are identified just by forename, because anyone reading the minu=
tes is expected to know who's who in this group. Even the set of minutes Br=
ian recommended had one such occurrence.)

--=20
Christopher Dearlove
Senior Principal Engineer, Communications Group
Communications, Networks and Image Analysis Capability
BAE Systems Advanced Technology Centre
West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
Tel: +44 1245 242194=A0|  Fax: +44 1245 242124
chris.dearlove@baesystems.com | http://www.baesystems.com

BAE Systems (Operations) Limited
Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre, =
Farnborough, Hants, GU14 6YU, UK
Registered in England & Wales No: 1996687


-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Ran=
dy Bush
Sent: 28 November 2012 11:57
To: John Leslie
Cc: Barry Leiba; IETF discussion list
Subject: Re: "IETF work is done on the mailing lists"

----------------------! WARNING ! ----------------------
This message originates from outside our organisation,
either from an external partner or from the internet.
Keep this in mind if you answer this message.
Follow the 'Report Suspicious Emails' link on IT matters
for instructions on reporting suspicious email messages.
--------------------------------------------------------

> I'm increasingly seeing a "paradigm" where the review happens _before_
> adoption as a WG draft.

and one consequence is that the design gets done outside of the ietf
process.

randy


********************************************************************
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.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.
********************************************************************


From ford@isoc.org  Wed Nov 28 07:00:43 2012
Return-Path: <ford@isoc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D97C121F84BC for <ietf@ietfa.amsl.com>; Wed, 28 Nov 2012 07:00:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.299
X-Spam-Level: 
X-Spam-Status: No, score=-102.299 tagged_above=-999 required=5 tests=[AWL=-1.300, BAYES_50=0.001, RCVD_IN_DNSWL_LOW=-1, 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 OT7Bk+Sq-lnF for <ietf@ietfa.amsl.com>; Wed, 28 Nov 2012 07:00:43 -0800 (PST)
Received: from smtp117.iad.emailsrvr.com (smtp117.iad.emailsrvr.com [207.97.245.117]) by ietfa.amsl.com (Postfix) with ESMTP id A984121F847C for <ietf@ietf.org>; Wed, 28 Nov 2012 07:00:43 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp51.relay.iad1a.emailsrvr.com (SMTP Server) with ESMTP id 1C12238010 for <ietf@ietf.org>; Wed, 28 Nov 2012 10:00:43 -0500 (EST)
X-Virus-Scanned: OK
Received: by smtp51.relay.iad1a.emailsrvr.com (Authenticated sender: ford-AT-isoc.org) with ESMTPSA id BABEF3800A for <ietf@ietf.org>; Wed, 28 Nov 2012 10:00:42 -0500 (EST)
From: Matthew Ford <ford@isoc.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: ANRP 2013 - please nominate
Message-Id: <2250F07E-7616-4AA0-8CE7-B7FA0102D470@isoc.org>
Date: Wed, 28 Nov 2012 15:00:42 +0000
To: "ietf@ietf.org Discussion" <ietf@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
X-Mailer: Apple Mail (2.1499)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Nov 2012 15:00:44 -0000

Hi,

Nominations for the 2013 ANRP awards are due by this Friday 30th =
November, so if you've read a great paper this year, please send us the =
details using the submission system at:

	http://irtf.org/anrp/2013/

or exceptionally, by email to anrp@irtf.org.

Thanks,
Mat=

From tglassey@earthlink.net  Wed Nov 28 07:12:50 2012
Return-Path: <tglassey@earthlink.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E8C9621F885C for <ietf@ietfa.amsl.com>; Wed, 28 Nov 2012 07:12:49 -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 srzuchv5j+2V for <ietf@ietfa.amsl.com>; Wed, 28 Nov 2012 07:12:49 -0800 (PST)
Received: from elasmtp-galgo.atl.sa.earthlink.net (elasmtp-galgo.atl.sa.earthlink.net [209.86.89.61]) by ietfa.amsl.com (Postfix) with ESMTP id 29F2021F886A for <ietf@ietf.org>; Wed, 28 Nov 2012 07:12:49 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=VBLNkAfF2k2wEnUho6CFzt+QXYjbGkLfmu4w4SrXW3dlYecXHtDVwrxCtjn/l6wc; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [67.180.133.21] (helo=[192.168.15.2]) by elasmtp-galgo.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <tglassey@earthlink.net>) id 1TdjJg-0002Kt-L5 for ietf@ietf.org; Wed, 28 Nov 2012 10:12:48 -0500
Message-ID: <50B629F0.5010506@earthlink.net>
Date: Wed, 28 Nov 2012 07:12:48 -0800
From: tglassey <tglassey@earthlink.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: "IETF work is done on the mailing lists"
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <50B5C839.4060909@gmail.com>
In-Reply-To: <50B5C839.4060909@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec7944cd63cabb42c1f3e7d5fcc9c1f9967e350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 67.180.133.21
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Nov 2012 15:12:50 -0000

On 11/28/2012 12:15 AM, Brian E Carpenter wrote:
> On 27/11/2012 18:00, Barry Leiba wrote:
> ...
>> So here's my question:
>> Does the community want us to push back on those situations?  Does the
>> community believe that the real IETF work is done on the mailing
>> lists, and not in the face-to-face meetings, to the extent that the
>> community would want the IESG to refuse to publish documents whose
>> process went as I've described above, on the basis that IETF process
>> was not properly followed?
> In general, yes please, with room for special cases as John suggested.
>
> At the same time I would like this part of RFC 2418 to be applied:
>
> "  All working group sessions (including those held outside of the IETF
>     meetings) shall be reported by making minutes available.  These
>     minutes should include the agenda for the session, an account of the
>     discussion including any decisions made, and a list of attendees."
>
> The list of attendees is now taken care of by the scanned blue sheets,
> but the barely literate "he said, she said" minutes from most WGs
> are pretty much useless. For people attempting to participate only
> via the mailing list this is a problem.
>
> Let's have more minutes like these:
> http://www.ietf.org/proceedings/85/minutes/minutes-85-opsawg
>
>     Brian
Brian - does this include conversations between principals of a WG 
effort who are conversing about genesis in that WG outside of the IETF 
mailing list - i.e. what happens to conversations inside a development 
team ? How is that genesis and creative power harnessed for inclusion 
into the IETF process?

Todd
>
> -----
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2013.0.2793 / Virus Database: 2629/5921 - Release Date: 11/26/12
>
>


-- 
Regards TSG
"Ex-Cruce-Leo"

//Confidential Mailing - Please destroy this if you are not the intended recipient.


From moore@network-heretics.com  Wed Nov 28 07:18:45 2012
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ADA9721F89DA for <ietf@ietfa.amsl.com>; Wed, 28 Nov 2012 07:18:45 -0800 (PST)
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, 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 8+i9St0KvdVc for <ietf@ietfa.amsl.com>; Wed, 28 Nov 2012 07:18:45 -0800 (PST)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id DC32021F896E for <ietf@ietf.org>; Wed, 28 Nov 2012 07:18:44 -0800 (PST)
Received: from compute1.internal (compute1.nyi.mail.srv.osa [10.202.2.41]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 7D341212F1 for <ietf@ietf.org>; Wed, 28 Nov 2012 10:18:44 -0500 (EST)
Received: from frontend1.nyi.mail.srv.osa ([10.202.2.160]) by compute1.internal (MEProxy); Wed, 28 Nov 2012 10:18:44 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=Gdx7b4/tD+lf/6WL8TC5dj Wnoh0=; b=cc0NUskzhWTYVngAp9Y1bR+OXrK07WdJg+PWSIXs4TBZ8vypt0Y4rV FRcHcl4JQo61HLTGZJyYD+FG5IYdw69rjcHVDkztEJzBlyONvAV28m4/JHWmQh8/ ac6i4V0/Frsm3buuIYL1pYL9rl5z6aVBF6/eanaShD16UxdMrOZ8Q=
X-Sasl-enc: aq3Hypls7veJ9Hzlpu13lT1NrvRQ9cL8dB2TBt1iW17M 1354115924
Received: from [192.168.1.20] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id D2B598E05A7; Wed, 28 Nov 2012 10:18:43 -0500 (EST)
Message-ID: <50B62B2D.1020603@network-heretics.com>
Date: Wed, 28 Nov 2012 10:18:05 -0500
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: "IETF work is done on the mailing lists"
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com>
In-Reply-To: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Nov 2012 15:18:45 -0000

On 11/27/2012 01:00 PM, Barry Leiba wrote:
> This brings up a question that I have as an AD: A number of times 
> since I started in this position in March, documents have come to the 
> IESG that prompted me (or another AD) to look into the document 
> history for... to find that there's basically no history. We see a 
> string of versions posted, some with significant updates to the text, 
> but *no* corresponding mailing list discussion. Nothing at all. The 
> first we see of the document on the mailing list is a working group 
> last call message, which gets somewhere between zero and two responses 
> (which say "It's ready."), and then it's sent to the responsible AD 
> requesting publication. When I ask the responsible AD or the document 
> shepherd about that, the response is that, well, no one commented on 
> the list, but it was discussed in the face-to-face meetings. A look in 
> the minutes of a few meetings shows that it was discussed, but, of 
> course, the minutes show little or none of the discussion. We accept 
> that, and we review the document as usual, accepting the document 
> shepherd's writeup that says that the document has "broad consensus of 
> the working group." So here's my question: Does the community want us 
> to push back on those situations?

Please, please, please push back on those discussions.

Far too many documents are being represented as WG consensus, and then 
IETF consensus, when there's nothing of the sort.   This degrades the 
overall quality of IETF output, confuses the community of people who use 
IETF standards, and potentially does harm to the Internet by promoting 
use of protocols that haven't been carefully vetted.

Simply presenting a document at a face-to-face meeting and asking people 
to raise hands or hum in approval isn't sufficient.   A necessary 
condition for IESG consideration of a WG document should be that several 
people have posted to the WG mailing list that they've read it, and that 
they consider it desirable and sound.

Keith




From wesley.george@twcable.com  Wed Nov 28 07:38:22 2012
Return-Path: <wesley.george@twcable.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 97E6121F8896 for <ietf@ietfa.amsl.com>; Wed, 28 Nov 2012 07:38:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.237
X-Spam-Level: 
X-Spam-Status: No, score=0.237 tagged_above=-999 required=5 tests=[AWL=0.700,  BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368]
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 P6C8iPUjLcke for <ietf@ietfa.amsl.com>; Wed, 28 Nov 2012 07:38:22 -0800 (PST)
Received: from cdpipgw02.twcable.com (cdpipgw02.twcable.com [165.237.59.23]) by ietfa.amsl.com (Postfix) with ESMTP id 0142D21F8880 for <ietf@ietf.org>; Wed, 28 Nov 2012 07:38:21 -0800 (PST)
X-SENDER-IP: 10.136.163.11
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.84,179,1355115600"; d="scan'208";a="459833229"
Received: from unknown (HELO PRVPEXHUB02.corp.twcable.com) ([10.136.163.11]) by cdpipgw02.twcable.com with ESMTP/TLS/RC4-MD5; 28 Nov 2012 10:35:35 -0500
Received: from PRVPEXVS15.corp.twcable.com ([10.136.163.79]) by PRVPEXHUB02.corp.twcable.com ([10.136.163.11]) with mapi; Wed, 28 Nov 2012 10:36:15 -0500
From: "George, Wes" <wesley.george@twcable.com>
To: John Leslie <john@jlc.net>, Barry Leiba <barryleiba@computer.org>
Date: Wed, 28 Nov 2012 10:36:29 -0500
Subject: When to adopt a draft as a WG doc (was RE: "IETF work is done on the mailing lists")
Thread-Topic: When to adopt a draft as a WG doc (was RE: "IETF work is done on the mailing lists")
Thread-Index: Ac3NfiDalgtXJNhmRxqTfOWxkMjAGA==
Message-ID: <2671C6CDFBB59E47B64C10B3E0BD5923033897C9BF@PRVPEXVS15.corp.twcable.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Nov 2012 15:38:22 -0000

> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> John Leslie
>
>     I'm increasingly seeing a "paradigm" where the review happens
> _before_ adoption as a WG draft. After adoption, there's a great lull
> until the deadline for the next IETF week. There tend to be a few,
> seemingly minor, edits for a version to be discussed. The meeting time
> is taken up listing changes, most of which get no discussion. Lather,
> rinse, repeat...

[WEG] I've seen several discussions recently across WG lists, WG chairs lis=
t, etc about this specific topic, and it's leading me to believe that we do=
 not have adequate guidance for either WG chairs or participants on when it=
 is generally appropriate to adopt a draft as a WG document. I see 3 basic =
variants just among the WGs that I'm actively involved in:
1) adopt early because the draft is talking about a subject the WG wants to=
 work on (may or may not be an official charter milestone), and then refine=
 a relatively rough draft through several I-D-ietf-[wg]-* revisions before =
WGLC
2) adopt after several revisions of I-D-[person]-[wg]-* because there has b=
een enough discussion to make the chairs believe that the WG has interest o=
r the draft has evolved into something the WG sees as useful/in charter; Th=
en there are only minor tweaks in the draft up until WGLC (the above model)
3) don't adopt the draft until some defined criteria are met (e.g. interope=
rable implementations), meaning that much of the real work gets done in the=
 individual version

It seems to me that these variants are dependent on the people in the WG, t=
he workload of the group, the chairs, past precedent, AD preferences, etc. =
It makes it difficult on both draft editors and those seeking to follow the=
 discussion for there to be such a disparity from WG to WG on when to adopt=
 drafts. I'm not convinced that there is a one-size-fits-all solution here,=
 but it might be nice to coalesce a little from where we are today.
So I wonder if perhaps we need clearer guidance on what the process is actu=
ally supposed to look like and why. If someone can point to a document that=
 gives guidance here, then perhaps we all need to be more conscientious abo=
ut ensuring that the WGs we participate in are following the available guid=
ance on the matter.

Wes George

This E-mail and any of its attachments may contain Time Warner Cable propri=
etary information, which is privileged, confidential, or subject to copyrig=
ht belonging to Time Warner Cable. This E-mail is intended solely for the u=
se of the individual or entity to which it is addressed. If you are not the=
 intended recipient of this E-mail, you are hereby notified that any dissem=
ination, distribution, copying, or action taken in relation to the contents=
 of and attachments to this E-mail is strictly prohibited and may be unlawf=
ul. If you have received this E-mail in error, please notify the sender imm=
ediately and permanently delete the original and any copy of this E-mail an=
d any printout.

From dhc@dcrocker.net  Wed Nov 28 07:50:16 2012
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E802F21F887D for <ietf@ietfa.amsl.com>; Wed, 28 Nov 2012 07:50:16 -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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RAE7aHNnrcv0 for <ietf@ietfa.amsl.com>; Wed, 28 Nov 2012 07:50:16 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 372A421F8788 for <ietf@ietf.org>; Wed, 28 Nov 2012 07:50:16 -0800 (PST)
Received: from [192.168.1.9] (adsl-67-127-190-125.dsl.pltn13.pacbell.net [67.127.190.125]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id qASFo7h4018733 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 28 Nov 2012 07:50:08 -0800
Message-ID: <50B632AD.7070909@dcrocker.net>
Date: Wed, 28 Nov 2012 07:50:05 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: Barry Leiba <barryleiba@computer.org>
Subject: Re: "IETF work is done on the mailing lists"
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com>
In-Reply-To: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Wed, 28 Nov 2012 07:50:08 -0800 (PST)
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Nov 2012 15:50:17 -0000

On 11/27/2012 10:00 AM, Barry Leiba wrote:
>   We see a string of versions posted, some with significant updates to
> the text, but *no* corresponding mailing list discussion.  Nothing at
> all.
...
> When I ask the responsible AD or the document shepherd about that, the
> response is that, well, no one commented on the list, but it was
> discussed in the face-to-face meetings.
...
> We accept that, and we review the document as usual, accepting the
> document shepherd's writeup that says that the document has "broad
> consensus of the working group."
>
> So here's my question:
> Does the community want us to push back on those situations?


Just to add my own input to this:

'Want' is almost irrelevant. In formal terms, it does not matter what 
was discussed at the face-to-face nor what notes are taken about it.

The formal rules of the IETF are that mailing lists are where formal 
decisions are made.

The working group needs to establish /explicit/ support for changes /on 
the list/.

You are reporting that, in formal terms, the IESG has been approving 
documents for which there is no formal record of community support...


d/

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From trammell@tik.ee.ethz.ch  Wed Nov 28 07:55:08 2012
Return-Path: <trammell@tik.ee.ethz.ch>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E25CA21F88E1 for <ietf@ietfa.amsl.com>; Wed, 28 Nov 2012 07:55:08 -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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B9mpAsHt4MeJ for <ietf@ietfa.amsl.com>; Wed, 28 Nov 2012 07:55:07 -0800 (PST)
Received: from smtp.ee.ethz.ch (smtp.ee.ethz.ch [129.132.2.219]) by ietfa.amsl.com (Postfix) with ESMTP id 4AE4A21F88DA for <ietf@ietf.org>; Wed, 28 Nov 2012 07:55:07 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by smtp.ee.ethz.ch (Postfix) with ESMTP id 98532D930B; Wed, 28 Nov 2012 16:55:01 +0100 (MET)
X-Virus-Scanned: by amavisd-new on smtp.ee.ethz.ch
Received: from smtp.ee.ethz.ch ([127.0.0.1]) by localhost (.ee.ethz.ch [127.0.0.1]) (amavisd-new, port 10024) with LMTP id BsBwEMoV4q0K; Wed, 28 Nov 2012 16:55:01 +0100 (MET)
Received: from pb-10243.ethz.ch (pb-10243.ethz.ch [82.130.102.152]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: briant) by smtp.ee.ethz.ch (Postfix) with ESMTPSA id 3778CD9304; Wed, 28 Nov 2012 16:55:01 +0100 (MET)
Subject: Re: When to adopt a draft as a WG doc (was RE: "IETF work is done on the mailing lists")
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=us-ascii
From: Brian Trammell <trammell@tik.ee.ethz.ch>
In-Reply-To: <2671C6CDFBB59E47B64C10B3E0BD5923033897C9BF@PRVPEXVS15.corp.twcable.com>
Date: Wed, 28 Nov 2012 16:55:00 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <9A890349-7577-4365-9F24-C2B3B71A1135@tik.ee.ethz.ch>
References: <2671C6CDFBB59E47B64C10B3E0BD5923033897C9BF@PRVPEXVS15.corp.twcable.com>
To: "George, Wes" <wesley.george@twcable.com>
X-Mailer: Apple Mail (2.1283)
Cc: Barry Leiba <barryleiba@computer.org>, John Leslie <john@jlc.net>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Nov 2012 15:55:09 -0000

Hi, Wes, all,

+1 to "no one-size-fits-all".=20

A model that's worked well in a few groups I've been involved in is =
something between (2) and (3), where the defined criteria is "complete =
enough that interoperable implementations could conceivably be =
produced", a slightly lower bar; with the added caveat that discussion =
of the developing individual draft is encouraged on the working group =
list, and will be given second-preference agenda time at meetings.

This allows a smaller group around the initial authors to build a =
coherent proposal, without shutting those out from the process who are =
motivated to contribute. The WG -00 then has at least plausible =
suggested answers to the most obvious questions raised, and can be =
modified by the WG from there (or, indeed, eventually rejected if it =
turns out the broad approach is incapable of drawing consensus support). =
This looks basically like a design team approach with self-appointed =
design teams.

This approach would tend to work better for incremental or =
self-contained work around an already-elaborated framework or theme.

Best regards,

Brian

On 28 Nov 2012, at 16:36 , George, Wes wrote:

>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf =
Of
>> John Leslie
>>=20
>>    I'm increasingly seeing a "paradigm" where the review happens
>> _before_ adoption as a WG draft. After adoption, there's a great lull
>> until the deadline for the next IETF week. There tend to be a few,
>> seemingly minor, edits for a version to be discussed. The meeting =
time
>> is taken up listing changes, most of which get no discussion. Lather,
>> rinse, repeat...
>=20
> [WEG] I've seen several discussions recently across WG lists, WG =
chairs list, etc about this specific topic, and it's leading me to =
believe that we do not have adequate guidance for either WG chairs or =
participants on when it is generally appropriate to adopt a draft as a =
WG document. I see 3 basic variants just among the WGs that I'm actively =
involved in:
> 1) adopt early because the draft is talking about a subject the WG =
wants to work on (may or may not be an official charter milestone), and =
then refine a relatively rough draft through several I-D-ietf-[wg]-* =
revisions before WGLC
> 2) adopt after several revisions of I-D-[person]-[wg]-* because there =
has been enough discussion to make the chairs believe that the WG has =
interest or the draft has evolved into something the WG sees as =
useful/in charter; Then there are only minor tweaks in the draft up =
until WGLC (the above model)
> 3) don't adopt the draft until some defined criteria are met (e.g. =
interoperable implementations), meaning that much of the real work gets =
done in the individual version
>=20
> It seems to me that these variants are dependent on the people in the =
WG, the workload of the group, the chairs, past precedent, AD =
preferences, etc. It makes it difficult on both draft editors and those =
seeking to follow the discussion for there to be such a disparity from =
WG to WG on when to adopt drafts. I'm not convinced that there is a =
one-size-fits-all solution here, but it might be nice to coalesce a =
little from where we are today.
> So I wonder if perhaps we need clearer guidance on what the process is =
actually supposed to look like and why. If someone can point to a =
document that gives guidance here, then perhaps we all need to be more =
conscientious about ensuring that the WGs we participate in are =
following the available guidance on the matter.
>=20
> Wes George
>=20
> This E-mail and any of its attachments may contain Time Warner Cable =
proprietary information, which is privileged, confidential, or subject =
to copyright belonging to Time Warner Cable. This E-mail is intended =
solely for the use of the individual or entity to which it is addressed. =
If you are not the intended recipient of this E-mail, you are hereby =
notified that any dissemination, distribution, copying, or action taken =
in relation to the contents of and attachments to this E-mail is =
strictly prohibited and may be unlawful. If you have received this =
E-mail in error, please notify the sender immediately and permanently =
delete the original and any copy of this E-mail and any printout.


From barryleiba@gmail.com  Wed Nov 28 07:58:57 2012
Return-Path: <barryleiba@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C905B21F88D0 for <ietf@ietfa.amsl.com>; Wed, 28 Nov 2012 07:58:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.931
X-Spam-Level: 
X-Spam-Status: No, score=-102.931 tagged_above=-999 required=5 tests=[AWL=0.046, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, 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 iPWipsOFqEqx for <ietf@ietfa.amsl.com>; Wed, 28 Nov 2012 07:58:57 -0800 (PST)
Received: from mail-ye0-f172.google.com (mail-ye0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id 3053621F883B for <ietf@ietf.org>; Wed, 28 Nov 2012 07:58:57 -0800 (PST)
Received: by mail-ye0-f172.google.com with SMTP id m14so2216357yen.31 for <ietf@ietf.org>; Wed, 28 Nov 2012 07:58:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=SrLBhZbmCWtPHGMWMNk7tI9FfTzEZo57hI/7wFLnzdY=; b=NWpIiy43GoMLqmWqedfk9Pip3EKPS86++yDFvAoEBBiAGzL0ZScqO90/2gGbb3LtaJ 0lo+YhadLKSn7nXEQx1diL9YujJgtSxCgUT4VNbc6xDx/sqfm+MhfLS2FM4ciYggj2x2 DdKBHE92rZBfxW4bIwXXkMSsNap4gtlyrt1xORlVGZnknzRM3qJ0nQzstYpZfk16Tau8 z72vx6OFo/EISerDHhPgQZ4/xGRbvFFa41Dr0/Yu/CA32YG35y9/4B8oE8I7FR7hckVJ Akfy8zI0bvrVIBzHKATm0UdcsmGG4czrZj1k8Htw2agSo1ZXaOwXjVQYVuvzvBln/Agd O8ZA==
MIME-Version: 1.0
Received: by 10.58.221.130 with SMTP id qe2mr30039949vec.14.1354118336593; Wed, 28 Nov 2012 07:58:56 -0800 (PST)
Sender: barryleiba@gmail.com
Received: by 10.58.28.231 with HTTP; Wed, 28 Nov 2012 07:58:56 -0800 (PST)
In-Reply-To: <2671C6CDFBB59E47B64C10B3E0BD5923033897C9BF@PRVPEXVS15.corp.twcable.com>
References: <2671C6CDFBB59E47B64C10B3E0BD5923033897C9BF@PRVPEXVS15.corp.twcable.com>
Date: Wed, 28 Nov 2012 10:58:56 -0500
X-Google-Sender-Auth: Lbpe4frFEXoZ4FViBmocOCvkkK4
Message-ID: <CALaySJLT=6RTZahqB1LO_Aw=7sAMiyrXK=xacwrBgLieZhqeDw@mail.gmail.com>
Subject: Re: When to adopt a draft as a WG doc (was RE: "IETF work is done on the mailing lists")
From: Barry Leiba <barryleiba@computer.org>
To: "George, Wes" <wesley.george@twcable.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Nov 2012 15:58:57 -0000

> we do not have adequate guidance for either WG chairs or participants on
> when it is generally appropriate to adopt a draft as a WG document.
...
> It seems to me that these variants are dependent on the people in the WG,
> the workload of the group, the chairs, past precedent, AD preferences, etc.
> It makes it difficult on both draft editors and those seeking to follow the
> discussion for there to be such a disparity from WG to WG on when to adopt
> drafts. I'm not convinced that there is a one-size-fits-all solution here, but it
> might be nice to coalesce a little from where we are today.
>
> So I wonder if perhaps we need clearer guidance on what the process is
> actually supposed to look like and why.

Let's start with a basic point and work from there:
There is no formal process that involves "adopting" anything.  Working
group chairs appoint document editors (this is in RFC 2418, Section
6.3).  There is nothing anywhere that specifies how the first version
of a WG document is formed.  One mechanism could be that the charter
says that the WG will develop a Lightweight Modular Network Operations
Protocol, so the WGCs say, "We appoint Wes George as the document
editor for the LMNOP doc."  Wes then goes off and creates
draft-ietf-xyzwg-lmnop-00 based on discussion so far, or even based on
his own opinion of a good start for the protocol spec.  Discussion
ensues and Wes makes changes based on the discussion, because, being a
good document editor, he knows how to make the document reflect what
the WG wants.  A couple of issues are contentious, and the WGCs handle
the evaluation of consensus for those, and Wes incorporates that.  In
the end, the WG as a whole thinks that the document accurately
reflects WG rough consensus, and the chairs request publication.

Another model is that two or more people submit candidate documents,
and the WG decides which one is the best starting point.  That's where
"adoption" comes in.  From there, the rest of the process goes the
same.

However we get to the -00 document, as long as the rest of the process
goes the way it's supposed to, we're fine.  We seem to have settled
into a culture of starting with individual submissions and "adopting"
them, but there's nothing that requires that, and for documents where
there's not significant contention between radically different
starting points, there's probably no need for it.

So, yes, the chairs get to decide how they want to seed the document
development process, and they have a pretty free hand in making that
decision.  Your ADs are always there for further guidance if you need
or want it.  But there's no formal process for that, and I think
that's how we want it to be.

Barry

From adrian@olddog.co.uk  Wed Nov 28 08:00:40 2012
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7447C21F891B for <ietf@ietfa.amsl.com>; Wed, 28 Nov 2012 08:00:40 -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 XnTpR5ZqDXsU for <ietf@ietfa.amsl.com>; Wed, 28 Nov 2012 08:00:39 -0800 (PST)
Received: from asmtp4.iomartmail.com (asmtp4.iomartmail.com [62.128.201.175]) by ietfa.amsl.com (Postfix) with ESMTP id 9706C21F890A for <ietf@ietf.org>; Wed, 28 Nov 2012 08:00:39 -0800 (PST)
Received: from asmtp4.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id qASG0VJS025643;  Wed, 28 Nov 2012 16:00:32 GMT
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id qASG0T5q025551 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 28 Nov 2012 16:00:29 GMT
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'George, Wes'" <wesley.george@twcable.com>, "'John Leslie'" <john@jlc.net>, "'Barry Leiba'" <barryleiba@computer.org>
References: <2671C6CDFBB59E47B64C10B3E0BD5923033897C9BF@PRVPEXVS15.corp.twcable.com>
In-Reply-To: <2671C6CDFBB59E47B64C10B3E0BD5923033897C9BF@PRVPEXVS15.corp.twcable.com>
Subject: RE: When to adopt a draft as a WG doc (was RE: "IETF work is done on	the mailing lists")
Date: Wed, 28 Nov 2012 16:00:27 -0000
Message-ID: <01a701cdcd81$7d365380$77a2fa80$@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: AQJh66a/LNfCMvKWuQdcHBWtm9X2zpbXK2aQ
Content-Language: en-gb
Cc: 'IETF discussion list' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Nov 2012 16:00:40 -0000

I led the discussion in the WG Chairs lunch at IETF 78 on this topic.
Slides at http://wiki.tools.ietf.org/group/edu/wiki/IETF78#

Adrian

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> George, Wes
> Sent: 28 November 2012 15:36
> To: John Leslie; Barry Leiba
> Cc: IETF discussion list
> Subject: When to adopt a draft as a WG doc (was RE: "IETF work is done on the
> mailing lists")
> 
> > From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> > John Leslie
> >
> >     I'm increasingly seeing a "paradigm" where the review happens
> > _before_ adoption as a WG draft. After adoption, there's a great lull
> > until the deadline for the next IETF week. There tend to be a few,
> > seemingly minor, edits for a version to be discussed. The meeting time
> > is taken up listing changes, most of which get no discussion. Lather,
> > rinse, repeat...
> 
> [WEG] I've seen several discussions recently across WG lists, WG chairs list,
etc
> about this specific topic, and it's leading me to believe that we do not have
> adequate guidance for either WG chairs or participants on when it is generally
> appropriate to adopt a draft as a WG document. I see 3 basic variants just
among
> the WGs that I'm actively involved in:
> 1) adopt early because the draft is talking about a subject the WG wants to
work
> on (may or may not be an official charter milestone), and then refine a
relatively
> rough draft through several I-D-ietf-[wg]-* revisions before WGLC
> 2) adopt after several revisions of I-D-[person]-[wg]-* because there has been
> enough discussion to make the chairs believe that the WG has interest or the
> draft has evolved into something the WG sees as useful/in charter; Then there
> are only minor tweaks in the draft up until WGLC (the above model)
> 3) don't adopt the draft until some defined criteria are met (e.g.
interoperable
> implementations), meaning that much of the real work gets done in the
> individual version
> 
> It seems to me that these variants are dependent on the people in the WG, the
> workload of the group, the chairs, past precedent, AD preferences, etc. It
makes
> it difficult on both draft editors and those seeking to follow the discussion
for
> there to be such a disparity from WG to WG on when to adopt drafts. I'm not
> convinced that there is a one-size-fits-all solution here, but it might be
nice to
> coalesce a little from where we are today.
> So I wonder if perhaps we need clearer guidance on what the process is
actually
> supposed to look like and why. If someone can point to a document that gives
> guidance here, then perhaps we all need to be more conscientious about
> ensuring that the WGs we participate in are following the available guidance
on
> the matter.
> 
> Wes George
> 
> This E-mail and any of its attachments may contain Time Warner Cable
proprietary
> information, which is privileged, confidential, or subject to copyright
belonging to
> Time Warner Cable. This E-mail is intended solely for the use of the
individual or
> entity to which it is addressed. If you are not the intended recipient of this
E-mail,
> you are hereby notified that any dissemination, distribution, copying, or
action
> taken in relation to the contents of and attachments to this E-mail is
strictly
> prohibited and may be unlawful. If you have received this E-mail in error,
please
> notify the sender immediately and permanently delete the original and any copy
> of this E-mail and any printout.


From lear@cisco.com  Wed Nov 28 08:32:38 2012
Return-Path: <lear@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 987CD21F84B5 for <ietf@ietfa.amsl.com>; Wed, 28 Nov 2012 08:32:38 -0800 (PST)
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=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, 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 uNO+QgvM92u1 for <ietf@ietfa.amsl.com>; Wed, 28 Nov 2012 08:32:38 -0800 (PST)
Received: from ams-iport-3.cisco.com (ams-iport-3.cisco.com [144.254.224.146]) by ietfa.amsl.com (Postfix) with ESMTP id C5C3B21F849A for <ietf@ietf.org>; Wed, 28 Nov 2012 08:32:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=348; q=dns/txt; s=iport; t=1354120358; x=1355329958; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=z/NoHHoTNl7kjVgYAWVyY7TYFc0dePv9rjDX2eiY4N4=; b=X+W8P3XA0mc4KqCCpIMywthP25hXpeTuquIeUQr06ZTQsnizDJU9F2T1 l4BV5LA51GrhZCVZuH7sJxfCAv1oVAC505479opXtzCce6RKICrPDgx5d DRfgB+vrpasvAPmMLc7zPYeUMgklEoeH0J6XcdK71Vcd6W/5bt2C7wAmA Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AnUKAHo7tlCQ/khN/2dsb2JhbABFhiq2J4JABAN+FnOCHgEBAQQjSwoBEAsYAgIFFgsCAgkDAgECAUUGDQEHAQGIC6wfknmBIo5LgRMDlgGQRIJx
X-IronPort-AV: E=McAfee;i="5400,1158,6909"; a="9982844"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-3.cisco.com with ESMTP; 28 Nov 2012 16:32:36 +0000
Received: from dhcp-10-55-85-194.cisco.com (dhcp-10-55-85-194.cisco.com [10.55.85.194]) by ams-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id qASGWZ7G005909 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 28 Nov 2012 16:32:36 GMT
Message-ID: <50B63CA3.4040907@cisco.com>
Date: Wed, 28 Nov 2012 17:32:35 +0100
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: Randy Bush <randy@psg.com>
Subject: Re: "IETF work is done on the mailing lists"
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <20121127231404.GC1941@verdi> <m2mwy26iud.wl%randy@psg.com>
In-Reply-To: <m2mwy26iud.wl%randy@psg.com>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Barry Leiba <barryleiba@computer.org>, John Leslie <john@jlc.net>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Nov 2012 16:32:38 -0000

On 11/28/12 12:57 PM, Randy Bush wrote:
>> I'm increasingly seeing a "paradigm" where the review happens _before_
>> adoption as a WG draft.
> and one consequence is that the design gets done outside of the ietf
> process.
>

But this isn't necessarily a bad thing.  It's nice to have reasonably
well thought out ideas come in.

Eliot


From ogud@ogud.com  Wed Nov 28 08:36:09 2012
Return-Path: <ogud@ogud.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 714EB21F8763 for <ietf@ietfa.amsl.com>; Wed, 28 Nov 2012 08:36:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, 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 6VX1pgJ6cHFk for <ietf@ietfa.amsl.com>; Wed, 28 Nov 2012 08:36:08 -0800 (PST)
Received: from smtp187.iad.emailsrvr.com (smtp187.iad.emailsrvr.com [207.97.245.187]) by ietfa.amsl.com (Postfix) with ESMTP id AF79221F8760 for <ietf@ietf.org>; Wed, 28 Nov 2012 08:36:08 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp28.relay.iad1a.emailsrvr.com (SMTP Server) with ESMTP id 20FF0E0ADE for <ietf@ietf.org>; Wed, 28 Nov 2012 11:36:08 -0500 (EST)
X-Virus-Scanned: OK
Received: by smtp28.relay.iad1a.emailsrvr.com (Authenticated sender: ogud-AT-ogud.com) with ESMTPSA id EA877E0AEC for <ietf@ietf.org>; Wed, 28 Nov 2012 11:36:07 -0500 (EST)
Message-ID: <50B63D76.7050708@ogud.com>
Date: Wed, 28 Nov 2012 11:36:06 -0500
From: Olafur Gudmundsson <ogud@ogud.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: When to adopt a draft as a WG doc (was RE: "IETF work is done on the mailing lists")
References: <2671C6CDFBB59E47B64C10B3E0BD5923033897C9BF@PRVPEXVS15.corp.twcable.com>
In-Reply-To: <2671C6CDFBB59E47B64C10B3E0BD5923033897C9BF@PRVPEXVS15.corp.twcable.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Nov 2012 16:36:09 -0000

I guess that a better question is:
	"What are the expectations if a draft becomes an WG document?"

The opinions ranges from:
a) It is something that some members of the WG consider inside the scope
of the charter.
....
z) This is a contract that the IESG will bless this document!

Not all working groups are the same, some work on brand new stuff and it
makes sense to have competing ideas progress and then the WG makes a
choice. In other cases the WG is just fixing something in an important
deployed protocol thus stricter criteria makes sense.

For a WG I have chaired we have two adoption paths:
a) publish draft as draft-<editor>-<wg>---, discuss on WG mailing list
once document is on track and people can make intelligent choice ask
for adoption.
b) Chairs based on discussion on lists or events, will
"commission" a WG document to address a particular issue. This will be
published as draft-ietf-<wg>- in version 00. Most of the time this is
reserved for updated version of published RFC's.

	Olafur


On 28/11/2012 10:36, George, Wes wrote:
>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On
>> Behalf Of John Leslie
>>
>> I'm increasingly seeing a "paradigm" where the review happens
>> _before_ adoption as a WG draft. After adoption, there's a great
>> lull until the deadline for the next IETF week. There tend to be a
>>  few, seemingly minor, edits for a version to be discussed. The
>> meeting time is taken up listing changes, most of which get no
>> discussion. Lather, rinse, repeat...
>
> [WEG] I've seen several discussions recently across WG lists, WG
> chairs list, etc about this specific topic, and it's leading me to
> believe that we do not have adequate guidance for either WG chairs or
> participants on when it is generally appropriate to adopt a draft as
> a WG document. I see 3 basic variants just among the WGs that I'm
> actively involved in: 1) adopt early because the draft is talking
> about a subject the WG wants to work on (may or may not be an
> official charter milestone), and then refine a relatively rough draft
> through several I-D-ietf-[wg]-* revisions before WGLC 2) adopt after
> several revisions of I-D-[person]-[wg]-* because there has been
> enough discussion to make the chairs believe that the WG has interest
> or the draft has evolved into something the WG sees as useful/in
> charter; Then there are only minor tweaks in the draft up until WGLC
> (the above model) 3) don't adopt the draft until some defined
> criteria are met (e.g. interoperable implementations), meaning that
> much of the real work gets done in the individual version
>
> It seems to me that these variants are dependent on the people in the
> WG, the workload of the group, the chairs, past precedent, AD
> preferences, etc. It makes it difficult on both draft editors and
> those seeking to follow the discussion for there to be such a
> disparity from WG to WG on when to adopt drafts. I'm not convinced
> that there is a one-size-fits-all solution here, but it might be nice
> to coalesce a little from where we are today. So I wonder if perhaps
> we need clearer guidance on what the process is actually supposed to
> look like and why. If someone can point to a document that gives
> guidance here, then perhaps we all need to be more conscientious
> about ensuring that the WGs we participate in are following the
> available guidance on the matter.
>
> Wes George
>
> This E-mail and any of its attachments may contain Time Warner Cable
>  proprietary information, which is privileged, confidential, or
> subject to copyright belonging to Time Warner Cable. This E-mail is
> intended solely for the use of the individual or entity to which it
> is addressed. If you are not the intended recipient of this E-mail,
> you are hereby notified that any dissemination, distribution,
> copying, or action taken in relation to the contents of and
> attachments to this E-mail is strictly prohibited and may be
> unlawful. If you have received this E-mail in error, please notify
> the sender immediately and permanently delete the original and any
> copy of this E-mail and any printout.
>
>


From dhc@dcrocker.net  Wed Nov 28 08:45:58 2012
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EBD8621F84CA for <ietf@ietfa.amsl.com>; Wed, 28 Nov 2012 08:45:57 -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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J+dM96kJ0QQ9 for <ietf@ietfa.amsl.com>; Wed, 28 Nov 2012 08:45:57 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 4E55721F8472 for <ietf@ietf.org>; Wed, 28 Nov 2012 08:45:56 -0800 (PST)
Received: from [192.168.1.9] (adsl-67-127-190-125.dsl.pltn13.pacbell.net [67.127.190.125]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id qASGjtnb021746 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Wed, 28 Nov 2012 08:45:55 -0800
Message-ID: <50B63FC1.6020202@dcrocker.net>
Date: Wed, 28 Nov 2012 08:45:53 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: IETF discussion list <ietf@ietf.org>
Subject: Pre-IETF work ( was - Re: "IETF work is done on the mailing lists")
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <20121127231404.GC1941@verdi> <m2mwy26iud.wl%randy@psg.com> <50B63CA3.4040907@cisco.com>
In-Reply-To: <50B63CA3.4040907@cisco.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Wed, 28 Nov 2012 08:45:55 -0800 (PST)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Nov 2012 16:45:58 -0000

>>> I'm increasingly seeing a "paradigm" where the review happens _before_
>>> adoption as a WG draft.
>> and one consequence is that the design gets done outside of the ietf
>> process.
>>
>
> But this isn't necessarily a bad thing.  It's nice to have reasonably
> well thought out ideas come in.


The IETF has a long history of starting efforts from many different 
levels of technical maturity.

However there seems to be some recent leadership pressure to change 
this, attempting an ad hoc policy, by suddenly choosing to challenge the 
importation of existing work apparently based on a spontaneous, personal 
belief that it is bad to have IETF start from existing, deployed 
specifications.

There is, for example, a difference between saying "given the maturity 
and deployment of the document, what is the technical work to be done in 
the IETF?" versus "given the maturity and deployment of the document, 
why are you bringing it to the IETF?"  In pure terms, the latter 
question is, of course, entirely valid.

In pragmatic terms, I'll suggest that it is cast in a way that is 
frankly unfriendly, as well as going against quite a bit of established 
-- and productive -- practice.

I'll remind folk of the Thaler research suggesting that such work has 
the best track record of success for the modern IETF.

d/
-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From rsk@gsp.org  Wed Nov 28 08:53:20 2012
Return-Path: <rsk@gsp.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1001321F88B9 for <ietf@ietfa.amsl.com>; Wed, 28 Nov 2012 08:53:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.854
X-Spam-Level: 
X-Spam-Status: No, score=-5.854 tagged_above=-999 required=5 tests=[AWL=0.744,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 pfkFEfthHYYf for <ietf@ietfa.amsl.com>; Wed, 28 Nov 2012 08:53:19 -0800 (PST)
Received: from taos.firemountain.net (taos.firemountain.net [207.114.3.54]) by ietfa.amsl.com (Postfix) with ESMTP id A7D5621F889F for <ietf@ietf.org>; Wed, 28 Nov 2012 08:53:18 -0800 (PST)
Received: from gsp.org (bltmd-207.114.17.40.dsl.charm.net [207.114.17.40]) by taos.firemountain.net (8.14.5/8.14.5) with ESMTP id qASGrExf016313 for <ietf@ietf.org>; Wed, 28 Nov 2012 11:53:15 -0500 (EST)
Date: Wed, 28 Nov 2012 11:53:09 -0500
From: Rich Kulawiec <rsk@gsp.org>
To: ietf@ietf.org
Subject: Re: mailing list memberships reminder -> passwords in the clear
Message-ID: <20121128165309.GA24779@gsp.org>
References: <20121102152445.92153.qmail@joyce.lan> <5094215B.6000502@cisco.com> <83AB905E-CE0A-4A80-B3CF-F9B32B58FCBD@cs.columbia.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <83AB905E-CE0A-4A80-B3CF-F9B32B58FCBD@cs.columbia.edu>
User-Agent: Mutt/1.5.20 (2009-06-14)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Nov 2012 16:53:20 -0000

First, an enthusiastic +1 to Steve's comments re security being
compatible with risk.

Second, Mailman is -- at this point -- easily the best available option
for mailing list management.  That is not to say it's perfect, of course
it's not -- but in terms of capability, support, development, community,
standards compliance, etc., it's the best we've got.

Third, if the data path from the IETF Mailman instance to your mail
client is compromised, then there are far more serious problems to
worry about than someone spuriously unsubscribing you or switching
you to/from digest mode or similar.

---rsk

From ford@isoc.org  Wed Nov 28 08:56:28 2012
Return-Path: <ford@isoc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7FB6821F85ED for <ietf@ietfa.amsl.com>; Wed, 28 Nov 2012 08:56:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.399
X-Spam-Level: 
X-Spam-Status: No, score=-104.399 tagged_above=-999 required=5 tests=[AWL=1.089, BAYES_00=-2.599, GB_I_INVITATION=-2, RCVD_IN_DNSWL_LOW=-1, SARE_NETPROD=0.111, 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 Y0ItapN7f2ZZ for <ietf@ietfa.amsl.com>; Wed, 28 Nov 2012 08:56:27 -0800 (PST)
Received: from smtp147.iad.emailsrvr.com (smtp147.iad.emailsrvr.com [207.97.245.147]) by ietfa.amsl.com (Postfix) with ESMTP id ECC2F21F8506 for <ietf@ietf.org>; Wed, 28 Nov 2012 08:56:24 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp54.relay.iad1a.emailsrvr.com (SMTP Server) with ESMTP id 7D0F72B09CA for <ietf@ietf.org>; Wed, 28 Nov 2012 11:56:24 -0500 (EST)
X-Virus-Scanned: OK
Received: by smtp54.relay.iad1a.emailsrvr.com (Authenticated sender: ford-AT-isoc.org) with ESMTPSA id E7B242B0635 for <ietf@ietf.org>; Wed, 28 Nov 2012 11:56:23 -0500 (EST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: ANRP 2013 - please nominate
From: Matthew Ford <ford@isoc.org>
In-Reply-To: <2250F07E-7616-4AA0-8CE7-B7FA0102D470@isoc.org>
Date: Wed, 28 Nov 2012 16:56:20 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <061C645E-EFED-451B-9922-876239A3CC7E@isoc.org>
References: <2250F07E-7616-4AA0-8CE7-B7FA0102D470@isoc.org>
To: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-Mailer: Apple Mail (2.1499)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Nov 2012 16:56:28 -0000

On 28 Nov 2012, at 15:00, Matthew Ford <ford@isoc.org> wrote:

> Hi,
>=20
> Nominations for the 2013 ANRP awards are due by this Friday 30th =
November, so if you've read a great paper this year, please send us the =
details using the submission system at:
>=20
> 	http://irtf.org/anrp/2013/
>=20
> or exceptionally, by email to anrp@irtf.org.
>=20
> Thanks,
> Mat


And, in case you are unfamiliar with the Applied Networking Research =
Prize (ANRP):

About the ANRP
--------------
The Applied Networking Research Prize (ANRP) is awarded for recent =
results in applied networking research that are relevant for =
transitioning into shipping Internet products and related =
standardization efforts. Researchers with relevant, recent results are =
encouraged to apply for this prize, which will offer them the =
opportunity to present and discuss their work with the engineers, =
network operators, policy makers and scientists that participate in the =
Internet Engineering Task Force (IETF) and its research arm, the =
Internet Research Task Force (IRTF). Third-party nominations for this =
prize are also encouraged. The goal of the Applied Networking Research =
Prize is to recognize the best new ideas in networking, and bring them =
to the IETF and IRTF especially in cases where they would not otherwise =
see much exposure or discussion.

The Applied Networking Research Prize (ANRP) consists of:

	=95 cash prize of $500 (USD)
	=95 invited talk at the IRTF Open Meeting
	=95 travel grant to attend a week-long IETF meeting (airfare, =
hotel, registration, stipend)
	=95 recognition at the IETF plenary
	=95 invitation to related social activities
	=95 potential for additional travel grants to future IETF =
meetings, based on community feedback

The Applied Networking Research Prize will be awarded once per calendar =
year. Each year, several winners will be chosen and invited to present =
their work at one of the three IETF meetings during the year.

How to Nominate
---------------
Only a single person can be nominated for the award. The basis of the =
nomination is a peer-reviewed, original journal, conference or workshop =
paper they authored, which was recently published or accepted for =
publication. The nominee must be one of the main authors of the =
nominated paper. Both self nominations (nominating one=92s own paper) =
and third-party nominations (nominating someone else=92s paper) are =
encouraged.

The nominated paper should provide a scientific foundation for possible =
future IETF engineering work or IRTFresearch and experimentation, =
analyze the behavior of Internet protocols in operational deployments or =
realistic testbeds, make an important contribution to the understanding =
of Internet scalability, performance, reliability, security or =
capability, or otherwise be of relevance to ongoing or future IETF or =
IRTF activities.

Applicants must briefly describe how the nominated paper relates to =
these goals, and are encouraged to describe how a presentation of these =
research results would foster their transition into new IETF engineering =
or IRTFexperimentation, or otherwise seed new activities that will have =
an impact on the real-world Internet.

The goal of the Applied Networking Research Prize (ANRP) is to foster =
the transitioning of research results into real-world benefits for the =
Internet. Therefore, applicants must indicate that they (or the nominee, =
in case of third-party nominations) are available to attend at least one =
of the year=92s IETF meetings in person and in its entirety.

Nominations must include:

	=95 the name and email address of the nominee
	=95 a bibliographic reference to the published (or accepted) =
nominated paper
	=95 a PDF copy of the nominated paper
	=95 a statement that describes how the nominated paper fulfills =
the goals of the award
	=95 a statement about which of the year=92s IETF meetings the =
nominee would be available to attend in person and in its entirety
	=95 a brief biography or CV of the nominee
	=95 optionally, any other supporting information (link to =
nominee=92s web site, etc.)
Nominations are submitted via the submission site. In exceptional cases, =
nominations may also be submitted by email to anrp@irtf.org.

All nominees will be notified by email about the decision regarding =
their nomination.

Nominations for the Applied Networking Research Prize (ANRP) are not =
considered to be contributions to the IETF. However, the invited talks =
at the IRTF Open Meeting are considered to be contributions, and the =
IRTF =93Intellectual Property Rights=94 statement does apply to them.=

From abdussalambaryun@gmail.com  Wed Nov 28 10:31:02 2012
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9745621F846A for <ietf@ietfa.amsl.com>; Wed, 28 Nov 2012 10:31:02 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J0dXlEYRXjmM for <ietf@ietfa.amsl.com>; Wed, 28 Nov 2012 10:31:01 -0800 (PST)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id C2BD221F8469 for <ietf@ietf.org>; Wed, 28 Nov 2012 10:31:01 -0800 (PST)
Received: by mail-vc0-f172.google.com with SMTP id fw7so13175680vcb.31 for <ietf@ietf.org>; Wed, 28 Nov 2012 10:31:01 -0800 (PST)
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=Ha80kMwTlQVBTN1Qq/rhDMIiFXcnPTLqEwc2y6/zH7w=; b=Iyyi66lP2ntE9t6lbaE2cR3s4XGQK2c5gmSoz7getN6jX2F17mO0QXTidxv7NxmHDC UMzrZ29aZFF3OWFQkdgUYVr/8eMmJxvcCQVRyCzub9eGuiErLkuW7KRGHjqoS/D6C9Xx igslaLJZom+PM1rq5TT1nXC3FT1LB7g4em0cR+r+7avLS5ZxyCSPDR7hTOL7g+FU32wP z67otMX5+WrY7l8rmM69dnukjkKbvC+lG0LRPUJcdsGOXs8ODJFRBo4sx005buBe3Hc/ wIJhXzoeWR+e1xZxPQTv133wkyGHcAYzh5oiXBC44Wb0vTsotUPiMb1CU55lnQQF1V/O nQLA==
MIME-Version: 1.0
Received: by 10.52.72.104 with SMTP id c8mr25756070vdv.20.1354127460905; Wed, 28 Nov 2012 10:31:00 -0800 (PST)
Received: by 10.220.145.5 with HTTP; Wed, 28 Nov 2012 10:31:00 -0800 (PST)
Date: Wed, 28 Nov 2012 18:31:00 +0000
Message-ID: <CADnDZ89jnwj_+vKVX1KdVegvMcdvUPjvp84wDCANuB1fMGpGkg@mail.gmail.com>
Subject: Re: "IETF work is done on the mailing lists"
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: barryleiba@computer.org
Content-Type: multipart/alternative; boundary=bcaec50162bd49b35704cf925ecd
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Nov 2012 18:31:02 -0000

--bcaec50162bd49b35704cf925ecd
Content-Type: text/plain; charset=ISO-8859-1

Hi Barry,

I thank you to open this discussion. I tried to open this discussion before
on the list but was ignored, however, seeing your input made me think that
there is importance to the subject. IMO I prefer the discussion list,
because we all integrate and we all are present in its domain. In F2F
meeting their is a certain time to meet and limited discussions and limited
input. Please note that most of the input of IETF is done on the list not
within F2F meetings. However, still we need F2F meetings to
insure/encourage the directions of work/discussions.

WG F2F meetings Main Purpose: Guidance, Directions, Sense Decisions,
Interact with other WGs, Exchanging ideas and questions, Marketing,
interaction with other organisations, etc.

WG Discussion List Participations Purpose: announcements, feedbacks, The
documented Work flow Processings, Making WG decisions, checking concensus,
questions and answers, editing work/drafts, arguments, etc.

I thought this is already in the IETF procedure that we are following, so
maybe the question is are we following best practices or we just are
following some people. I think so far that participants are sometimes
following and sometimes not, which is disapointment (some one asked me once
on the list why I was disapointed this is one reason).

Regards
AB

--bcaec50162bd49b35704cf925ecd
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div>Hi Barry,</div><div>=A0</div><div>I thank you to open this discussion.=
 I tried to open this discussion before on the list but was ignored, howeve=
r, seeing your input made me think that there is importance to the subject.=
 IMO I prefer the discussion list, because we all integrate and we all are =
present in its domain. In F2F meeting their is a certain time to meet and l=
imited discussions and limited input. Please note that most of the input of=
 IETF is done on the list not within F2F meetings. However, still we need F=
2F meetings to insure/encourage the directions of work/discussions.</div>
<div>=A0</div><div>WG F2F meetings Main=A0Purpose: Guidance, Directions, Se=
nse Decisions, Interact with other WGs, Exchanging ideas and questions, Mar=
keting, interaction with other organisations, etc.</div><div>=A0</div><div>=
WG Discussion List Participations Purpose: announcements, feedbacks, The do=
cumented Work flow Processings, Making WG decisions, checking concensus, qu=
estions and answers, editing work/drafts, arguments, etc.</div>
<div>=A0</div><div>I thought this is already in the IETF procedure that we =
are following, so maybe the question is are we following best practices or =
we just are following some people. I think so far that participants are som=
etimes following and sometimes not, which is disapointment (some one asked =
me once on the list why I was disapointed this is one reason).</div>
<div>=A0</div><div>Regards</div><div>AB</div>

--bcaec50162bd49b35704cf925ecd--

From abdussalambaryun@gmail.com  Wed Nov 28 10:53:25 2012
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A67BE21F87AC for <ietf@ietfa.amsl.com>; Wed, 28 Nov 2012 10:53:25 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W3ftoSd4vK8Z for <ietf@ietfa.amsl.com>; Wed, 28 Nov 2012 10:53:25 -0800 (PST)
Received: from mail-gg0-f172.google.com (mail-gg0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id E3FC221F86C6 for <ietf@ietf.org>; Wed, 28 Nov 2012 10:53:24 -0800 (PST)
Received: by mail-gg0-f172.google.com with SMTP id r1so873874ggn.31 for <ietf@ietf.org>; Wed, 28 Nov 2012 10:53:24 -0800 (PST)
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=41xHj5SWSYY55oh5le4TSm29iGWpq2YgydkX+QARFNY=; b=G8wJpJHwC8sy0fEwT+z/+Iflh74jN6GT2uYuE0sc8D07fCYgO0EeXX3VfRniAHxvol gqVuvYEgNcwqBSizzgaWXoDFw3+xU1cWzCt6lg2MUGXQm8ZpdqjWklitU9L7owhRCeDb xv5WOzHvYp4wvuGQAR6zNUO0xPAvWr7A/OfG1jigDDa5DmMYW8oRmCMrpq/lA3895Liw UqMIcUFUCqmjEfJfWPi6a357pGo2HuDsF2GM+5jFwzIhL7pYRGG5/fojNmJVRuOyIb9b XCt5WECHAP7qATaYUIFnaGMLqPDDv8c+MLjpxfWT/ZDLy56BnSKlpHB1DLb1MIBlIgJS o5tg==
MIME-Version: 1.0
Received: by 10.58.243.166 with SMTP id wz6mr30224748vec.28.1354128804452; Wed, 28 Nov 2012 10:53:24 -0800 (PST)
Received: by 10.220.145.5 with HTTP; Wed, 28 Nov 2012 10:53:24 -0800 (PST)
Date: Wed, 28 Nov 2012 18:53:24 +0000
Message-ID: <CADnDZ894SLhPDcNtFBi=RypmWS3cW8yegcjLp-2FWLsrPqDKng@mail.gmail.com>
Subject: Re: When to adopt a draft as a WG doc (was RE: "IETF work is done on the mailing lists")
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=047d7b86f4b25e97cf04cf92aea8
Cc: barryleiba@computer.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Nov 2012 18:53:25 -0000

--047d7b86f4b25e97cf04cf92aea8
Content-Type: text/plain; charset=ISO-8859-1

> It seems to me that these variants are dependent on the people in the WG,
> the workload of the group, the chairs, past precedent, AD preferences,
etc.
> It makes it difficult on both draft editors and those seeking to follow
the
> discussion for there to be such a disparity from WG to WG on when to adopt
> drafts. I'm not convinced that there is a one-size-fits-all solution
here, but it
> might be nice to coalesce a little from where we are today.
>
> So I wonder if perhaps we need clearer guidance on what the process is
> actually supposed to look like and why.
I think the IETF procedures are clear that the WG should authorise all
works, not the chairs nor the ADs. However, chairs guide the discussions on
the list (which in few times does not happen because we are volunteering),
and ADs guide the chairs and direct the WG output. The WG input is only
authorised by the participants through rough consensus.


>So, yes, the chairs get to decide how they want to seed the document
development process, and they have a pretty free hand in making that
decision.  Your ADs are always there for further guidance if you need
or want it.
AB> I disagree that chairs have such authority on process without checking
the WG if there was an objection or not. The ADs are there for the chairs
guidance too not only participants. The chairs role is important to
encourage/manage participants input time/effort in faivor of the WG
charters. However, I agree that chairs MAY take decision on behalf of WG
because they want to save time and they know the WG initial opinion by
experience (still they need to check if there is any objection).

>But there's no formal process for that, and I think
that's how we want it to be.

I don't want no formal in a formal organisation, usually unformal process
only happen in unformal organisations, so is IETF a formal or non-formal. I
beleive we are in a formal so our managers (chairs and ADs) SHOULD follow
formal procedures and participants MAY do both.

I read the procedures and this is what I came out with if I am wrong please
refer me to where does the procedure mention that WG Chairs have such
authority.

AB

--047d7b86f4b25e97cf04cf92aea8
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div>&gt; It seems to me that these variants are dependent on the people in=
 the WG,<br>&gt; the workload of the group, the chairs, past precedent, AD =
preferences, etc.<br>&gt; It makes it difficult on both draft editors and t=
hose seeking to follow the<br>
&gt; discussion for there to be such a disparity from WG to WG on when to a=
dopt<br>&gt; drafts. I&#39;m not convinced that there is a one-size-fits-al=
l solution here, but it<br>&gt; might be nice to coalesce a little from whe=
re we are today.<br>
&gt;<br>&gt; So I wonder if perhaps we need clearer guidance on what the pr=
ocess is<br>&gt; actually supposed to look like and why.<br></div><div>I th=
ink the IETF procedures are clear that the WG should=A0authorise all works,=
 not the chairs nor the ADs. However, chairs guide the discussions on the l=
ist (which in few times=A0does not happen because we are volunteering), and=
 ADs guide the chairs and direct the WG output. The WG input is only author=
ised by the participants through rough consensus.</div>
<div>=A0</div><div>=A0</div><div>&gt;So, yes, the chairs get to decide how =
they want to seed the document<br>development process, and they have a pret=
ty free hand in making that<br>decision.=A0 Your ADs are always there for f=
urther guidance if you need<br>
or want it.=A0 <br></div><div>AB&gt; I disagree that chairs have such autho=
rity on process without checking the WG if there was an objection or not. T=
he ADs are there for the chairs guidance too not only participants. The cha=
irs role is important to encourage/manage=A0participants input time/effort =
in faivor of the WG charters. However, I agree that chairs MAY take decisio=
n on behalf of WG because they want to save time and they know the WG initi=
al opinion by experience (still they need to check if there is any objectio=
n).</div>
<div>=A0</div><div>&gt;But there&#39;s no formal process for that, and I th=
ink<br>that&#39;s how we want it to be.</div><div>=A0</div><div>I don&#39;t=
 want no formal in a formal organisation, usually unformal process only hap=
pen in unformal organisations, so is IETF a formal or non-formal. I beleive=
 we are in a formal so our managers (chairs and ADs) SHOULD follow formal p=
rocedures and participants MAY do both.</div>
<div>=A0</div><div>I read the procedures and this is what I came out with i=
f I am wrong please refer me to where does the procedure mention that WG=A0=
Chairs have such authority.</div><div>=A0</div><div>AB</div>

--047d7b86f4b25e97cf04cf92aea8--

From abdussalambaryun@gmail.com  Wed Nov 28 11:35:10 2012
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E605B21F84B2 for <ietf@ietfa.amsl.com>; Wed, 28 Nov 2012 11:35:10 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GbrcHuzUgDjZ for <ietf@ietfa.amsl.com>; Wed, 28 Nov 2012 11:35:10 -0800 (PST)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 2394521F8506 for <ietf@ietf.org>; Wed, 28 Nov 2012 11:35:10 -0800 (PST)
Received: by mail-vc0-f172.google.com with SMTP id fw7so13243898vcb.31 for <ietf@ietf.org>; Wed, 28 Nov 2012 11:35:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=ipy0ERO25xczAokNVqLWnYZut/8NQr03sY3pfP+qPec=; b=wM0Emx/uugk0S6z+bsgw4uR4KOnsongx7n0XY9XPwE9bI+7yONbw1UxTDcd5eT3KhC h/DYitp1HJKTJYyhcdO5xVZHy0GKC3kJHN3+QYw051AgF4MD3HaTIfURbLjwoyxewTZc hbBQMKCh/WaWvw7Uj0K9ga/93WO0Rj0HffCOGpzCt01L5V+sMFNNWheBrxtQZ28Yj9Zj SRU0dcUmWGYtKZZOmeOxqIZfVjELR+ITWBaF8BdtxOZgNjlFzM9BerZ9xRUEXqMsD4Vj OIh4k3xIxDDuEQLUGjQlrdwxche+3Y4+AOWKv/16nq7L90JDU1pfcl3aCbUIMgF/vlrW waJA==
MIME-Version: 1.0
Received: by 10.58.198.135 with SMTP id jc7mr29705887vec.51.1354131309481; Wed, 28 Nov 2012 11:35:09 -0800 (PST)
Received: by 10.220.145.5 with HTTP; Wed, 28 Nov 2012 11:35:09 -0800 (PST)
Date: Wed, 28 Nov 2012 19:35:09 +0000
Message-ID: <CADnDZ8-FRwkTgDKi=kr4fmZv5=tvUAcon0oQ1SrjYbgG4rfv1g@mail.gmail.com>
Subject: When do we ask community for opinion and When we produce an RFC for the community?
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=047d7b5d8cd7ae4e7f04cf9343a2
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Nov 2012 19:35:11 -0000

--047d7b5d8cd7ae4e7f04cf9343a2
Content-Type: text/plain; charset=ISO-8859-1

http://www.ietf.org/mail-archive/web/ietf/current/msg76001.html
> Does the community want us to push back on those situations?

I think we follow the IETF RFCs or our community amend/change the procedure
related RFCs to be practical. We may need historical RFCs to understand why
such change (the change in opinion/practices as community opinion is
changing).

> Does the community believe that the real IETF work is done on
> the mailing lists, and not in the face-to-face meetings, to
> the extent that the community would want the IESG to refuse to
> publish documents whose process went as I've described above,
> on the basis that IETF process was not properly followed?

I think the community cannot answer that question.
Overall, could we depend on asking the IETF community about something that
is against the IETF procedure and then we claim that we are following the
community. I thought we are following our approved documents or RFCs its
the communities opinion as well. If it is very easy to ask question to the
community to make a procedure then why we need RFCs? I thought that
sometimes IETF managers ask the community questions to sense the rough
consensus for purposes of guidance, not for the purpose of processing the
IETF's work flow.

I once written an RFC to update 2119 but some participants don't want that,
but still I don't beleive that I need to ask them nor the community. I will
go through procedure because I feel I have right to do so. However, once I
asked community for feedback on a draft I will write, but participants
argued why do I ask while still did not write. I do ask only to sense the
community, but still have the right to decide my volunteering work/input.

My question is when do we ask community (from participant level, or
from managerial level) and when we produce an RFC (which purpose)?


Thanking you,
AB

--047d7b5d8cd7ae4e7f04cf9343a2
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div><a href=3D"http://www.ietf.org/mail-archive/web/ietf/current/msg76001.=
html">http://www.ietf.org/mail-archive/web/ietf/current/msg76001.html</a></=
div><div>&gt; Does the community want us to push back on those situations?<=
/div>
<div>=A0</div><div>I think we follow the IETF RFCs or our community amend/c=
hange the procedure related RFCs to be practical. We may need historical RF=
Cs to understand why such change (the change in opinion/practices as commun=
ity opinion is changing).</div>
<div><br>&gt; Does the community believe that the real IETF work is done on=
<br>&gt; the mailing lists, and not in the face-to-face meetings, to<br>&gt=
; the extent that the community would want the IESG to refuse to<br>&gt; pu=
blish documents whose process went as I&#39;ve described above,<br>
&gt; on the basis that IETF process was not properly followed?</div><div>=
=A0</div><div>I think the community cannot answer that question.<br></div><=
div>Overall, could we depend on asking the IETF community about something t=
hat is against the IETF procedure and then we claim that we are following t=
he community. I thought we are following our approved documents or RFCs its=
 the communities opinion as well. If it is very easy to ask question to the=
 community to make a procedure then why we need RFCs? I thought that someti=
mes IETF managers ask the community questions to sense the rough consensus =
for purposes of guidance, not for the purpose of processing the IETF&#39;s =
work flow.</div>
<div>=A0</div><div>I once written an RFC to update 2119 but some participan=
ts don&#39;t want that, but still I don&#39;t beleive that I need to ask th=
em nor the community.=A0I will go through procedure because I feel I have r=
ight to do so. However, once I asked community for feedback on a draft I wi=
ll write, but participants argued why do I ask while still did not write. I=
 do ask only to sense the community, but still have the right to decide my =
volunteering work/input.</div>
<div>=A0</div><div>My question is when do we=A0ask community (from=A0partic=
ipant level, or from=A0managerial level) and when we produce an RFC (which=
=A0purpose)?</div><div>=A0</div><div>=A0</div><div>Thanking you,</div><div>=
AB</div>

--047d7b5d8cd7ae4e7f04cf9343a2--

From john-ietf@jck.com  Wed Nov 28 12:54:02 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 83EAC21F895B for <ietf@ietfa.amsl.com>; Wed, 28 Nov 2012 12:54:00 -0800 (PST)
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=[AWL=0.000, 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 ZtYJXHzqaKpb for <ietf@ietfa.amsl.com>; Wed, 28 Nov 2012 12:53:59 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id CEF4821F843E for <ietf@ietf.org>; Wed, 28 Nov 2012 12:53:54 -0800 (PST)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1Tdodl-0009Y2-50; Wed, 28 Nov 2012 15:53:53 -0500
Date: Wed, 28 Nov 2012 15:53:43 -0500
From: John C Klensin <john-ietf@jck.com>
To: SM <sm@resistor.net>
Subject: Re: Barely literate minutes (was: "IETF work is done on the  mailing lists")
Message-ID: <66705A84964227D7EC38A341@JcK-HP8200.jck.com>
In-Reply-To: <6.2.5.6.2.20121128023905.0afdcde0@resistor.net>
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <50B5C839.4060909@gmail.com> <59924CD37D50616BA8EB8EF7@JcK-HP8200.jck.com> <6.2.5.6.2.20121128023905.0afdcde0@resistor.net>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Nov 2012 20:54:02 -0000

--On Wednesday, November 28, 2012 03:28 -0800 SM
<sm@resistor.net> wrote:

> At 01:25 28-11-2012, John C Klensin wrote:
>> This is, IMO, a consequence of our developing fancy tools and
>> then uncritically relying on them.  A Jabber log or real-time
>> Etherpad may be, and probably is, a very helpful way to keep
>> real-time notes within a meeting but some WGs have substituted
>> nearly-unedited versions of them (especially the latter) for
>> minutes.  They are not minutes, certainly not minutes as
> 
> Yes.
> 
> Nobody likes to write minutes.  Very few people volunteer
> their free time to do them (thanks to John Leslie for scribing
> the IESG minutes).  When there is a discussion about producing
> minutes people come up with proposals for fancy tools.  This
> is where someone says: "Etherpad can do that".  There is a
> moment of silence when somebody finds out that there's nobody
> using Etherpad to take notes about what's going on.  Who would
> have thought that these fancy tools cannot work without
> people? :-)
> 
>> contemplated by RFC 2418, and I sincerely hope that the IESG
>> and the community push back on those "barely literate" notes
>> before there is an appeal against a WG decision or document
>> approval that is based, even in part, on failure of the WG to
>> comply with that 2418 requirement.
> 
> The community is too lethargic to push back on those "barely
> literate" notes.  One of these days there will be such an
> appeal.

Let me be clear.  For most WGs and purposes, most of the time,
the "minutes" are the minutes and I'm certainly not going to be
the one who makes a big fuss about clarity or literacy unless
they are so incomplete and incompetent that posting them becomes
a joke.  _However_ if a WG wants to make/be an exception to the
principle that consensus has to be demonstrated on the mailing
list and instead wants to rely on face to face discussions, than
that WG is, IMO, obligated to have minutes complete and
comprehensible enough that someone who did not participate in
the meeting, even remotely, can determine what went on and why
and hence whether the proposed solution or agreement is
acceptable.   If  the WG cannot produce such minutes, then I
think it is obligated to be able to demonstrate consensus from
the mailing list discussions alone.

Rather clear tradeoff, IMO.

   john




From swb@internet2.edu  Wed Nov 28 13:11:26 2012
Return-Path: <swb@internet2.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1189C21F89DD for <ietf@ietfa.amsl.com>; Wed, 28 Nov 2012 13:11:26 -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 uc-aWGR4YhSn for <ietf@ietfa.amsl.com>; Wed, 28 Nov 2012 13:11:25 -0800 (PST)
Received: from int-proxy02.merit.edu (int-proxy02.merit.edu [207.75.116.231]) by ietfa.amsl.com (Postfix) with ESMTP id 5D77C21F895A for <ietf@ietf.org>; Wed, 28 Nov 2012 13:11:25 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by int-proxy02.merit.edu (Postfix) with ESMTP id CB02026804C; Wed, 28 Nov 2012 16:11:24 -0500 (EST)
X-Virus-Scanned: amavisd-new at int-proxy02.merit.edu
Received: from int-proxy02.merit.edu ([127.0.0.1]) by localhost (int-proxy02.merit.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0W2pgn0GPHHp; Wed, 28 Nov 2012 16:11:14 -0500 (EST)
Received: from swbi2mbp.local (cpe-67-241-75-185.twcny.res.rr.com [67.241.75.185]) by int-proxy02.merit.edu (Postfix) with ESMTPSA id 15F7F26804B; Wed, 28 Nov 2012 16:11:14 -0500 (EST)
Message-ID: <50B67DF1.6020308@internet2.edu>
Date: Wed, 28 Nov 2012 16:11:13 -0500
From: Scott Brim <swb@internet2.edu>
Organization: Internet2
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: Barely literate minutes
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <50B5C839.4060909@gmail.com> <59924CD37D50616BA8EB8EF7@JcK-HP8200.jck.com> <6.2.5.6.2.20121128023905.0afdcde0@resistor.net> <66705A84964227D7EC38A341@JcK-HP8200.jck.com>
In-Reply-To: <66705A84964227D7EC38A341@JcK-HP8200.jck.com>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: SM <sm@resistor.net>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Nov 2012 21:11:26 -0000

On 11/28/12 15:53, John C Klensin allegedly wrote:
> Let me be clear.  For most WGs and purposes, most of the time,
> the "minutes" are the minutes and I'm certainly not going to be
> the one who makes a big fuss about clarity or literacy unless
> they are so incomplete and incompetent that posting them becomes
> a joke.  _However_ if a WG wants to make/be an exception to the
> principle that consensus has to be demonstrated on the mailing
> list and instead wants to rely on face to face discussions, than
> that WG is, IMO, obligated to have minutes complete and
> comprehensible enough that someone who did not participate in
> the meeting, even remotely, can determine what went on and why
> and hence whether the proposed solution or agreement is
> acceptable.   If  the WG cannot produce such minutes, then I
> think it is obligated to be able to demonstrate consensus from
> the mailing list discussions alone.
> 
> Rather clear tradeoff, IMO.

... and in those cases it is very important that the "minutes" (although
I would avoid that as a pre-loaded term) cover as much of the arguments
as possible.  A reader on the mailing list will be utterly shortchanged
if all he/she gets are conclusions and action points.  In the past,
individual WGs have argued about whether to include actual names in the
meeting notes.  Personally I'm in favor but even without them, at least
the issues and pros and cons of a significant decision must be
documented in detail.

On the larger topic, and the relationship of the mailing list to the f2f
meetings, here is a policy we tried in IntArea:
http://tools.ietf.org/wg/intarea/trac/wiki/MeetingTimePrioritization

Scott


From hartmans@mit.edu  Wed Nov 28 13:24:37 2012
Return-Path: <hartmans@mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BAFA721F8848 for <ietf@ietfa.amsl.com>; Wed, 28 Nov 2012 13:24:34 -0800 (PST)
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=-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 ZgxBz2sEM06b for <ietf@ietfa.amsl.com>; Wed, 28 Nov 2012 13:24:34 -0800 (PST)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id 4945321F888D for <ietf@ietf.org>; Wed, 28 Nov 2012 13:24:33 -0800 (PST)
Received: from carter-zimmerman.suchdamage.org (c-98-217-126-210.hsd1.ma.comcast.net [98.217.126.210]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.painless-security.com (Postfix) with ESMTPS id 240E220167; Wed, 28 Nov 2012 16:22:52 -0500 (EST)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 3F8F3420E; Wed, 28 Nov 2012 16:24:30 -0500 (EST)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: John C Klensin <john-ietf@jck.com>
Subject: Re: Barely literate minutes
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <50B5C839.4060909@gmail.com> <59924CD37D50616BA8EB8EF7@JcK-HP8200.jck.com> <6.2.5.6.2.20121128023905.0afdcde0@resistor.net> <66705A84964227D7EC38A341@JcK-HP8200.jck.com>
Date: Wed, 28 Nov 2012 16:24:30 -0500
In-Reply-To: <66705A84964227D7EC38A341@JcK-HP8200.jck.com> (John C. Klensin's message of "Wed, 28 Nov 2012 15:53:43 -0500")
Message-ID: <tslobih5skx.fsf@mit.edu>
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
Cc: SM <sm@resistor.net>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Nov 2012 21:24:38 -0000

>>>>> "John" == John C Klensin <john-ietf@jck.com> writes:


    John> Let me be clear.  For most WGs and purposes, most of the time,
    John> the "minutes" are the minutes and I'm certainly not going to
    John> be the one who makes a big fuss about clarity or literacy
    John> unless they are so incomplete and incompetent that posting
    John> them becomes a joke.  _However_ if a WG wants to make/be an
    John> exception to the principle that consensus has to be
    John> demonstrated on the mailing list and instead wants to rely on
    John> face to face discussions, than that WG is, IMO, obligated to
    John> have minutes complete and comprehensible enough that someone
    John> who did not participate in the meeting, even remotely, can
    John> determine what went on and why and hence whether the proposed
    John> solution or agreement is acceptable.  If the WG cannot produce
    John> such minutes, then I think it is obligated to be able to
    John> demonstrate consensus from the mailing list discussions alone.

Unfortunately demonstraiting discussions based on the mailing list alone
also opens latitude for appeals.  According to RFc 2418, chairs must
combine the face-to-face discussions and mailing lists when judging
consensus.
If I as a participant believe that the face-to-face discussions when
added to the mailing list discussion would change the outcome and the
chairs say they are only considering the mailing list discussions, I
have valid grounds for an appeal.

Take a look at the discussions surrounding the IPv6 site-local appeal
and particular at the responses generated at the IAB and IESG level for
some of our historical thinking on this.

Personally I'd strongly support an update to RFC 2418 that
allowed|encouraged|required chairs to take a consensus call entirely to
the list .

From stpeter@stpeter.im  Wed Nov 28 13:36:03 2012
Return-Path: <stpeter@stpeter.im>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE39B21F84D2 for <ietf@ietfa.amsl.com>; Wed, 28 Nov 2012 13:36:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.487
X-Spam-Level: 
X-Spam-Status: No, score=-102.487 tagged_above=-999 required=5 tests=[AWL=0.113, 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 WKDtC9n5FM+a for <ietf@ietfa.amsl.com>; Wed, 28 Nov 2012 13:36:02 -0800 (PST)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id CF8FD21F84C1 for <ietf@ietf.org>; Wed, 28 Nov 2012 13:36:02 -0800 (PST)
Received: from [10.129.24.67] (unknown [128.107.239.234]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id E40E740062; Wed, 28 Nov 2012 14:40:59 -0700 (MST)
Message-ID: <50B683C4.2030503@stpeter.im>
Date: Wed, 28 Nov 2012 14:36:04 -0700
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: SM <sm@resistor.net>
Subject: Re: Barely literate minutes
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <50B5C839.4060909@gmail.com> <59924CD37D50616BA8EB8EF7@JcK-HP8200.jck.com> <6.2.5.6.2.20121128023905.0afdcde0@resistor.net>
In-Reply-To: <6.2.5.6.2.20121128023905.0afdcde0@resistor.net>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: John C Klensin <john-ietf@jck.com>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Nov 2012 21:36:03 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 11/28/12 4:28 AM, SM wrote:
> Hi John,
> 
> [subject line mutated to reflect topic being discussed]
> 
> At 01:25 28-11-2012, John C Klensin wrote:
>> This is, IMO, a consequence of our developing fancy tools and 
>> then uncritically relying on them.  A Jabber log or real-time 
>> Etherpad may be, and probably is, a very helpful way to keep 
>> real-time notes within a meeting but some WGs have substituted 
>> nearly-unedited versions of them (especially the latter) for 
>> minutes.  They are not minutes, certainly not minutes as
> 
> Yes.
> 
> Nobody likes to write minutes.  Very few people volunteer their
> free time to do them...

IMHO it is the chairs' responsibility to listen to the audio recording
and produce minutes from that (or at least check the scribe's minutes
against the audio recording). I've done this in the past (full
disclosure: not always) and it is a lot of work.

Peter

- -- 
Peter Saint-Andre
https://stpeter.im/


-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.18 (Darwin)
Comment: Using GnuPG with undefined - http://www.enigmail.net/

iEYEARECAAYFAlC2g8QACgkQNL8k5A2w/vxDFACgnuyRJALETl7djVtK2kjQkzzK
MVoAoJJcQcVA5jmk6UJg28DfFcPLlqRi
=9cgO
-----END PGP SIGNATURE-----

From dhc@dcrocker.net  Wed Nov 28 13:46:02 2012
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 064E921F847B for <ietf@ietfa.amsl.com>; Wed, 28 Nov 2012 13:46:02 -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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ws4loINlEYix for <ietf@ietfa.amsl.com>; Wed, 28 Nov 2012 13:46:01 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 6BE5D21F8587 for <ietf@ietf.org>; Wed, 28 Nov 2012 13:46:01 -0800 (PST)
Received: from [192.168.1.9] (adsl-67-127-190-125.dsl.pltn13.pacbell.net [67.127.190.125]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id qASLjx8n003899 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 28 Nov 2012 13:45:59 -0800
Message-ID: <50B68612.7080107@dcrocker.net>
Date: Wed, 28 Nov 2012 13:45:54 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: Peter Saint-Andre <stpeter@stpeter.im>
Subject: Re: Barely literate minutes
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <50B5C839.4060909@gmail.com> <59924CD37D50616BA8EB8EF7@JcK-HP8200.jck.com> <6.2.5.6.2.20121128023905.0afdcde0@resistor.net> <50B683C4.2030503@stpeter.im>
In-Reply-To: <50B683C4.2030503@stpeter.im>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Wed, 28 Nov 2012 13:45:59 -0800 (PST)
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Nov 2012 21:46:02 -0000

On 11/28/2012 1:36 PM, Peter Saint-Andre wrote:
> IMHO it is the chairs' responsibility to listen to the audio recording
> and produce minutes from that (or at least check the scribe's minutes
> against the audio recording). I've done this in the past (full
> disclosure: not always) and it is a lot of work.


I strongly disagree.

Chairs have a high workload already.  A strength of a working group 
needs to be its ability to distribute work amongst participants.

If a working group cannot obtain the services of a participant willing 
to take notes and be responsible for getting wg review of them, then the 
wg has bigger problems.

d/

ps. I'll repeat that I think f2f needs to be essentially irrelevant to 
the assessment of wg consensus, except perhaps as an efficiency hack 
that permits more terse exchanges on the mailing list.
-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From hartmans@mit.edu  Wed Nov 28 14:33:38 2012
Return-Path: <hartmans@mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 12F1321F892F for <ietf@ietfa.amsl.com>; Wed, 28 Nov 2012 14:33:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.299
X-Spam-Level: 
X-Spam-Status: No, score=-102.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, 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 H7ipP5nFNwXG for <ietf@ietfa.amsl.com>; Wed, 28 Nov 2012 14:33:37 -0800 (PST)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id 989DC21F8914 for <ietf@ietf.org>; Wed, 28 Nov 2012 14:33:37 -0800 (PST)
Received: from carter-zimmerman.suchdamage.org (c-98-217-126-210.hsd1.ma.comcast.net [98.217.126.210]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.painless-security.com (Postfix) with ESMTPS id 991D020167; Wed, 28 Nov 2012 17:31:56 -0500 (EST)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 53BEE420E; Wed, 28 Nov 2012 17:33:35 -0500 (EST)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: dcrocker@bbiw.net
Subject: Re: Barely literate minutes
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <50B5C839.4060909@gmail.com> <59924CD37D50616BA8EB8EF7@JcK-HP8200.jck.com> <6.2.5.6.2.20121128023905.0afdcde0@resistor.net> <50B683C4.2030503@stpeter.im> <50B68612.7080107@dcrocker.net>
Date: Wed, 28 Nov 2012 17:33:35 -0500
In-Reply-To: <50B68612.7080107@dcrocker.net> (Dave Crocker's message of "Wed,  28 Nov 2012 13:45:54 -0800")
Message-ID: <tsl38zt5pds.fsf@mit.edu>
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
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Nov 2012 22:33:38 -0000

>>>>> "Dave" == Dave Crocker <dhc@dcrocker.net> writes:

    Dave> On 11/28/2012 1:36 PM, Peter Saint-Andre wrote:
    >> IMHO it is the chairs' responsibility to listen to the audio
    >> recording and produce minutes from that (or at least check the
    >> scribe's minutes against the audio recording). I've done this in
    >> the past (full disclosure: not always) and it is a lot of work.


    Dave> I strongly disagree.

    Dave> Chairs have a high workload already.  A strength of a working
    Dave> group needs to be its ability to distribute work amongst
    Dave> participants.

    Dave> If a working group cannot obtain the services of a participant
    Dave> willing to take notes and be responsible for getting wg review
    Dave> of them, then the wg has bigger problems.


I'm mostly with Dave here.  As a chair I(and AD) I've sometimes found it
necessary to listen to an audio recording, and I'm really incredibly
glad they're there.
However, I don't want that to be the norm.
I found audio recordings really helpful for example in dealing with
appeals or threatened appeals.

From stpeter@stpeter.im  Wed Nov 28 14:45:01 2012
Return-Path: <stpeter@stpeter.im>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B90F321F8938 for <ietf@ietfa.amsl.com>; Wed, 28 Nov 2012 14:45:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.49
X-Spam-Level: 
X-Spam-Status: No, score=-102.49 tagged_above=-999 required=5 tests=[AWL=0.109, 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 HerJAU8L0LQB for <ietf@ietfa.amsl.com>; Wed, 28 Nov 2012 14:45:00 -0800 (PST)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id DD67821F8933 for <ietf@ietf.org>; Wed, 28 Nov 2012 14:45:00 -0800 (PST)
Received: from [10.129.24.67] (unknown [128.107.239.233]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id C2ECC40062; Wed, 28 Nov 2012 15:49:57 -0700 (MST)
Message-ID: <50B693ED.7000609@stpeter.im>
Date: Wed, 28 Nov 2012 15:45:01 -0700
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: dcrocker@bbiw.net
Subject: Re: Barely literate minutes
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <50B5C839.4060909@gmail.com> <59924CD37D50616BA8EB8EF7@JcK-HP8200.jck.com> <6.2.5.6.2.20121128023905.0afdcde0@resistor.net> <50B683C4.2030503@stpeter.im> <50B68612.7080107@dcrocker.net>
In-Reply-To: <50B68612.7080107@dcrocker.net>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Nov 2012 22:45:02 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 11/28/12 2:45 PM, Dave Crocker wrote:
> 
> 
> On 11/28/2012 1:36 PM, Peter Saint-Andre wrote:
>> IMHO it is the chairs' responsibility to listen to the audio
>> recording and produce minutes from that (or at least check the
>> scribe's minutes against the audio recording). I've done this in
>> the past (full disclosure: not always) and it is a lot of work.
> 
> 
> I strongly disagree.
> 
> Chairs have a high workload already.  A strength of a working
> group needs to be its ability to distribute work amongst
> participants.
> 
> If a working group cannot obtain the services of a participant
> willing to take notes and be responsible for getting wg review of
> them, then the wg has bigger problems.

In my experience, if a lot is happening in the WG session at an IETF
meeting then it is extremely difficult for any one participant (or
even a team of two working on etherpad) to take accurate notes. One
example that I chaired was the second codec BoF in Hiroshima (and
forget about the first one in Stockholm!). However, I think Ted Hardie
and I did a pretty good job with the second httpbis session in Paris.
YMMV. But I do think the chairs are ultimately responsible for the
minutes.

> ps. I'll repeat that I think f2f needs to be essentially irrelevant
> to the assessment of wg consensus, except perhaps as an efficiency
> hack that permits more terse exchanges on the mailing list.

That's a separate topic, but I tend to disagree. Why the heck even
have meetings? And I concur with Marc Blanchet that some WGs really
gel and make good progress in person but don't have great threads on
the mailing list.

Peter

- -- 
Peter Saint-Andre
https://stpeter.im/

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.18 (Darwin)
Comment: Using GnuPG with undefined - http://www.enigmail.net/

iEYEARECAAYFAlC2k+0ACgkQNL8k5A2w/vxlDgCg7oeaVnKObA7LW8aNyIpu7Lnn
DnYAoOQc3TL4TQW+LZD566zseeH7OzKj
=IolB
-----END PGP SIGNATURE-----

From presnick@qti.qualcomm.com  Wed Nov 28 14:56:59 2012
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5AD8921F8890 for <ietf@ietfa.amsl.com>; Wed, 28 Nov 2012 14:56:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.556
X-Spam-Level: 
X-Spam-Status: No, score=-102.556 tagged_above=-999 required=5 tests=[AWL=0.043, 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 FErgTdEOBP75 for <ietf@ietfa.amsl.com>; Wed, 28 Nov 2012 14:56:58 -0800 (PST)
Received: from sabertooth01.qualcomm.com (sabertooth01.qualcomm.com [65.197.215.72]) by ietfa.amsl.com (Postfix) with ESMTP id ACC2F21F875A for <ietf@ietf.org>; Wed, 28 Nov 2012 14:56:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1354142466; x=1385678466; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=X9WxOjqqNGQL1r4X4DmEoFZ5kbnK0slBXtG5U3oMTU8=; b=thLBChwvDGI2pql6HzMkJbPgYodYdh1CFyaRdDqeI4+H5SQZ9IEa8WsT vQH8hL+iQHlhrjLT/EZg3ymA5JS0Sq7Z0KfSOV0qs4h9jqaVuXghTWCPe rNzZzSMtLFsV3K6gIBynKVJSumI2x5OdHACVj7NJmAiSFixLM4HOoihiC 8=;
X-IronPort-AV: E=McAfee;i="5400,1158,6910"; a="9559603"
Received: from ironmsg01-lv.qualcomm.com ([10.47.202.180]) by sabertooth01.qualcomm.com with ESMTP; 28 Nov 2012 14:41:05 -0800
X-IronPort-AV: E=McAfee;i="5400,1158,6910"; a="2629213"
Received: from nasanexhc08.na.qualcomm.com ([172.30.39.7]) by ironmsg01-lv.qualcomm.com with ESMTP/TLS/RC4-SHA; 28 Nov 2012 14:56:57 -0800
Received: from presnick-mac.local (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.7) with Microsoft SMTP Server (TLS) id 14.2.318.4; Wed, 28 Nov 2012 14:56:57 -0800
Message-ID: <50B696B0.30904@qti.qualcomm.com>
Date: Wed, 28 Nov 2012 16:56:48 -0600
From: Pete Resnick <presnick@qti.qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: Peter Saint-Andre <stpeter@stpeter.im>
Subject: Re: Barely literate minutes
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com>	<50B5C839.4060909@gmail.com>	<59924CD37D50616BA8EB8EF7@JcK-HP8200.jck.com>	<6.2.5.6.2.20121128023905.0afdcde0@resistor.net>	<50B683C4.2030503@stpeter.im> <50B68612.7080107@dcrocker.net> <50B693ED.7000609@stpeter.im>
In-Reply-To: <50B693ED.7000609@stpeter.im>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.39.5]
Cc: dcrocker@bbiw.net, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Nov 2012 22:56:59 -0000

On 11/28/12 4:45 PM, Peter Saint-Andre wrote:

> On 11/28/12 2:45 PM, Dave Crocker wrote:
>
>    
>> ps. I'll repeat that I think f2f needs to be essentially irrelevant
>> to the assessment of wg consensus, except perhaps as an efficiency
>> hack that permits more terse exchanges on the mailing list.
>>      
> That's a separate topic, but I tend to disagree. Why the heck even
> have meetings? And I concur with Marc Blanchet that some WGs really
> gel and make good progress in person but don't have great threads on
> the mailing list.
>    

It is a fact of life that some WGs only make progress face-to-face. I 
think that's often a sign of a problem, but it's a fact. But if that 
happens, the chair needs to (with the help of minutes takers and other 
participants) post detailed notes of the discussion to the list and ask 
for objections. That serves two functions: (a) It makes a record of work 
that was done; and (b) it gives people who don't attend meetings 
(including new folks who come along) a chance to participate and voice 
their concerns. *Achievement* of consensus might have to occur f2f for 
some issues in some WGs, but it seems to me that *assessment* of 
consensus must be completely possible on the list, even if the only 
poster to the list is the chair with all of the f2f notes.

pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478


From randy@psg.com  Wed Nov 28 15:07:17 2012
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 346DE21F84E9 for <ietf@ietfa.amsl.com>; Wed, 28 Nov 2012 15:07:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.473
X-Spam-Level: 
X-Spam-Status: No, score=-2.473 tagged_above=-999 required=5 tests=[AWL=0.126,  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 6D6vph0ddoys for <ietf@ietfa.amsl.com>; Wed, 28 Nov 2012 15:07:16 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id CF04121F84E1 for <ietf@ietf.org>; Wed, 28 Nov 2012 15:07:16 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from <randy@psg.com>) id 1Tdqip-0007AG-GR; Wed, 28 Nov 2012 23:07:15 +0000
Date: Thu, 29 Nov 2012 08:07:14 +0900
Message-ID: <m2lidl5ntp.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
Subject: Re: Barely literate minutes
In-Reply-To: <50B696B0.30904@qti.qualcomm.com>
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <50B5C839.4060909@gmail.com> <59924CD37D50616BA8EB8EF7@JcK-HP8200.jck.com> <6.2.5.6.2.20121128023905.0afdcde0@resistor.net> <50B683C4.2030503@stpeter.im> <50B68612.7080107@dcrocker.net> <50B693ED.7000609@stpeter.im> <50B696B0.30904@qti.qualcomm.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Cc: IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Nov 2012 23:07:17 -0000

> It is a fact of life that some WGs only make progress face-to-face. I
> think that's often a sign of a problem, but it's a fact.

i am not so sure it's a problem.  email is a great miscommunication
mechanism.  so mailing lists go disfunctional far more easily than face
to face.

we're funny monkeys and seem to need physical presence.  we'll see how
we do with remote participation if we ever untangle that charlie
foxtrot.

randy

From dhc@dcrocker.net  Wed Nov 28 15:16:04 2012
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B0B1321F8590 for <ietf@ietfa.amsl.com>; Wed, 28 Nov 2012 15:16:04 -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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hfuGvuJlS1Eq for <ietf@ietfa.amsl.com>; Wed, 28 Nov 2012 15:16:04 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id EEEFB21F8482 for <ietf@ietf.org>; Wed, 28 Nov 2012 15:16:03 -0800 (PST)
Received: from [192.168.1.9] (adsl-67-127-190-125.dsl.pltn13.pacbell.net [67.127.190.125]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id qASNFuvP008518 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 28 Nov 2012 15:15:57 -0800
Message-ID: <50B69B2A.6040305@dcrocker.net>
Date: Wed, 28 Nov 2012 15:15:54 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: Peter Saint-Andre <stpeter@stpeter.im>
Subject: Re: Barely literate minutes
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <50B5C839.4060909@gmail.com> <59924CD37D50616BA8EB8EF7@JcK-HP8200.jck.com> <6.2.5.6.2.20121128023905.0afdcde0@resistor.net> <50B683C4.2030503@stpeter.im> <50B68612.7080107@dcrocker.net> <50B693ED.7000609@stpeter.im>
In-Reply-To: <50B693ED.7000609@stpeter.im>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Wed, 28 Nov 2012 15:15:58 -0800 (PST)
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Nov 2012 23:16:04 -0000

On 11/28/2012 2:45 PM, Peter Saint-Andre wrote:
> In my experience, if a lot is happening in the WG session at an IETF
> meeting then it is extremely difficult for any one participant (or
> even a team of two working on etherpad) to take accurate notes.
...
> But I do think the chairs are ultimately responsible for the
> minutes.

The chairs are responsible for running things and ensuring fair and 
thorough process.  Part of running things is delegating tasks.

If someone signs up to take notes, then they ought to have 
responsibility to produce them, including reviewing the audio, if that's 
needed.  The wg approves minutes, not the chairs.  The chairs should 
manage the overall process, but I'll repeat:  A wg needs to distribute 
its workload and if it can't do that, it has basic problems.


>> ps. I'll repeat that I think f2f needs to be essentially irrelevant
>> to the assessment of wg consensus, except perhaps as an efficiency
>> hack that permits more terse exchanges on the mailing list.
>
> That's a separate topic, but I tend to disagree. Why the heck even
> have meetings?

Meetings are for more efficient discussion of particular topics, as well 
as the development of support for choices.  But support is different 
than saying "wg decision".

To the extent that a f2f is making definitive decisions, then the IETF 
has become exclusionary against those unable to attend the f2f meeting.

And no, remote participation is never going to be equivalent.  Having to 
'attend' at 2am remotely is not the same as attending at 10am locally.

d/
-- 
-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From sm@resistor.net  Wed Nov 28 15:50:25 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 716BC21F8A4F for <ietf@ietfa.amsl.com>; Wed, 28 Nov 2012 15:50:24 -0800 (PST)
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=-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 7DJ5uqiLXpVn for <ietf@ietfa.amsl.com>; Wed, 28 Nov 2012 15:50:23 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9CFAC21F899A for <ietf@ietf.org>; Wed, 28 Nov 2012 15:50:23 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id qASNoCv5009377; Wed, 28 Nov 2012 15:50:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1354146618; bh=SMQILayPg2v1V7M8syAKZta18y0e/HEPpsdEAREJfzY=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=G/0ybqIZ0ylfbhZDW8+1tndh5zED1C6VxE4LbCMyTO6mEkU6rUWgIpLYgp0SjsEXG 6q+PpMQNfKf/eOT23IfEEvReiDpeTIj/NKM6LqD09f6zBJEHaFvomSTLnnLQgw873R i0pdh/pnNKBlNu+NVe9JwLQRJxpDmxHbB/X4u0dk=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1354146618; i=@resistor.net; bh=SMQILayPg2v1V7M8syAKZta18y0e/HEPpsdEAREJfzY=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=oTAlmi6csQyeDjnE88QBkLkJr5lX7L41K1B+a4erX774rL7Tkq+3NURMqSgRWiTUX hsWOcMDIc+53rsyzoZItxcC2jzLj4ed/IsDDOM0tN3cSpYeQCdLD+5aXgXkZOSnglX Yeq6aokmJcU3eRAmJyqpHrqZvP/FsGODY8MoRsOM=
Message-Id: <6.2.5.6.2.20121128150642.09f155d8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 28 Nov 2012 15:49:19 -0800
To: dcrocker@bbiw.net
From: SM <sm@resistor.net>
Subject: Re: Barely literate minutes
In-Reply-To: <50B68612.7080107@dcrocker.net>
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <50B5C839.4060909@gmail.com> <59924CD37D50616BA8EB8EF7@JcK-HP8200.jck.com> <6.2.5.6.2.20121128023905.0afdcde0@resistor.net> <50B683C4.2030503@stpeter.im> <50B68612.7080107@dcrocker.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Nov 2012 23:50:25 -0000

Hi Dave,
At 13:45 28-11-2012, Dave Crocker wrote:
>Chairs have a high workload already.  A strength of a working group 
>needs to be its ability to distribute work amongst participants.

Yes.

>If a working group cannot obtain the services of a participant 
>willing to take notes and be responsible for getting wg review of 
>them, then the wg has bigger problems.

I listen to the audio as it allows me to understand the decisions and 
see whether the notes will give some random person an understanding 
of what happened.

Regards,
-sm 


From bob.hinden@gmail.com  Wed Nov 28 15:57:29 2012
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A5C5C21F8459 for <ietf@ietfa.amsl.com>; Wed, 28 Nov 2012 15:57:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.849
X-Spam-Level: 
X-Spam-Status: No, score=-103.849 tagged_above=-999 required=5 tests=[AWL=-0.250, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, 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 Ayreju8zz38z for <ietf@ietfa.amsl.com>; Wed, 28 Nov 2012 15:57:29 -0800 (PST)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id 2A07821F889F for <ietf@ietf.org>; Wed, 28 Nov 2012 15:57:29 -0800 (PST)
Received: by mail-pb0-f44.google.com with SMTP id uo1so9844404pbc.31 for <ietf@ietf.org>; Wed, 28 Nov 2012 15:57:29 -0800 (PST)
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 :content-transfer-encoding:message-id:references:to:x-mailer; bh=i4gbCpsvpsoazxQrF3sF2O41+3NcwVKackKRhHgHvmo=; b=jkZmY8kFjp0w7e4bP1nw0NUAfctxbHVpLUxphevJIGtxhJjEy8Tmr9H5fuy1X6/onL GEf02Ie9sXUw4FUixGJr3SxWJwYJ9FVHon4vaqo7KDkDX5IDo8erGDdUCfkNzd56PLvK 2ub/QZJ9uql5EkSfQR35CtDN7TeoT76eqyJ9/ib4D/ccAWeQOvz05Xa9TIobxEzvnOeA EjdkT5rln26rSsKf5fdZ27+F2x5HA/c3hqUieOZY7oPWWsRlT2UvIuOYxt7rag3uGoQE UQEMJHuMLvTK9D4ovpNIgVzGYzSG8VKC7LrYVXTlbpR0MzGr3NE9ITEeUI+grTogf1zC azGQ==
Received: by 10.68.193.167 with SMTP id hp7mr63760115pbc.124.1354147048989; Wed, 28 Nov 2012 15:57:28 -0800 (PST)
Received: from [172.16.224.219] ([209.97.127.34]) by mx.google.com with ESMTPS id a8sm13281055paz.18.2012.11.28.15.57.24 (version=SSLv3 cipher=OTHER); Wed, 28 Nov 2012 15:57:28 -0800 (PST)
Subject: Re: Barely literate minutes
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=us-ascii
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <m2lidl5ntp.wl%randy@psg.com>
Date: Wed, 28 Nov 2012 15:57:23 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <BB22CC86-F9B8-4727-BCA3-F617221944F2@gmail.com>
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <50B5C839.4060909@gmail.com> <59924CD37D50616BA8EB8EF7@JcK-HP8200.jck.com> <6.2.5.6.2.20121128023905.0afdcde0@resistor.net> <50B683C4.2030503@stpeter.im> <50B68612.7080107@dcrocker.net> <50B693ED.7000609@stpeter.im> <50B696B0.30904@qti.qualcomm.com> <m2lidl5ntp.wl%randy@psg.com>
To: Randy Bush <randy@psg.com>
X-Mailer: Apple Mail (2.1283)
Cc: Pete Resnick <presnick@qti.qualcomm.com>, Bob Hinden <bob.hinden@gmail.com>, IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Nov 2012 23:57:29 -0000

On Nov 28, 2012, at 3:07 PM, Randy Bush wrote:

>> It is a fact of life that some WGs only make progress face-to-face. I
>> think that's often a sign of a problem, but it's a fact.
>=20
> i am not so sure it's a problem.  email is a great miscommunication
> mechanism.  so mailing lists go disfunctional far more easily than =
face
> to face.

+1

It's much easier to reach a consensus face to face, than on a mailing =
list.  I think we have all seen this.

Bob

>=20
> we're funny monkeys and seem to need physical presence.  we'll see how
> we do with remote participation if we ever untangle that charlie
> foxtrot.
>=20
> randy


From gih@apnic.net  Wed Nov 28 18:48:04 2012
Return-Path: <gih@apnic.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9BF6D21F88CF for <ietf@ietfa.amsl.com>; Wed, 28 Nov 2012 18:48:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, 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 rP+Czc15UbTO for <ietf@ietfa.amsl.com>; Wed, 28 Nov 2012 18:48:04 -0800 (PST)
Received: from asmtp.apnic.net (asmtp.apnic.net [IPv6:2001:dc0:2001:11::199]) by ietfa.amsl.com (Postfix) with ESMTP id CFF2221F87B6 for <ietf@ietf.org>; Wed, 28 Nov 2012 18:48:02 -0800 (PST)
Received: from [IPv6:2001:388:1000:110:38dd:f84e:9488:5278] (unknown [IPv6:2001:388:1000:110:38dd:f84e:9488:5278]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by asmtp.apnic.net (Postfix) with ESMTP id 8C889B68D5; Thu, 29 Nov 2012 12:48:00 +1000 (EST)
Subject: Re: When to adopt a draft as a WG doc (was RE: "IETF work is done on the mailing lists")
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Content-Type: text/plain; charset=us-ascii
From: Geoff Huston <gih@apnic.net>
In-Reply-To: <2671C6CDFBB59E47B64C10B3E0BD5923033897C9BF@PRVPEXVS15.corp.twcable.com>
Date: Thu, 29 Nov 2012 13:48:01 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <957E700E-839A-4152-AB03-80075CF4EC0D@apnic.net>
References: <2671C6CDFBB59E47B64C10B3E0BD5923033897C9BF@PRVPEXVS15.corp.twcable.com>
To: "George, Wes" <wesley.george@twcable.com>
X-Mailer: Apple Mail (2.1499)
Cc: Barry Leiba <barryleiba@computer.org>, John Leslie <john@jlc.net>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Nov 2012 02:48:04 -0000

On 29/11/2012, at 2:36 AM, "George, Wes" <wesley.george@twcable.com> =
wrote:

>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf =
Of
>> John Leslie
>>=20
>>    I'm increasingly seeing a "paradigm" where the review happens
>> _before_ adoption as a WG draft. After adoption, there's a great lull
>> until the deadline for the next IETF week. There tend to be a few,
>> seemingly minor, edits for a version to be discussed. The meeting =
time
>> is taken up listing changes, most of which get no discussion. Lather,
>> rinse, repeat...
>=20
> [WEG] I've seen several discussions recently across WG lists, WG =
chairs list, etc about this specific topic, and it's leading me to =
believe that we do not have adequate guidance for either WG chairs or =
participants on when it is generally appropriate to adopt a draft as a =
WG document. I see 3 basic variants just among the WGs that I'm actively =
involved in:
> 1) adopt early because the draft is talking about a subject the WG =
wants to work on (may or may not be an official charter milestone), and =
then refine a relatively rough draft through several I-D-ietf-[wg]-* =
revisions before WGLC
> 2) adopt after several revisions of I-D-[person]-[wg]-* because there =
has been enough discussion to make the chairs believe that the WG has =
interest or the draft has evolved into something the WG sees as =
useful/in charter; Then there are only minor tweaks in the draft up =
until WGLC (the above model)
> 3) don't adopt the draft until some defined criteria are met (e.g. =
interoperable implementations), meaning that much of the real work gets =
done in the individual version


4) adopt after seeing a reasonable number of WG members post "NOT in =
favour of adoption", on the purported grounds that such expressions of =
disinterest in adopting the draft by some strange twist of logic are =
portrayed to point to "interest in discussing the document"

  Geoff








From gih@apnic.net  Wed Nov 28 18:56:20 2012
Return-Path: <gih@apnic.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3260F11E80A3 for <ietf@ietfa.amsl.com>; Wed, 28 Nov 2012 18:56:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, 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 eu2zEYKIJm55 for <ietf@ietfa.amsl.com>; Wed, 28 Nov 2012 18:56:19 -0800 (PST)
Received: from asmtp.apnic.net (asmtp.apnic.net [IPv6:2001:dc0:2001:11::199]) by ietfa.amsl.com (Postfix) with ESMTP id A73B311E809B for <ietf@ietf.org>; Wed, 28 Nov 2012 18:56:18 -0800 (PST)
Received: from [IPv6:2001:388:1000:110:38dd:f84e:9488:5278] (unknown [IPv6:2001:388:1000:110:38dd:f84e:9488:5278]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by asmtp.apnic.net (Postfix) with ESMTP id 09D78B6744; Thu, 29 Nov 2012 12:56:17 +1000 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: "IETF work is done on the mailing lists"
From: Geoff Huston <gih@apnic.net>
In-Reply-To: <50B63CA3.4040907@cisco.com>
Date: Thu, 29 Nov 2012 13:56:17 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <D0EF612C-DFF5-4D16-BA96-F65204CC1CB2@apnic.net>
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <20121127231404.GC1941@verdi> <m2mwy26iud.wl%randy@psg.com> <50B63CA3.4040907@cisco.com>
To: Eliot Lear <lear@cisco.com>
X-Mailer: Apple Mail (2.1499)
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Nov 2012 02:56:20 -0000

On 29/11/2012, at 3:32 AM, Eliot Lear <lear@cisco.com> wrote:

>=20
> On 11/28/12 12:57 PM, Randy Bush wrote:
>>> I'm increasingly seeing a "paradigm" where the review happens =
_before_
>>> adoption as a WG draft.
>> and one consequence is that the design gets done outside of the ietf
>> process.
>>=20
>=20
> But this isn't necessarily a bad thing.  It's nice to have reasonably
> well thought out ideas come in.
>=20

Which then become highly defined precepts that become incredibly =
resistant to IETF change on the basis that they have been well thought =
out already (and probably are IPR-ridden) and at that stage the IETF =
process is functionally reduced to rubber stamping. At that stage the =
value of the IETF imprimatur becomes highly dubious to the industry its =
meant to serve.

It's not clear to me if this idea of taking in 'mature' work is =
altogether a good thing.




From john-ietf@jck.com  Wed Nov 28 20:31:01 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 24D0D21F8443 for <ietf@ietfa.amsl.com>; Wed, 28 Nov 2012 20:31:01 -0800 (PST)
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=[AWL=0.000, 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 sYe1YK-3xOv2 for <ietf@ietfa.amsl.com>; Wed, 28 Nov 2012 20:30:36 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 3BF421F0C82 for <ietf@ietf.org>; Wed, 28 Nov 2012 20:30:36 -0800 (PST)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1Tdvlg-000A3O-IZ; Wed, 28 Nov 2012 23:30:32 -0500
Date: Wed, 28 Nov 2012 23:30:29 -0500
From: John C Klensin <john-ietf@jck.com>
To: Scott Brim <swb@internet2.edu>
Subject: Re: Barely literate minutes
Message-ID: <DBB649D8EF09DA0D3F62F846@JcK-HP8200.jck.com>
In-Reply-To: <50B67DF1.6020308@internet2.edu>
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <50B5C839.4060909@gmail.com> <59924CD37D50616BA8EB8EF7@JcK-HP8200.jck.com> <6.2.5.6.2.20121128023905.0afdcde0@resistor.net> <66705A84964227D7EC38A341@JcK-HP8200.jck.com> <50B67DF1.6020308@internet2.edu>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: SM <sm@resistor.net>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Nov 2012 04:31:01 -0000

--On Wednesday, November 28, 2012 16:11 -0500 Scott Brim
<swb@internet2.edu> wrote:

> On 11/28/12 15:53, John C Klensin allegedly wrote:
>> Let me be clear.  For most WGs and purposes, most of the time,
>> the "minutes" are the minutes and I'm certainly not going to
>> be the one who makes a big fuss about clarity or literacy
>> unless they are so incomplete and incompetent that posting
>> them becomes a joke.  _However_ if a WG wants to make/be an
>> exception to the principle that consensus has to be
>> demonstrated on the mailing list and instead wants to rely on
>> face to face discussions, than that WG is, IMO, obligated to
>> have minutes complete and comprehensible enough that someone
>> who did not participate in the meeting, even remotely, can
>...
> ... and in those cases it is very important that the "minutes"
> (although I would avoid that as a pre-loaded term) cover as
> much of the arguments as possible.  A reader on the mailing
> list will be utterly shortchanged if all he/she gets are
> conclusions and action points.  In the past, individual WGs
> have argued about whether to include actual names in the
> meeting notes.  Personally I'm in favor but even without them,
> at least the issues and pros and cons of a significant
> decision must be documented in detail.

Yes, exactly.
    john



From andrew.hutton@siemens-enterprise.com  Thu Nov 29 01:26:34 2012
Return-Path: <andrew.hutton@siemens-enterprise.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C1AEA21F88C8 for <ietf@ietfa.amsl.com>; Thu, 29 Nov 2012 01:26:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.556
X-Spam-Level: 
X-Spam-Status: No, score=-2.556 tagged_above=-999 required=5 tests=[AWL=0.043,  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 2bRtXjJ-Gz46 for <ietf@ietfa.amsl.com>; Thu, 29 Nov 2012 01:26:34 -0800 (PST)
Received: from senmx11-mx.siemens-enterprise.com (senmx11-mx.siemens-enterprise.com [62.134.46.9]) by ietfa.amsl.com (Postfix) with ESMTP id B0EF821F8860 for <ietf@ietf.org>; Thu, 29 Nov 2012 01:26:33 -0800 (PST)
Received: from MCHP02HTC.global-ad.net (unknown [172.29.42.235]) by senmx11-mx.siemens-enterprise.com (Server) with ESMTP id 3CC541EB84EF; Thu, 29 Nov 2012 10:26:32 +0100 (CET)
Received: from MCHP04MSX.global-ad.net ([169.254.1.206]) by MCHP02HTC.global-ad.net ([172.29.42.235]) with mapi id 14.02.0318.001; Thu, 29 Nov 2012 10:26:32 +0100
From: "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>
To: "dcrocker@bbiw.net" <dcrocker@bbiw.net>, Peter Saint-Andre <stpeter@stpeter.im>
Subject: RE: Barely literate minutes
Thread-Topic: Barely literate minutes
Thread-Index: AQHNzbBeAP0v4TxVikWT/UcvXCirNZf/t1cAgADSdpA=
Date: Thu, 29 Nov 2012 09:26:31 +0000
Message-ID: <9F33F40F6F2CD847824537F3C4E37DDF01373D6B@MCHP04MSX.global-ad.net>
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <50B5C839.4060909@gmail.com>	<59924CD37D50616BA8EB8EF7@JcK-HP8200.jck.com> <6.2.5.6.2.20121128023905.0afdcde0@resistor.net> <50B683C4.2030503@stpeter.im> <50B68612.7080107@dcrocker.net>
In-Reply-To: <50B68612.7080107@dcrocker.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.29.42.225]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Nov 2012 09:26:34 -0000

QXMgYSBjaGFpciBJIGFsd2F5cyBmaW5kIGl0IHVzZWZ1bCB0byBnbyBiYWNrIGFuZCByZXZpZXcg
dGhlIGF1ZGlvL01lZXRlY2hvIHJlY29yZGluZyBmb2xsb3dpbmcgdGhlIG1lZXRpbmcgYW5kIHdo
aWxzdCBkb2luZyBzbyBJIG1pZ2h0IGFzIHdlbGwgdGlkeSB1cCB0aGUgbWludXRlcy4NCg0KVGhl
IEYyRiBtZWV0aW5nIHRpbWUgY2FuIGJlIHF1aXRlIGhlY3RpYyBmb3IgdGhlIGNoYWlycyBhbmQg
SSB0ZW5kIHRvIGJlIGNvbmNlbnRyYXRpbmcgb24gbWFraW5nIHN1cmUgdGhhdCB3ZSBzdGF5IG9u
IHRpbWUgYW5kIGV2ZXJ5Ym9keSBnZXRzIGEgZmFpciBjaGFuY2UgdG8gc2F5IHdoYXQgdGhleSB3
YW50IHRvLiAgU28gaXQgaXMgYSBtdXN0IHRvIGdvIGJhY2sgb3ZlciB0aGUgcmVjb3JkaW5nIGFu
ZCBtYWtlIHN1cmUgSSB1bmRlcnN0b29kIGFsbCB0aGUgcG9pbnRzIHBlb3BsZSBtYWRlIGR1cmlu
ZyB0aGUgbWVldGluZyBhbmQgSSBtaWdodCBhcyB3ZWxsIGNoZWNrIHRoZSBtaW51dGVzIHdoaWxz
dCBkb2luZyBzby4NCg0KQW5keSANCg0KDQoNCg0KDQo+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0t
LS0tDQo+IEZyb206IGlldGYtYm91bmNlc0BpZXRmLm9yZyBbbWFpbHRvOmlldGYtYm91bmNlc0Bp
ZXRmLm9yZ10gT24gQmVoYWxmIE9mDQo+IERhdmUgQ3JvY2tlcg0KPiBTZW50OiAyOCBOb3ZlbWJl
ciAyMDEyIDIxOjQ2DQo+IFRvOiBQZXRlciBTYWludC1BbmRyZQ0KPiBDYzogSUVURiBkaXNjdXNz
aW9uIGxpc3QNCj4gU3ViamVjdDogUmU6IEJhcmVseSBsaXRlcmF0ZSBtaW51dGVzDQo+IA0KPiAN
Cj4gDQo+IE9uIDExLzI4LzIwMTIgMTozNiBQTSwgUGV0ZXIgU2FpbnQtQW5kcmUgd3JvdGU6DQo+
ID4gSU1ITyBpdCBpcyB0aGUgY2hhaXJzJyByZXNwb25zaWJpbGl0eSB0byBsaXN0ZW4gdG8gdGhl
IGF1ZGlvDQo+IHJlY29yZGluZw0KPiA+IGFuZCBwcm9kdWNlIG1pbnV0ZXMgZnJvbSB0aGF0IChv
ciBhdCBsZWFzdCBjaGVjayB0aGUgc2NyaWJlJ3MgbWludXRlcw0KPiA+IGFnYWluc3QgdGhlIGF1
ZGlvIHJlY29yZGluZykuIEkndmUgZG9uZSB0aGlzIGluIHRoZSBwYXN0IChmdWxsDQo+ID4gZGlz
Y2xvc3VyZTogbm90IGFsd2F5cykgYW5kIGl0IGlzIGEgbG90IG9mIHdvcmsuDQo+IA0KPiANCj4g
SSBzdHJvbmdseSBkaXNhZ3JlZS4NCj4gDQo+IENoYWlycyBoYXZlIGEgaGlnaCB3b3JrbG9hZCBh
bHJlYWR5LiAgQSBzdHJlbmd0aCBvZiBhIHdvcmtpbmcgZ3JvdXANCj4gbmVlZHMgdG8gYmUgaXRz
IGFiaWxpdHkgdG8gZGlzdHJpYnV0ZSB3b3JrIGFtb25nc3QgcGFydGljaXBhbnRzLg0KPiANCj4g
SWYgYSB3b3JraW5nIGdyb3VwIGNhbm5vdCBvYnRhaW4gdGhlIHNlcnZpY2VzIG9mIGEgcGFydGlj
aXBhbnQgd2lsbGluZw0KPiB0byB0YWtlIG5vdGVzIGFuZCBiZSByZXNwb25zaWJsZSBmb3IgZ2V0
dGluZyB3ZyByZXZpZXcgb2YgdGhlbSwgdGhlbg0KPiB0aGUNCj4gd2cgaGFzIGJpZ2dlciBwcm9i
bGVtcy4NCj4gDQo+IGQvDQo+IA0KPiBwcy4gSSdsbCByZXBlYXQgdGhhdCBJIHRoaW5rIGYyZiBu
ZWVkcyB0byBiZSBlc3NlbnRpYWxseSBpcnJlbGV2YW50IHRvDQo+IHRoZSBhc3Nlc3NtZW50IG9m
IHdnIGNvbnNlbnN1cywgZXhjZXB0IHBlcmhhcHMgYXMgYW4gZWZmaWNpZW5jeSBoYWNrDQo+IHRo
YXQgcGVybWl0cyBtb3JlIHRlcnNlIGV4Y2hhbmdlcyBvbiB0aGUgbWFpbGluZyBsaXN0Lg0KPiAt
LQ0KPiAgIERhdmUgQ3JvY2tlcg0KPiAgIEJyYW5kZW5idXJnIEludGVybmV0V29ya2luZw0KPiAg
IGJiaXcubmV0DQo=

From daedulus@btconnect.com  Thu Nov 29 01:39:48 2012
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B9FE721F8981 for <ietf@ietfa.amsl.com>; Thu, 29 Nov 2012 01:39:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.099
X-Spam-Level: 
X-Spam-Status: No, score=-5.099 tagged_above=-999 required=5 tests=[AWL=-1.500, 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 LrVMDf8HXfVr for <ietf@ietfa.amsl.com>; Thu, 29 Nov 2012 01:39:47 -0800 (PST)
Received: from va3outboundpool.messaging.microsoft.com (va3ehsobe005.messaging.microsoft.com [216.32.180.31]) by ietfa.amsl.com (Postfix) with ESMTP id AE05721F8AD1 for <ietf@ietf.org>; Thu, 29 Nov 2012 01:39:47 -0800 (PST)
Received: from mail49-va3-R.bigfish.com (10.7.14.250) by VA3EHSOBE006.bigfish.com (10.7.40.26) with Microsoft SMTP Server id 14.1.225.23; Thu, 29 Nov 2012 09:39:46 +0000
Received: from mail49-va3 (localhost [127.0.0.1])	by mail49-va3-R.bigfish.com (Postfix) with ESMTP id 61D071602ED; Thu, 29 Nov 2012 09:39:46 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.253.197; KIP:(null); UIP:(null); IPV:NLI; H:DBXPRD0710HT005.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -25
X-BigFish: PS-25(zzbb2dI98dI9371I542M1432Izz1de0h1202h1d1ah1d2ahzz8275ch1033IL17326ah8275bh8275dhz2dh2a8h5a9h668h839hd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h304l1155h)
Received: from mail49-va3 (localhost.localdomain [127.0.0.1]) by mail49-va3 (MessageSwitch) id 1354181983791606_10917; Thu, 29 Nov 2012 09:39:43 +0000 (UTC)
Received: from VA3EHSMHS025.bigfish.com (unknown [10.7.14.251])	by mail49-va3.bigfish.com (Postfix) with ESMTP id B2FD91000B8; Thu, 29 Nov 2012 09:39:43 +0000 (UTC)
Received: from DBXPRD0710HT005.eurprd07.prod.outlook.com (157.56.253.197) by VA3EHSMHS025.bigfish.com (10.7.99.35) with Microsoft SMTP Server (TLS) id 14.1.225.23; Thu, 29 Nov 2012 09:39:43 +0000
Received: from SN2PRD0610HT001.namprd06.prod.outlook.com (157.56.234.133) by pod51017.outlook.com (10.255.79.168) with Microsoft SMTP Server (TLS) id 14.16.239.5; Thu, 29 Nov 2012 09:39:41 +0000
Message-ID: <004901cdce15$474bd6c0$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com>	<50B5C839.4060909@gmail.com>	<59924CD37D50616BA8EB8EF7@JcK-HP8200.jck.com>	<6.2.5.6.2.20121128023905.0afdcde0@resistor.net>	<50B683C4.2030503@stpeter.im><50B68612.7080107@dcrocker.net> <50B693ED.7000609@stpeter.im> <50B696B0.30904@qti.qualcomm.com>
Subject: Re: Barely literate minutes
Date: Thu, 29 Nov 2012 09:38:15 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [157.56.234.133]
X-OriginatorOrg: btconnect.com
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Nov 2012 09:39:48 -0000

----- Original Message -----
From: "Pete Resnick" <presnick@qti.qualcomm.com>
To: "Peter Saint-Andre" <stpeter@stpeter.im>
Cc: <dcrocker@bbiw.net>; "IETF discussion list" <ietf@ietf.org>
Sent: Wednesday, November 28, 2012 10:56 PM
> On 11/28/12 4:45 PM, Peter Saint-Andre wrote:
> > On 11/28/12 2:45 PM, Dave Crocker wrote:
> >
> >> ps. I'll repeat that I think f2f needs to be essentially irrelevant
> >> to the assessment of wg consensus, except perhaps as an efficiency
> >> hack that permits more terse exchanges on the mailing list.
> >>
> > That's a separate topic, but I tend to disagree. Why the heck even
> > have meetings? And I concur with Marc Blanchet that some WGs really
> > gel and make good progress in person but don't have great threads on
> > the mailing list.
> >
>
> It is a fact of life that some WGs only make progress face-to-face. I

Pete

I find that strange, not something I have ever seen (at least judging by
the minutes of WG meetings which I have not attended).

I see many WG which only make progress just prior to the closing of I-D
submission up to the point soon after submission reopens, but that is
not the same thing as making progress by meeting.

And I do know of two or so WG which make progress at a meeting; but they
seem to me to be WG that are too small to be a WG in the first place,
where the work is driven by less than half a dozen people who gain much
from meeting but where the breadth of experience and knowledge is
missing and where the output is then, for me, suspect.

WG of a substantial size seem to me to gain little or nothing from
meeting, as the minutes show.

Tom Petch








> think that's often a sign of a problem, but it's a fact. But if that
> happens, the chair needs to (with the help of minutes takers and other
> participants) post detailed notes of the discussion to the list and
ask
> for objections. That serves two functions: (a) It makes a record of
work
> that was done; and (b) it gives people who don't attend meetings
> (including new folks who come along) a chance to participate and voice
> their concerns. *Achievement* of consensus might have to occur f2f for
> some issues in some WGs, but it seems to me that *assessment* of
> consensus must be completely possible on the list, even if the only
> poster to the list is the chair with all of the f2f notes.
>
> pr
>
> --
> Pete Resnick<http://www.qualcomm.com/~presnick/>
> Qualcomm Technologies, Inc. - +1 (858)651-4478
>
>



From lear@cisco.com  Thu Nov 29 01:42:20 2012
Return-Path: <lear@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A872F21F88C8 for <ietf@ietfa.amsl.com>; Thu, 29 Nov 2012 01:42:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.098
X-Spam-Level: 
X-Spam-Status: No, score=-110.098 tagged_above=-999 required=5 tests=[AWL=0.500, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, 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 4mudCb4ng6yz for <ietf@ietfa.amsl.com>; Thu, 29 Nov 2012 01:42:20 -0800 (PST)
Received: from ams-iport-3.cisco.com (ams-iport-3.cisco.com [144.254.224.146]) by ietfa.amsl.com (Postfix) with ESMTP id D6A1721F8430 for <ietf@ietf.org>; Thu, 29 Nov 2012 01:42:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3742; q=dns/txt; s=iport; t=1354182140; x=1355391740; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=4K8iQZkbGSedwL3tnpHXqr17sB6OR1I9nVFCBHB6qEU=; b=hPlt8viyzXE6pVRpnB3GetLmH6kEBy3GpcmRJ4c2eNoAfOXLZ9XvOqvV 81ulL9B/zDKg3Qnpf+t2CvaVaTzwFbpO+1/uM77uPdH2hNLj6PgzyVkrn +Wm1MFoBfbRFnhzpc98j/BQuMzl03NIkdfrREz72smUmS+oNZSyXfTrdd c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ai4FAHEst1CQ/khM/2dsb2JhbABEgkmDYoVftBkWc4IeAQEBAwEOFUIJBgQBBQsLBAoTFgsCAgkDAgECAUUGDQEHAQGIBgasZZJlj22BEwOWAZBEgnM
X-IronPort-AV: E=McAfee;i="5400,1158,6910"; a="10003041"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-3.cisco.com with ESMTP; 29 Nov 2012 09:42:18 +0000
Received: from ams3-vpn-dhcp5205.cisco.com (ams3-vpn-dhcp5205.cisco.com [10.61.84.84]) by ams-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id qAT9gH0b013386 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 29 Nov 2012 09:42:18 GMT
Message-ID: <50B72DF9.9030901@cisco.com>
Date: Thu, 29 Nov 2012 10:42:17 +0100
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: Geoff Huston <gih@apnic.net>
Subject: Re: "IETF work is done on the mailing lists"
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <20121127231404.GC1941@verdi> <m2mwy26iud.wl%randy@psg.com> <50B63CA3.4040907@cisco.com> <D0EF612C-DFF5-4D16-BA96-F65204CC1CB2@apnic.net>
In-Reply-To: <D0EF612C-DFF5-4D16-BA96-F65204CC1CB2@apnic.net>
X-Enigmail-Version: 1.4.6
Content-Type: multipart/alternative; boundary="------------000507000401010203050705"
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Nov 2012 09:42:20 -0000

This is a multi-part message in MIME format.
--------------000507000401010203050705
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

[apologies to some for duplicates]

Hi Geoff,

On 11/29/12 3:56 AM, Geoff Huston wrote:

> It's nice to have reasonably well thought out ideas come in.
>
> Which then become highly defined precepts that become incredibly resistant to IETF change on the basis that they have been well thought out already (and probably are IPR-ridden) and at that stage the IETF process is functionally reduced to rubber stamping. At that stage the value of the IETF imprimatur becomes highly dubious to the industry its meant to serve.

In my experience, when the IETF has been offered work that the other
party felt was "complete" and would refuse to allow changes to, we've
demurred (c.f., html).  On the other hand, in the instances I'm aware,
when the IETF did accept the work, it was always made clear that the
IETF had change control (and used it).  A perfect current example of
this right now is scim.  There were numerous implementations of scim,
and it was brought to the IETF not only for the imprimatur but also to
improve the work.

A simpler explanation is that the authors and editors of work are more
immersed than others, and therefore project more authority.  Certainly
that has been the case in nearly all efforts I've been involved, with a
notable exception that also is illustrative: oauth, where an editor left
the IETF precisely because he could not agree with the results.  that's
a good indication that we're striking a balance.

Eliot



--------------000507000401010203050705
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-text-plain" wrap="true" graphical-quote="true"
      style="font-family: -moz-fixed; font-size: 12px;" lang="x-unicode">
      <pre wrap="">[apologies to some for duplicates]

Hi Geoff,

On 11/29/12 3:56 AM, Geoff Huston wrote:
</pre>
      <blockquote type="cite" style="color: #000000;">
        <pre wrap="">It's nice to have reasonably well thought out ideas come in.

Which then become highly defined precepts that become incredibly resistant to IETF change on the basis that they have been well thought out already (and probably are IPR-ridden) and at that stage the IETF process is functionally reduced to rubber stamping. At that stage the value of the IETF imprimatur becomes highly dubious to the industry its meant to serve.
</pre>
      </blockquote>
      <pre wrap="">In my experience, when the IETF has been offered work that the other
party felt was "complete" and would refuse to allow changes to, we've
demurred (c.f., html).  On the other hand, in the instances I'm aware,
when the IETF did accept the work, it was always made clear that the
IETF had change control (and used it).  A perfect current example of
this right now is scim.  There were numerous implementations of scim,
and it was brought to the IETF not only for the imprimatur but also to
improve the work.

A simpler explanation is that the authors and editors of work are more
immersed than others, and therefore project more authority.  Certainly
that has been the case in nearly all efforts I've been involved, with a
notable exception that also is illustrative: oauth, where an editor left
the IETF precisely because he could not agree with the results.  that's
a good indication that we're striking a balance.

Eliot


</pre>
    </div>
  </body>
</html>

--------------000507000401010203050705--

From superuser@gmail.com  Thu Nov 29 06:28:02 2012
Return-Path: <superuser@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5ABE221F89EF for <ietf@ietfa.amsl.com>; Thu, 29 Nov 2012 06:28:02 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Nezb7V1MNckf for <ietf@ietfa.amsl.com>; Thu, 29 Nov 2012 06:28:01 -0800 (PST)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id 2284D21F89E4 for <ietf@ietf.org>; Thu, 29 Nov 2012 06:28:00 -0800 (PST)
Received: by mail-lb0-f172.google.com with SMTP id y2so12472297lbk.31 for <ietf@ietf.org>; Thu, 29 Nov 2012 06:28:00 -0800 (PST)
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 :cc:content-type; bh=q2yejxyeAShJcn9Dg/lPqzSzd7jtjYZg07CM/3o+nAU=; b=h7z9djTj0CyUELwVbZIhSSrLuAd4oM+e6vquyJz6rjM9TzD2hQ84dpsdnlWyP1XX2R N9n0M1nCpfsta2ECMbTPUIxcdim+jlJ8Y7tXar8rwZsfOPN7dmvBtwKpdvP5m4nWpcEM 8YlUEEfN6oS/NM0Jx7rWoSfuHtaewDneV0rHYeKb2KSRTjTSdxylfL3hU4A3kQ0umaOA Z/cO0ZMlMWbfDIggscK2KLNRCEhQ437yJJwrLdigHan6pGMHJBRPG0s+rgu5V0mwT5cm ur96yuWpxljqWkfWuXGRDO1lPSkBl45r9NF2jowsMt/dEsiQvWvg+77apJFSJJqSOCTU pySQ==
MIME-Version: 1.0
Received: by 10.152.111.68 with SMTP id ig4mr22099005lab.50.1354199279926; Thu, 29 Nov 2012 06:27:59 -0800 (PST)
Received: by 10.112.61.67 with HTTP; Thu, 29 Nov 2012 06:27:59 -0800 (PST)
In-Reply-To: <50B632AD.7070909@dcrocker.net>
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <50B632AD.7070909@dcrocker.net>
Date: Thu, 29 Nov 2012 06:27:59 -0800
Message-ID: <CAL0qLwZ-pPkgLi2dRH2ezaMMS+jwt1kipb0f6KTT91kaua-SRw@mail.gmail.com>
Subject: Re: "IETF work is done on the mailing lists"
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: Dave Crocker <dcrocker@bbiw.net>
Content-Type: multipart/alternative; boundary=f46d04083b5108ffa504cfa31795
Cc: Barry Leiba <barryleiba@computer.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Nov 2012 14:28:02 -0000

--f46d04083b5108ffa504cfa31795
Content-Type: text/plain; charset=ISO-8859-1

I also support pushing back in those circumstances, but I do (or would, as
an AD) accept the minutes as a record of WG discussion.  Minutes are, or at
least are supposed to be, posted to the list for discussion and informal
approval by the WG.  This just means the minutes, especially about
documents that only got f2f discussion, need to be adequately detailed.
Often, they are not.

-MSK


On Wed, Nov 28, 2012 at 7:50 AM, Dave Crocker <dhc@dcrocker.net> wrote:

>
>
> On 11/27/2012 10:00 AM, Barry Leiba wrote:
>
>>   We see a string of versions posted, some with significant updates to
>> the text, but *no* corresponding mailing list discussion.  Nothing at
>> all.
>>
> ...
>
>  When I ask the responsible AD or the document shepherd about that, the
>> response is that, well, no one commented on the list, but it was
>> discussed in the face-to-face meetings.
>>
> ...
>
>  We accept that, and we review the document as usual, accepting the
>> document shepherd's writeup that says that the document has "broad
>> consensus of the working group."
>>
>> So here's my question:
>> Does the community want us to push back on those situations?
>>
>
>
> Just to add my own input to this:
>
> 'Want' is almost irrelevant. In formal terms, it does not matter what was
> discussed at the face-to-face nor what notes are taken about it.
>
> The formal rules of the IETF are that mailing lists are where formal
> decisions are made.
>
> The working group needs to establish /explicit/ support for changes /on
> the list/.
>
> You are reporting that, in formal terms, the IESG has been approving
> documents for which there is no formal record of community support...
>
>
> d/
>
> --
>  Dave Crocker
>  Brandenburg InternetWorking
>  bbiw.net
>

--f46d04083b5108ffa504cfa31795
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

I also support pushing back in those circumstances, but I do (or would, as =
an AD) accept the minutes as a record of WG discussion.=A0 Minutes are, or =
at least are supposed to be, posted to the list for discussion and informal=
 approval by the WG.=A0 This just means the minutes, especially about docum=
ents that only got f2f discussion, need to be adequately detailed.=A0 Often=
, they are not.<br>
<br>-MSK<br><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">O=
n Wed, Nov 28, 2012 at 7:50 AM, Dave Crocker <span dir=3D"ltr">&lt;<a href=
=3D"mailto:dhc@dcrocker.net" target=3D"_blank">dhc@dcrocker.net</a>&gt;</sp=
an> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im"><br>
<br>
On 11/27/2012 10:00 AM, Barry Leiba wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
=A0 We see a string of versions posted, some with significant updates to<br=
>
the text, but *no* corresponding mailing list discussion. =A0Nothing at<br>
all.<br>
</blockquote></div>
...<div class=3D"im"><br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
When I ask the responsible AD or the document shepherd about that, the<br>
response is that, well, no one commented on the list, but it was<br>
discussed in the face-to-face meetings.<br>
</blockquote></div>
...<div class=3D"im"><br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
We accept that, and we review the document as usual, accepting the<br>
document shepherd&#39;s writeup that says that the document has &quot;broad=
<br>
consensus of the working group.&quot;<br>
<br>
So here&#39;s my question:<br>
Does the community want us to push back on those situations?<br>
</blockquote>
<br>
<br></div>
Just to add my own input to this:<br>
<br>
&#39;Want&#39; is almost irrelevant. In formal terms, it does not matter wh=
at was discussed at the face-to-face nor what notes are taken about it.<br>
<br>
The formal rules of the IETF are that mailing lists are where formal decisi=
ons are made.<br>
<br>
The working group needs to establish /explicit/ support for changes /on the=
 list/.<br>
<br>
You are reporting that, in formal terms, the IESG has been approving docume=
nts for which there is no formal record of community support...<span class=
=3D"HOEnZb"><font color=3D"#888888"><br>
<br>
<br>
d/<br>
<br>
-- <br>
=A0Dave Crocker<br>
=A0Brandenburg InternetWorking<br>
=A0<a href=3D"http://bbiw.net" target=3D"_blank">bbiw.net</a><br>
</font></span></blockquote></div><br></div>

--f46d04083b5108ffa504cfa31795--

From vesely@tana.it  Thu Nov 29 06:30:20 2012
Return-Path: <vesely@tana.it>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5161F21F89E4 for <ietf@ietfa.amsl.com>; Thu, 29 Nov 2012 06:30:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.719
X-Spam-Level: 
X-Spam-Status: No, score=-4.719 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_DNSWL_MED=-4]
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 r-Yb8xUAypC7 for <ietf@ietfa.amsl.com>; Thu, 29 Nov 2012 06:30:13 -0800 (PST)
Received: from wmail.tana.it (mail.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id 799E521F89FC for <ietf@ietf.org>; Thu, 29 Nov 2012 06:30:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=beta; t=1354199411; bh=Cu5LXUur/NZENGo73U4iGSYcRbKsj6JJvmLZzKBr0Gw=; l=2186; h=Date:From:To:References:In-Reply-To; b=M8oqYVf6fms/UyLK1AWIF6a7et/d5hdIUgtuxyH3HSyiLUgGvvqKnKmnWRRJ40GNO DxmfwegciwWDBxLttuTU1AwTBUr9hMDq84sNagQEoVPkHirlnGrqf9HgVEb3ONXqB2 afMJSdJk4XR3cdTg+RXQUNDLLyw4ImILHetYvXBU=
Received: from [172.25.197.158] (pcale.tana [172.25.197.158]) (AUTH: CRAM-MD5 uXDGrn@SYT0/k, TLS: TLSv1/SSLv3,256bits,AES256-SHA) by wmail.tana.it with ESMTPSA; Thu, 29 Nov 2012 15:30:11 +0100 id 00000000005DC035.0000000050B77173.0000493D
Message-ID: <50B77173.9050507@tana.it>
Date: Thu, 29 Nov 2012 15:30:11 +0100
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: "IETF work is done on the mailing lists"
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <50B62B2D.1020603@network-heretics.com>
In-Reply-To: <50B62B2D.1020603@network-heretics.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Nov 2012 14:30:20 -0000

On Wed 28/Nov/2012 16:18:05 +0100 Keith Moore wrote:
> On 11/27/2012 01:00 PM, Barry Leiba wrote:
>> This brings up a question that I have as an AD: A number of times
>> since I started in this position in March, documents have come to
>> the IESG that prompted me (or another AD) to look into the document
>> history for... to find that there's basically no history. We see a
>> string of versions posted, some with significant updates to the
>> text, but *no* corresponding mailing list discussion. Nothing at
>> all. The first we see of the document on the mailing list is a
>> working group last call message, which gets somewhere between zero
>> and two responses (which say "It's ready."), and then it's sent to
>> the responsible AD requesting publication. When I ask the
>> responsible AD or the document shepherd about that, the response is
>> that, well, no one commented on the list, but it was discussed in
>> the face-to-face meetings. A look in the minutes of a few meetings
>> shows that it was discussed, but, of course, the minutes show little
>> or none of the discussion. We accept that, and we review the
>> document as usual, accepting the document shepherd's writeup that
>> says that the document has "broad consensus of the working group."
>> So here's my question: Does the community want us to push back on
>> those situations?
> 
> Please, please, please push back on those discussions.
> 
> Far too many documents are being represented as WG consensus, and then
> IETF consensus, when there's nothing of the sort.   This degrades the
> overall quality of IETF output, confuses the community of people who
> use IETF standards, and potentially does harm to the Internet by
> promoting use of protocols that haven't been carefully vetted.
> 
> Simply presenting a document at a face-to-face meeting and asking
> people to raise hands or hum in approval isn't sufficient.   A
> necessary condition for IESG consideration of a WG document should be
> that several people have posted to the WG mailing list that they've
> read it, and that they consider it desirable and sound.

+1, s/several/some/, especially if qualified.

jm2c

From ed.lewis@neustar.biz  Thu Nov 29 06:55:01 2012
Return-Path: <ed.lewis@neustar.biz>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3DA3821F8A91 for <ietf@ietfa.amsl.com>; Thu, 29 Nov 2012 06:55:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.112
X-Spam-Level: 
X-Spam-Status: No, score=-99.112 tagged_above=-999 required=5 tests=[AWL=-0.510, BAYES_50=0.001, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, 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 9Bjh-f-Qwe5G for <ietf@ietfa.amsl.com>; Thu, 29 Nov 2012 06:55:00 -0800 (PST)
Received: from eastrmfepo203.cox.net (eastrmfepo203.cox.net [68.230.241.218]) by ietfa.amsl.com (Postfix) with ESMTP id 5B76E21F8A9C for <ietf@ietf.org>; Thu, 29 Nov 2012 06:55:00 -0800 (PST)
Received: from eastrmimpo210 ([68.230.241.225]) by eastrmfepo203.cox.net (InterMail vM.8.01.04.00 201-2260-137-20101110) with ESMTP id <20121129145459.VQUX29905.eastrmfepo203.cox.net@eastrmimpo210> for <ietf@ietf.org>; Thu, 29 Nov 2012 09:54:59 -0500
Received: from [127.0.0.1] ([68.98.141.167]) by eastrmimpo210 with cox id VSuy1k00H3cuADQ01SuyCl; Thu, 29 Nov 2012 09:54:59 -0500
X-CT-Class: Clean
X-CT-Score: 0.00
X-CT-RefID: str=0001.0A020208.50B77743.017E,ss=1,re=0.000,fgs=0
X-CT-Spam: 0
X-Authority-Analysis: v=2.0 cv=R/2B6KtX c=1 sm=1 a=d1qrA6Qzssd1VjKW2xnq3A==:17 a=rF00rw514xQA:10 a=hGBaWAWWAAAA:8 a=tWcmSJXfkFgA:10 a=_uzwh7vSzyqAhrw6kWcA:9 a=CjuIK1q_8ugA:10 a=9k6G2--EmesA:10 a=agg2HGAVC6OLpUPsuK0A:9 a=_W_S_7VecoQA:10 a=G3reoBGSmkuZ1qkS:21 a=d1qrA6Qzssd1VjKW2xnq3A==:117
X-CM-Score: 0.00
Authentication-Results: cox.net; none
Subject: Re: "IETF work is done on the mailing lists"
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: multipart/alternative; boundary="Apple-Mail=_148DD917-9CD9-438B-859F-FEA883B93BA0"
From: Edward Lewis <ed.lewis@neustar.biz>
In-Reply-To: <50B72DF9.9030901@cisco.com>
Date: Thu, 29 Nov 2012 09:54:58 -0500
Message-Id: <968CBBD9-D7B1-4F27-A596-81A0EDE9C504@neustar.biz>
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <20121127231404.GC1941@verdi> <m2mwy26iud.wl%randy@psg.com> <50B63CA3.4040907@cisco.com> <D0EF612C-DFF5-4D16-BA96-F65204CC1CB2@apnic.net> <50B72DF9.9030901@cisco.com>
To: IETF discussion list <ietf@ietf.org>
X-Mailer: Apple Mail (2.1283)
Cc: Edward Lewis <ed.lewis@neustar.biz>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Nov 2012 14:55:01 -0000

--Apple-Mail=_148DD917-9CD9-438B-859F-FEA883B93BA0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Nov 29, 2012, at 4:42, Eliot Lear wrote:
> A simpler explanation is that the authors and editors of work are more
> immersed than others, and therefore project more authority.

To me, when "projecting authority" one is either demonstrating a deeper =
understanding of the topic than others or is bullying the others.  So I =
have a mixed reaction to that statement.  One the one hand it could be =
that work done elsewhere and brought the IETF comes along with people =
helping to educate the IETF or comes with people bullying the IETF.

I guess what I'm trying to express is that when baked work is brought =
into the IETF it is subjective whether the process is healthy or not.

Earlier in the thread I saw that someone expressed dismay that BOFs seem =
to be WG's that have already been meeting in secret.  I agree with that. =
 At the last meeting in Atlanta, I filled in sessions with BOFs and =
found that the ones I chose seemed as if they were already on the way to =
a predetermined solution.  Only one had a presentation trying to set up =
the problem to be solved, others just had detailed talks on draft =
solutions.  In one there was a complaint that the mail list wasn't very =
active - not a WG, a BOF!  Not very engaging.

Bringing in baked work because there are multiple independent and =
non-interoperable solutions is what the IETF is all about.  Bringing in =
a baked specification just to get a stamp on it is not.

=
-=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-
Edward Lewis            =20
NeuStar                    You can leave a voice message at =
+1-571-434-5468

There are no answers - just tradeoffs, decisions, and responses.


--Apple-Mail=_148DD917-9CD9-438B-859F-FEA883B93BA0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><div><div>On Nov 29, 2012, at 4:42, Eliot Lear =
wrote:</div><blockquote type=3D"cite"><div bgcolor=3D"#FFFFFF" =
text=3D"#000000"><div class=3D"moz-text-plain" wrap=3D"true" =
graphical-quote=3D"true" lang=3D"x-unicode"><pre wrap=3D"">A simpler =
explanation is that the authors and editors of work are more
immersed than others, and therefore project more =
authority.</pre></div></div></blockquote></div><div>To me, when =
"projecting authority" one is either demonstrating a deeper =
understanding of the topic than others or is bullying the others. =
&nbsp;So I have a mixed reaction to that statement. &nbsp;One the one =
hand it could be that work done elsewhere and brought the IETF comes =
along with people helping to educate the IETF or comes with people =
bullying the IETF.</div><div><br></div><div>I guess what I'm trying to =
express is that when baked work is brought into the IETF it is =
subjective whether the process is healthy or =
not.</div><div><br></div><div>Earlier in the thread I saw that someone =
expressed dismay that BOFs seem to be WG's that have already been =
meeting in secret. &nbsp;I agree with that. &nbsp;At the last meeting in =
Atlanta, I filled in sessions with BOFs and found that the ones I chose =
seemed as if they were already on the way to a predetermined solution. =
&nbsp;Only one had a presentation trying to set up the problem to be =
solved, others just had detailed talks on draft solutions. &nbsp;In one =
there was a complaint that the mail list wasn't very active - not a WG, =
a BOF! &nbsp;Not very engaging.</div><div><br></div><div>Bringing in =
baked work because there are multiple independent and non-interoperable =
solutions is what the IETF is all about. &nbsp;Bringing in a baked =
specification just to get a stamp on it is not.</div><br><div>
<span class=3D"Apple-style-span" style=3D"border-collapse: separate; =
color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: =
0px; text-transform: none; white-space: normal; widows: 2; word-spacing: =
0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; =
">-=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<span></sp=
an>-=3D-=3D-=3D-<span class=3D"Apple-style-span" style=3D"border-collapse:=
 separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; orphans: 2; text-align: -webkit-auto; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div><div>Edward =
Lewis&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<span></s=
pan>&nbsp;&nbsp;&nbsp;<br>NeuStar&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;<span></span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp; You can leave a voice message at =
+1-571-434-5468<br><br>There are no answers - just tradeoffs, decisions, =
and responses.</div></div></div></span></span>
</div>
<br></div></body></html>=

--Apple-Mail=_148DD917-9CD9-438B-859F-FEA883B93BA0--

From barryleiba.mailing.lists@gmail.com  Thu Nov 29 07:11:32 2012
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B261E21F8773 for <ietf@ietfa.amsl.com>; Thu, 29 Nov 2012 07:11:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.977
X-Spam-Level: 
X-Spam-Status: No, score=-102.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, 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 WCKSiGUUGPMr for <ietf@ietfa.amsl.com>; Thu, 29 Nov 2012 07:11:32 -0800 (PST)
Received: from mail-la0-f44.google.com (mail-la0-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id D6A3521F8660 for <ietf@ietf.org>; Thu, 29 Nov 2012 07:11:31 -0800 (PST)
Received: by mail-la0-f44.google.com with SMTP id d3so12336691lah.31 for <ietf@ietf.org>; Thu, 29 Nov 2012 07:11:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=5zzR2JPvlxxZVsuXbl/nzIQWJOmHcROEVYPlLbHha0o=; b=iQN+zLgc3BcIoQM7BNs1s7BB04QGMyz1ydt/od0strbw6q/XcNw2GWz7P+/HMO1DS7 WAHH4VEwSIb4O0G4cSyfHcHvvCQcj8kBCNPyFxPSunlk+nFhnxpQr02Sjc50zHdvA8eQ wSuen73eK79YWYl+i347NSWI9KbIdeT5MvKfzZlGnrqY2+fByAaOk9yqwVRJ1FYYf6hj exnOLxrZDOkfUW4zdCpLnSK2wsZEvNj30POoWC5fyPG88MDrgxc9a8dPKpc7FB2uKavr QeKtlIKE02pgckUb1fO2p2wI7GVw/gXeKl3dXYmOw32H5e6wwyD8pIfB3ynSYlNNh2DD 79EQ==
MIME-Version: 1.0
Received: by 10.112.10.34 with SMTP id f2mr10067480lbb.47.1354201890612; Thu, 29 Nov 2012 07:11:30 -0800 (PST)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.112.12.166 with HTTP; Thu, 29 Nov 2012 07:11:30 -0800 (PST)
In-Reply-To: <50B696B0.30904@qti.qualcomm.com>
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <50B5C839.4060909@gmail.com> <59924CD37D50616BA8EB8EF7@JcK-HP8200.jck.com> <6.2.5.6.2.20121128023905.0afdcde0@resistor.net> <50B683C4.2030503@stpeter.im> <50B68612.7080107@dcrocker.net> <50B693ED.7000609@stpeter.im> <50B696B0.30904@qti.qualcomm.com>
Date: Thu, 29 Nov 2012 10:11:30 -0500
X-Google-Sender-Auth: -wU1QHY-AFNvDsUWqRs4G3Fi38s
Message-ID: <CAC4RtVAG+pKSQMwPyB6GJ7jxJM4hNpU81Yt8he6ZsEMrg_rTbQ@mail.gmail.com>
Subject: Re: Barely literate minutes
From: Barry Leiba <barryleiba@computer.org>
To: IETF discussion list <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Nov 2012 15:11:32 -0000

On Wed, Nov 28, 2012 at 5:56 PM, Pete Resnick <presnick@qti.qualcomm.com> wrote:
...
> chair needs to (with the help of minutes takers and other participants) post
> detailed notes of the discussion to the list and ask for objections. That
> serves two functions: (a) It makes a record of work that was done; and (b)
> it gives people who don't attend meetings (including new folks who come
> along) a chance to participate and voice their concerns. *Achievement* of
> consensus might have to occur f2f for some issues in some WGs, but it seems
> to me that *assessment* of consensus must be completely possible on the
> list, even if the only poster to the list is the chair with all of the f2f
> notes.

What I would prefer to see is that in addition to minutes there be
separate messages posted to the list for each document, detailing the
discussion of that document in the meeting and the changes that will
result from the discussion.  That can be posted by the chair, but I'd
really expect it to come from a document editor.  That makes sure that
everyone can see what the document editor heard and intends to do with
the document, and allows the working group to continue the discussion
or say, "Yes, that's what we heard as well, and it's fine."

And I think that should be posted as soon after the meeting session as
possible.  It should definitely not wait for the document updates to
be done, perhaps weeks later, after everyone who was there has
forgotten the details.

I think I have a topic to discuss at the App chairs lunch in Orlando.  :-)

Barry

From dhc@dcrocker.net  Thu Nov 29 07:36:39 2012
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C436521F85ED for <ietf@ietfa.amsl.com>; Thu, 29 Nov 2012 07:36:39 -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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7WJqk78mbBvb for <ietf@ietfa.amsl.com>; Thu, 29 Nov 2012 07:36:39 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 32C3921F85E2 for <ietf@ietf.org>; Thu, 29 Nov 2012 07:36:39 -0800 (PST)
Received: from [192.168.1.9] (adsl-67-127-190-125.dsl.pltn13.pacbell.net [67.127.190.125]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id qATFaccM004073 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Thu, 29 Nov 2012 07:36:38 -0800
Message-ID: <50B78102.1020705@dcrocker.net>
Date: Thu, 29 Nov 2012 07:36:34 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Barely literate minutes
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <50B5C839.4060909@gmail.com> <59924CD37D50616BA8EB8EF7@JcK-HP8200.jck.com> <6.2.5.6.2.20121128023905.0afdcde0@resistor.net> <50B683C4.2030503@stpeter.im> <50B68612.7080107@dcrocker.net> <50B693ED.7000609@stpeter.im> <50B696B0.30904@qti.qualcomm.com> <m2lidl5ntp.wl%randy@psg.com> <BB22CC86-F9B8-4727-BCA3-F617221944F2@gmail.com>
In-Reply-To: <BB22CC86-F9B8-4727-BCA3-F617221944F2@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Thu, 29 Nov 2012 07:36:39 -0800 (PST)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Nov 2012 15:36:39 -0000

On 11/28/2012 3:57 PM, Bob Hinden wrote:
> It's much easier to reach a consensus face to face, than on a mailing list.  I think we have all seen this.


F2f meetings are explicitly managed, with significant control of the 
room.  Mailing list exchanges are typically not managed at all.

Given the difference, it's not surprising that one proves more 
productive than the other.

d/

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From wesley.george@twcable.com  Thu Nov 29 08:25:29 2012
Return-Path: <wesley.george@twcable.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1A1EE21F860E for <ietf@ietfa.amsl.com>; Thu, 29 Nov 2012 08:25:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.738
X-Spam-Level: 
X-Spam-Status: No, score=-0.738 tagged_above=-999 required=5 tests=[AWL=0.725,  BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, 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 tA3ceSrfVQvT for <ietf@ietfa.amsl.com>; Thu, 29 Nov 2012 08:25:27 -0800 (PST)
Received: from cdpipgw01.twcable.com (cdpipgw01.twcable.com [165.237.59.22]) by ietfa.amsl.com (Postfix) with ESMTP id C721021F8AEB for <ietf@ietf.org>; Thu, 29 Nov 2012 08:25:23 -0800 (PST)
X-SENDER-IP: 10.136.163.12
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.84,184,1355115600"; d="scan'208";a="479886851"
Received: from unknown (HELO PRVPEXHUB03.corp.twcable.com) ([10.136.163.12]) by cdpipgw01.twcable.com with ESMTP/TLS/RC4-MD5; 29 Nov 2012 11:23:45 -0500
Received: from PRVPEXVS15.corp.twcable.com ([10.136.163.79]) by PRVPEXHUB03.corp.twcable.com ([10.136.163.12]) with mapi; Thu, 29 Nov 2012 11:24:10 -0500
From: "George, Wes" <wesley.george@twcable.com>
To: Barry Leiba <barryleiba@computer.org>
Date: Thu, 29 Nov 2012 11:24:23 -0500
Subject: RE: When to adopt a draft as a WG doc (was RE: "IETF work is done on the mailing lists")
Thread-Topic: When to adopt a draft as a WG doc (was RE: "IETF work is done on the mailing lists")
Thread-Index: Ac3NgUYYjxrF4cvXSdur4QEEC1KpeQAtzuYw
Message-ID: <2671C6CDFBB59E47B64C10B3E0BD59230338A657EC@PRVPEXVS15.corp.twcable.com>
References: <2671C6CDFBB59E47B64C10B3E0BD5923033897C9BF@PRVPEXVS15.corp.twcable.com> <CALaySJLT=6RTZahqB1LO_Aw=7sAMiyrXK=xacwrBgLieZhqeDw@mail.gmail.com>
In-Reply-To: <CALaySJLT=6RTZahqB1LO_Aw=7sAMiyrXK=xacwrBgLieZhqeDw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Nov 2012 16:25:29 -0000

> From: barryleiba@gmail.com [mailto:barryleiba@gmail.com] On Behalf Of
> Barry Leiba
>
> There is no formal process that involves "adopting" anything.  Working
> group chairs appoint document editors (this is in RFC 2418, Section
> 6.3).  There is nothing anywhere that specifies how the first version of
> a WG document is formed.
[WEG] snip
> We seem to have settled into
> a culture of starting with individual submissions and "adopting"
> them, but there's nothing that requires that

[WEG] What this says to me is that we are adhering to an ad hoc or de facto=
 process, and therefore in most cases we're not really thinking about why w=
e do it, or even if we should, we're just going with the flow of past prece=
dent. AKA, "that's the way we've always done it/that's just the way we do t=
hings around here". We wouldn't do that with a technical protocol that we d=
efined, we'd update the standard to reflect reality as implemented. So why =
are we behaving differently with our internal protocol?
If it works and people like it, let's document it so that it can be applied=
 consistently. If people think it's unnecessary and we should stick to the =
documentation as written (no adoption), let's do that. If we actively *don'=
t* want an IETF-wide procedure here, we can even document that the process =
for WG adoption of drafts is WG-specific and could document those specifics=
 in a WG policies wiki document maintained by the chairs. There are plenty =
of WGs that have specific ways that they like to handle document submission=
, reviews, and requests for agenda time. It might be useful to have that al=
l in one place so that people can know what's expected of them.
>
> So, yes, the chairs get to decide how they want to seed the document
> development process, and they have a pretty free hand in making that
> decision.  Your ADs are always there for further guidance if you need or
> want it.  But there's no formal process for that, and I think that's how
> we want it to be.
[WEG] Barry, I respectfully disagree. The whole point I'm making here (and =
Geoff underscored nicely) is that it's currently too variable and too relia=
nt on a small group of individual volunteers implementing it correctly. Whe=
n things are not documented, we are dependent on having leadership who inna=
tely know how to do the right thing. But that leadership turns over fairly =
frequently. so assuming that we'll always have people in leadership who kno=
w how to make this process work "correctly" without some guidance is pretty=
 risky, IMO. As the IETF ages and grows, and personnel (participants and le=
aders) turn over, the oral tradition breaks down in a hurry. Further, no ma=
tter how good the individuals are at their "jobs" within the IETF, applying=
 undocumented policy (especially doing it inconsistently) looks to the outs=
ide world as arbitrary and capricious, or as centralizing authority, and th=
at's not at all productive in an open standards development process. It can=
 be discouraging to new participants, because it contributes to the overwhe=
lming nature of figuring out how to get started as a new document author, a=
nd it can make the process seem more closed than it actually is.

It is quite possible to document a policy or procedure with directional gui=
dance and enough flexibility to allow intelligent adults to think for thems=
elves and adapt to the reality of the situation during implementation. I'm =
willing to work on an update to 2418 to cover this apparent gap, but I'd li=
ke to know whether others agree that this is a problem (and are willing to =
work on the update with me).

Wes George


This E-mail and any of its attachments may contain Time Warner Cable propri=
etary information, which is privileged, confidential, or subject to copyrig=
ht belonging to Time Warner Cable. This E-mail is intended solely for the u=
se of the individual or entity to which it is addressed. If you are not the=
 intended recipient of this E-mail, you are hereby notified that any dissem=
ination, distribution, copying, or action taken in relation to the contents=
 of and attachments to this E-mail is strictly prohibited and may be unlawf=
ul. If you have received this E-mail in error, please notify the sender imm=
ediately and permanently delete the original and any copy of this E-mail an=
d any printout.

From barryleiba@gmail.com  Thu Nov 29 11:06:43 2012
Return-Path: <barryleiba@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 68E6321F8B4D for <ietf@ietfa.amsl.com>; Thu, 29 Nov 2012 11:06:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.977
X-Spam-Level: 
X-Spam-Status: No, score=-102.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, 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 sRcLqOLXUGMS for <ietf@ietfa.amsl.com>; Thu, 29 Nov 2012 11:06:42 -0800 (PST)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id A5FD621F8B26 for <ietf@ietf.org>; Thu, 29 Nov 2012 11:06:42 -0800 (PST)
Received: by mail-vb0-f44.google.com with SMTP id fc26so8053992vbb.31 for <ietf@ietf.org>; Thu, 29 Nov 2012 11:06:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=XlBMykzUyryRVtaJ/HAlEFbgKGaVdj8hn04mhTfciEk=; b=iCYFKPd9nZIou5fXr+KV4h6TVrdmdoYyfdIt0HjHkHdCtDiwhMKPPmg1Q6ck91svN5 HiTDbt2EdKsEL27iB14YmvuFTa0Gl6WeDr2K+W7EccyPp+8wlDWAQlwxAvfdz4hhd/nx ZazFyCTGgLwc8Ji0sY2RZEccl0phmpyKJULvWnUQL7sUNtCRvXLJCwwjXuJpltvVRNxw vIEeeK49lUm1EyLWUGHOjof/p7oisqsNdmzg6K08zJBfepcGcjGzmS5HV7PBrFAJ/9vi CrE0NXXSIBbfRiE0qmWYc9VZKXZsP4r1AEHr9G//xppBOIset6xsLXid40rA3FNixPHp nBqQ==
MIME-Version: 1.0
Received: by 10.220.119.196 with SMTP id a4mr32918753vcr.19.1354216000484; Thu, 29 Nov 2012 11:06:40 -0800 (PST)
Sender: barryleiba@gmail.com
Received: by 10.58.28.231 with HTTP; Thu, 29 Nov 2012 11:06:40 -0800 (PST)
In-Reply-To: <2671C6CDFBB59E47B64C10B3E0BD59230338A657EC@PRVPEXVS15.corp.twcable.com>
References: <2671C6CDFBB59E47B64C10B3E0BD5923033897C9BF@PRVPEXVS15.corp.twcable.com> <CALaySJLT=6RTZahqB1LO_Aw=7sAMiyrXK=xacwrBgLieZhqeDw@mail.gmail.com> <2671C6CDFBB59E47B64C10B3E0BD59230338A657EC@PRVPEXVS15.corp.twcable.com>
Date: Thu, 29 Nov 2012 14:06:40 -0500
X-Google-Sender-Auth: clTuyN-FBBt_otJoryWxLSmShq4
Message-ID: <CALaySJ+1LX6kzpDZYwQaJAqkzH4zLdRoMaJNH9HcHQG-78jA7Q@mail.gmail.com>
Subject: Re: When to adopt a draft as a WG doc (was RE: "IETF work is done on the mailing lists")
From: Barry Leiba <barryleiba@computer.org>
To: "George, Wes" <wesley.george@twcable.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Nov 2012 19:06:43 -0000

> If we actively *don't*
> want an IETF-wide procedure here, we can even document that the process
> for WG adoption of drafts is WG-specific and could document those specifics
> in a WG policies wiki document maintained by the chairs.

I believe that one is the case, though others can weigh in with
opinions as well.  Yes, we could change our documentation to
explicitly say that this particular decision is a management choice.
But I'll caution you against trying to do that in general: we have a
million things that are unspecified and should be unspecified and left
to management choice.  Trying to find all of those and explicitly say
so will be a frustrating exercise, and one that won't have a lot of
value in the end.  In general, we specify what we want to specify, and
what's left is up to judgment and management.

> Further, no matter how good the individuals are at their "jobs" within the IETF,
> applying undocumented policy (especially doing it inconsistently) looks to the
> outside world as arbitrary and capricious

Here's where we have a gap, you and I: what you call undocumented
policy I call a management choice.  How to assign document editors is
a management choice.  How to record track issues is a management
choice.  How much to open up general discussion, vs requiring focus on
certain things now, and others later, is a management choice.  Whether
to process one or two documents at a time, or do five or six is a
management choice.  Even whether to have a formal "working group last
call" is a management choice -- that one *is* discussed in 2418,
because it's common enough and we thought it important enough.  But a
WGC who decides it's not necessary for a particular document isn't
violating any process or policy.

We hire the best and the brightest as our working group chairs in
order to rely on their judgment and management abilities, exactly
because a lot of flexibility is necessary, so a lot of judgment is
necessary as well.

Again, trying to nail everything down isn't desirable.  And even
trying to nail down the list of things that aren't nailed down isn't,
as I see it.

Barry

From melinda.shore@gmail.com  Thu Nov 29 11:45:48 2012
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0196A21F8BDC for <ietf@ietfa.amsl.com>; Thu, 29 Nov 2012 11:45:48 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ov0aWbu63DJN for <ietf@ietfa.amsl.com>; Thu, 29 Nov 2012 11:45:47 -0800 (PST)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id 80CB121F8BF5 for <ietf@ietf.org>; Thu, 29 Nov 2012 11:45:47 -0800 (PST)
Received: by mail-pb0-f44.google.com with SMTP id uo1so10516758pbc.31 for <ietf@ietf.org>; Thu, 29 Nov 2012 11:45:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=HyBxZbFrCPhYuJl95kv6CBg4lAJEwliPMb2oXllkYzs=; b=MyWuTKtGRqUz6ql9QWX2FIxTo+enFOIekYU0EppQodmJu9ZK0hp4WahZ3brB4mhquM Dch9ErCFw3Sv39dBIPgii13h/AYu55dGjGm+fWn8dziZRXbuqEWS+xIJHZr4CQ0rLcnX x1dd4Onj3Ikewtc352IIQOVnaLuEQqG3w92aDbTvTvGQXpTi99cojnukwl4QOyDlN+Hx nt0JZF7Qyxg5Gf7B7Wn6/pjrRbkaDNEHdQrFjhXgX9a6CoOYLB3n4f62wpkvMTUNx1UY 4uPtsG2rLgQFJbGax0jA9PZepGTp5KWzBsTog/OC7kuuxT+7y9cUEIUokV5juq6vfYLD CXGg==
Received: by 10.68.189.5 with SMTP id ge5mr71056259pbc.1.1354218347258; Thu, 29 Nov 2012 11:45:47 -0800 (PST)
Received: from spandex.local (66-230-101-170-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.101.170]) by mx.google.com with ESMTPS id ai8sm1684972pbd.14.2012.11.29.11.45.45 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 29 Nov 2012 11:45:46 -0800 (PST)
Message-ID: <50B7BB68.4050807@gmail.com>
Date: Thu, 29 Nov 2012 10:45:44 -0900
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: When to adopt a draft as a WG doc (was RE: "IETF work is done on the mailing lists")
References: <2671C6CDFBB59E47B64C10B3E0BD5923033897C9BF@PRVPEXVS15.corp.twcable.com> <CALaySJLT=6RTZahqB1LO_Aw=7sAMiyrXK=xacwrBgLieZhqeDw@mail.gmail.com> <2671C6CDFBB59E47B64C10B3E0BD59230338A657EC@PRVPEXVS15.corp.twcable.com> <CALaySJ+1LX6kzpDZYwQaJAqkzH4zLdRoMaJNH9HcHQG-78jA7Q@mail.gmail.com>
In-Reply-To: <CALaySJ+1LX6kzpDZYwQaJAqkzH4zLdRoMaJNH9HcHQG-78jA7Q@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Nov 2012 19:45:48 -0000

On 11/29/12 10:06 AM, Barry Leiba wrote:
> I believe that one is the case, though others can weigh in with
> opinions as well.  Yes, we could change our documentation to
> explicitly say that this particular decision is a management choice.
> But I'll caution you against trying to do that in general: we have a
> million things that are unspecified and should be unspecified and left
> to management choice.  Trying to find all of those and explicitly say
> so will be a frustrating exercise, and one that won't have a lot of
> value in the end.  In general, we specify what we want to specify, and
> what's left is up to judgment and management.

Hear, hear (and I feel pretty strongly about this).  There are
correction mechanisms if someone feels that a process has gone
off the rails and I prefer to rely on those than trying to
micromanage IETF process.  Right now it seems to be the case
that keeping much unspecified and having strong chairs is a better
use of limited resources than trying to shove everything into a
box.  I'll note that it seems possible that overspecifying process
could potentially cause more protests rather than fewer.

Melinda


From sm@resistor.net  Thu Nov 29 11:58:01 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B51A121F8C35 for <ietf@ietfa.amsl.com>; Thu, 29 Nov 2012 11:58:01 -0800 (PST)
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=[AWL=0.000, 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 4WbtSXa6zzxA for <ietf@ietfa.amsl.com>; Thu, 29 Nov 2012 11:58:01 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id E222021F8C32 for <ietf@ietf.org>; Thu, 29 Nov 2012 11:58:00 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id qATJvq1F006932; Thu, 29 Nov 2012 11:57:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1354219078; bh=gy63S6nm6JB72LukLtF39obBKFGa7N8ybaRiykXhzTg=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=UVJ1BkDxpE7SJBz5Eg9o7QtvjyExVJhvCTDwzoeIsWEsdJ7/JQXA0HeGYbQ6wges1 JJdMrCvsp7VCQ4wguAOgaMIaVxGuZ3IpSvdxOnX4k7tULykWye3KoqhQwF4X/Onko/ xYKyNmfWjoIv8TDgF07+CHK1xPsGxL6ChYtExeRs=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1354219078; i=@resistor.net; bh=gy63S6nm6JB72LukLtF39obBKFGa7N8ybaRiykXhzTg=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=d0610xOE0eg4FGNxCSY6iTBBTdHMZ6B++ZwAv2NOkOoRf6AzKvon5l9Iyk3tWByqO mLqDgTAo3I7yuD2dw7MVi5D5bcuoJW8NVlXDIFx5PwN6mr4ZCpbi6ZaQojxF+kxgEv KI+d33NHt/e3QnHZ/yyiDXATEM5DXNYD0JdifPXk=
Message-Id: <6.2.5.6.2.20121129082748.09ea5878@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 29 Nov 2012 10:51:22 -0800
To: Edward Lewis <ed.lewis@neustar.biz>
From: SM <sm@resistor.net>
Subject: Re: "IETF work is done on the mailing lists"
In-Reply-To: <968CBBD9-D7B1-4F27-A596-81A0EDE9C504@neustar.biz>
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <20121127231404.GC1941@verdi> <m2mwy26iud.wl%randy@psg.com> <50B63CA3.4040907@cisco.com> <D0EF612C-DFF5-4D16-BA96-F65204CC1CB2@apnic.net> <50B72DF9.9030901@cisco.com> <968CBBD9-D7B1-4F27-A596-81A0EDE9C504@neustar.biz>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Nov 2012 19:58:01 -0000

Hi Ed,
At 06:54 29-11-2012, Edward Lewis wrote:
>Earlier in the thread I saw that someone expressed dismay that BOFs 
>seem to be WG's that have already been meeting in secret.  I agree 
>with that.  At the last meeting in Atlanta, I filled in sessions 
>with BOFs and found that the ones I chose seemed as if they were 
>already on the way to a predetermined solution.  Only one had a 
>presentation trying to set up the problem to be solved, others just 
>had detailed talks on draft solutions.  In one there was a complaint 
>that the mail list wasn't very active - not a WG, a BOF!  Not very engaging.

Christopher DearLove used the term [1] "inner circle".  There are 
people who will meet outside of the sessions listed on the agenda to 
discuss some predetermined solution.  By the time the problem gets to 
be discussed in a BoF there might be a draft proposing a solution.

Picking a few BoFs from the last agenda:

   RFC Format BoF

It was pointed out that it was not a BoF.  The agenda [2] mentions 
"Applicability of previously proposed solutions".  It does not 
provide any details about the proposed solutions.  I think that some 
people asked about that before the meeting.

   HTTPAUTH BoF

The agenda mentions [3] "5 presentations".  It does not list the 
presentations.  The people who have been reading the relevant mailing 
list would be able to know what might be presented.

   WPKOPS BoF

The agenda [4] does not mention any proposed solution.  There is an 
IETF mailing list where there was prior discussion about that BoF.

   Extensions of the Bonjour Protocol Suite (mdnsext) BoF

The agenda [5] mentions "Goals of the BoF" with a link.  I don't 
recall whether any proposed solution was discussed.

People generally complain when a mailing list is active.  When a 
mailing list is very active people start insulting each other.

Scott Brim posted a policy that was tried [6].  I doubt that there 
would be IETF consensus about implementing that across all IETF sessions.

As for engaging mailing lists, well, they can end up being 
unmanageable.  I'll mention an example.  This thread is a sub-thread 
where an Area Director [7] suggested "Please be brief and 
polite".  Nobody in their right mind would attempt to enforce that.

>Bringing in baked work because there are multiple independent and 
>non-interoperable solutions is what the IETF is all about.  Bringing 
>in a baked specification just to get a stamp on it is not.

Some people like having that stamp.

Regards,
-sm


1. http://www.ietf.org/mail-archive/web/ietf/current/msg76024.html
2. http://tools.ietf.org/agenda/85/agenda-85-rfcform.html
3. http://tools.ietf.org/agenda/85/agenda-85-httpauth.html
4. http://tools.ietf.org/agenda/85/agenda-85-wpkops.html
5. http://tools.ietf.org/agenda/85/agenda-85-mdnsext.html
6. http://www.ietf.org/mail-archive/web/ietf/current/msg76042.html
7. http://www.ietf.org/mail-archive/web/ietf/current/msg76001.html 


From sm@resistor.net  Thu Nov 29 13:03:39 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 69CAF21F8BB0 for <ietf@ietfa.amsl.com>; Thu, 29 Nov 2012 13:03:39 -0800 (PST)
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=-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 yGheAdYCUuIf for <ietf@ietfa.amsl.com>; Thu, 29 Nov 2012 13:03:38 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id B6D5A21F885F for <ietf@ietf.org>; Thu, 29 Nov 2012 13:03:38 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id qATL3UCS001814; Thu, 29 Nov 2012 13:03:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1354223016; bh=zSWtYhv06gGT1u36fDWiMoDJP2wItle8MDfVxzYRADU=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=UtANp/5qJnKmMmqKBxC0mIAQymBgFxP+kBhO2zdfGY20TDWwiucDdXbcPkx6SmWTb iQO4VL/xxocqXJOxf88hLDSQLPmZ2HRdRGDygUDiJWRc/Dtfufkr6kMxu4XXBpXaVb nT4/xwsZDijiOIVw6R3bC+PDsks5dBLCYLXugF2Q=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1354223016; i=@resistor.net; bh=zSWtYhv06gGT1u36fDWiMoDJP2wItle8MDfVxzYRADU=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=J1jV2KNrosa6ONs+/oz8jl9j3czpNH5/LMdpnCHhHPZDmgccUP0SCNIKYvnG9Az8T HzmiPvxDFFs1e0APs1r4Ps2D1eZr4QEdznb5jtGbiD3Wo2DSnXyHmutnkZgaIdMa44 /9n49dV20329yBOgdlaNX9RdA94ekJvh3KYd1b0Y=
Message-Id: <6.2.5.6.2.20121129105444.0b8d3400@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 29 Nov 2012 12:03:59 -0800
To: IETF discussion list <ietf@ietf.org>
From: SM <sm@resistor.net>
Subject: RE: When to adopt a draft as a WG doc (was RE: "IETF work is done on the mailing lists")
In-Reply-To: <2671C6CDFBB59E47B64C10B3E0BD59230338A657EC@PRVPEXVS15.corp .twcable.com>
References: <2671C6CDFBB59E47B64C10B3E0BD5923033897C9BF@PRVPEXVS15.corp.twcable.com> <CALaySJLT=6RTZahqB1LO_Aw=7sAMiyrXK=xacwrBgLieZhqeDw@mail.gmail.com> <2671C6CDFBB59E47B64C10B3E0BD59230338A657EC@PRVPEXVS15.corp.twcable.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Nov 2012 21:03:39 -0000

At 08:24 29-11-2012, George, Wes wrote:
>adoption), let's do that. If we actively *don't* want an IETF-wide 
>procedure here, we can even document that the process for WG 
>adoption of drafts is WG-specific and could document those specifics 
>in a WG policies wiki document maintained by the chairs. There are 
>plenty of WGs that have specific ways that they like to handle 
>document submission, reviews, and requests for agenda time. It might 
>be useful to have that all in one place so that people can know 
>what's expected of them.

There is a wiki for WG Chairs.  Melinda Shore posted some comments on 
this list several months ago.  She followed up and added material to 
the wiki [1].  There must be over a hundred WG Chairs.  Only a 
handful of them have bothered to add material to the wiki.

>[WEG] Barry, I respectfully disagree. The whole point I'm making 
>here (and Geoff underscored nicely) is that it's currently too 
>variable and too reliant on a small group of individual volunteers 
>implementing it correctly. When things are not documented, we

The problem which Geoff Huston commented about might have occurred in 
a working group within the Routing Area.

According to some RFC:

   "All relevant documents to be discussed at a session should be published
    and available as Internet-Drafts at least two weeks before
    a session starts."

If the above was followed there shouldn't be any draft submissions 
during the week a meeting is held.  The following working groups 
posted drafts during that period:

  DHC
  BMWG
  MPLS
  TSVWG
  MMUSIC
  CODEC
  6MAN
  MANET
  HIP
  APPSAWG
  P2PSIP
  SAVI
  DIME
  DNSOP
  OAUTH
  IDR
  SIPREC
  SIPCORE
  L2VPN
  FECFRAME
  MILE
  EAI
  STRAW
  PRECIS
  XMPP
  JOSE
  PCP
  URNBIS
  LISP
  NFSV4
  MBONED
  SIPCLF
  OPSEC
  TRILL
  CCAMP
  MIF
  REPUTE
  ECRIT
  PAWS

At 11:45 29-11-2012, Melinda Shore wrote:
box.  I'll note that it seems possible that overspecifying process
>could potentially cause more protests rather than fewer.

Yes.  Section 6.5.1 of a document, which everyone claims to have read 
and understood, spells out what people should do if they want to protest.

Regards,
-sm

1. http://www.ietf.org/mail-archive/web/ietf/current/msg75826.html  


From wjhns1@hardakers.net  Thu Nov 29 13:14:16 2012
Return-Path: <wjhns1@hardakers.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D1A821F8C3A for <ietf@ietfa.amsl.com>; Thu, 29 Nov 2012 13:14:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.555
X-Spam-Level: 
X-Spam-Status: No, score=-2.555 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DATE_IN_PAST_03_06=0.044]
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 NtomTop7PWcC for <ietf@ietfa.amsl.com>; Thu, 29 Nov 2012 13:14:15 -0800 (PST)
Received: from mail.hardakers.net (unknown [IPv6:2001:470:1f00:187::1]) by ietfa.amsl.com (Postfix) with ESMTP id D3A7E21F8C38 for <ietf@ietf.org>; Thu, 29 Nov 2012 13:14:15 -0800 (PST)
Received: from localhost (unknown [50.13.187.159]) by mail.hardakers.net (Postfix) with ESMTPSA id 1879C53 for <ietf@ietf.org>; Thu, 29 Nov 2012 13:14:14 -0800 (PST)
From: Wes Hardaker <wjhns1@hardakers.net>
To: ietf@ietf.org
Subject: request to make the "tools version" of the agenda the default
Date: Thu, 29 Nov 2012 10:11:38 -0800
Message-ID: <0lr4ncgtyd.fsf@wjh.hardakers.net>
User-Agent: Gnus/5.130006 (Ma Gnus v0.6) Emacs/24.1 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Nov 2012 21:14:16 -0000

So, the 'tools version' with all the wonderful spiffy links to helpful
things (the materials, the etherpad, the ...) and the spiffy
highlighting ability (Dark Red!  I love dark red!) has been very stable
and highly useful for quite a while now.  But the default link on the
web page still points to the less-useful HTML version (which has a link
at the top to get to the tools version).  I'd argue this is backwards at
this point, and the tools version is so much more useful (and just as
stable) as the plain-html version that it should be the default.  Can we
do that for March+?


[I know, we just *ended* a face-to-face meeting so why am I bringing up
face-to-face meeting topics so far before the next one?  That's unheard
of!  Call me crazy...]

-- 
Wes Hardaker
SPARTA, Inc.

From randy@psg.com  Thu Nov 29 13:14:20 2012
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F2AFD21F8C44 for <ietf@ietfa.amsl.com>; Thu, 29 Nov 2012 13:14:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.454
X-Spam-Level: 
X-Spam-Status: No, score=-2.454 tagged_above=-999 required=5 tests=[AWL=0.145,  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 107j0OqhAHH1 for <ietf@ietfa.amsl.com>; Thu, 29 Nov 2012 13:14:19 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 915D121F8C40 for <ietf@ietf.org>; Thu, 29 Nov 2012 13:14:19 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from <randy@psg.com>) id 1TeBR4-000BsF-9x; Thu, 29 Nov 2012 21:14:18 +0000
Date: Fri, 30 Nov 2012 06:14:16 +0900
Message-ID: <m2hao82jtj.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Melinda Shore <melinda.shore@gmail.com>
Subject: Re: When to adopt a draft as a WG doc (was RE: "IETF work is done	on the mailing lists")
In-Reply-To: <50B7BB68.4050807@gmail.com>
References: <2671C6CDFBB59E47B64C10B3E0BD5923033897C9BF@PRVPEXVS15.corp.twcable.com> <CALaySJLT=6RTZahqB1LO_Aw=7sAMiyrXK=xacwrBgLieZhqeDw@mail.gmail.com> <2671C6CDFBB59E47B64C10B3E0BD59230338A657EC@PRVPEXVS15.corp.twcable.com> <CALaySJ+1LX6kzpDZYwQaJAqkzH4zLdRoMaJNH9HcHQG-78jA7Q@mail.gmail.com> <50B7BB68.4050807@gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Nov 2012 21:14:20 -0000

> I'll note that it seems possible that overspecifying process
> could potentially cause more protests rather than fewer.

or good folk just walking away.  there is a reason we are at the ietf
and not the itu.  rule obsessed and process hidebound is probably not
the most productive use of smart folks' time.

randy

From adrian@olddog.co.uk  Thu Nov 29 13:16:09 2012
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7166221F8C47 for <ietf@ietfa.amsl.com>; Thu, 29 Nov 2012 13:16:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.587
X-Spam-Level: 
X-Spam-Status: No, score=-2.587 tagged_above=-999 required=5 tests=[AWL=0.012,  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 r3uWZy+zhFXK for <ietf@ietfa.amsl.com>; Thu, 29 Nov 2012 13:16:08 -0800 (PST)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) by ietfa.amsl.com (Postfix) with ESMTP id 87EEE21F8C40 for <ietf@ietf.org>; Thu, 29 Nov 2012 13:16:08 -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 qATLG638032036;  Thu, 29 Nov 2012 21:16:07 GMT
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id qATLG6vw032030 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 29 Nov 2012 21:16:06 GMT
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'SM'" <sm@resistor.net>, "'IETF discussion list'" <ietf@ietf.org>
References: <2671C6CDFBB59E47B64C10B3E0BD5923033897C9BF@PRVPEXVS15.corp.twcable.com>	<CALaySJLT=6RTZahqB1LO_Aw=7sAMiyrXK=xacwrBgLieZhqeDw@mail.gmail.com>	<2671C6CDFBB59E47B64C10B3E0BD59230338A657EC@PRVPEXVS15.corp.twcable.com> <6.2.5.6.2.20121129105444.0b8d3400@resistor.net>
In-Reply-To: <6.2.5.6.2.20121129105444.0b8d3400@resistor.net>
Subject: RE: When to adopt a draft as a WG doc (was RE: "IETF work is	done on the mailing lists")
Date: Thu, 29 Nov 2012 21:16:05 -0000
Message-ID: <02ba01cdce76$be921580$3bb64080$@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: AQJh66a/LNfCMvKWuQdcHBWtm9X2zgHx7K5AAdAQl6UCU5WZU5aoaTUg
Content-Language: en-gb
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Nov 2012 21:16:09 -0000

Just picking at one point...

> According to some RFC:
> 
>    "All relevant documents to be discussed at a session should be published
>     and available as Internet-Drafts at least two weeks before
>     a session starts."
> 
> If the above was followed there shouldn't be any draft submissions
> during the week a meeting is held.

What about drafts that not for discussion at a session? What about drafts that
have completed last call or are in IESG processing?

Cheers,
Adrian


From randy@psg.com  Thu Nov 29 13:42:42 2012
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 70E2121F8C3A for <ietf@ietfa.amsl.com>; Thu, 29 Nov 2012 13:42:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.466
X-Spam-Level: 
X-Spam-Status: No, score=-2.466 tagged_above=-999 required=5 tests=[AWL=0.133,  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 3kl0Vq+uivH8 for <ietf@ietfa.amsl.com>; Thu, 29 Nov 2012 13:42:42 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 0E44C21F8BFF for <ietf@ietf.org>; Thu, 29 Nov 2012 13:42:42 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from <randy@psg.com>) id 1TeBsX-000BzC-Bl for ietf@ietf.org; Thu, 29 Nov 2012 21:42:41 +0000
Date: Fri, 30 Nov 2012 06:42:40 +0900
Message-ID: <m2fw3s2ii7.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: IETF Disgust <ietf@ietf.org>
Subject: Re: Last Call: <draft-bonica-special-purpose-03.txt> (Special-Purpose Address Registries) to Best Current Practice
In-Reply-To: <20121129205534.8983.43593.idtracker@ietfa.amsl.com>
References: <20121129205534.8983.43593.idtracker@ietfa.amsl.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Nov 2012 21:42:42 -0000

first cuppa, so i am easily confuddled.  and apologies for doing this at
last call.

are the following definitions

   o  Routable - A boolean value indicating whether a IP datagram whose
      destination address is drawn from the allocated special-purpose
      address block is routable (i.e., may traverse more than a single
      IP interface)

   o  Global - A boolean value indicating whether a IP datagram whose
      destination address is drawn from the allocated special-purpose
      address block is routable beyond a specified administrative
      domain.

intended to be baked in hardware, or are they SHOULDs to operators?  i
look at RFC 1918 space and 127.0.0.0/8 and am not so sure how hard these
boundaries are meant to be.  i worry because i think we regret how we
specified (threw away is more like it) E space.

does the prefix describes a specific prefix length or a covering range?

e.g. 192.0.0.0/24 is neither routable nor global, while a subnet,
192.0.0.0/29, is routable.  i.e. might i route and forward
192.0.0.128/25?

randy

From lee@asgard.org  Thu Nov 29 13:45:31 2012
Return-Path: <lee@asgard.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD50221F8C69 for <ietf@ietfa.amsl.com>; Thu, 29 Nov 2012 13:45:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.367
X-Spam-Level: 
X-Spam-Status: No, score=-2.367 tagged_above=-999 required=5 tests=[AWL=0.232,  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 y1LlYkFcyQQy for <ietf@ietfa.amsl.com>; Thu, 29 Nov 2012 13:45:31 -0800 (PST)
Received: from atl4mhob13.myregisteredsite.com (atl4mhob13.myregisteredsite.com [209.17.115.51]) by ietfa.amsl.com (Postfix) with ESMTP id 42A6821F8C61 for <ietf@ietf.org>; Thu, 29 Nov 2012 13:45:31 -0800 (PST)
Received: from mailpod.hostingplatform.com (mail.networksolutionsemail.com [205.178.146.50]) by atl4mhob13.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id qATLjUFl008153 for <ietf@ietf.org>; Thu, 29 Nov 2012 16:45:30 -0500
Received: (qmail 3059 invoked by uid 0); 29 Nov 2012 21:45:30 -0000
Received: from unknown (HELO HDC00042402) (lee@asgard.org@204.235.115.165) by 0 with ESMTPA; 29 Nov 2012 21:45:30 -0000
From: "Lee Howard" <lee@asgard.org>
To: "'Barry Leiba'" <barryleiba@computer.org>, "'IETF discussion list'" <ietf@ietf.org>
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com>	<50B5C839.4060909@gmail.com>	<59924CD37D50616BA8EB8EF7@JcK-HP8200.jck.com>	<6.2.5.6.2.20121128023905.0afdcde0@resistor.net>	<50B683C4.2030503@stpeter.im> <50B68612.7080107@dcrocker.net>	<50B693ED.7000609@stpeter.im> <50B696B0.30904@qti.qualcomm.com> <CAC4RtVAG+pKSQMwPyB6GJ7jxJM4hNpU81Yt8he6ZsEMrg_rTbQ@mail.gmail.com>
In-Reply-To: <CAC4RtVAG+pKSQMwPyB6GJ7jxJM4hNpU81Yt8he6ZsEMrg_rTbQ@mail.gmail.com>
Subject: RE: Barely literate minutes
Date: Thu, 29 Nov 2012 16:45:29 -0500
Message-ID: <00c001cdce7a$d9fa6490$8def2db0$@asgard.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQGuCiyth3j9q+DAiXDkQJ8JXg2BkwHLVCNwAgpNoc8BQtQrvQGJGIMNAV4GQ9QBkXXqWgFZnJuFAbM55QuX2/G4YA==
Content-Language: en-us
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Nov 2012 21:45:32 -0000

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
Barry Leiba
> Sent: Thursday, November 29, 2012 10:12 AM
> To: IETF discussion list
> Subject: Re: Barely literate minutes
> 
> On Wed, Nov 28, 2012 at 5:56 PM, Pete Resnick <presnick@qti.qualcomm.com>
wrote:
> ...
> > chair needs to (with the help of minutes takers and other
> > participants) post detailed notes of the discussion to the list and
> > ask for objections. That serves two functions: (a) It makes a record
> > of work that was done; and (b) it gives people who don't attend
> > meetings (including new folks who come
> > along) a chance to participate and voice their concerns. *Achievement*
> > of consensus might have to occur f2f for some issues in some WGs, but
> > it seems to me that *assessment* of consensus must be completely
> > possible on the list, even if the only poster to the list is the chair
> > with all of the f2f notes.
> 
> What I would prefer to see is that in addition to minutes there be
separate messages posted to
> the list for each document, detailing the discussion of that document in
the meeting and the
> changes that will result from the discussion.  That can be posted by the
chair, but I'd really
> expect it to come from a document editor.  That makes sure that everyone
can see what the
> document editor heard and intends to do with the document, and allows the
working group to
> continue the discussion or say, "Yes, that's what we heard as well, and
it's fine."

As a document author, I've learned that I need to have a friend take good
notes for me, because
all of the great comments I get at the mike are lost otherwise.  I can't
take notes while I'm
standing up, facilitating discussion.

As a working group chair I take my own notes, as backup to the note-taker,
then merge the
notes.

Lee



From gih@apnic.net  Thu Nov 29 14:26:47 2012
Return-Path: <gih@apnic.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B941321F8AAA for <ietf@ietfa.amsl.com>; Thu, 29 Nov 2012 14:26:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, 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 Qah13BYaLvb7 for <ietf@ietfa.amsl.com>; Thu, 29 Nov 2012 14:26:47 -0800 (PST)
Received: from asmtp.apnic.net (asmtp.apnic.net [IPv6:2001:dc0:2001:11::199]) by ietfa.amsl.com (Postfix) with ESMTP id C942F21F8AA6 for <ietf@ietf.org>; Thu, 29 Nov 2012 14:26:45 -0800 (PST)
Received: from 2001-44b8-1121-1a00-3448-34ba-4195-613f.static.ipv6.internode.on.net (2001-44b8-1121-1a00-3448-34ba-4195-613f.static.ipv6.internode.on.net [IPv6:2001:44b8:1121:1a00:3448:34ba:4195:613f]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by asmtp.apnic.net (Postfix) with ESMTP id 774EAB6745; Fri, 30 Nov 2012 08:26:43 +1000 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: Last Call: <draft-bonica-special-purpose-03.txt> (Special-Purpose Address Registries) to Best Current Practice
From: Geoff Huston <gih@apnic.net>
In-Reply-To: <20121129205534.8983.43593.idtracker@ietfa.amsl.com>
Date: Fri, 30 Nov 2012 09:26:42 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <7C5BEF8A-70E1-4E96-BC5C-7D2D43E09A58@apnic.net>
References: <20121129205534.8983.43593.idtracker@ietfa.amsl.com>
To: ietf@ietf.org
X-Mailer: Apple Mail (2.1499)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Nov 2012 22:26:47 -0000

On 30/11/2012, at 7:55 AM, The IESG <iesg-secretary@ietf.org> wrote:

>=20
> The IESG has received a request from an individual submitter to =
consider
> the following document:
> - 'Special-Purpose Address Registries'
>  <draft-bonica-special-purpose-03.txt> as Best Current Practice
>=20
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2013-01-02. Exceptionally, comments may =
be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>=20
> Abstract
>=20
>=20
>   This memo instructs IANA to restructure its IPv4 and IPv6 Special-
>   Purpose Address Registries.  Upon restructuring, the aforementioned
>   registries will record all special-purpose address blocks,
>   maintaining a common set of information regarding each address =
block.
>=20
>   This memo updates RFC 5736 and RFC 4773, which define the current
>   structure of the IPv4 and IPv6 Special-Purpose Address Registries.
>   It also obsoletes RFC 5735 and RFC 5156 which document special-
>   purpose address blocks that are not currently, but will in the
>   future, be recorded in the IPv4 and IPv6 Special-Purpose Address
>   Registries.
>=20


I am not in favour of publication of this draft in its current form.=20

The reasons for this are that I believe that the draft continues to =
promote a position that has been espoused in recent drafts it references =
that blurs the distinction between a special purpose address assignment =
and an address reservation. I believe that this distinction is a useful =
distinction and the number registries should explicitly preserve this =
distinction rather than blur it out.

In my view reservations are an implicit part of the address plan for the =
protocol, and the expectation behind the reservation is that all =
implementations of the protocol will honour the same set of reservations =
in the same way. For example 0/8 is a reservation - all conformant =
implementations of the IPv4 would be expected to treat addresses drawn =
from 0/8 in the same fashion, namely as self identification.

On the other hand I see 192.88.99.0/24 as an IANA special purpose =
assignment - its use is by a particular application or service, and =
conformant implementations of the IPv4 protocol stack are under no =
obligation to treat IP packets that include this address in any way that =
is different to any other general use IPv4 address.

I see the proposal to push reservations and special purpose allocations =
into a single registry as being a source of potential confusion in so =
far as it a) blurs the distinction between what all conformant =
implementations of the protocol stack must respect in terms of =
reservation of addresses and the behaviour of the protocol stack if and =
when a reserved address is encountered and b) does not explicitly state =
the policies relating to the manner in which an address block is =
reserved and the policies relating to the manner in which an address =
block is assigned by virtue of a special purpose registry assignment.

I also disagree with the approach to publish the intended contents of =
this special purpose registry as an RFC ans the registry itself is the =
intended mode of authoritatively describing those resources that have =
been assigned for special purposes. Obviously any RFC will age out and =
drift away from the registry, and the need to constantly publish =
updating RFCs to ensure that the latest RFC is reasonably close to the =
registry contents seems to me to be counter-productive at best.

I can appreciate the "better housekeeping" motivation behind this draft, =
to group all IANA-held resources into a single registry, but I do not =
agree with this motivation given that the reason WHY resources are =
located in an IANA-maintained registry is then not explicit. Such =
addresses as listed in this draft can be delineated into reservations as =
part of the protocol's overall address plan, and special purpose address =
assignments that are undertaken by the IANA in support of particular =
applications and service operation that are not necessarily part of the =
protocol's underlying address plan and do not require reserved =
behaviours on the part of implementions of the protocol stack when such =
addresses are encountered.


Geoff











From randy@psg.com  Thu Nov 29 14:27:53 2012
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C6C8821F8AB4 for <ietf@ietfa.amsl.com>; Thu, 29 Nov 2012 14:27:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.477
X-Spam-Level: 
X-Spam-Status: No, score=-2.477 tagged_above=-999 required=5 tests=[AWL=0.122,  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 2kyBVtTUTUwh for <ietf@ietfa.amsl.com>; Thu, 29 Nov 2012 14:27:53 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 5C44C21F8AB2 for <ietf@ietf.org>; Thu, 29 Nov 2012 14:27:53 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from <randy@psg.com>) id 1TeCaD-000CH2-KF; Thu, 29 Nov 2012 22:27:50 +0000
Date: Fri, 30 Nov 2012 07:27:48 +0900
Message-ID: <m2624o2gez.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: "Lee Howard" <lee@asgard.org>
Subject: Re: Barely literate minutes
In-Reply-To: <00c001cdce7a$d9fa6490$8def2db0$@asgard.org>
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <50B5C839.4060909@gmail.com> <59924CD37D50616BA8EB8EF7@JcK-HP8200.jck.com> <6.2.5.6.2.20121128023905.0afdcde0@resistor.net> <50B683C4.2030503@stpeter.im> <50B68612.7080107@dcrocker.net> <50B693ED.7000609@stpeter.im> <50B696B0.30904@qti.qualcomm.com> <CAC4RtVAG+pKSQMwPyB6GJ7jxJM4hNpU81Yt8he6ZsEMrg_rTbQ@mail.gmail.com> <00c001cdce7a$d9fa6490$8def2db0$@asgard.org>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Cc: 'Barry Leiba' <barryleiba@computer.org>, 'IETF discussion list' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Nov 2012 22:27:53 -0000

> As a document author, I've learned that I need to have a friend take
> good notes for me, because all of the great comments I get at the mike
> are lost otherwise.

this gap makes me crazy, so much is often lost.  but i do not think
technology or process will close this hole.  too much depends on fairly
deep understanding of the subject.

> I can't take notes while I'm standing up, facilitating discussion.

i can't take notes while i am trying to understand and think about the
important semantics of a discussion, period.  but much of this may be a
personal failing, poor typist, rotting mind, ...

randy

From randy@psg.com  Thu Nov 29 14:31:32 2012
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1385521F8AD8 for <ietf@ietfa.amsl.com>; Thu, 29 Nov 2012 14:31:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.485
X-Spam-Level: 
X-Spam-Status: No, score=-2.485 tagged_above=-999 required=5 tests=[AWL=0.114,  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 FnXRqz+T1axI for <ietf@ietfa.amsl.com>; Thu, 29 Nov 2012 14:31:31 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 5666621F8AD7 for <ietf@ietf.org>; Thu, 29 Nov 2012 14:31:31 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from <randy@psg.com>) id 1TeCdb-000CJt-36; Thu, 29 Nov 2012 22:31:19 +0000
Date: Fri, 30 Nov 2012 07:31:18 +0900
Message-ID: <m24nk82g95.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Geoff Huston <gih@apnic.net>
Subject: Re: Last Call: <draft-bonica-special-purpose-03.txt> (Special-Purpose	Address Registries) to Best Current Practice
In-Reply-To: <7C5BEF8A-70E1-4E96-BC5C-7D2D43E09A58@apnic.net>
References: <20121129205534.8983.43593.idtracker@ietfa.amsl.com> <7C5BEF8A-70E1-4E96-BC5C-7D2D43E09A58@apnic.net>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Nov 2012 22:31:32 -0000

hi geoff,

i get your point.  but it sure is convenient to find everything in one
place.  can your issues be addressed by adding an attribute(s) to the
entries?

randy

From gih@apnic.net  Thu Nov 29 14:37:08 2012
Return-Path: <gih@apnic.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B62FA21F89A2 for <ietf@ietfa.amsl.com>; Thu, 29 Nov 2012 14:37:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, NO_RELAYS=-0.001, 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 QDubn49KD5dB for <ietf@ietfa.amsl.com>; Thu, 29 Nov 2012 14:37:08 -0800 (PST)
Received: from asmtp.apnic.net (asmtp.apnic.net [IPv6:2001:dc0:2001:11::199]) by ietfa.amsl.com (Postfix) with ESMTP id 2CFA321F8954 for <ietf@ietf.org>; Thu, 29 Nov 2012 14:37:08 -0800 (PST)
Received: from 2001-44b8-1121-1a00-3448-34ba-4195-613f.static.ipv6.internode.on.net (2001-44b8-1121-1a00-3448-34ba-4195-613f.static.ipv6.internode.on.net [IPv6:2001:44b8:1121:1a00:3448:34ba:4195:613f]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by asmtp.apnic.net (Postfix) with ESMTP id B1AF3B6745; Fri, 30 Nov 2012 08:37:05 +1000 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: When to adopt a draft as a WG doc (was RE: "IETF work is done	on the mailing lists")
From: Geoff Huston <gih@apnic.net>
In-Reply-To: <m2hao82jtj.wl%randy@psg.com>
Date: Fri, 30 Nov 2012 09:37:04 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <3488E0C6-726E-4D75-BDEB-03DA5401A0F6@apnic.net>
References: <2671C6CDFBB59E47B64C10B3E0BD5923033897C9BF@PRVPEXVS15.corp.twcable.com> <CALaySJLT=6RTZahqB1LO_Aw=7sAMiyrXK=xacwrBgLieZhqeDw@mail.gmail.com> <2671C6CDFBB59E47B64C10B3E0BD59230338A657EC@PRVPEXVS15.corp.twcable.com> <CALaySJ+1LX6kzpDZYwQaJAqkzH4zLdRoMaJNH9HcHQG-78jA7Q@mail.gmail.com> <50B7BB68.4050807@gmail.com> <m2hao82jtj.wl%randy@psg.com>
To: Randy Bush <randy@psg.com>
X-Mailer: Apple Mail (2.1499)
Cc: "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Nov 2012 22:37:08 -0000

On 30/11/2012, at 8:14 AM, Randy Bush <randy@psg.com> wrote:

>> I'll note that it seems possible that overspecifying process
>> could potentially cause more protests rather than fewer.
>=20
> or good folk just walking away.  there is a reason we are at the ietf
> and not the itu.  rule obsessed and process hidebound is probably not
> the most productive use of smart folks' time.
>=20

On the other hand any organised social activity is organised by virtue =
of the adoption
of a common set of "norms" about the behaviour of individuals - we call =
em "rules"
and "processes", but the purpose is common. To what extent the activity =
is tolerant
of exceptions, and to what extent the group activity is capable of self
examination and evolution in the light of such exceptions is critical =
for longevity.

Rigid systems tend to ossify while flexible systems tend to adapt.

So for me its not that the ITU is any more rule and processed obsessed =
than the IETF's WGs.=20
I'm sure we could all cite instances all along the spectrum of behaviour =
in both
forums. The distinction for me is the ability of the forum to undertake
self examination and evolve the rules and processes in the light of what =
may have
originally been seen as exceptional behaviour.

Geoff



From gih@apnic.net  Thu Nov 29 14:45:37 2012
Return-Path: <gih@apnic.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5BB2821F8B27 for <ietf@ietfa.amsl.com>; Thu, 29 Nov 2012 14:45:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.103
X-Spam-Level: 
X-Spam-Status: No, score=-102.103 tagged_above=-999 required=5 tests=[AWL=-0.498, BAYES_00=-2.599, RELAY_IS_203=0.994, 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 fi5kzKckjnbp for <ietf@ietfa.amsl.com>; Thu, 29 Nov 2012 14:45:36 -0800 (PST)
Received: from asmtp.apnic.net (asmtp.apnic.net [IPv6:2001:dc0:2001:11::199]) by ietfa.amsl.com (Postfix) with ESMTP id 7E64621F8AB6 for <ietf@ietf.org>; Thu, 29 Nov 2012 14:45:35 -0800 (PST)
Received: from dhcp148.potaroo.net (eth143.act.adsl.internode.on.net [203.16.208.142]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by asmtp.apnic.net (Postfix) with ESMTP id 524C1B6745; Fri, 30 Nov 2012 08:45:34 +1000 (EST)
Subject: Re: Last Call: <draft-bonica-special-purpose-03.txt> (Special-Purpose	Address Registries) to Best Current Practice
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Content-Type: text/plain; charset=us-ascii
From: Geoff Huston <gih@apnic.net>
In-Reply-To: <m24nk82g95.wl%randy@psg.com>
Date: Fri, 30 Nov 2012 09:45:32 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <CDE0AD71-206A-4447-8C9D-09ADF616A00E@apnic.net>
References: <20121129205534.8983.43593.idtracker@ietfa.amsl.com> <7C5BEF8A-70E1-4E96-BC5C-7D2D43E09A58@apnic.net> <m24nk82g95.wl%randy@psg.com>
To: Randy Bush <randy@psg.com>
X-Mailer: Apple Mail (2.1499)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Nov 2012 22:45:37 -0000

On 30/11/2012, at 9:31 AM, Randy Bush <randy@psg.com> wrote:

> hi geoff,
>=20
> i get your point.  but it sure is convenient to find everything in one
> place.  can your issues be addressed by adding an attribute(s) to the
> entries?


Convenience vs maning a semantic distinction overt.

Yes, it is possible to add an attribute to a common registry.

On the other hand it is possible to realign what entries go in which =
registry according to:

- "reservations" to be in the "main" registry, using a working =
definition of a "reservation" as something that all implementations of =
the protocol have to honour.

- all other IANA special purpose address assignments to be placed in =
this special purpose registry (including, for example RFC1918 space, =
6to4 relays, etc), and the RFC to document the process of special =
purpose assignment.


Geoff








From randy@psg.com  Thu Nov 29 15:04:51 2012
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7748121F8AC9 for <ietf@ietfa.amsl.com>; Thu, 29 Nov 2012 15:04:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.5
X-Spam-Level: 
X-Spam-Status: No, score=-2.5 tagged_above=-999 required=5 tests=[AWL=0.099, 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 E-06jobAKa6d for <ietf@ietfa.amsl.com>; Thu, 29 Nov 2012 15:04:51 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 1FD9121F8ABB for <ietf@ietf.org>; Thu, 29 Nov 2012 15:04:51 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from <randy@psg.com>) id 1TeDA1-000Cg3-0W; Thu, 29 Nov 2012 23:04:49 +0000
Date: Fri, 30 Nov 2012 08:04:47 +0900
Message-ID: <m21ufc2epc.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Geoff Huston <gih@apnic.net>
Subject: Re: Last Call: <draft-bonica-special-purpose-03.txt> (Special-Purpose Address Registries) to Best Current Practice
In-Reply-To: <CDE0AD71-206A-4447-8C9D-09ADF616A00E@apnic.net>
References: <20121129205534.8983.43593.idtracker@ietfa.amsl.com> <7C5BEF8A-70E1-4E96-BC5C-7D2D43E09A58@apnic.net> <m24nk82g95.wl%randy@psg.com> <CDE0AD71-206A-4447-8C9D-09ADF616A00E@apnic.net>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Cc: IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Nov 2012 23:04:51 -0000

> Yes, it is possible to add an attribute to a common registry.
> 
> On the other hand it is possible to realign what entries go in which
> registry according to:
> 
> - "reservations" to be in the "main" registry, using a working
>   definition of a "reservation" as something that all implementations
>   of the protocol have to honour.
> 
> - all other IANA special purpose address assignments to be placed in
>   this special purpose registry (including, for example RFC1918 space,
>   6to4 relays, etc), and the RFC to document the process of special
>   purpose assignment.

an N-ary attribute or N lists, semantically about the same, syntax seems
a matter of taste.  i agree with the distinction, and am happy with
either syntax.

randy

From presnick@qti.qualcomm.com  Thu Nov 29 15:06:10 2012
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E2D321F8B2A for <ietf@ietfa.amsl.com>; Thu, 29 Nov 2012 15:06:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.566
X-Spam-Level: 
X-Spam-Status: No, score=-102.566 tagged_above=-999 required=5 tests=[AWL=0.033, 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 GlYWC6SBSYV0 for <ietf@ietfa.amsl.com>; Thu, 29 Nov 2012 15:06:09 -0800 (PST)
Received: from sabertooth02.qualcomm.com (sabertooth02.qualcomm.com [65.197.215.38]) by ietfa.amsl.com (Postfix) with ESMTP id AF4F321F8B29 for <ietf@ietf.org>; Thu, 29 Nov 2012 15:06:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1354228827; x=1385764827; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=UrrGTCK2Wh8e/hGJu0JEpBB2q0xunCnQQcu33f8vt98=; b=lZtVX5j3C95zAFlqiG6g+ZUlfUGO4kLSyIAexVb2VfsSvrLGoIx3c5he BFKU72JwGK+tpqRAJCED1CtVsVaCTwHMUcAgnge31GsIHywf2saaPjzxK 0KSAJloiGc8eLJJ0c5lUWo6dKhDS4x10M8G1CgIF9cZxUYMw1Q23b3fvM E=;
X-IronPort-AV: E=McAfee;i="5400,1158,6911"; a="9745349"
Received: from ironmsg04-r.qualcomm.com ([172.30.46.18]) by sabertooth02.qualcomm.com with ESMTP; 29 Nov 2012 14:40:26 -0800
X-IronPort-AV: E=McAfee;i="5400,1158,6911"; a="434957141"
Received: from nasanexhc08.na.qualcomm.com ([172.30.39.7]) by Ironmsg04-R.qualcomm.com with ESMTP/TLS/RC4-SHA; 29 Nov 2012 15:06:08 -0800
Received: from presnick-mac.local (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.7) with Microsoft SMTP Server (TLS) id 14.2.318.4; Thu, 29 Nov 2012 15:06:08 -0800
Message-ID: <50B7EA5D.2030803@qti.qualcomm.com>
Date: Thu, 29 Nov 2012 17:06:05 -0600
From: Pete Resnick <presnick@qti.qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: Lee Howard <lee@asgard.org>
Subject: Re: Barely literate minutes
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com>	<50B5C839.4060909@gmail.com>	<59924CD37D50616BA8EB8EF7@JcK-HP8200.jck.com>	<6.2.5.6.2.20121128023905.0afdcde0@resistor.net>	<50B683C4.2030503@stpeter.im>	<50B68612.7080107@dcrocker.net>	<50B693ED.7000609@stpeter.im>	<50B696B0.30904@qti.qualcomm.com>	<CAC4RtVAG+pKSQMwPyB6GJ7jxJM4hNpU81Yt8he6ZsEMrg_rTbQ@mail.gmail.com> <00c001cdce7a$d9fa6490$8def2db0$@asgard.org>
In-Reply-To: <00c001cdce7a$d9fa6490$8def2db0$@asgard.org>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.39.5]
Cc: 'Barry Leiba' <barryleiba@computer.org>, 'IETF discussion list' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Nov 2012 23:06:10 -0000

On 11/29/12 3:45 PM, Lee Howard wrote:
> I can't take notes while I'm standing up, facilitating discussion.
>    

Interesting. I am forced to (only somewhat facetiously) ask: Why are 
*you* standing up, facilitating discussion, if you are the editor? 
Shouldn't that be the chair's job? More seriously: Since we started this 
PowerPoint/Comments-at-the-mic thing oh so many years ago, doing 
document reviews in presentation form where the editor is the one doing 
the slides has created this problem. Perhaps a better mode would be for 
the editor to write up the list of open issues, have the chair project 
them if need be, and the editor can get up to the mic with 
explanations/questions as needed but otherwise remain seated so they can 
jot down the notes they need. I think I've done something like that a 
long time ago as an editor. Worth trying, I'd think.

pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478


From spencer@wonderhamster.org  Thu Nov 29 15:16:29 2012
Return-Path: <spencer@wonderhamster.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8878A21F89C3 for <ietf@ietfa.amsl.com>; Thu, 29 Nov 2012 15:16:29 -0800 (PST)
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=[AWL=0.000, 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 iw-ZtNbsJC8Y for <ietf@ietfa.amsl.com>; Thu, 29 Nov 2012 15:16:29 -0800 (PST)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.195]) by ietfa.amsl.com (Postfix) with ESMTP id ED70421F8947 for <ietf@ietf.org>; Thu, 29 Nov 2012 15:16:28 -0800 (PST)
Received: from [192.168.12.170] ([50.58.7.243]) by mrelay.perfora.net (node=mrus4) with ESMTP (Nemesis) id 0MWkmh-1TjthZ3bnX-00Y07b; Thu, 29 Nov 2012 18:16:28 -0500
Message-ID: <50B7ECD1.5080302@wonderhamster.org>
Date: Thu, 29 Nov 2012 17:16:33 -0600
From: Spencer Dawkins <spencer@wonderhamster.org>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: When to adopt a draft as a WG doc (was RE: "IETF work is	done on the mailing lists")
References: <2671C6CDFBB59E47B64C10B3E0BD5923033897C9BF@PRVPEXVS15.corp.twcable.com>	<CALaySJLT=6RTZahqB1LO_Aw=7sAMiyrXK=xacwrBgLieZhqeDw@mail.gmail.com>	<2671C6CDFBB59E47B64C10B3E0BD59230338A657EC@PRVPEXVS15.corp.twcable.com> <6.2.5.6.2.20121129105444.0b8d3400@resistor.net> <02ba01cdce76$be921580$3bb64080$@olddog.co.uk>
In-Reply-To: <02ba01cdce76$be921580$3bb64080$@olddog.co.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V02:K0:Zd30uoafvxtQS449DhPgi3rk/+2b1Rfi5vY2ZNOdmBZ 7TFHl7Uk/VAJaXQ6u6EP3wvPa2IhNSZ2YDdJaFQb1zI4oa3LFV Oig6u3ADDYzH3YPXfO+ZDZDINTSz3ERS72vCiABRUrQsOnUzpy yoyksZ5CNwNqrvSpqlZE9XBtVjujwsq4p9dXCHUTatvdgRkYW0 1Xyo+Z48ek8e+W89djx4x3BdqNbTJU53R7m/QPbgmbCpNvuqzT iooG1xkZmARWSxNxsMzRlZYFNLM4fecYkB4GE25H0ybuu5Otqv As5mD0DyBy3ZvEjI3/QxtfqZvhSq3oc8Q8HUKVb4cag6SBM0eZ 3JGkOw6++yysp1ofau1anDwTg3MXVuEzfVCiwUarx
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Nov 2012 23:16:29 -0000

On 11/29/2012 3:16 PM, Adrian Farrel wrote:
> Just picking at one point...
>
>> According to some RFC:
>>
>>     "All relevant documents to be discussed at a session should be published
>>      and available as Internet-Drafts at least two weeks before
>>      a session starts."
>>
>> If the above was followed there shouldn't be any draft submissions
>> during the week a meeting is held.
>
> What about drafts that not for discussion at a session? What about drafts that
> have completed last call or are in IESG processing?
>
> Cheers,
> Adrian

In addition to the cases Adrian asked about, isn't there also the case 
of an author/editor updating a draft that has already been discussed and 
then submitting it during IETF week?

Thanks,

Spencer



From wesley.george@twcable.com  Thu Nov 29 15:31:52 2012
Return-Path: <wesley.george@twcable.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B3A821F88F2 for <ietf@ietfa.amsl.com>; Thu, 29 Nov 2012 15:31:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.383
X-Spam-Level: 
X-Spam-Status: No, score=-0.383 tagged_above=-999 required=5 tests=[AWL=0.080,  BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368]
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 nau57H3k0xkq for <ietf@ietfa.amsl.com>; Thu, 29 Nov 2012 15:31:51 -0800 (PST)
Received: from cdpipgw02.twcable.com (cdpipgw02.twcable.com [165.237.59.23]) by ietfa.amsl.com (Postfix) with ESMTP id 7D06021F88E0 for <ietf@ietf.org>; Thu, 29 Nov 2012 15:31:51 -0800 (PST)
X-SENDER-IP: 10.136.163.14
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.84,188,1355115600"; d="scan'208";a="460988217"
Received: from unknown (HELO PRVPEXHUB05.corp.twcable.com) ([10.136.163.14]) by cdpipgw02.twcable.com with ESMTP/TLS/RC4-MD5; 29 Nov 2012 18:31:06 -0500
Received: from PRVPEXVS15.corp.twcable.com ([10.136.163.79]) by PRVPEXHUB05.corp.twcable.com ([10.136.163.14]) with mapi; Thu, 29 Nov 2012 18:31:50 -0500
From: "George, Wes" <wesley.george@twcable.com>
To: Barry Leiba <barryleiba@computer.org>
Date: Thu, 29 Nov 2012 18:32:05 -0500
Subject: RE: When to adopt a draft as a WG doc (was RE: "IETF work is done on the mailing lists")
Thread-Topic: When to adopt a draft as a WG doc (was RE: "IETF work is done on the mailing lists")
Thread-Index: Ac3OZRdeQSUTAaLRSoSdwmTQZVbvKQAAoJlw
Message-ID: <2671C6CDFBB59E47B64C10B3E0BD59230338A65F10@PRVPEXVS15.corp.twcable.com>
References: <2671C6CDFBB59E47B64C10B3E0BD5923033897C9BF@PRVPEXVS15.corp.twcable.com> <CALaySJLT=6RTZahqB1LO_Aw=7sAMiyrXK=xacwrBgLieZhqeDw@mail.gmail.com> <2671C6CDFBB59E47B64C10B3E0BD59230338A657EC@PRVPEXVS15.corp.twcable.com> <CALaySJ+1LX6kzpDZYwQaJAqkzH4zLdRoMaJNH9HcHQG-78jA7Q@mail.gmail.com>
In-Reply-To: <CALaySJ+1LX6kzpDZYwQaJAqkzH4zLdRoMaJNH9HcHQG-78jA7Q@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Nov 2012 23:31:52 -0000

> From: barryleiba@gmail.com [mailto:barryleiba@gmail.com] On Behalf Of
> Barry Leiba

> we have a
> million things that are unspecified and should be unspecified and left
> to management choice.  Trying to find all of those and explicitly say so
> will be a frustrating exercise, and one that won't have a lot of value
> in the end.  In general, we specify what we want to specify, and what's
> left is up to judgment and management.
[WEG] I'm sorry if it was unclear, but I am not saying that *everything* mu=
st be specified, nor do I think anyone should undertake an effort to even i=
dentify all of the things that are currently unspecified. I'm pointing out =
a specific area of confusion and inconsistency that has been created by som=
ething that is unspecified and asking "should we specify?"
>
> > Further, no matter how good the individuals are at their "jobs" within
> > the IETF, applying undocumented policy (especially doing it
> > inconsistently) looks to the outside world as arbitrary and capricious
>
> Here's where we have a gap, you and I: what you call undocumented policy
> I call a management choice.
[WEG] that's not really a gap, especially because you can replace my words =
with yours and the statement above still holds. I am saying is that there i=
s an inconsistency because different people are making different choices on=
 how to proceed, hopefully with the consensus of the WG behind them. IMO, t=
he inconsistency goes beyond merely being flexible to accommodate the wides=
t variety of cases, and adds confusion and variability to the process. I th=
ink the gap arises from the fact that you do not see this as inconsistent o=
r that you do not see the inconsistency as a bad thing. It may not be bad i=
n all cases, but I think there's a middle ground between overcreation and o=
verapplication of rules and relative anarchy. I'm just trying to make sure =
we're actually in that happy medium, and that this is indeed the result of =
a conscious decision rather than simply imitating what we see in other WGs =
because that seems to work. FWIW, the WG Chairs wiki is also silent on this=
 matter, and perhaps that is the best place to add a discussion about WG ad=
option of I-Ds. Is that more palatable?

>
> We hire the best and the brightest as our working group chairs in order
> to rely on their judgment and management abilities,

[WEG] Well, no disrespect to any current or former AD, but this is giving u=
s entirely too much credit for why the vast majority of our WG chairs are g=
ood at their jobs when it's more likely attributable to luck. Unlike other =
leadership positions in IETF, there's no formal interview or "hiring" proce=
ss to determine who out of the group of engineers that make up IETF is best=
 qualified to start chairing a WG. I certainly had no specific experience t=
hat made me any better than anyone else at being a WG chair the first time =
around. My qualifications included a non-zero amount of common sense, avail=
able cycles, interest in the topic, and <joking> the poor sense not to decl=
ine when asked to serve </joking>. There's no mandatory training class. If =
one is lucky, you get paired with an experienced co-chair (I did) and given=
 a pointer to the wiki (I didn't) to help you learn on the fly. It's clear =
that we trust our WG chairs, and there's nothing wrong with that. But somet=
imes providing them with more guidance is helpful.

Wes George

This E-mail and any of its attachments may contain Time Warner Cable propri=
etary information, which is privileged, confidential, or subject to copyrig=
ht belonging to Time Warner Cable. This E-mail is intended solely for the u=
se of the individual or entity to which it is addressed. If you are not the=
 intended recipient of this E-mail, you are hereby notified that any dissem=
ination, distribution, copying, or action taken in relation to the contents=
 of and attachments to this E-mail is strictly prohibited and may be unlawf=
ul. If you have received this E-mail in error, please notify the sender imm=
ediately and permanently delete the original and any copy of this E-mail an=
d any printout.

From melinda.shore@gmail.com  Thu Nov 29 15:38:58 2012
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BD44421F8B08 for <ietf@ietfa.amsl.com>; Thu, 29 Nov 2012 15:38:58 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5J3fmc3HMriT for <ietf@ietfa.amsl.com>; Thu, 29 Nov 2012 15:38:58 -0800 (PST)
Received: from mail-da0-f44.google.com (mail-da0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id A9C7221F8AE9 for <ietf@ietf.org>; Thu, 29 Nov 2012 15:38:55 -0800 (PST)
Received: by mail-da0-f44.google.com with SMTP id z20so3810797dae.31 for <ietf@ietf.org>; Thu, 29 Nov 2012 15:38:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=OUX3u22C7EeiZyEML9NrenUGUKhgT2zZTFgafo9d/YQ=; b=sw0qo3QjT/M+NhTEky0sAOiw1y4ysz7nwrDhz4V6izawz+WFf2m64Q/fEMQfQBJBrA lKt1jjj8EnDVPQrf0NYH/eoYdrAz1S9nsujavsqkHr8AAJ4XWWHfIQSXMZ7wsivqR7C8 /h9dfz5N7WmwKatzkhFXHcPPMhj5DhqZv3a1aTPPLUhYZRm4vZ5DZhyj+tZTAbm8wHfi 1ox8oEwzxyUhpWwpPUqSQdju82VQGK8bgwPRATBBziaNDXXqERPUwaVoIliaRQqYWCQF mVzWMvHl+fANUPvRsSuAspJ8dQ/Eril6hSL0j68+kfRLCUuB47vJVt7sMJG0JiTIIckV CVBQ==
Received: by 10.69.1.73 with SMTP id be9mr289857pbd.116.1354232335400; Thu, 29 Nov 2012 15:38:55 -0800 (PST)
Received: from spandex.local (66-230-101-170-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.101.170]) by mx.google.com with ESMTPS id x2sm1799487paw.8.2012.11.29.15.38.54 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 29 Nov 2012 15:38:54 -0800 (PST)
Message-ID: <50B7F20C.908@gmail.com>
Date: Thu, 29 Nov 2012 14:38:52 -0900
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: When to adopt a draft as a WG doc (was RE: "IETF work is done on the mailing lists")
References: <2671C6CDFBB59E47B64C10B3E0BD5923033897C9BF@PRVPEXVS15.corp.twcable.com> <CALaySJLT=6RTZahqB1LO_Aw=7sAMiyrXK=xacwrBgLieZhqeDw@mail.gmail.com> <2671C6CDFBB59E47B64C10B3E0BD59230338A657EC@PRVPEXVS15.corp.twcable.com> <CALaySJ+1LX6kzpDZYwQaJAqkzH4zLdRoMaJNH9HcHQG-78jA7Q@mail.gmail.com> <2671C6CDFBB59E47B64C10B3E0BD59230338A65F10@PRVPEXVS15.corp.twcable.com>
In-Reply-To: <2671C6CDFBB59E47B64C10B3E0BD59230338A65F10@PRVPEXVS15.corp.twcable.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Nov 2012 23:38:58 -0000

On 11/29/12 2:32 PM, George, Wes wrote:
> [WEG] I'm sorry if it was unclear, but I am not saying that
> *everything* must be specified, nor do I think anyone should
> undertake an effort to even identify all of the things that are
> currently unspecified. I'm pointing out a specific area of confusion
> and inconsistency that has been created by something that is
> unspecified and asking "should we specify?"

I'm not very clear on what problem you're trying to solve, or
why it's a problem.  I've seen some stuff around working
group draft adoption that I don't like very much but am not
sure that I'd identify those as a "problem," per se, or that
they would be done better with yet another process document.

Lo, those many years ago I co-chaired (with Avri Doria) the
"problem" working group.  It was a very bad experience, and
I think left me convinced that dorking around with formalizing
process stuff should absolutely not be done unless someone's
identified a specific problem that interferes with getting
documents out.  Process we just don't happen to like is not
a problem.

Melinda

From sm@resistor.net  Thu Nov 29 15:40:52 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E26BA21F8B1E for <ietf@ietfa.amsl.com>; Thu, 29 Nov 2012 15:40:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[AWL=1.000, BAYES_00=-2.599, GB_I_LETTER=-2, 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 e63jm8KRqBhn for <ietf@ietfa.amsl.com>; Thu, 29 Nov 2012 15:40:52 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D4D221F8B25 for <ietf@ietf.org>; Thu, 29 Nov 2012 15:40:50 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id qATNeiDK015315; Thu, 29 Nov 2012 15:40:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1354232449; bh=NY4R3YuxYFRSXjkak4fPJjfhY6U/K8BNDEPzmlfQRlc=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=XWVOwjV5rUE/PQ2GVwW6KKkUrgEi+Xv8M1OemGE/QFScRjYcojLb5t3qLZmI5EERh vgtFTQfm/LU8N/+AoqP8P0W2YhAIn0bXuBt/wmsT+V5jwXHhf3dZxtpaTEmb0WzX52 +ib/OkJGjCSRu4HlNdLUfc+Z049UWbIpMl4Eiyow=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1354232449; i=@resistor.net; bh=NY4R3YuxYFRSXjkak4fPJjfhY6U/K8BNDEPzmlfQRlc=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=luSrgpZ/eE1Woo80iJtH5ARkNXe97nFaZKnuNjzPsybKBMi8OqNxYNN1zAO22A4VI YvqCGPv8rlsBXdKsEqeylGemoJqeU4atI1O3bmv25CHGrQemue6LEaSWidK8tmtDRq OWHiN3ARZHuUUJmGCt0ysYyqUdQaLwib+nZDRH/4=
Message-Id: <6.2.5.6.2.20121129133139.0a015900@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 29 Nov 2012 15:39:51 -0800
To: adrian@olddog.co.uk
From: SM <sm@resistor.net>
Subject: RE: When to adopt a draft as a WG doc (was RE: "IETF work is	done on the mailing lists")
In-Reply-To: <02ba01cdce76$be921580$3bb64080$@olddog.co.uk>
References: <2671C6CDFBB59E47B64C10B3E0BD5923033897C9BF@PRVPEXVS15.corp.twcable.com> <CALaySJLT=6RTZahqB1LO_Aw=7sAMiyrXK=xacwrBgLieZhqeDw@mail.gmail.com> <2671C6CDFBB59E47B64C10B3E0BD59230338A657EC@PRVPEXVS15.corp.twcable.com> <6.2.5.6.2.20121129105444.0b8d3400@resistor.net> <02ba01cdce76$be921580$3bb64080$@olddog.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Nov 2012 23:40:53 -0000

Hi Adrian,
At 13:16 29-11-2012, Adrian Farrel wrote:
>What about drafts that not for discussion at a session? What about drafts that
>have completed last call or are in IESG processing?

I did not verify the state of the drafts for above when I listed the 
working groups.  I listed a working group which did not have any 
session.  I know that one of the working groups in the list has 
documents going through IESG processing.  If you ask me whether the 
list is a good representation of the text I quoted, my answer would be no.

There are three meetings slots in a year.  If a group misses that 
slot it losses the opportunity for three months of work (assuming 
that there is discussion on the mailing list).  People are free to 
object to object about the process not being followed to the letter 
or about arbitrary decisions of the chair.  If I was a WG Chair and 
somebody asked why the work is being delayed or the working group is 
doing nothing I would point to the objection.  What I won't say is 
whether people who will be implementing the work or who are actually 
going to review the work will walk away.

Regards,
-sm 


From presnick@qti.qualcomm.com  Thu Nov 29 15:41:50 2012
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2490E21F8B34 for <ietf@ietfa.amsl.com>; Thu, 29 Nov 2012 15:41:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.569
X-Spam-Level: 
X-Spam-Status: No, score=-102.569 tagged_above=-999 required=5 tests=[AWL=0.030, 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 1S7WzrDTxxSC for <ietf@ietfa.amsl.com>; Thu, 29 Nov 2012 15:41:49 -0800 (PST)
Received: from sabertooth01.qualcomm.com (sabertooth01.qualcomm.com [65.197.215.72]) by ietfa.amsl.com (Postfix) with ESMTP id 49D0621F8B31 for <ietf@ietf.org>; Thu, 29 Nov 2012 15:41:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1354231553; x=1385767553; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=/+06sti7ruklQd2CR8wHdVz8bw7OZMTJoI+XK7mEaII=; b=r9/9E32OWJZZWS7ooHqa5baZFF6K98t/0igWYYvTVvQjghTlPj5zAyeu OOFPaFK8gb3ihOH51CdEuoVaiPw/H0WX+xfYSDyqfwly2aKRxLi2z3hSN g30zdW30RZ4Q0UlrA3OBbeJZg0pECXDRrKaZT22qF7/T1x05V3tvAhEAx Y=;
X-IronPort-AV: E=McAfee;i="5400,1158,6911"; a="9752795"
Received: from ironmsg04-r.qualcomm.com ([172.30.46.18]) by sabertooth01.qualcomm.com with ESMTP; 29 Nov 2012 15:25:52 -0800
X-IronPort-AV: E=McAfee;i="5400,1158,6911"; a="434978330"
Received: from nasanexhc08.na.qualcomm.com ([172.30.39.7]) by Ironmsg04-R.qualcomm.com with ESMTP/TLS/RC4-SHA; 29 Nov 2012 15:41:48 -0800
Received: from presnick-mac.local (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.7) with Microsoft SMTP Server (TLS) id 14.2.318.4; Thu, 29 Nov 2012 15:41:48 -0800
Message-ID: <50B7F2BA.9000600@qti.qualcomm.com>
Date: Thu, 29 Nov 2012 17:41:46 -0600
From: Pete Resnick <presnick@qti.qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: Geoff Huston <gih@apnic.net>
Subject: Re: Last Call: <draft-bonica-special-purpose-03.txt> (Special-Purpose Address Registries) to Best Current Practice
References: <20121129205534.8983.43593.idtracker@ietfa.amsl.com> <7C5BEF8A-70E1-4E96-BC5C-7D2D43E09A58@apnic.net>
In-Reply-To: <7C5BEF8A-70E1-4E96-BC5C-7D2D43E09A58@apnic.net>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.39.5]
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Nov 2012 23:41:50 -0000

Like Randy, I am completely agnostic on the question of dividing the 
registries vs. adding an attribute to the registries to distinguish 
between reservations and other special uses. But one comment on the 
other item in your message:

On 11/29/12 4:26 PM, Geoff Huston wrote:

> I also disagree with the approach to publish the intended contents of this special purpose registry as an RFC ans the registry itself is the intended mode of authoritatively describing those resources that have been assigned for special purposes. Obviously any RFC will age out and drift away from the registry, and the need to constantly publish updating RFCs to ensure that the latest RFC is reasonably close to the registry contents seems to me to be counter-productive at best.
>    

I think (hope) you've misinterpreted this. The document serves two 
purposes: To define the registries (section 2.1, which is really the 
BCPish part of this document) and to populate the registries with 
initial values (sections 2.2 and 2.3). 2.1 is the real content of the 
documentthat will live on, get updated, etc., whereas 2.2 and 2.3 are 
probably better as an appendix, and I don't think there's any 
expectation that those sections ought to be kept up to date with future 
RFCs to match the registry. (Indeed, it might be nice if 2.2 and 2.3 
were removed before publication, but that's not been our practice.)

Does that allay your concern?

For the authors, one thing I did notice in section 2:

    IANA will update the aforementioned registries as requested in the
    "IANA Considerations" section of an IESG-reviewed document.  The "
    IANA Considerations" section must include all of the information
    specified in Section 2.1 of this document.

It would probably be better to use the specific 5226 language of "IETF 
Review", "IESG Approval" or "Standards Action" (whichever you really 
mean) instead of "an IESG-reviewed document".

pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478


From gih@apnic.net  Thu Nov 29 16:15:17 2012
Return-Path: <gih@apnic.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AAC5521F8AA0 for <ietf@ietfa.amsl.com>; Thu, 29 Nov 2012 16:15:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, 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 t2X54Bajt5V7 for <ietf@ietfa.amsl.com>; Thu, 29 Nov 2012 16:15:17 -0800 (PST)
Received: from asmtp.apnic.net (asmtp.apnic.net [IPv6:2001:dc0:2001:11::199]) by ietfa.amsl.com (Postfix) with ESMTP id C9A4421F8AA1 for <ietf@ietf.org>; Thu, 29 Nov 2012 16:15:16 -0800 (PST)
Received: from [IPv6:2001:388:1000:110:bc95:1f16:d3c8:240f] (unknown [IPv6:2001:388:1000:110:bc95:1f16:d3c8:240f]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by asmtp.apnic.net (Postfix) with ESMTP id 4E9F3B6745; Fri, 30 Nov 2012 10:15:15 +1000 (EST)
Subject: Re: Last Call: <draft-bonica-special-purpose-03.txt> (Special-Purpose Address Registries) to Best Current Practice
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Content-Type: text/plain; charset=iso-8859-1
From: Geoff Huston <gih@apnic.net>
In-Reply-To: <50B7F2BA.9000600@qti.qualcomm.com>
Date: Fri, 30 Nov 2012 11:15:15 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <1D916C75-C75D-4DF7-95E4-4787D6904A03@apnic.net>
References: <20121129205534.8983.43593.idtracker@ietfa.amsl.com> <7C5BEF8A-70E1-4E96-BC5C-7D2D43E09A58@apnic.net> <50B7F2BA.9000600@qti.qualcomm.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
X-Mailer: Apple Mail (2.1499)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Nov 2012 00:15:17 -0000

On 30/11/2012, at 10:41 AM, Pete Resnick <presnick@qti.qualcomm.com> =
wrote:

> Like Randy, I am completely agnostic on the question of dividing the =
registries vs. adding an attribute to the registries to distinguish =
between reservations and other special uses. But one comment on the =
other item in your message:
>=20
> On 11/29/12 4:26 PM, Geoff Huston wrote:
>=20
>> I also disagree with the approach to publish the intended contents of =
this special purpose registry as an RFC ans the registry itself is the =
intended mode of authoritatively describing those resources that have =
been assigned for special purposes. Obviously any RFC will age out and =
drift away from the registry, and the need to constantly publish =
updating RFCs to ensure that the latest RFC is reasonably close to the =
registry contents seems to me to be counter-productive at best.
>>  =20
>=20
> I think (hope) you've misinterpreted this. The document serves two =
purposes: To define the registries (section 2.1, which is really the =
BCPish part of this document)

And I was saying that I would prefer to see protocol address plan =
reservations not be included in the special purpose registry.


> and to populate the registries with initial values (sections 2.2 and =
2.3).

Some time ago there was value in this "initial population" concept to =
sort some of the claims of special purpose address assignments, but I =
thought that we were over it and the draft restates what is already n =
the registry.


> 2.1 is the real content of the documentthat will live on, get updated, =
etc., whereas 2.2 and 2.3 are probably better as an appendix, and I =
don't think there's any expectation that those sections ought to be kept =
up to date with future RFCs to match the registry. (Indeed, it might be =
nice if 2.2 and 2.3 were removed before publication, but that's not been =
our practice.)

Personally the removal before publication of the registry contents would =
be something I would support.

>=20
> Does that allay your concern?
>=20


no - as I would prefer to see protocol address plan reservations not be =
included in the special purpose registry. The IPv4 address plan =
reservations appear to be 0/8, 127/8 and  240/4. The others appear to be =
various forms of special prupose assignments. In IPv6 I see reservations =
for ::1/128, ::/128 as far as I can tell - the remainder are reasonably =
seen as Special Purpose Assignments I would suggest.

regards,

  Geoff


From sm@resistor.net  Thu Nov 29 18:05:55 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9406721F89B7 for <ietf@ietfa.amsl.com>; Thu, 29 Nov 2012 18:05:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.766
X-Spam-Level: 
X-Spam-Status: No, score=-102.766 tagged_above=-999 required=5 tests=[AWL=-0.167, 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 PNmue3rCcHB3 for <ietf@ietfa.amsl.com>; Thu, 29 Nov 2012 18:05:55 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id E5C9A21F89A2 for <ietf@ietf.org>; Thu, 29 Nov 2012 18:05:54 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id qAU25mn4000484; Thu, 29 Nov 2012 18:05:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1354241153; bh=6gphMw22XqMRpahusq/mbo3oUZOy4ZBYKlDbDV9Us+A=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=TMhDz+8UvOVdSHaH5L2KtX+TZJ1CgtQxCoYLHBagoOQ/lSNKDAoTNPe6lewZSBh8g xLPONzd4UYKE/zp8FbRT9ReRYiv5kmQMgqA8Qq4Tuy5tPlfPeh8K/ejGBej6Wmb5vo zvNHpR+JyRsFFHdQ0XHtDA9klMTgYyUomSOpR4xc=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1354241153; i=@resistor.net; bh=6gphMw22XqMRpahusq/mbo3oUZOy4ZBYKlDbDV9Us+A=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=tzf1GG2Zpo93rIztrHqb8DAHXN/z85TG+8mAJ/CtYJj6DIr6v17sM3p5J/2GPXWUb t7xmbpx8zzeGQWOilewtPUKFmPSTa61r4pfEXya1dNmApXkl9sYmQxjZH+x7ssif+W BEKYnbpFWkPT7vp4/3sNwxfGWFgl8jw5WDT/k2BA=
Message-Id: <6.2.5.6.2.20121129155742.0a015b90@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 29 Nov 2012 16:37:46 -0800
To: Spencer Dawkins <spencer@wonderhamster.org>
From: SM <sm@resistor.net>
Subject: Re: When to adopt a draft as a WG doc (was RE: "IETF work is	done on the mailing lists")
In-Reply-To: <50B7ECD1.5080302@wonderhamster.org>
References: <2671C6CDFBB59E47B64C10B3E0BD5923033897C9BF@PRVPEXVS15.corp.twcable.com> <CALaySJLT=6RTZahqB1LO_Aw=7sAMiyrXK=xacwrBgLieZhqeDw@mail.gmail.com> <2671C6CDFBB59E47B64C10B3E0BD59230338A657EC@PRVPEXVS15.corp.twcable.com> <6.2.5.6.2.20121129105444.0b8d3400@resistor.net> <02ba01cdce76$be921580$3bb64080$@olddog.co.uk> <50B7ECD1.5080302@wonderhamster.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Nov 2012 02:05:55 -0000

Hi Spencer,
At 15:16 29-11-2012, Spencer Dawkins wrote:
>In addition to the cases Adrian asked about, isn't there also the 
>case of an author/editor updating a draft that has already been 
>discussed and then submitting it during IETF week?

Yes.

Regards,
-sm 


From sm@resistor.net  Thu Nov 29 19:36:00 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E626121F8472 for <ietf@ietfa.amsl.com>; Thu, 29 Nov 2012 19:36:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.742
X-Spam-Level: 
X-Spam-Status: No, score=-102.742 tagged_above=-999 required=5 tests=[AWL=-0.143, 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 7Z7jH5q41kJN for <ietf@ietfa.amsl.com>; Thu, 29 Nov 2012 19:35:59 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id D3C2F21F843E for <ietf@ietf.org>; Thu, 29 Nov 2012 19:35:59 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id qAU3Zrwa024703 for <ietf@ietf.org>; Thu, 29 Nov 2012 19:35:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1354246559; bh=iSrwgjA5D8fM6/dlcDCZPgO0HIzex6wc5seNQursBAQ=; h=Date:To:From:Subject:In-Reply-To:References:Cc; b=FYPrNEnhPMrOHsY4SzVes4WeUqw2tppHuxQtyL0bSTe4/7L63cf4ExcjWLNJTlRT+ 7ExoPQRJM1a0oQah3cYzMhrbhw/yXuX4SBAxUvB5/2KfD8QS2J8+Pghp4WSAiX9SON eWXhBLfD7nvsxMxzw13Iy3XXmzodaToN8ZKCmuxA=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1354246559; i=@resistor.net; bh=iSrwgjA5D8fM6/dlcDCZPgO0HIzex6wc5seNQursBAQ=; h=Date:To:From:Subject:In-Reply-To:References:Cc; b=OMzVPKuRR/JzcDd3qe/oV1nR4uzvL9r42JJHSFUhi1IlUi+9+B3ygjKC+Twwlpg24 4DmIE3iLJQnqLiNcQUZMV0lUS0BnrDm1O7l+9MpuFeSdqNSa/4gcQLpnmR72V9z4CH EE3JzvZZ7IGSBOQ01jJAdVea4cqNU+25g3RLA/yA=
Message-Id: <6.2.5.6.2.20121129165519.0a037840@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 29 Nov 2012 19:22:46 -0800
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-bonica-special-purpose-03.txt> (Special-Purpose Address Registries) to Best Current Practice
In-Reply-To: <20121129205534.8983.43593.idtracker@ietfa.amsl.com>
References: <20121129205534.8983.43593.idtracker@ietfa.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Nov 2012 03:36:01 -0000

At 12:55 29-11-2012, The IESG wrote:

>The IESG has received a request from an individual submitter to consider
>the following document:
>- 'Special-Purpose Address Registries'
>   <draft-bonica-special-purpose-03.txt> as Best Current Practice
>
>The IESG plans to make a decision in the next few weeks, and solicits
>final comments on this action. Please send substantive comments to the
>ietf@ietf.org mailing lists by 2013-01-02. Exceptionally, comments may be

 From the Abstract:

   "This memo updates RFC 5736 and RFC 4773, which define the current
    structure of the IPv4 and IPv6 Special-Purpose Address Registries.
    It also obsoletes RFC 5735 and RFC 5156 which document special-
    purpose address blocks that are not currently, but will in the
    future, be recorded in the IPv4 and IPv6 Special-Purpose Address
    Registries."

BCP 153 is about Special Use IPv4 addresses.  This intended BCP will 
create a mishmash as the draft covers both IPv4 and IPv6.  I suggest 
handling the IP versions in two separate drafts.

RFC 5375 is being obsoleted by this draft.  RFC 6598 updates RFC 
5375.  Could someone explain that to me (see 
http://www.rfc-editor.org/errata_search.php?rfc=5375&eid=3309 and the 
relevant discussion for details)?

The following text is from RFC 3330 which was written by the Internet 
Assigned Numbers Authority:

   "Throughout its entire history, the Internet has employed a central
    Internet Assigned Numbers Authority (IANA) responsible for the
    allocation and assignment of various identifiers needed for the
    operation of the Internet [RFC1174].  In the case of the IPv4 address
    space, the IANA allocates parts of the address space to Regional
    Internet Registries according to their established needs.  These
    Regional Internet Registries are responsible for the assignment of
    IPv4 addresses to operators and users of the Internet within their
    regions.

    [paragraph omitted]

    On an ongoing basis, the IANA has been designated by the IETF to make
    assignments in support of the Internet Standards Process [RFC2860].
    Section 4 of this document describes that assignment process."

The text was also present in RFC 5735.  I unfortunately have to 
object to the disappearance of that text.

RFC 5736 provides direction to IANA concerning the creation and 
management of the IANA IPv4 Special Purpose Address Registry.   The 
information in RFC 5375 is not obsolete.

 From the IANA Considerations Section:

   'IANA will update the aforementioned registries as requested in the
    "IANA Considerations" section of an IESG-reviewed document.  The "
    IANA Considerations" section must include all of the information
    specified in Section 2.1 of this document.'

RFC 5735 mentions that:

   "Among other things, [RFC2860] requires that protocol parameters be
    assigned according to the criteria and procedures specified in
    RFCs, including Proposed, Draft, and full Internet Standards and
    Best Current Practice documents, and any other RFC that calls for
    IANA assignment."

This draft changes it.

Regards,
-sm 


From nomcom-chair@ietf.org  Thu Nov 29 21:13:53 2012
Return-Path: <nomcom-chair@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F077B21F88C7; Thu, 29 Nov 2012 21:13:52 -0800 (PST)
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=-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 XXEwUBBgiC5g; Thu, 29 Nov 2012 21:13:52 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 87B9121F88C2; Thu, 29 Nov 2012 21:13:52 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: NomCom Chair <nomcom-chair@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
Subject: NomCom 2012: Feedback Request - IAOC and TSV
X-Test-IDTracker: no
X-IETF-IDTracker: 4.36
Message-ID: <20121130051352.5549.44773.idtracker@ietfa.amsl.com>
Date: Thu, 29 Nov 2012 21:13:52 -0800
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Nov 2012 05:13:53 -0000

The IETF Nominating Committee (NomCom) is currently working to fill the =

IAOC mid-term vacancy created by the resignation of Marshall =

Eubanks. The NomCom is requesting feedback from the community to =

help us fill this position. However, the NomCom needs to move quickly to =

fill this vacancy. Therefore, to be useful, the NomCom must receive =

community feedback on or before Tuesday, December 11.

We appreciate the responses to our previous call for nominations. The =

individuals we are currently considering for the IAOC mid-term vacancy =

are:
-- Randy Bush =

-- Barbara Fraser
-- Wes George
-- Tobias Gondrom
-- Chris Griffiths
-- John Levine

The NomCom would greatly appreciate input from the community on =

general considerations that should be taken into account in filling the =

IAOC vacancy. The NomCom would additionally appreciate community =

input related to particular individuals. =


The NomCom is happy to accept community input either via email to =

nomcom12@ietf.org, or via the NomCom web feedback tool:
https://www.ietf.org/group/nomcom/2012/input/

Additionally, the NomCom had previously re-opened nominations for the
position of Transport Area Director and we have identified several =

additional candidates who are willing to be considered for the position. =

However, the NomCom would benefit from additional feedback related to =

this position. The individuals the NomCom is considering for the position =

of Transport Area Director:
-- Ken Carlberg
-- Nandita Dukkipati
-- Linda Dunbar
-- Tom Haynes

Again, the NomCom welcomes feedback on general considerations for =

filling the position of Transport AD, as well as feedback on particular =

candidates. The NomCom is happy to accept community input either via =

email to nomcom12@ietf.org, or via the NomCom web feedback tool:
https://www.ietf.org/group/nomcom/2012/input/

Note that use of the NomCom web feedback tool requires an ietf.org =

account. Anyone can acquire an ietf.org account at: =

datatracker.ietf.org/accounts/

From narten@us.ibm.com  Thu Nov 29 21:53:09 2012
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B074D21F88B8 for <ietf@ietfa.amsl.com>; Thu, 29 Nov 2012 21:53:09 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IbgYQyOAbBy6 for <ietf@ietfa.amsl.com>; Thu, 29 Nov 2012 21:53:09 -0800 (PST)
Received: from e37.co.us.ibm.com (e37.co.us.ibm.com [32.97.110.158]) by ietfa.amsl.com (Postfix) with ESMTP id EF46721F8894 for <ietf@ietf.org>; Thu, 29 Nov 2012 21:53:08 -0800 (PST)
Received: from /spool/local by e37.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Thu, 29 Nov 2012 22:53:07 -0700
Received: from d03dlp03.boulder.ibm.com (9.17.202.179) by e37.co.us.ibm.com (192.168.1.137) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Thu, 29 Nov 2012 22:53:05 -0700
Received: from d03relay03.boulder.ibm.com (d03relay03.boulder.ibm.com [9.17.195.228]) by d03dlp03.boulder.ibm.com (Postfix) with ESMTP id 0039319D803C for <ietf@ietf.org>; Thu, 29 Nov 2012 22:53:05 -0700 (MST)
Received: from d03av02.boulder.ibm.com (d03av02.boulder.ibm.com [9.17.195.168]) by d03relay03.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id qAU5r4rP253378 for <ietf@ietf.org>; Thu, 29 Nov 2012 22:53:04 -0700
Received: from d03av02.boulder.ibm.com (loopback [127.0.0.1]) by d03av02.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id qAU5r4Kk020171 for <ietf@ietf.org>; Thu, 29 Nov 2012 22:53:04 -0700
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.44.115.148]) by d03av02.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id qAU5r3T6020119 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 29 Nov 2012 22:53:04 -0700
Received: from rotala.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.5/8.12.5) with ESMTP id qAU5r3YS012700 for <ietf@ietf.org>; Fri, 30 Nov 2012 00:53:03 -0500
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.5/8.14.5/Submit) id qAU5r286012662 for ietf@ietf.org; Fri, 30 Nov 2012 00:53:02 -0500
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201211300553.qAU5r286012662@rotala.raleigh.ibm.com>
Date: Fri, 30 Nov 2012 00:53:02 -0500
To: ietf@ietf.org
Subject: Weekly posting summary for ietf@ietf.org
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 12113005-7408-0000-0000-00000AA91A98
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Nov 2012 05:53:09 -0000

Total of 108 messages in the last 7 days.
 
script run at: Fri Nov 30 00:53:02 EST 2012
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  7.41% |    8 |  7.25% |    55552 | sm@resistor.net
  6.48% |    7 |  6.37% |    48769 | gih@apnic.net
  7.41% |    8 |  5.35% |    40943 | randy@psg.com
  4.63% |    5 |  4.54% |    34786 | presnick@qti.qualcomm.com
  4.63% |    5 |  3.97% |    30427 | dhc@dcrocker.net
  3.70% |    4 |  3.88% |    29727 | barryleiba@computer.org
  3.70% |    4 |  3.26% |    25003 | john-ietf@jck.com
  2.78% |    3 |  3.55% |    27176 | abdussalambaryun@gmail.com
  2.78% |    3 |  3.53% |    27059 | wesley.george@twcable.com
  2.78% |    3 |  3.06% |    23408 | ford@isoc.org
  2.78% |    3 |  2.51% |    19203 | melinda.shore@gmail.com
  1.85% |    2 |  2.30% |    17641 | daedulus@btconnect.com
  1.85% |    2 |  1.98% |    15197 | lear@cisco.com
  1.85% |    2 |  1.84% |    14107 | adrian@olddog.co.uk
  1.85% |    2 |  1.83% |    14033 | brian.e.carpenter@gmail.com
  1.85% |    2 |  1.66% |    12749 | hartmans-ietf@mit.edu
  1.85% |    2 |  1.64% |    12543 | stpeter@stpeter.im
  1.85% |    2 |  1.45% |    11130 | listsebby@me.com
  1.85% |    2 |  1.43% |    10960 | paul@nohats.ca
  0.93% |    1 |  1.76% |    13490 | mjethanandani@gmail.com
  0.93% |    1 |  1.73% |    13226 | dmm@1-4-5.net
  0.93% |    1 |  1.60% |    12243 | bensons@queuefull.net
  0.93% |    1 |  1.47% |    11292 | ed.lewis@neustar.biz
  0.93% |    1 |  1.30% |     9924 | superuser@gmail.com
  0.93% |    1 |  1.29% |     9864 | agmalis@gmail.com
  0.93% |    1 |  1.23% |     9425 | trammell@tik.ee.ethz.ch
  0.93% |    1 |  1.17% |     8948 | ogud@ogud.com
  0.93% |    1 |  1.11% |     8497 | worley@ariadne.com
  0.93% |    1 |  1.08% |     8238 | john@jlc.net
  0.93% |    1 |  1.05% |     8076 | narten@us.ibm.com
  0.93% |    1 |  1.04% |     7935 | d3e3e3@gmail.com
  0.93% |    1 |  1.02% |     7782 | hsantos@isdg.net
  0.93% |    1 |  1.02% |     7775 | ggx@gigix.net
  0.93% |    1 |  0.99% |     7607 | chris.dearlove@baesystems.com
  0.93% |    1 |  0.99% |     7593 | joelja@bogus.com
  0.93% |    1 |  0.96% |     7332 | moore@network-heretics.com
  0.93% |    1 |  0.94% |     7183 | marc.blanchet@viagenie.ca
  0.93% |    1 |  0.92% |     7039 | vesely@tana.it
  0.93% |    1 |  0.92% |     7008 | lee@asgard.org
  0.93% |    1 |  0.91% |     6932 | tglassey@earthlink.net
  0.93% |    1 |  0.90% |     6863 | andrew.hutton@siemens-enterprise.com
  0.93% |    1 |  0.89% |     6813 | swb@internet2.edu
  0.93% |    1 |  0.87% |     6674 | dwm@xpasc.com
  0.93% |    1 |  0.86% |     6605 | touch@isi.edu
  0.93% |    1 |  0.85% |     6548 | dromasca@avaya.com
  0.93% |    1 |  0.85% |     6509 | cb.list6@gmail.com
  0.93% |    1 |  0.84% |     6442 | brian@innovationslab.net
  0.93% |    1 |  0.84% |     6442 | bob.hinden@gmail.com
  0.93% |    1 |  0.80% |     6135 | johnl@taugh.com
  0.93% |    1 |  0.78% |     5992 | morrowc.lists@gmail.com
  0.93% |    1 |  0.77% |     5880 | spencer@wonderhamster.org
  0.93% |    1 |  0.76% |     5843 | drc@virtualized.org
  0.93% |    1 |  0.71% |     5455 | ynir@checkpoint.com
  0.93% |    1 |  0.71% |     5439 | ned+ietf@mauve.mrochek.com
  0.93% |    1 |  0.70% |     5346 | fernando@gont.com.ar
  0.93% |    1 |  0.66% |     5055 | ajs@anvilwalrusden.com
  0.93% |    1 |  0.66% |     5041 | rsk@gsp.org
  0.93% |    1 |  0.65% |     4982 | wjhns1@hardakers.net
--------+------+--------+----------+------------------------
100.00% |  108 |100.00% |   765886 | Total


From bertietf@bwijnen.net  Fri Nov 30 00:03:20 2012
Return-Path: <bertietf@bwijnen.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4AA4821F88E9 for <ietf@ietfa.amsl.com>; Fri, 30 Nov 2012 00:03:20 -0800 (PST)
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=-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 kOpy9Jq98QDz for <ietf@ietfa.amsl.com>; Fri, 30 Nov 2012 00:03:19 -0800 (PST)
Received: from postgirl.ripe.net (postgirl.ipv6.ripe.net [IPv6:2001:67c:2e8:11::c100:1342]) by ietfa.amsl.com (Postfix) with ESMTP id B018221F87AC for <ietf@ietf.org>; Fri, 30 Nov 2012 00:03:18 -0800 (PST)
Received: from ayeaye.ripe.net ([193.0.23.5]) by postgirl.ripe.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from <bertietf@bwijnen.net>) id 1TeLZ4-0000hI-CA; Fri, 30 Nov 2012 09:03:15 +0100
Received: from cat.ripe.net ([193.0.1.249] helo=BWMACBOOK.local) by ayeaye.ripe.net with esmtp (Exim 4.72) (envelope-from <bertietf@bwijnen.net>) id 1TeLZ4-0005VS-8o; Fri, 30 Nov 2012 09:03:14 +0100
Message-ID: <50B86841.6000802@bwijnen.net>
Date: Fri, 30 Nov 2012 09:03:13 +0100
From: "Bert Wijnen (IETF)" <bertietf@bwijnen.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: Wes Hardaker <wjhns1@hardakers.net>
Subject: Re: request to make the "tools version" of the agenda the default
References: <0lr4ncgtyd.fsf@wjh.hardakers.net>
In-Reply-To: <0lr4ncgtyd.fsf@wjh.hardakers.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Anti-Virus: Kaspersky Anti-Virus for Linux Mail Server 5.6.48/RELEASE, bases: 20120425 #7816575, check: 20121130 clean
X-RIPE-Spam-Level: --
X-RIPE-Spam-Report: Spam Total Points:   -2.9 points pts rule name              description ---- ---------------------- ------------------------------------ -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP -1.9 BAYES_00               BODY: Bayes spam probability is 0 to 1% [score: 0.0000]
X-RIPE-Signature: 86ab03e524994f79ca2c75a176445dd47fdff945e09745f0e13998a6972ec516
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Nov 2012 08:03:20 -0000

+1

On 11/29/12 7:11 PM, Wes Hardaker wrote:
>
> So, the 'tools version' with all the wonderful spiffy links to helpful
> things (the materials, the etherpad, the ...) and the spiffy
> highlighting ability (Dark Red!  I love dark red!) has been very stable
> and highly useful for quite a while now.  But the default link on the
> web page still points to the less-useful HTML version (which has a link
> at the top to get to the tools version).  I'd argue this is backwards at
> this point, and the tools version is so much more useful (and just as
> stable) as the plain-html version that it should be the default.  Can we
> do that for March+?
>
>
> [I know, we just *ended* a face-to-face meeting so why am I bringing up
> face-to-face meeting topics so far before the next one?  That's unheard
> of!  Call me crazy...]
>

From hartmans@mit.edu  Fri Nov 30 04:30:21 2012
Return-Path: <hartmans@mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 373FE21F870B for <ietf@ietfa.amsl.com>; Fri, 30 Nov 2012 04:30:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.524
X-Spam-Level: 
X-Spam-Status: No, score=-102.524 tagged_above=-999 required=5 tests=[AWL=0.075, 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 zj2EnDYNQN7r for <ietf@ietfa.amsl.com>; Fri, 30 Nov 2012 04:30:20 -0800 (PST)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id ACD9F21F8703 for <ietf@ietf.org>; Fri, 30 Nov 2012 04:30:20 -0800 (PST)
Received: from carter-zimmerman.suchdamage.org (c-98-217-126-210.hsd1.ma.comcast.net [98.217.126.210]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.painless-security.com (Postfix) with ESMTPS id 772E820180; Fri, 30 Nov 2012 07:28:36 -0500 (EST)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 37343420E; Fri, 30 Nov 2012 07:30:18 -0500 (EST)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: "Bert Wijnen \(IETF\)" <bertietf@bwijnen.net>
Subject: Re: request to make the "tools version" of the agenda the default
References: <0lr4ncgtyd.fsf@wjh.hardakers.net> <50B86841.6000802@bwijnen.net>
Date: Fri, 30 Nov 2012 07:30:18 -0500
In-Reply-To: <50B86841.6000802@bwijnen.net> (Bert Wijnen's message of "Fri, 30 Nov 2012 09:03:13 +0100")
Message-ID: <tslboeftgrp.fsf@mit.edu>
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
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Nov 2012 12:30:21 -0000

Another +1 for prefering tools.ietf.org to ietf.org especially for the
wg pages.
The tools site is significantly more accessible than the IETF site.
One main reason is that the tools site actually uses html heading
elements. Screen readers can easily jump to headings, but I have to tab
through every link in the ietf website's top and navigation to find the
information.
That gets kind of old:-)

mainly pointing this out lest someone argue that the static html version
is more accessible. At least for the blind, it's not.

From wesley.george@twcable.com  Fri Nov 30 06:09:35 2012
Return-Path: <wesley.george@twcable.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3EBBB21F8A7C for <ietf@ietfa.amsl.com>; Fri, 30 Nov 2012 06:09:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.896
X-Spam-Level: 
X-Spam-Status: No, score=-0.896 tagged_above=-999 required=5 tests=[AWL=0.567,  BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, 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 9OH9o2qorekd for <ietf@ietfa.amsl.com>; Fri, 30 Nov 2012 06:09:34 -0800 (PST)
Received: from cdpipgw01.twcable.com (cdpipgw01.twcable.com [165.237.59.22]) by ietfa.amsl.com (Postfix) with ESMTP id 4FFE721F8A60 for <ietf@ietf.org>; Fri, 30 Nov 2012 06:09:34 -0800 (PST)
X-SENDER-IP: 10.136.163.14
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.84,191,1355115600"; d="scan'208";a="480535192"
Received: from unknown (HELO PRVPEXHUB05.corp.twcable.com) ([10.136.163.14]) by cdpipgw01.twcable.com with ESMTP/TLS/RC4-MD5; 30 Nov 2012 09:09:32 -0500
Received: from PRVPEXVS15.corp.twcable.com ([10.136.163.79]) by PRVPEXHUB05.corp.twcable.com ([10.136.163.14]) with mapi; Fri, 30 Nov 2012 09:09:33 -0500
From: "George, Wes" <wesley.george@twcable.com>
To: Melinda Shore <melinda.shore@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>
Date: Fri, 30 Nov 2012 09:09:49 -0500
Subject: RE: When to adopt a draft as a WG doc (was RE: "IETF work is done on the mailing lists")
Thread-Topic: When to adopt a draft as a WG doc (was RE: "IETF work is done on the mailing lists")
Thread-Index: Ac3OisbYfc3A2i4/SE+KKgZKyH92JwAc5IpQ
Message-ID: <2671C6CDFBB59E47B64C10B3E0BD59230338A6610A@PRVPEXVS15.corp.twcable.com>
References: <2671C6CDFBB59E47B64C10B3E0BD5923033897C9BF@PRVPEXVS15.corp.twcable.com> <CALaySJLT=6RTZahqB1LO_Aw=7sAMiyrXK=xacwrBgLieZhqeDw@mail.gmail.com> <2671C6CDFBB59E47B64C10B3E0BD59230338A657EC@PRVPEXVS15.corp.twcable.com> <CALaySJ+1LX6kzpDZYwQaJAqkzH4zLdRoMaJNH9HcHQG-78jA7Q@mail.gmail.com> <2671C6CDFBB59E47B64C10B3E0BD59230338A65F10@PRVPEXVS15.corp.twcable.com> <50B7F20C.908@gmail.com>
In-Reply-To: <50B7F20C.908@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Nov 2012 14:09:35 -0000

> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> Melinda Shore
>
> I'm not very clear on what problem you're trying to solve, or why it's a
> problem.  I've seen some stuff around working group draft adoption that
> I don't like very much but am not sure that I'd identify those as a
> "problem," per se, or that they would be done better with yet another
> process document.
[WEG] My original message simply notes that this is the 3rd or more time in=
 my recent memory that there has been a serious question within some part o=
f the IETF about when in a document's lifecycle and maturity is the "right"=
 time to adopt it as a WG document, and whether it is appropriate to discus=
s an individual document in a WG at any length without adopting it. It seem=
ed odd to me that there would be this much confusion on the matter, and I p=
rovided several examples of different philosophies that I have observed whe=
n it comes to handling this question. The response I got back indicated tha=
t WG adoption of drafts isn't really "a thing" as far as the official docum=
entation of document lifecycle is concerned, which made me wonder if perhap=
s we do as much WG adoption of drafts as we do mainly out of inertia, eithe=
r people doing it because that's how they've seen others do it in the past,=
 or doing it because they assume it's part of the documented process, rathe=
r than for any real reason. I'm not a big fan of doing things for no reason=
, so the ensuing discussion was intended to tease this out a bit to see whe=
ther we should have some clearer guidelines around WG draft adoption, bette=
r education on the reasoning behind it, or whether maybe we should stop doi=
ng it. Is it the largest problem facing the IETF? Not by a long shot. But i=
t seemed worth a little discussion, at least to me.

> Process we just don't happen to like is not a problem.
>
[WEG] process we don't happen to like because it adds no value or confuses =
people or wastes time is very much a problem. But I didn't bring this up be=
cause I didn't like the process, I brought it up because I was seeking a li=
ttle clarity on the underlying reasons we use the process (at least partial=
ly to improve my own knowledge as a WG chair and draft author). Thus far th=
at clarity has still not presented itself.

Wes George

This E-mail and any of its attachments may contain Time Warner Cable propri=
etary information, which is privileged, confidential, or subject to copyrig=
ht belonging to Time Warner Cable. This E-mail is intended solely for the u=
se of the individual or entity to which it is addressed. If you are not the=
 intended recipient of this E-mail, you are hereby notified that any dissem=
ination, distribution, copying, or action taken in relation to the contents=
 of and attachments to this E-mail is strictly prohibited and may be unlawf=
ul. If you have received this E-mail in error, please notify the sender imm=
ediately and permanently delete the original and any copy of this E-mail an=
d any printout.

From john-ietf@jck.com  Fri Nov 30 06:51:44 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B1BA21F88C7 for <ietf@ietfa.amsl.com>; Fri, 30 Nov 2012 06:51:44 -0800 (PST)
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=-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 L3u9UNnH77x1 for <ietf@ietfa.amsl.com>; Fri, 30 Nov 2012 06:51:44 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id D91D021F8AC8 for <ietf@ietf.org>; Fri, 30 Nov 2012 06:51:43 -0800 (PST)
Received: from localhost ([::1]) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1TeRwL-000F9m-4L; Fri, 30 Nov 2012 09:51:41 -0500
Date: Fri, 30 Nov 2012 09:51:41 -0500
From: John C Klensin <john-ietf@jck.com>
To: Wes Hardaker <wjhns1@hardakers.net>, ietf@ietf.org
Subject: Re: request to make the "tools version" of the agenda the default
Message-ID: <8CCC9454D1E6317473AC4576@[192.168.6.112]>
In-Reply-To: <0lr4ncgtyd.fsf@wjh.hardakers.net>
References: <0lr4ncgtyd.fsf@wjh.hardakers.net>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Nov 2012 14:51:44 -0000

--On Thursday, 29 November, 2012 10:11 -0800 Wes Hardaker
<wjhns1@hardakers.net> wrote:

> 
> So, the 'tools version' with all the wonderful spiffy links to
> helpful things (the materials, the etherpad, the ...) and the
> spiffy highlighting ability (Dark Red!  I love dark red!) has
> been very stable and highly useful for quite a while now.  But
> the default link on the web page still points to the
> less-useful HTML version (which has a link at the top to get
> to the tools version).  

FWIW, I agree that the "tools version" is better in every way
that I can think of than the static HTML version.  But for those
of us who are still enough members of the dinosaur age to still
sometimes read things on WiFi-free airplanes and trains and
(shudder) still sometimes mark up paper, _please_ don't
implement this change the way the change to the I-D
announcements was done, i.e., by forcing a several-stage
click-through process to get to whatever versions are not the
preferred version of the year.

   john 






From loa@pi.nu  Fri Nov 30 07:11:22 2012
Return-Path: <loa@pi.nu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0248B21F8B80 for <ietf@ietfa.amsl.com>; Fri, 30 Nov 2012 07:11:22 -0800 (PST)
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=-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 5KIosZo0AmTJ for <ietf@ietfa.amsl.com>; Fri, 30 Nov 2012 07:11:16 -0800 (PST)
Received: from mail.pi.nu (ns1.elverljung.se [195.206.248.139]) by ietfa.amsl.com (Postfix) with ESMTP id EF0BA21F8C08 for <ietf@ietf.org>; Fri, 30 Nov 2012 07:11:15 -0800 (PST)
Received: from [192.168.1.64] (81-236-221-144-no93.tbcn.telia.com [81.236.221.144]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.pi.nu (Postfix) with ESMTPSA id 8524382388; Fri, 30 Nov 2012 16:11:07 +0100 (CET)
Message-ID: <50B8CC84.70603@pi.nu>
Date: Fri, 30 Nov 2012 16:11:00 +0100
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: request to make the "tools version" of the agenda the default
References: <0lr4ncgtyd.fsf@wjh.hardakers.net> <8CCC9454D1E6317473AC4576@[192.168.6.112]>
In-Reply-To: <8CCC9454D1E6317473AC4576@[192.168.6.112]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Nov 2012 15:11:22 -0000

John,

I took this request as request to change the default, given that the
tool-version is what I use (mostly) that change would be beneficial,
but I'd be reluctant to see the HTML-version go away immediately.

/Loa

On 2012-11-30 15:51, John C Klensin wrote:
>
>
> --On Thursday, 29 November, 2012 10:11 -0800 Wes Hardaker
> <wjhns1@hardakers.net> wrote:
>
>>
>> So, the 'tools version' with all the wonderful spiffy links to
>> helpful things (the materials, the etherpad, the ...) and the
>> spiffy highlighting ability (Dark Red!  I love dark red!) has
>> been very stable and highly useful for quite a while now.  But
>> the default link on the web page still points to the
>> less-useful HTML version (which has a link at the top to get
>> to the tools version).
>
> FWIW, I agree that the "tools version" is better in every way
> that I can think of than the static HTML version.  But for those
> of us who are still enough members of the dinosaur age to still
> sometimes read things on WiFi-free airplanes and trains and
> (shudder) still sometimes mark up paper, _please_ don't
> implement this change the way the change to the I-D
> announcements was done, i.e., by forcing a several-stage
> click-through process to get to whatever versions are not the
> preferred version of the year.
>
>     john
>
>
>
>
>

-- 


Loa Andersson                         email: loa.andersson@ericsson.com
Sr Strategy and Standards Manager            loa@pi.nu
Ericsson Inc                          phone: +46 10 717 52 13
                                              +46 767 72 92 13

From john-ietf@jck.com  Fri Nov 30 07:39:50 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6DC5121F8B25 for <ietf@ietfa.amsl.com>; Fri, 30 Nov 2012 07:39:50 -0800 (PST)
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=-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 sgcpVb+Tse1p for <ietf@ietfa.amsl.com>; Fri, 30 Nov 2012 07:39:50 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id ED9DF21F8B24 for <ietf@ietf.org>; Fri, 30 Nov 2012 07:39:49 -0800 (PST)
Received: from localhost ([::1]) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1TeSgt-000FWh-KO; Fri, 30 Nov 2012 10:39:47 -0500
Date: Fri, 30 Nov 2012 10:39:45 -0500
From: John C Klensin <john-ietf@jck.com>
To: Loa Andersson <loa@pi.nu>
Subject: Re: request to make the "tools version" of the agenda the default
Message-ID: <18C4713424DC63629B268A03@[192.168.6.112]>
In-Reply-To: <50B8CC84.70603@pi.nu>
References: <0lr4ncgtyd.fsf@wjh.hardakers.net> <8CCC9454D1E6317473AC4576@[192.168.6.112]> <50B8CC84.70603@pi.nu>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Nov 2012 15:39:50 -0000

--On Friday, 30 November, 2012 16:11 +0100 Loa Andersson
<loa@pi.nu> wrote:

> John,
> 
> I took this request as request to change the default, given
> that the
> tool-version is what I use (mostly) that change would be
> beneficial,
> but I'd be reluctant to see the HTML-version go away
> immediately.

I think changing the default is fine.  I'd also be reluctant to
see the "normal" HTML version go away immediately but would be
especially reluctant to see the plain text version go away or
even become less accessible (require more clicks or searching to
navigate too).

   john









From suresh.krishnan@ericsson.com  Fri Nov 30 07:56:45 2012
Return-Path: <suresh.krishnan@ericsson.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 93B3E21F85FA for <ietf@ietfa.amsl.com>; Fri, 30 Nov 2012 07:56:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 q27iUhHZOndm for <ietf@ietfa.amsl.com>; Fri, 30 Nov 2012 07:56:45 -0800 (PST)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id DFC2C21F86A8 for <ietf@ietf.org>; Fri, 30 Nov 2012 07:56:44 -0800 (PST)
Received: from eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id qAUG4tbZ032336; Fri, 30 Nov 2012 10:05:16 -0600
Received: from [142.133.112.133] (147.117.20.214) by smtps-am.internal.ericsson.com (147.117.20.31) with Microsoft SMTP Server (TLS) id 8.3.279.1; Fri, 30 Nov 2012 10:56:12 -0500
Message-ID: <50B8D68A.10304@ericsson.com>
Date: Fri, 30 Nov 2012 10:53:46 -0500
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Randy Bush <randy@psg.com>
Subject: Re: Barely literate minutes
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <50B5C839.4060909@gmail.com> <59924CD37D50616BA8EB8EF7@JcK-HP8200.jck.com> <6.2.5.6.2.20121128023905.0afdcde0@resistor.net> <50B683C4.2030503@stpeter.im> <50B68612.7080107@dcrocker.net> <50B693ED.7000609@stpeter.im> <50B696B0.30904@qti.qualcomm.com> <CAC4RtVAG+pKSQMwPyB6GJ7jxJM4hNpU81Yt8he6ZsEMrg_rTbQ@mail.gmail.com> <00c001cdce7a$d9fa6490$8def2db0$@asgard.org> <m2624o2gez.wl%randy@psg.com>
In-Reply-To: <m2624o2gez.wl%randy@psg.com>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: 'Barry Leiba' <barryleiba@computer.org>, 'IETF discussion list' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Nov 2012 15:56:45 -0000

On 11/29/2012 05:27 PM, Randy Bush wrote:
>> As a document author, I've learned that I need to have a friend take
>> good notes for me, because all of the great comments I get at the mike
>> are lost otherwise.
> 
> this gap makes me crazy, so much is often lost.  but i do not think
> technology or process will close this hole.  too much depends on fairly
> deep understanding of the subject.
> 
>> I can't take notes while I'm standing up, facilitating discussion.

+1.

> 
> i can't take notes while i am trying to understand and think about the
> important semantics of a discussion, period.  but much of this may be a
> personal failing, poor typist, rotting mind, ...

I have this same issue as well. If I need to participate in a few
discussions in the wg I decline to take minutes there as I do not
believe I could do a good job with the minutes.

For the record, as a minute taker, it takes me approximately 2x meeting
time to come up with the minutes (I go back to the audio to fill in
gaps, send individual mails to commenters to better understand their
comments etc.) in addition to *almost completely* missing participation
in the meeting.

Thanks
Suresh


From dhc@dcrocker.net  Fri Nov 30 08:06:33 2012
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C80721F8585 for <ietf@ietfa.amsl.com>; Fri, 30 Nov 2012 08:06:33 -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=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 UmGKGJ6tVq2f for <ietf@ietfa.amsl.com>; Fri, 30 Nov 2012 08:06:32 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 86F4A21F8543 for <ietf@ietf.org>; Fri, 30 Nov 2012 08:06:29 -0800 (PST)
Received: from [192.168.1.9] (adsl-67-127-190-125.dsl.pltn13.pacbell.net [67.127.190.125]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id qAUG6MXw015295 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 30 Nov 2012 08:06:23 -0800
Message-ID: <50B8D979.1010203@dcrocker.net>
Date: Fri, 30 Nov 2012 08:06:17 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: Barry Leiba <barryleiba@computer.org>
Subject: Re: When to adopt a draft as a WG doc (was RE: "IETF work is done on the mailing lists")
References: <2671C6CDFBB59E47B64C10B3E0BD5923033897C9BF@PRVPEXVS15.corp.twcable.com> <CALaySJLT=6RTZahqB1LO_Aw=7sAMiyrXK=xacwrBgLieZhqeDw@mail.gmail.com>
In-Reply-To: <CALaySJLT=6RTZahqB1LO_Aw=7sAMiyrXK=xacwrBgLieZhqeDw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Fri, 30 Nov 2012 08:06:23 -0800 (PST)
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Nov 2012 16:06:33 -0000

On 11/28/2012 7:58 AM, Barry Leiba wrote:
> Let's start with a basic point and work from there:
> There is no formal process that involves "adopting" anything.

If you mean that we haven't documented a/the formal process, you are 
correct.  If you mean that the IETF has not moved towards rather formal 
steps for explicitly adopting working group drafts, I disagree.

There is flexibility in the process that has developed, but it's become 
quite formal.  The first shakey steps were controlling assignment of 
"draft-<wgname>" roughly 20 years ago and it has evolved from there.

Today, there is typically explicit text in the charter about adoption or 
there is explicit wg approval.


>   There is nothing anywhere that specifies how the first version
> of a WG document is formed.

Right.  Our documentation of our formal processes has lagged.

The next part of your note summarizes a couple of common starting points 
for drafts.


On 11/29/2012 11:06 AM, Barry Leiba wrote:
> Here's where we have a gap, you and I: what you call undocumented
> policy I call a management choice.

There certainly are parts of wg management that are left to chair 
discretion.  However the IETF also likes to use squishy language like 
"management choice" to avoid being disciplined in its formal processes. 
We are constantly afraid of edge conditions, and use that fear as an 
excuse for being inconsistent in the handling of typical cases.

In the current discussion, I think there needs to be an essential 
distinction:  For example, choosing editors is /formally/ a management 
choice.  Approval of drafts is not.

I think the essential point is the difference between 'what' and 'how'.

The IETF has unusual flexibility in the 'how', and often leaves the 
choices to management... but implicitly based on acceptance of the 
working group.

In very specific circumstances, such as selecting editors, the freedom 
of management choice is permitted for the 'what'.



d/
-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From sm@resistor.net  Fri Nov 30 09:01:42 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6EED421F8B13 for <ietf@ietfa.amsl.com>; Fri, 30 Nov 2012 09:01:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.46
X-Spam-Level: 
X-Spam-Status: No, score=-102.46 tagged_above=-999 required=5 tests=[AWL=-0.361, BAYES_00=-2.599, GB_ABOUTYOU=0.5, 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 mXFxgd2oMxKq for <ietf@ietfa.amsl.com>; Fri, 30 Nov 2012 09:01:41 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id AD48221F8B01 for <ietf@ietf.org>; Fri, 30 Nov 2012 09:01:41 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id qAUH1YPI028060; Fri, 30 Nov 2012 09:01:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1354294900; bh=ZLhqU+/hNgpG66/o2X/hJ5bA83nBw6qPHhYGn4ZADyU=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=wsYdavGQD7pmhtHW7Lfxk3kctKxnw4oo7puo86Mucsb4dQWse2NSyLZ/Qg/U+kXAn DHbBmueevhnFgX49pI0K6dDe2QHr7hRJLB2LZCKDEGno8On3YgodRLISB1yFIOGktP keB+KZ6fucRQIc2h4rdb8LppuAk8Hsvr6YjcF/rQ=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1354294900; i=@resistor.net; bh=ZLhqU+/hNgpG66/o2X/hJ5bA83nBw6qPHhYGn4ZADyU=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=mGJDDCNKOzR24knCQZvmnNwFwuXVL4pJwkhlv39Yisj1410LuC316gHsPeXmTka6o Tva5IjEzCiS6HS/6jeWJ+pOYLCeoAKHEjDP4gZ6zkRjpjwXcLD2yYeTWhAYC0Y5efG Ze2Yg1sq52Sm7lUwrYRtHYpqbNjEtx1iXBBm6mDY=
Message-Id: <6.2.5.6.2.20121130070345.0bed3da8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 30 Nov 2012 08:43:11 -0800
To: "George, Wes" <wesley.george@twcable.com>
From: SM <sm@resistor.net>
Subject: RE: When to adopt a draft as a WG doc (was RE: "IETF work is done on the mailing lists")
In-Reply-To: <2671C6CDFBB59E47B64C10B3E0BD59230338A6610A@PRVPEXVS15.corp .twcable.com>
References: <2671C6CDFBB59E47B64C10B3E0BD5923033897C9BF@PRVPEXVS15.corp.twcable.com> <CALaySJLT=6RTZahqB1LO_Aw=7sAMiyrXK=xacwrBgLieZhqeDw@mail.gmail.com> <2671C6CDFBB59E47B64C10B3E0BD59230338A657EC@PRVPEXVS15.corp.twcable.com> <CALaySJ+1LX6kzpDZYwQaJAqkzH4zLdRoMaJNH9HcHQG-78jA7Q@mail.gmail.com> <2671C6CDFBB59E47B64C10B3E0BD59230338A65F10@PRVPEXVS15.corp.twcable.com> <50B7F20C.908@gmail.com> <2671C6CDFBB59E47B64C10B3E0BD59230338A6610A@PRVPEXVS15.corp.twcable.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Nov 2012 17:01:42 -0000

At 06:09 30-11-2012, George, Wes wrote:
>[WEG] My original message simply notes that this is the 3rd or more 
>time in my recent memory that there has been a serious question 
>within some part of the IETF about when in a document's lifecycle 
>and maturity is the "right" time to adopt it as a WG document, and 
>whether it is appropriate to discuss an individual document in a WG 
>at any length without adopting it. It seemed odd to me that there 
>would be this much confusion on the matter, and I provided several 
>examples of different philosophies that I have observed when it 
>comes to handling this question. The response I got back indicated 
>that WG adoption of drafts isn't really "a thing" as far as the 
>official documentation of document lifecycle is concerned, which 
>made me wonder if perhaps we do as much WG adoption of drafts as we 
>do mainly out of inertia, either people doing it because that's how 
>they've seen others do it in the past, or doing it because they 
>assume it's part of the documented process, rather than for any real 
>reason. I'm not a big fan of doing things for no reason, so the 
>ensuing discussion was intended to tease this out a bit to see 
>whether we should have some clearer guidelines around WG draft 
>adoption, better education on the reasoning behind it, or whether 
>maybe we should stop doing it. Is it the largest problem facing the 
>IETF? Not by a long shot. But it seemed worth a little discussion, 
>at least to me.

You seem to have things under control in SUNSET.  After reading your 
messages to this mailing list I didn't understand what you were asking.

There is no such thing as a "right" time to adopt a document.  Look 
at it this way, if you get it right nobody will know, if you get it 
wrong the working group will say bad things about you, if you get it 
really wrong the Area Director will be on your back.  The choices for 
a working group chair are:

  (a) To get the work done

  (b) Not to do anything wrong

If you choose (a) you will end up a lot of enemies.  If you choose 
(b) you may or may not have a long career in the IETF.

It is possible to discuss an individual document in a working group 
without adopting it.  It is, as you mentioned, a matter of 
philosophy.  If you find it disruptive you can say no.

A lot of the things done in the IETF are done because we see others 
doing it.  In essence they are done for no reason.  On the Internet 
there is something called a sense of entitlement.  The author of a 
draft may assume that he has a right to a RFC number.  You can help 
him/her to get that RFC number as you were selected as working group 
chair to make everyone happy (or is it something else :-)).

I'll quote 
http://wiki.tools.ietf.org/group/edu/attachment/wiki/IETF78/IETF78-WGchairs-Adrian-Farrel.ppt?format=raw

   '"Do you think this I-D should become a WG draft?"

    - Can easily turn into a vote

    - Ask for reasons to be given to accompany a "no" opinion

    - Ask for expressions of willingness to work on or review the draft

    Avoid votes!'

>[WEG] process we don't happen to like because it adds no value or 
>confuses people or wastes time is very much a problem. But I didn't 
>bring this up because I didn't like the process, I brought it up 
>because I was seeking a little clarity on the underlying reasons we 
>use the process (at least partially to improve my own knowledge as a 
>WG chair and draft author). Thus far that clarity has still not 
>presented itself.

I'll edit what you said: "[adoption] doesn't happen because it adds 
no value or confuses people or wastes time".

It seems that what you are asking about is a sanity check.  You could 
sound some people to get a sense of which direction to take.

Regards,
-sm 


From wjhns1@hardakers.net  Fri Nov 30 11:10:23 2012
Return-Path: <wjhns1@hardakers.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB5D121F89B3 for <ietf@ietfa.amsl.com>; Fri, 30 Nov 2012 11:10:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.588
X-Spam-Level: 
X-Spam-Status: No, score=-2.588 tagged_above=-999 required=5 tests=[AWL=0.011,  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 WQEu312ug6Vo for <ietf@ietfa.amsl.com>; Fri, 30 Nov 2012 11:10:23 -0800 (PST)
Received: from mail.hardakers.net (dawn.hardakers.net [IPv6:2001:470:1f00:187::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E20721F865C for <ietf@ietf.org>; Fri, 30 Nov 2012 11:10:23 -0800 (PST)
Received: from localhost (unknown [50.13.187.159]) by mail.hardakers.net (Postfix) with ESMTPSA id 09852250; Fri, 30 Nov 2012 11:10:21 -0800 (PST)
From: Wes Hardaker <wjhns1@hardakers.net>
To: John C Klensin <john-ietf@jck.com>
Subject: Re: request to make the "tools version" of the agenda the default
References: <0lr4ncgtyd.fsf@wjh.hardakers.net> <8CCC9454D1E6317473AC4576@[192.168.6.112]> <50B8CC84.70603@pi.nu> <18C4713424DC63629B268A03@[192.168.6.112]>
Date: Fri, 30 Nov 2012 11:10:20 -0800
In-Reply-To: <18C4713424DC63629B268A03@[192.168.6.112]> (John C. Klensin's message of "Fri\, 30 Nov 2012 10\:39\:45 -0500")
Message-ID: <0la9tydi03.fsf@wjh.hardakers.net>
User-Agent: Gnus/5.130006 (Ma Gnus v0.6) Emacs/24.1 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Nov 2012 19:10:23 -0000

John C Klensin <john-ietf@jck.com> writes:

> I think changing the default is fine.  I'd also be reluctant to
> see the "normal" HTML version go away immediately but would be
> especially reluctant to see the plain text version go away or
> even become less accessible (require more clicks or searching to
> navigate too).

I suspect we can all agree that this would be optimal:

1) have the tools version be the default (my original statement)
2) have the html version still present
3) have the text version still present
4) produce an xml version for better parsing
   (ever try and write an agenda app? Half your time is spent writing a
   .txt or .html parser)
5) have each of the above have links between them

I'd assume that this is difficult (aside from #4 which would take the
most time as it's not just a switch-flip); although it's possible
someone has done it already and I just haven't learned of it.
-- 
Wes Hardaker
SPARTA, Inc.

From rbarnes@bbn.com  Fri Nov 30 11:16:41 2012
Return-Path: <rbarnes@bbn.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A8BA521F89A9 for <ietf@ietfa.amsl.com>; Fri, 30 Nov 2012 11:16:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 xjh7JAsI89Hg for <ietf@ietfa.amsl.com>; Fri, 30 Nov 2012 11:16:41 -0800 (PST)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.1.81]) by ietfa.amsl.com (Postfix) with ESMTP id 1A33721F89A2 for <ietf@ietf.org>; Fri, 30 Nov 2012 11:16:41 -0800 (PST)
Received: from ros-dhcp192-1-51-58.bbn.com ([192.1.51.58]:62901) by smtp.bbn.com with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77 (FreeBSD)) (envelope-from <rbarnes@bbn.com>) id 1TeW4g-0008R8-Rz; Fri, 30 Nov 2012 14:16:34 -0500
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: request to make the "tools version" of the agenda the default
From: Richard Barnes <rbarnes@bbn.com>
In-Reply-To: <0la9tydi03.fsf@wjh.hardakers.net>
Date: Fri, 30 Nov 2012 14:16:34 -0500
Content-Transfer-Encoding: 7bit
Message-Id: <7EB1F9A9-5E55-45EB-9AB5-42973EFCDEF5@bbn.com>
References: <0lr4ncgtyd.fsf@wjh.hardakers.net> <8CCC9454D1E6317473AC4576@[192.168.6.112]> <50B8CC84.70603@pi.nu> <18C4713424DC63629B268A03@[192.168.6.112]> <0la9tydi03.fsf@wjh.hardakers.net>
To: Wes Hardaker <wjhns1@hardakers.net>
X-Mailer: Apple Mail (2.1499)
Cc: John C Klensin <john-ietf@jck.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Nov 2012 19:16:41 -0000

On Nov 30, 2012, at 2:10 PM, Wes Hardaker <wjhns1@hardakers.net> wrote:

> John C Klensin <john-ietf@jck.com> writes:
> 
>> I think changing the default is fine.  I'd also be reluctant to
>> see the "normal" HTML version go away immediately but would be
>> especially reluctant to see the plain text version go away or
>> even become less accessible (require more clicks or searching to
>> navigate too).
> 
> I suspect we can all agree that this would be optimal:
> 
> 1) have the tools version be the default (my original statement)
> 2) have the html version still present
> 3) have the text version still present
> 4) produce an xml version for better parsing
>   (ever try and write an agenda app? Half your time is spent writing a
>   .txt or .html parser)

s/xml/json/

Ever try writing an XML app?  Half your time is spent writing a .xml parser.

From fernando@gont.com.ar  Fri Nov 30 14:04:33 2012
Return-Path: <fernando@gont.com.ar>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F4EF21F841A for <ietf@ietfa.amsl.com>; Fri, 30 Nov 2012 14:04:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.512
X-Spam-Level: 
X-Spam-Status: No, score=-0.512 tagged_above=-999 required=5 tests=[AWL=-1.542, BAYES_00=-2.599, FB_INCREASE_VOL=3.629]
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 pQsK6vaDxS5D for <ietf@ietfa.amsl.com>; Fri, 30 Nov 2012 14:04:32 -0800 (PST)
Received: from web01.jbserver.net (web01.jbserver.net [93.186.182.34]) by ietfa.amsl.com (Postfix) with ESMTP id B0DDC21F8419 for <ietf@ietf.org>; Fri, 30 Nov 2012 14:04:32 -0800 (PST)
Received: from 187-135-17-190.fibertel.com.ar ([190.17.135.187] helo=[192.168.1.113]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fernando@gont.com.ar>) id 1TeYgi-0003in-2V; Fri, 30 Nov 2012 23:04:00 +0100
Message-ID: <50B92CF9.4050104@gont.com.ar>
Date: Fri, 30 Nov 2012 19:02:33 -0300
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Lee Howard <lee@asgard.org>
Subject: Re: Barely literate minutes
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com>	<50B5C839.4060909@gmail.com>	<59924CD37D50616BA8EB8EF7@JcK-HP8200.jck.com>	<6.2.5.6.2.20121128023905.0afdcde0@resistor.net>	<50B683C4.2030503@stpeter.im> <50B68612.7080107@dcrocker.net>	<50B693ED.7000609@stpeter.im> <50B696B0.30904@qti.qualcomm.com> <CAC4RtVAG+pKSQMwPyB6GJ7jxJM4hNpU81Yt8he6ZsEMrg_rTbQ@mail.gmail.com> <00c001cdce7a$d9fa6490$8def2db0$@asgard.org>
In-Reply-To: <00c001cdce7a$d9fa6490$8def2db0$@asgard.org>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: 'Barry Leiba' <barryleiba@computer.org>, 'IETF discussion list' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Nov 2012 22:04:33 -0000

On 11/29/2012 06:45 PM, Lee Howard wrote:
>
> As a document author, I've learned that I need to have a friend take good
> notes for me, because
> all of the great comments I get at the mike are lost otherwise.  I can't
> take notes while I'm
> standing up, facilitating discussion.

FWIW, I've got used to listen to the audio recordings -- particualrly if
I have not attended that meeting.

At times, that has implied pre-processing the audio to increase the
volume level or reduce the background noise.

This has also proven to be useful, when, while there, I couldn't fully
understand what the guy at the mike was saying, either because of
low-volume, background noise, or a strong accent I wasn't used to.

Cheers,
-- 
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@si6networks.com
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1




From barryleiba.mailing.lists@gmail.com  Fri Nov 30 15:29:13 2012
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 365CD21F88BB for <ietf@ietfa.amsl.com>; Fri, 30 Nov 2012 15:29:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.977
X-Spam-Level: 
X-Spam-Status: No, score=-102.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, 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 QyIyFlVEhpkr for <ietf@ietfa.amsl.com>; Fri, 30 Nov 2012 15:29:12 -0800 (PST)
Received: from mail-la0-f44.google.com (mail-la0-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id 1446F21F8894 for <ietf@ietf.org>; Fri, 30 Nov 2012 15:29:11 -0800 (PST)
Received: by mail-la0-f44.google.com with SMTP id d3so862551lah.31 for <ietf@ietf.org>; Fri, 30 Nov 2012 15:29:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=xQ1Zn4rNllAqLrNllSJw0qmEGoWJ4OYPbxzy34D8iiM=; b=V/IaJGg+pVI+OPdzqPb3Ejjzqi3vo37S3MDWRetULs2MmWUz+Oya2I3ox+2FEp70qv YorVh73Wn5G+Jmg+Cohr0Yw+/G7y44M7xRse2Noe3i1hEGxk0K4AJbkni21LhUH4l1Bk QsKBTlO0l8vMKPF6QBMNxmf1y0eh3N4MpCF3JuxKdB45elX5pysKPYrjtRIx/So9UI4u xOxsSHAWzKcZvB7/2dd3pSCpdnInngg0z1VzNTsHl83MscpdGFeY1HrvmSXbYeWLH4aJ 7N6arb8Dq5u5TI7AZIJs9yJmzv2o2q7HV9mEQKvhObc1xOMhK0sn7CA1C9Ep7nmLNLpT suAw==
MIME-Version: 1.0
Received: by 10.152.105.33 with SMTP id gj1mr2789255lab.49.1354318151048; Fri, 30 Nov 2012 15:29:11 -0800 (PST)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.112.12.166 with HTTP; Fri, 30 Nov 2012 15:29:10 -0800 (PST)
In-Reply-To: <50B8D979.1010203@dcrocker.net>
References: <2671C6CDFBB59E47B64C10B3E0BD5923033897C9BF@PRVPEXVS15.corp.twcable.com> <CALaySJLT=6RTZahqB1LO_Aw=7sAMiyrXK=xacwrBgLieZhqeDw@mail.gmail.com> <50B8D979.1010203@dcrocker.net>
Date: Fri, 30 Nov 2012 18:29:10 -0500
X-Google-Sender-Auth: MMDo172DFC0b2yl_ytoLF61aues
Message-ID: <CAC4RtVAuN6eCZtmuTZveuRtqCK=RGHS51PfBu28BvQnax=dm6A@mail.gmail.com>
Subject: Re: When to adopt a draft as a WG doc (was RE: "IETF work is done on the mailing lists")
From: Barry Leiba <barryleiba@computer.org>
To: Dave Crocker <dcrocker@bbiw.net>
Content-Type: text/plain; charset=ISO-8859-1
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Nov 2012 23:29:13 -0000

>> There is no formal process that involves "adopting" anything.
>
> If you mean that we haven't documented a/the formal process, you are
> correct.  If you mean that the IETF has not moved towards rather formal
> steps for explicitly adopting working group drafts, I disagree.
...
> Today, there is typically explicit text in the charter about adoption or
> there is explicit wg approval.

Indeed: we always have the option of having the charter limit
management options.  That's a fine thing to do when it's appropriate,
and some combination of the working group proponents, the community as
a whole, and the IESG decides what's appropriate.  For chartering, the
IESG has the final word.

> Right.  Our documentation of our formal processes has lagged.

I find that to be an interesting interpretation.  I don't see it that way.

I do, indeed, mean that the IETF has not moved towards rather formal
steps for explicitly adopting working group drafts.  We have a common
custom, which many -- probably most -- working groups use.  As Wes
noted, it's not used in a consistent way, exactly because it is NOT a
formal process in any sense.

We have a very well defined mechanism (a formal process) for making it
a formal process, and we haven't done so.  Wes noted that he'd like
to; perhaps you'd like to join him in that.  The formal process, as
you know, would be to submit an Internet Draft with a target status of
BCP, and either find an AD to sponsor it as an individual submission
or make a BoF request and try to get a working group chartered for it.

Only when that document becomes an approved BCP will we actually have
formal steps.  Until then, we have a custom that's usually, but not
always, followed.

Barry
